A Vietnam 90 day e-visa is an electronic visa issued by the Vietnam Immigration Department that can be valid up to 90 days and can be single-entry or multiple-entry. Apply only through the Vietnam Electronic Visa Portal domains thithucdientu.gov.vn or evisa.gov.vn, upload a passport data page image and a straight-looking photo without glasses, and keep saved confirmations, payment proof, and the approved PDF (printed, too).
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.
By the end, you should have four concrete outputs you can use under pressure:
These outputs work because they force commitments early. Early commitments are cheap to adjust. Late fixes are expensive, emotional, and usually rushed.
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:
This is not overkill. It is baseline risk control when your move timeline depends on one clean submission.
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.
| Packet item | Why it matters | Owner |
|---|---|---|
| Application draft (all fields) | Prevents retyping while rushed | You |
| Passport scan + photo files | Makes corrections and resubmits faster | You |
| Submission confirmations | Proves what you submitted and when | You |
| Payment artifacts | Gives traceability for follow-up | You |
| Final approval PDF | Primary document for travel checks | You |
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.
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.
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.
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.
| Decision checkpoint | What you align | Safe action |
|---|---|---|
| Entry type | Planned movements inside and outside Vietnam | Choose from itinerary, then confirm on approval |
| Validity window | Housing and work ramp timing | Start your move plan from approved dates |
| Identity consistency | Airline and border checks | Keep passport and approval details identical |
Good operations means one decision, one record, one execution path.
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.
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.
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.
| Question to answer now | If yes | Decision effect |
|---|---|---|
| Might you leave Vietnam at least once? | You need re-entry flexibility | Use the option that supports that |
| Are your dates and location truly fixed? | Simpler flow is viable | Keep the simpler option and stick to it |
Your goal is not maximum flexibility. Your goal is the fewest moving parts that still fit your trip.
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.
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:
This gives you control over decisions that are otherwise made emotionally in the final week.
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 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.
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.
| Check | What to confirm | If it fails |
|---|---|---|
| Exact domain | Type it yourself or use your saved bookmark | Stop and restart from your trusted portal path |
| Path | Confirm you are in the expected official application flow | Stop and restart from your trusted portal path |
| Messaging | Distrust pages built around guaranteed approval or urgent countdowns | Stop and restart from your trusted portal path |
| Proof | Save artifacts you can reopen later, including receipts and confirmations | Stop and restart from your trusted portal path |
If one check fails, stop and restart from your trusted portal path. That one reset is cheaper than untangling a bad submission later.
Use this table as a quick pattern match. The goal is speed, not debate.
| Signal you notice | What it usually means | Safer move |
|---|---|---|
| Site ownership is unclear | You may be outside official flow | Exit and return to verified portal |
| Fee is unexpectedly high | Markup or unnecessary add-ons | Pause payment and verify path |
| Document cannot be validated | Possible fake approval artifact | Treat as untrusted and re-check source |
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.
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.
| Checkpoint | What to confirm |
|---|---|
| Portal path | They disclose exactly which portal path they use |
| Submission copies | They provide copies of what they submit on your behalf |
| Fee breakdown | They show fee breakdowns clearly, including service markup |
| Confirmations | They pass confirmations and reference details immediately |
| Document control | You retain final documents and control of the archive |
Before paying, confirm these points:
If they cannot meet those basics, walk away. The whole point of paying for help is reducing uncertainty, not adding a second black box.
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.
Complete this phase before submission starts:
Done means you can explain your route, dates, and supporting files without guessing or searching.
Submission is a transaction. Treat it like one, with traceability from the first click to the final record.
Done means every critical step has retrievable proof and each proof item links back to the same application.
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.
Done means a delay does not force a full rebuild of your trip plan.
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.
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.
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.
Before final submit, confirm each of these items explicitly:
| Item | What to confirm |
|---|---|
| Identity fields | Match passport exactly |
| Passport number | Character-perfect with related identifiers |
| Planned dates | Reflect what you actually intend to do |
| Arrival details | Real and current, not placeholders |
| First-stay address | 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.
This process catches avoidable mistakes quickly:
If you are solo, simulate Person B. Step away, then re-check with fresh eyes. The small delay is worth the accuracy.
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.
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.
| Entry type | Commonly cited fee (planning only) | Done criteria |
|---|---|---|
| Single-entry e-visa | $25 USD | Live fee confirmed in portal before paying |
| Multiple-entry e-visa | $50 USD | Live fee confirmed in portal before paying |
The discipline is the point. You are building a habit of checking the live portal, not trusting a screenshot or a blog summary.
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 is not admin theater. It is what lets you resolve issues quickly when something goes sideways.
Keep these items together in one folder:
Use consistent filenames so retrieval takes seconds, not minutes. Example patterns:
VN-eVisa_LastName_PassportLast4_SubmittedYYYY-MM-DD.pdfPayment_Receipt_RefXXXXX.pngThis 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.
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.
Use three storage locations so one failure does not block you:
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.
Audit-ready means you can answer identity, approval, and timing questions fast, using the documents that actually control the decision.
Your packet should include:
Keep the package compact and consistent. Fast retrieval reduces friction at every checkpoint, and it reduces the temptation to over-explain.
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.
Multiple entry is not hard. It is just easy to get sloppy. Before each re-entry, do a quick pre-check:
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."
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.
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.
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:
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 usually comes from weak tracking, not bad intent. Treat it like any other deadline with real consequences.
A simple control stack is enough:
The goal is predictable action. You are trying to remove surprise from the final week, not trying to remember details while juggling travel logistics.
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.
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.
| Topic | Decision you are making | What to track |
|---|---|---|
| Immigration permission | Entry and stay window under approved e-visa | Validity dates and entry type |
| Work authorization | Whether activity needs additional permission | Role, client or employer setup, local operating model |
| Tax residency | When time and ties create obligations | Day count, lease terms, arrival timing |
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.
If you are staying for months, conservative defaults keep your position cleaner and reduce avoidable contradictions:
Consistency is a risk-control tool. It is also how you avoid explaining mismatches that never needed to exist.
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.
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.
Follow the sequence. Sequence is your risk control.
When details are unclear, use conservative defaults:
These defaults are simple, durable, and easy to repeat.
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.
Yes. Official guidance describes the Vietnam e-visa as valid for a maximum of 90 days. Treat "up to 90 days" as the cap. Build your timeline around the exact validity dates you receive.
It can be single-entry or multiple-entry. Official guidance also lists fees as $25 for single-entry and $50 for multiple-entry. Choose the entry type first, then pay the matching fee.
As of 08:00 on 11/11/2024 (GMT+7), Vietnam's Electronic Visa Portal announced it operates on two official domains: thithucdientu.gov.vn and evisa.gov.vn. Use those domains as your trust anchor. Ignore "new portal" claims that don't match them.
Official application instructions state the e-visa is processed in 3 working days. Apply early enough that "3 working days" still leaves you buffer time. You want room to fix mistakes without panic.
Official instructions say you upload two images: your passport data page image and a photograph. The photo requirement stated is specific: straight looking without glasses. Keep the inputs clean so you don't trigger avoidable rework.
Official wording describes applicants as outside Vietnam who want to enter Vietnam. If you're already in Vietnam, treat that as a red flag for this pathway. Confirm your options through the official portal before you assume you can apply.
Don't travel on a document if a critical identity field looks wrong. Use the official portal's guidance to confirm whether you should correct it or submit a new application. Act quickly, since the fee is not refunded if an application is refused.
Priya helps global professionals navigate visas and relocation strategy with clear timelines, documentation checklists, and risk-aware decision points.
Priya specializes in international contract law for independent contractors. She ensures that the legal advice provided is accurate, actionable, and up-to-date with current regulations.
Educational content only. Not legal, tax, or financial advice.
Ho Chi Minh City is a strong base if your priority is keeping work momentum while relocating. You get density, plenty of places to work from, and a social scene that can help you settle quickly. It is a weaker fit if your best days depend on calm streets, easy walking, and long stretches of quiet. In practice, Saigon tends to reward people who want convenience and activity more than retreat pace.
Start with legal fit, not lifestyle filters. The practical order is simple: choose a route you can actually document, then decide where you want to live. That single change cuts a lot of wasted comparison work and stops you from falling in love with places that were never a real filing option.
If you get one thing right, get your residency posture and your evidence stack aligned. That single decision drives almost every other tax decision you make in Vietnam because it sets scope. Scope comes from two inputs: residency and sourcing.