Payment Gateway Vietnam: Cards, MoMo, VietQR and Bank Routes

This guide is for cross-border e-commerce, gaming, digital-content, software-as-a-service (SaaS) and subscription businesses. It distinguishes public market evidence from provider documentation and merchant-specific approval. HaiPay publishes this guide and provides payment services, so its own coverage is assessed under the same evidence rules. It is educational information, not financial, investment, legal or tax advice.

What a Vietnam payment gateway needs to support

Begin with six questions that describe the payment operation you need:

1. Customer: Is the buyer a Vietnamese resident using a local wallet or bank app, or an international cardholder?
2. Method: Does the checkout need cards, MoMo, bank-account QR, bank transfer, or a combination?
3. Entity: Which legal entity signs the agreement, and is that business model approved?
4. Currency: What does the buyer see, which balance is credited, and which currency reaches the merchant bank?
5. Operations: Which callback, query, refund, dispute and reconciliation steps are available for each route?
6. Commercial terms: Which transaction, foreign-exchange (FX), tax, transfer, reserve and settlement terms appear in the signed quote?

If a provider answers with a method count or the word “multi-currency”, the answer is incomplete. Each question needs a route-level response.

For a broader view of gateway roles, start with the international payment gateway guide. The distinction between local and cross-border acquiring also helps locate FX and settlement responsibilities.

Vietnam's card, wallet and bank-QR landscape

Three method families matter here, and they should not be collapsed into one “local payments” label.

• Cards let a buyer enter card credentials at checkout. The merchant still needs an approved card route, authentication design and dispute process.
• MoMo is a wallet and payment product. A customer approves through the MoMo environment; the exact mobile or desktop handoff depends on the integration.
• VietQR is a common brand used with National Payment Corporation of Vietnam (NAPAS)-related bank-account QR transfers; it is not an electronic-wallet product. The code identifies an account-based transfer destination. A compatible scanner can be a bank or payment app, so the scanning app alone does not define the payment route.

State Bank of Vietnam (SBV) material on the VietQR/NAPAS247 launch describes a common brand used through NAPAS, member banks and intermediaries. NAPAS describes the underlying flow as account-to-account transfer by QR. These market facts do not prove that any gateway or merchant account has the route enabled.

Source: SBV-hosted VietQR/NAPAS247 bulletin and NAPAS 247 with VietQR, verified 2026-09-03.

Card payments for international merchants

Cards can remain useful for international customers, subscriptions and buyers who do not use a Vietnamese wallet or bank app. A card option does not remove the need for local methods, and a Vietnam method list does not establish the card flow for your account.

HaiPay's public pricing page lists Visa and Mastercard under Vietnam. Its current Vietnam application programming interface (API) method table does not show a separate card collection row. A merchant should therefore ask which card product and production application identifier (appId) apply, which currencies are accepted, and how authentication, recurring payments, refunds and disputes work.

Do not transfer a general card ticket range to a local wallet, QR or bank route that processes Vietnamese dong (VND). Method limits and operating rules belong to the approved route.

Source: HaiPay Pricing and HaiPay Vietnam API, verified 2026-09-03.

MoMo wallet payments

MoMo is a wallet product, not a synonym for Vietnamese QR payments. First-party MoMo onboarding material says direct merchants register through MoMo for Business, submit company information, enter testing, and complete technical integration and company-account verification before production keys are issued.

Those are MoMo's direct onboarding facts. They do not describe an aggregator's eligibility, commercial terms or settlement. A merchant considering MoMo through another provider should ask:

• What name and logo will appear at checkout?
• Does a desktop customer scan a wallet QR, while mobile redirects to or opens the wallet app?
• Which production appId and route are approved for the merchant entity?
• Which callback and query status can trigger fulfilment?
• Are refunds supported for this route, and how are they reconciled?
• What are the presentment, balance and settlement currencies?

Source: MoMo merchant-profile onboarding, verified 2026-09-03. The source describes direct MoMo onboarding, not HaiPay account terms.

VietQR and bank-account QR payments

VietQR belongs to the bank-account QR path. NAPAS describes its service as a QR-enabled account-to-account transfer through the NAPAS network. An SBV-hosted launch bulletin connects the common VietQR brand to EMVCo payment-QR specifications and the basic QR standard issued under Decision 1928.

A later SBV release describes Decision 2525 and the customer-presented QR standard numbered TCCS 04:2024. That is a different presentation direction. The release does not establish that Decision 2525 replaced Decision 1928.

The label on the provider side still matters. A generic QR route may return a QR code without proving that the underlying standard or brand is VietQR. Ask the provider to identify the standard or brand, supported customer apps, production route, callback and reconciliation fields in writing.

NAPAS-level institution counts or transaction ceilings should not be used as a gateway's account coverage or route limit. The provider and merchant agreement control that narrower scope.

Source: NAPAS 247 with VietQR, SBV-hosted VietQR/NAPAS247 bulletin and SBV release on Decision 2525, verified 2026-09-03.

MoMo versus VietQR: different customer flows

Choose between these flows by the customer's account and action. Do not choose by the fact that both may involve a QR image.

Market availability, published route and merchant activation

A payment method passes three separate gates:

1. Market existence: an operator or official source shows that the method exists in Vietnam.
2. Provider documentation: a provider publishes a method, route label or API path for Vietnam.
3. Merchant activation: the provider confirms the route for the merchant's entity, appId, currencies and production account.

Evidence does not move from one gate to the next automatically. The existence of VietQR does not prove provider support. A published route does not prove that a given merchant can activate it.

Source: HaiPay Pricing, HaiPay Vietnam API, MoMo, NAPAS and SBV sources cited above; verified 2026-09-03.

VND and US dollars (USD): presentment, balance and settlement are different

“Supports VND” can refer to several different points in the funds flow. Ask about each one:

1. The amount and currency shown to the shopper.
2. The order currency sent to the collection endpoint.
3. The payment-method processing currency.
4. The platform balance credited after collection.
5. The point, if any, where conversion occurs.
6. The merchant settlement currency.
7. The payout account, bank currency, fees and transit time.

The current Vietnam API describes VND and USD collection paths and says successful transactions increase the corresponding platform balance. That is evidence about order and balance currency. It does not say which currency reaches a specific merchant bank account.

The same rule applies to a Global Cashier response that contains original-currency and floating-rate fields. A rate field shows a conversion result was represented; it does not identify the benchmark, price side, sample time, markup or settlement currency.

Source: HaiPay Vietnam API and Global Cashier, verified 2026-09-03.

Fees, tax, FX and settlement

Compare the complete commercial stack, not one transaction percentage.

Published pricing is a starting structure

HaiPay's public schedule lists the following general fields:

None of these fields is a quoted price for MoMo, VietQR, BANK, MOMO_VND or another specific Vietnam route. The merchant entity, route, market, volume, transaction quality, risk review and signed agreement determine the applied terms.

Source: HaiPay Pricing, verified 2026-09-03.

Treat settlement as three clocks

A settlement tier is only one clock. The payout schedule controls when a provider releases funds, and bank transit controls when the destination bank posts them. A complete quote should also name the day convention and explain weekends and public holidays.

HaiPay's public settlement guide says its tiers count calendar days, while execution occurs on working days. It also says the actual timeline depends on the contracting entity, volume, transaction quality and quote. This guide does not apply a single public tier to every Vietnam route.

Source: HaiPay settlement guide, verified 2026-09-03.

Make the FX definition reproducible

Ask the provider to confirm the applicable FX reference and final applied rate in the merchant quote. The quote should define the source, currency pair, buy or sell side, sampling time and timezone, aggregation method, markup, outbound fee and route.

An FX reference does not imply any additional payment or settlement method.

How to verify a tax line in a Vietnam quote

Do not turn an unexplained quote percentage into a national payment-gateway tax rate. Vietnam's value-added tax (VAT) and corporate-income-tax framework has changed across laws, decrees and circulars, including amendments effective in 2026. The applicable treatment can depend on the contracting entity, income or service classification, contract allocation, calculation method and transition rules.

For every tax or tax-handling line, obtain:

• The exact legal or contractual name.
• The current legal basis.
• The tax base: gross merchandise value, processing fee, net settlement or another defined amount.
• The party that withholds and the party that declares or remits.
• Whether the amount is included in the quote or added to it.
• The contracting entity, route and merchant type.
• The gross-up rule, effective date, transition treatment and exceptions.
• Written confirmation from the relevant tax or compliance owner.

This checklist is due diligence, not tax advice. An accountant or tax adviser should assess the merchant's own facts and current law.

Source: Vietnam Law 09/2026/QH16 and Circular 20/2026/TT-BTC, verified 2026-09-03.

Merchant entity and route activation

Resolve the legal entity before building around a method. A method can exist in the market and appear on a pricing page, yet remain unavailable for a specific business model or account.

Send the provider a compact activation pack:

• Full merchant legal name, incorporation country and website.
• Product or service, customer locations and fulfilment model.
• Expected monthly value, transaction count and average order value.
• Refund, subscription, dispute and delivery profile.
• Required methods, currencies and countries.
• Desired settlement currency and destination bank account.
• Required production date and integration model.

Ask for the contracting entity, approved route, appId, method display name, presentment currency and settlement terms in the same written response. A sandbox credential or documentation page is not production approval.

Status, refunds, disputes and reconciliation

Checkout success is only the first operating state. Before launch, map the route across the full lifecycle:

The current public Vietnam documentation contains inconsistent numerical ranges and sample fields that do not all align with a Vietnam collection flow. This guide therefore does not reproduce route limits or code examples. Obtain a current production specification and test it through approved user acceptance testing (UAT) cases.

Vietnam Payment-Route Evidence Matrix

This matrix reports what the current public sources establish. “Documented” does not mean activated.

Source: HaiPay Pricing, HaiPay Vietnam API, MoMo onboarding, NAPAS and SBV sources cited above; verified 2026-09-03.

A practical route-selection flow

1. Fix the contracting entity. Stop if the provider cannot name it or assess the business model.
2. List real customer contexts. Separate local wallet users, compatible bank-app users and international cardholders.
3. Choose the method family. Keep cards, MoMo, bank-account QR and bank transfer distinct.
4. Name the production route. Do not accept “QR” as proof of a specific scheme.
5. Split the currency chain. Record presentment, order, balance, conversion, settlement and bank-account currency.
6. Test the state machine. Cover callback, query, duplicate events, expiry, fulfilment, refund and dispute cases.
7. Review the reconciliation file. Finance should be able to join the order, payment, fee, FX, reversal and payout.
8. Sign the complete quote. Include route, tax, FX, settlement, payout, reserve and exception terms.

Stop at any unresolved gate. Integration effort should follow written activation, not precede it.

Where HaiPay may fit—and what to confirm

HaiPay's public Vietnam row lists cards, MoMo, bank transfers and VietQR. Its Vietnam API separately documents generic VND QR, bank and MoMo labels, plus USD QR and bank labels. These sources make HaiPay a candidate for a scoped discussion, but they do not activate a merchant account.

Source: HaiPay Pricing and HaiPay Vietnam API, verified 2026-09-03.

HaiPay may fit if the required method, entity and currency path are confirmed together, and if the operations package meets the merchant's refund, dispute and reconciliation needs. Review the local payment product, card product and public pricing structure, then contact HaiPay with the route-selection checklist.

Request one written response that covers:

• Contracting entity and approved merchant profile.
• Production appId, route code and checkout display name.
• VND or USD presentment, balance, conversion and settlement path.
• Customer action on desktop and mobile.
• Route limits in the current production specification.
• Callback, query, refund, cancel, dispute and reconciliation behaviour.
• Settlement clock, payout schedule, bank transit and transfer charges.
• Exact tax and FX definitions, including scope and effective date.

Sources

1. State Bank of Vietnam, VietQR/NAPAS247 launch bulletin. Accessed 2026-09-03. Supports the common-brand, operator and Decision 1928 context.
2. NAPAS, NAPAS 247 with VietQR. Accessed 2026-09-03. Supports the bank-account QR and NAPAS-network flow.
3. MoMo Developer, Merchant Profile onboarding. Accessed 2026-09-03. Supports direct MoMo registration, testing and production-key prerequisites.
4. State Bank of Vietnam, Decision 2525 and TCCS 04:2024 release. Accessed 2026-09-03. Supports the later customer-presented QR standard context.
5. HaiPay, Payment Gateway Pricing. Accessed 2026-09-03. Supports public pricing structure, Vietnam marketing labels and quote limitations.
6. HaiPay, Vietnam API. Accessed 2026-09-03. Supports documented collection paths, route labels and platform-balance wording; numerical limits and sample payloads are intentionally not reproduced.
7. HaiPay, Global Cashier. Accessed 2026-09-03. Supports the VN currency row and original-currency/rate response fields, not a benchmark or settlement claim.
8. HaiPay, Payment Settlement Time. Accessed 2026-09-03. Supports the calendar-day, working-day, payout and bank-transit framework.
9. Vietnam Government Portal, Law 09/2026/QH16. Accessed 2026-09-03. Supports the current amendment layer across VAT and corporate income tax.
10. Vietnam Government Portal, Circular 20/2026/TT-BTC. Accessed 2026-09-03. Supports current foreign-enterprise corporate-income-tax implementation and transition context.