Vietnam's 90-Day E-Visa: A Guide for Long-Term Travelers

You're not "just applying for a visa"-you're staging a 90-day move without surprises#

Treat this like relocation operations, not a quick form fill. Decide your constraints first, then submit. That one sequence removes most avoidable mistakes and keeps your timeline stable.

When plans fail, they usually fail in predictable ways. Your entry type does not match your real movement. You submit through a lookalike site and lose days. A payment attempt fails and you cannot prove what happened. One typo gets copied into every document you show later. This playbook gives you one operating model so your outcome does not depend on luck, memory, or last-minute improvisation.

What this playbook gives you (so you stop guessing)#

By the end, you should have four concrete outputs you can use under pressure:

• A clear single-entry vs multiple-entry decision tied to your actual itinerary.
• A submission timeline with buffers for correction loops and payment retries.
• A short field-check routine that catches identity and date mismatches before submission.
• An audit-ready packet you can retrieve quickly at an airline desk or during re-entry checks.

These outputs work because they force commitments early. Early commitments are cheap to adjust. Late fixes are expensive, emotional, and usually rushed.

Safe verification habit (no heroics)#

Use the Vietnam Electronic Visa Portal you intend to submit through as your source of truth for requirements and fields. Treat everything else as context, not authority.

Keep one repeatable habit:

• Open the portal from your own bookmark, not a fresh search result.
• Re-check key requirements right before submission, because program details can change.
• Save confirmation pages, receipts, and approval artifacts immediately.
• If any page or fee looks unfamiliar, pause and verify before you continue.

This is not overkill. It is baseline risk control when your move timeline depends on one clean submission.

Your "visa packet" (audit-ready, reusable)#

A visa packet is one folder that lets you answer questions fast with proof. Keep one cloud copy and one offline copy so you can operate even when Wi-Fi fails. The goal is retrieval under pressure, not perfect documentation.

If you are also handling housing, SIM setup, and onboarding in Hanoi or Ho Chi Minh City, keep those tasks in a separate operations folder. Mixing move logistics with visa artifacts creates noise right when you need precision.

The mental model: what a Vietnam 90-day e-visa is (and what it isn't)#

A Vietnam 90-day e-visa is an electronically issued visa from the Vietnam Immigration Department with validity up to 90 days. It can be single entry or multiple entry. Everything you do in this process should map back to that core idea.

A visa is permission to travel and enter, issued by competent Vietnamese authorities. An e-visa is one visa type issued through an electronic system. Your approval document is the controlling record for dates, entry type, and identity fields.

The practical operator takeaway is simple: planning assumptions are not controlling. The approved document is. If your itinerary, your booking emails, and your memory disagree with the approval PDF, the approval PDF wins.

What "90-day" really means#

The answer is direct: 90 days is a ceiling, not a promise.

Treat it as the maximum possible validity. Then anchor flights, housing, and your first-week plan to the exact validity shown on your approved document. If any other document points to a different timeline, fix the mismatch before travel day.

This prevents a common failure mode: people plan against a label, then ignore the record that actually governs their stay.

Single vs multiple entry: decide, then verify#

Choose entry type from your real movement plan, not your best-case mood. If you may leave and return during the validity window, treat that as a real constraint now. If you expect to stay in one place, keep the simpler path.

After approval, verify what was actually granted. Never assume your selection and the granted result are automatically identical. Build this into your workflow as a mandatory check, not a hopeful glance.

Good operations means one decision, one record, one execution path.

Where you apply (and how you avoid drift)#

Foreigners outside Vietnam can personally apply for an e-visa. Keep your submission path tight so you do not drift into copycat flows that cost time and money.

From 08:00 on 11/11/2024 (GMT+7), the Vietnam Electronic Visa Portal operates on two domains: thithucdientu.gov.vn and evisa.gov.vn. Treat those domains as your trust anchor. If a page does not clearly align with that official path, stop and verify before sharing personal data or payment details.

Operational rule: your approved dates, entry type, and identity fields must match across every document you present. That is what keeps airline desk checks and border checks boring.

The 10-minute setup: entry type + ports + timing (the decision framework that prevents rework)#

Do this setup before touching the application form. Ten focused minutes here saves you from the most common rework loops later.

You are making four decisions: entry type, planned ports, your personal go/no-go date, and a single source of truth for files. Once these are locked, execution gets dull and predictable. That is the outcome you want.

1) Entry type: write down your real movement plan#

Write your likely movement plan in plain language first. Then choose the entry type that matches it. This is less about flexibility and more about removing ambiguity.

If you expect side trips, treat that as a constraint now. If you intend to stay put in one city, lock that as a rule and avoid optional complexity. Do not choose based on fear of missing out. Choose based on what you are most likely to do.

Your goal is not maximum flexibility. Your goal is the fewest moving parts that still fit your trip.

2) Ports: verify before you buy anything irreversible#

Confirm planned entry and exit points inside the official application flow before buying anything non-refundable. This protects you from planning against stale screenshots or third-party summaries.

When the ports you need appear as selectable options, you have a reliable signal. Until then, keep flight commitments reversible and avoid tight same-day dependencies. The point is not paranoia. The point is avoiding expensive decisions before you have a confirmed set of selectable inputs.

3) Timing: set a personal "go/no-go" date#

Set a personal cut-off date now. If approval is not in hand by that date, you switch to contingency instead of improvising under stress.

Build two buffers into that date:

• A correction buffer for form fixes, payment retries, and document re-checks.
• A calendar buffer for weekends, public holidays, and operational delays around travel.

This gives you control over decisions that are otherwise made emotionally in the final week.

4) Single source of truth: one folder, one reality#

Create one folder that contains every file tied to this application. Use clear names and consistent versions so retrieval is instant when you are asked for something specific.

Include draft inputs, upload files, confirmations, payment artifacts, and the final approval document. Keep both cloud and offline copies. If you coordinate with a partner, agree on one naming convention up front to avoid version drift.

One folder means one reality. One reality means fewer avoidable mistakes.

Scam-proofing: the domains you should trust (and how to validate them fast)#

Scam risk is real because fake visa sites can look close enough when you are rushed. They win on urgency and confusion. You win by forcing every action through verified paths, and by keeping proof as you go.

Most scams cluster around the same pain points: inflated fees, fake approval letters, or pressure messaging designed to trigger immediate payment. Your defense is not cleverness. It is consistency: verified domain, saved artifacts, and no decisions made in panic.

The 60-second verification checklist (operator version)#

Before you enter personal details or payment data, run a fast gate. You are not trying to investigate the internet. You are trying to prevent drift.

• Exact domain check: type it yourself or use your saved bookmark.
• Path check: confirm you are in the expected official application flow.
• Messaging check: distrust pages built around guaranteed approval or urgent countdowns.
• Proof check: save only artifacts you can reopen later, including receipts and confirmations.

If one check fails, stop and restart from your trusted portal path. That one reset is cheaper than untangling a bad submission later.

Fast scam signals (and what to do instead)#

Use this table as a quick pattern match. The goal is speed, not debate.

A practical warning from traveler tutorials is consistent: people often pay much more than necessary after using unofficial sites. Keep the process dull, verifiable, and repeatable.

If you consider an agency, use a rubric (not panic)#

Use an agency only if you genuinely need support and can keep full control of your document trail. Do not outsource accountability for identity data, fee visibility, or final records.

Before paying, confirm these points:

• They disclose exactly which portal path they use.
• They provide copies of what they submit on your behalf.
• They show fee breakdowns clearly, including service markup.
• They pass confirmations and reference details immediately.
• They agree that you retain final documents and control of the archive.

If they cannot meet those basics, walk away. The whole point of paying for help is reducing uncertainty, not adding a second black box.

Your execution plan: a move-grade checklist with "done" criteria#

Execution is where good plans fail when done criteria are vague. Define done at each phase so progress is clear and auditable.

Speed is not the objective. Clean movement with evidence at every step is. Keep official guidance as your authority, then run the work as operations.

Phase 1 (Plan + confirm constraints)#

Complete this phase before submission starts:

• Entry strategy chosen and documented against real itinerary.
• Entry and arrival constraints verified from official guidance you checked yourself.
• Core inputs prepared, including passport scan and compliant photo files.
• Carrier expectations checked so desk surprises are less likely.

Done means you can explain your route, dates, and supporting files without guessing or searching.

Phase 2 (Submit + pay + capture proof)#

Submission is a transaction. Treat it like one, with traceability from the first click to the final record.

• Save application code or reference immediately.
• Save confirmation page as PDF or screenshot.
• Save payment receipt or equivalent transaction artifact.
• Run a second review of critical identity and itinerary fields before final submit.

Done means every critical step has retrievable proof and each proof item links back to the same application.

Phase 3 (Monitor + harden before travel)#

After submission, shift from form work to monitoring and resilience. You are protecting the rest of your move plan from a single point of failure.

• Check status through the official process and log outcomes by date.
• Keep contingency options alive if timing tightens.
• Build offline access to key documents and first-stay details.

Done means a delay does not force a full rebuild of your trip plan.

Arrival day (Border execution)#

Arrival is execution, not improvisation. Walk up with your passport and approval artifacts ready. Keep your story consistent with submitted details, including dates and first-stay context.

If a mismatch appears, stay calm, present saved evidence, and follow official support instructions. A smooth arrival usually comes from preparation, not persuasion.

Application form pitfalls to avoid (and the "two-person review" that prevents them)#

Most painful delays come from small input errors. The fix is straightforward: reduce variability, then run quality control before you press submit.

Treat this form like finance operations. Precision beats speed every time.

The operator mindset: accuracy beats speed#

Assume the system reads every field literally and compares it against what you uploaded. Close enough is not safe.

Your target is full alignment between passport details, planned travel details, and first-stay details. Any mismatch should trigger a pause. Ten calm minutes now is cheaper than a rushed rework cycle later, especially when your flights and accommodation start to lock in.

The pre-submit checklist (high-signal, no fluff)#

Before final submit, confirm each of these items explicitly:

• Identity fields match passport exactly.
• Passport number and related identifiers are character-perfect.
• Planned dates reflect what you actually intend to do.
• Arrival details are real and current, not placeholders.
• First-stay address is legitimate and easy to reference if asked.

If one item is uncertain, fix it first. Do not submit to see what happens. In operations, hope is not a control.

The "two-person review" mini-process#

This process catches avoidable mistakes quickly:

• Person A builds the form with passport scan and itinerary visible.
• Person B audits the final review screen against the same documents.
• Person B reads critical fields aloud while Person A confirms.
• Submission happens only after both agree key fields align.

If you are solo, simulate Person B. Step away, then re-check with fresh eyes. The small delay is worth the accuracy.

Payment, fees, and traceability: the part travel blogs skip (and the part that derails real timelines)#

Payment control is part of visa control. If payment evidence is weak, every follow-up gets harder, and you lose time reassembling what should have been captured in the moment.

The operational goal here is simple: you should be able to prove what you paid, when you paid, and which application it belongs to without searching old messages or guessing which screenshot is which.

Fees: know the common numbers, verify the real ones#

Use commonly cited numbers for planning only. Verify live amounts in the official portal before you pay. That keeps budgeting realistic while preventing stale assumptions from driving execution.

The discipline is the point. You are building a habit of checking the live portal, not trusting a screenshot or a blog summary.

Refunds: default to "no" unless the portal says "yes"#

Use a conservative refund baseline. Assume fees do not return unless the portal clearly states otherwise for your case.

Some guidance states paid fees are non-refundable when applications are refused. Operate from that assumption. It pushes you to tighten data quality before submission and reduces the chance you pay twice because of an avoidable mistake.

Traceability: build your payment-proof bundle#

Traceability is not admin theater. It is what lets you resolve issues quickly when something goes sideways.

Keep these items together in one folder:

• Submission confirmation artifact.
• Payment receipt or transaction proof.
• Application reference code.
• Final approval PDF when issued.

Use consistent filenames so retrieval takes seconds, not minutes. Example patterns:

• VN-eVisa_LastName_PassportLast4_SubmittedYYYY-MM-DD.pdf
• Payment_Receipt_RefXXXXX.png

This is the work that keeps your timeline intact when things get noisy. You do not want to be reconstructing proof while standing in a queue or replying to support.

After approval: your "audit-ready visa packet" (so airline desks and re-entries don't slow you down)#

Approval is not the finish line. The finish line is proving your case quickly when asked, even when you are tired, offline, or dealing with a desk interaction that is optimized for speed.

Build a packet that still works with low battery, weak signal, or someone who just wants fast verification and clean documents.

Store it in three places (redundancy beats regret)#

Use three storage locations so one failure does not block you:

• Cloud folder for master copies.
• Offline phone storage for quick access.
• One printed copy for desk interactions that prefer paper.

Some airline checks can require a printed approval letter, and a phone file may not be accepted in every context. Redundancy is cheap compared to a missed flight.

What "audit-ready" actually means#

Audit-ready means you can answer identity, approval, and timing questions fast, using the documents that actually control the decision.

Your packet should include:

• Printed visa approval letter.
• Offline digital copy on your phone.
• Passport bio page scan.
• Application reference details.
• One-line timeline log with submitted date, approval date, planned entry date, and planned exit date.

Keep the package compact and consistent. Fast retrieval reduces friction at every checkpoint, and it reduces the temptation to over-explain.

Airline counter playbook#

At the counter, lead with the printed approval letter. Keep your phone PDF as backup. Answer the question asked, then provide the matching artifact from your folder.

Avoid long narratives. Clean documents and concise answers usually move faster than explaining your whole trip.

Re-entry playbook (multiple-entry travelers)#

Multiple entry is not hard. It is just easy to get sloppy. Before each re-entry, do a quick pre-check:

• Confirm your re-entry date sits inside the validity window.
• Confirm passport details still match what the approval was issued against.

If anything changed, pause and verify before travel. Re-entry friction is usually preventable when you treat this like a repeatable pre-flight check, not a one-time admin task you already "handled."

Long-stay scenarios: extensions, visa runs, overstays, and "rules vary-verify here"#

Plan long stays around what is granted now, not what might be available later. That keeps you compliant even when policy details shift or when rumors move faster than official updates.

Treat the end date on your approval as a hard operational boundary. Build your timeline backward from that date, and make your decisions early enough that you are acting from options, not pressure.

Extensions: treat them as upside, not a plan#

Default to this: plan to exit before current validity ends. If extension options exist and are confirmed through official channels, treat them as upside rather than baseline.

Trips built on "maybe extension" often fail in the final days when options narrow. Build certainty first. Add flexibility only after certainty is secured and verified.

The realistic "beyond 90 days" mindset#

For planning, anchor to what you can verify. The policy update described a move from 30 days to 90 days starting 15 August 2023. It also described multiple entry as allowing unlimited entries and exits within that 90-day validity window.

Use those facts with discipline:

• Multiple entry can reduce friction for side trips during the valid window.
• When the window ends, assume permission to stay ends unless you have confirmed next steps.

Do not wait until day 89 to design your next move. If you want a calm exit or a clean transition, you need lead time.

Overstay risk: solve it with systems, not optimism#

Overstay risk usually comes from weak tracking, not bad intent. Treat it like any other deadline with real consequences.

A simple control stack is enough:

• Put your final legal day on multiple calendars.
• Set a decision deadline 7-14 days before that date.
• Trigger a stop-work check if key identity fields appear wrong after approval.

The goal is predictable action. You are trying to remove surprise from the final week, not trying to remember details while juggling travel logistics.

Remote work reality check: your e-visa is an entry/stay document, not a work permit (and what to do next)#

Keep immigration, work authorization, and tax analysis separate. Mixing them creates avoidable mistakes and sloppy assumptions.

An e-visa addresses entry and stay. It does not automatically answer whether a specific work activity is authorized. Treat that as a separate question that deserves its own verification path.

Separate the questions (and solve them in order)#

Start by separating document roles. A visa is an entry document. A work permit is a separate authorization for foreign employees. Tax residency is another track tied to presence and local ties, and Understanding Vietnamese Taxes for Foreigners is the better deep dive for that side of the move.

Solve these in order so one answer does not get reused for the wrong question. Clarity here prevents you from relying on an entry document to justify decisions it was never meant to cover.

Operational defaults that reduce risk#

If you are staying for months, conservative defaults keep your position cleaner and reduce avoidable contradictions:

• Keep records consistent across contracts, invoices, and travel docs.
• Keep stated purpose and dates consistent across forms and communications.
• Manage runway early, since validity can be up to 90 days but decisions should happen before the final weeks.

Consistency is a risk-control tool. It is also how you avoid explaining mismatches that never needed to exist.

Tax reality: day-count and leases can matter#

Common summaries flag 183 days or more as a threshold used in residency discussions, whether measured in a calendar year or across 12 consecutive months from arrival. The same summary set also notes that a rented house with a lease term of 183 days or more can appear in permanent-residence criteria.

Treat those points as planning signals, not conclusions. Track your days deliberately and treat long leases as tax-relevant choices, not only housing decisions.

Wrap-up: your move-ready default for Vietnam's 90-day e-visa#

Run this process like operations. Decide entry type from real movement, verify through official domains, and keep your packet audit-ready from day one.

Do that consistently and you reduce avoidable stress while keeping flexibility where it matters.

The playbook (in order)#

• Decide entry type from likely movements, not ideal scenarios.
• Verify current portal path and live fees before payment.
• Submit with a second-person quality check on critical fields.
• Save confirmations and payment proof immediately.
• Build approval packet in cloud, offline storage, and print.
• Re-check validity and identity alignment before each travel event.

Follow the sequence. Sequence is your risk control.

Safe defaults under uncertainty#

When details are unclear, use conservative defaults:

• Assume fees are not refundable unless the portal says otherwise.
• Assume extension availability can change and should not be Plan A.
• Assume small data errors become big timeline problems if left unchecked.
• Assume proof beats memory in any escalation.

These defaults are simple, durable, and easy to repeat.

One control to keep forever: the travel ops folder#

Keep one reusable travel ops folder for every border crossing and admin workflow. Include identity files, approvals, receipts, and consistency documents in one searchable structure.

If you run multi-country travel with repeated entries, this folder turns recurring stress into routine execution. Keep it current, keep it clean, and keep retrieval under 30 seconds.