How we rank payments for Vietnam sellers

This page is the rulebook for the Payments vertical. If a cell in the compare table looks blunt, it is because we scored the constraint first and the marketing page second.

What we are optimizing for

The job to be done is simple: which billing rail can a Vietnam seller actually use without getting burned?

We care more about direct Vietnam individual and business access, payouts, and Merchant of Record coverage than about feature lists. A beautiful checkout that you cannot open from Hanoi is a No.

Feasibility bands

Feasibility is a traffic light, not a review score.

High — A Vietnam seller can reasonably attempt this as a primary rail. Official country support holds, and we have a recent verification date. Caveats still appear inline (FastSpring VietQR, Airwallex Billing eligibility).
Low — Official access may exist, but community risk, payout holds, or a thin evidence trail make it a poor primary choice. Keep these as caution or backup, not the plan you bet a launch on.
No — There is no reliable direct-VN merchant path under our criterion. Stripe sits here: Connect or Global Payouts is not the same as a Stripe Payments merchant account in Vietnam.

High does not mean “buy this.” It means “this is the shortlist we would actually try first.”

Community risk, in plain language

Community risk is how often merchants report the ugly outcomes: frozen balances, surprise KYC, terminated stores, 120-day holds, support that disappears.

Low / Low-Medium — Complaints exist (they always do) but they are not the dominant story.
Medium — Worth reading the notes. Official support can still coexist with account-review pain.
High — Treat payouts and account continuity as unproven. Do not make this your only processor.
N/A — We are not scoring merchant-community noise because the product is not available as a direct VN merchant.

We do not pretend a Twitter thread is a court ruling. We also do not ignore a pile of similar hold stories.

Last Verified and UNVERIFIED

Every row has a Last Verified value.

An ISO date (for example 2026-09-10) means we re-checked official docs or the current public evidence on that day.
The token UNVERIFIED means the row is in the dataset but has not had a fresh check. In the UI it shows as Needs re-check. Do not treat those cells as current truth.

When evidence changes, we update the CSV and write a changelog entry. We do not silently rewrite a verdict inside a React component.

How a row gets into the High shortlist

Today that is three names, on purpose:

Paddle — MoR, Vietnam still absent from the unsupported-country list.
FastSpring — MoR, broad country coverage; VietQR still coming soon.
Airwallex — High for businesses; Billing eligibility needs a live check after the 2026 expansion.

Lemon Squeezy, Polar, Dodo Payments, and Creem can look attractive on a pricing page. They sit in Low because the operational risk is the story, not the country flag.

What we do not claim

This is not legal, tax, or financial advice. Processors change country lists, KYC rules, and payout desks without emailing you. Read the evidence notes, click through to the official page, and assume your account can still be reviewed.

How the data is maintained

The compare table is generated from data/payments/vn-payments-platforms.csv. Long-form verdict and FAQ copy for the must-ship platform pages lives in content/payments/enrichment.json. Edit those files, rebuild, and the hub, table, sitemap lastmod, and detail pages move together.