Product guides · 6 min read

The builder's guide to QR payouts in Southeast Asia

Everything a product team needs to know before shipping payouts onto the national QR rails of Vietnam, Thailand, and the Philippines.

Why QR rails, not bank wires

Across Southeast Asia, the default way people receive money is not a bank wire. It is a national QR network tied to their bank account or wallet: VietQR in Vietnam, PromptPay in Thailand, QR Ph in the Philippines. These rails settle in seconds, reach street-level merchants and rural recipients alike, and cost a fraction of an international wire.

For a payout product, that changes the design target. You are not delivering to an IBAN in three days. You are delivering to a phone number, a national ID, or a scanned QR code, and the recipient expects the money before they put their phone away.

Addressing: how recipients are identified

Each rail has its own addressing model. PromptPay resolves phone numbers and national IDs. VietQR encodes bank and account directly in the QR payload. QR Ph unifies addressing across every participating Philippine bank and e-money issuer. A good payout API hides these differences: you pass a recipient reference, and routing resolves the rail-specific address underneath.

FX: quote first, then execute

Cross-border payouts live or die on FX transparency. The pattern that works: create a quote with a locked rate, show the recipient amount to your user, then execute against that quote. The amount you display is the amount that arrives. Anything else generates support tickets.

Settlement: what "instant" actually means

Two clocks run on every payout. The first is delivery: the recipient sees funds on their local rail in seconds. The second is settlement between you and your payout provider, which runs on an agreed cycle. Design your ledger so the two are independent, and reconcile with itemized FX per payout rather than netted totals.

Compliance: build it into the flow

Every payout should pass AML and sanctions screening before it touches a rail, and your provider should carry partner-led compliance in each destination market. Ask where screening happens, who holds the local licenses, and what happens to a payout that fails screening mid-flight. The answers tell you more than any sales deck.

Where to start

Pick one corridor with real demand, ship it end to end, then expand. On Zennopay, the second market is a parameter change rather than a new integration: the same API call reaches every rail on the ledger. See current coverage or read the API docs to go deeper.