How Southeast Asia actually pays.
Cards are the minority rail across much of Southeast Asia. Here is how customers prefer to pay in each market — and what it takes to accept all of it without six integrations.
Why "cards only" quietly caps your revenue.
Across the region, e-wallets, real-time bank transfers and national QR standards sit between most customers and a card form. International cards that do get entered can fail on issuer checks, 3-D Secure friction or FX surprises. The practical result: businesses that add local rails see checkout completion move — because customers pay with money they can actually reach.
Wallet-first consumers
In several markets the primary payment account is a wallet app, not a card. If your checkout doesn't speak wallet, you're invisible at the moment of purchase.
National QR standards
Thailand (PromptPay QR) and Indonesia (QRIS) standardized how consumers scan to pay. Merchants who display the local QR accept from every participating bank and app at once.
Real-time bank rails
InstaPay and PESONet (Philippines), FAST (Singapore), PromptPay (Thailand) — account-to-account transfers are routine consumer behaviour, not an edge case.
Web top-up flows
Games, novels and short-drama apps commonly send buyers to a web top-up centre — a sign the team needs payment rails beyond app-store billing.
Market by market.
The rails below reflect what ApeX covers today. Licensing status is noted where we hold local licences.
| Market | Rails that matter | What to know |
|---|---|---|
| Thailand · local acquiring | PromptPay · TrueMoney · cards | PromptPay QR is the default for many Thai shoppers; wallets complement rather than replace it. Thai-language checkout matters. |
| Philippines · local acquiring | GCash · Maya · InstaPay · PESONet | A wallet duopoly with deep consumer adoption; InstaPay for instant transfers, PESONet for batch. Remittance habits make wallets the default for digital goods. |
| Indonesia | QRIS · OVO · DANA · GoPay | One national QR (QRIS) routes to every major wallet and participating bank — a single display code reaches the whole ecosystem. |
| Vietnam | MoMo · ZaloPay · bank transfer | Wallets plus direct bank transfer; international card failure rates push many teams toward local rails and web top-up flows. |
| Singapore · local acquiring | PayNow · FAST · cards | Cards are mainstream, but PayNow is the local default for account-to-account payment. |
| Malaysia | FPX · Touch 'n Go · GrabPay | FPX online banking dominates larger baskets; wallets cover the small, frequent ones. |
What to look for in a Southeast Asia gateway.
One integration, every rail
Each extra PSP means another contract, reconciliation format and failure mode. A single API that speaks wallet, QR and card keeps your checkout and your ledger simple.
Settlement you can plan around
Ask where funds land, in which currency, and on what schedule. ApeX settles locally and can convert to USDC or USDT when you want the money on-chain the same day.
Routing and retries
Smart routing that retries a failed authorization across methods recovers revenue a single-rail gateway silently loses.
Licences where it counts
Local acquiring under local licences (ApeX: Singapore, the Philippines, Thailand) keeps funds and compliance onshore — and your reserves where the disputes happen.
Ready to see rates for your mix? Check pricing or browse the coverage table.
How local rails differ from cards.
The gap is structural, not cosmetic: who confirms the payment, where the money sits, and what happens when something goes wrong.
Cards are a credit-line instrument: an authorization is a promise to charge, a descriptor appears on a statement later, and a dispute can claw the money back long after delivery. Local rails are usually account-to-account — the customer approves each payment inside their own wallet or banking app, and the money moves from funds they already have. That difference in confirmation is why local methods tend to feel safer to shoppers, and why completion often improves when a local method sits next to the card form.
Approval behaviour differs for the same reason. A card authorization can decline on issuer risk rules, cross-border flags or 3-D Secure friction even when the customer has funds available. Local rails move the confirmation into an environment the customer already trusts — a QR scan, a wallet balance, a bank app they open daily — so fewer payments die between intent and confirmation. The exact improvement varies by market and audience, so treat any benchmark as a hypothesis and measure it in your own checkout.
Cost and disputes follow the same pattern. Local methods are typically priced per transaction without the layered interchange and scheme fees that cross-border cards carry, and formal chargebacks are far less common because the customer explicitly approves every payment in their own app. Fewer dispute workflows is a real operational saving — but it shifts the weight onto prevention, because recovering an account-to-account transfer after the fact is much harder than reversing a card payment. Fraud controls move earlier in the flow, into device checks and payment-page hygiene, rather than after-the-fact reversals.
| Dimension | Cards | Local rails |
|---|---|---|
| Confirmation | Issuer authorization, later statement descriptor | Customer approves in their own wallet or banking app |
| Common failure points | Issuer risk rules, 3-D Secure friction, cross-border flags | Insufficient wallet balance at the moment of scan; unsupported devices |
| Cost structure | Interchange, scheme and cross-border fees stack up | Typically a per-transaction local price |
| Disputes | Formal chargeback process with reversals | Formal disputes are rare; prevention matters more than reversal |
Wallet-first vs bank-first corridors.
Most Southeast Asian markets lean one of two ways — and your checkout, support and settlement should lean with them.
In wallet-first markets the consumer wallet app is the centre of daily payments. The Philippines is the clearest example: GCash and Maya form a wallet duopoly with deep adoption, and remittance habits make wallets the default for digital goods. Vietnam leans similar, with MoMo and ZaloPay carrying much of everyday checkout. In these corridors, the wallet badge is your headline payment method — give it first position, and make sure support can walk a customer through a wallet app they already use every day.
Bank-first corridors keep account-to-account transfer at the centre. Singapore's PayNow sits on top of the FAST rail and is the local default for account-to-account payment; Malaysia's FPX dominates larger online baskets, with wallets like Touch 'n Go and GrabPay covering the small, frequent ones. Thailand blends both worlds: PromptPay QR is the everyday default, with wallets complementing rather than replacing it. Indonesia deliberately spans the divide — QRIS is one national QR standard that routes to every major wallet and participating bank, so a single displayed code reaches the whole ecosystem.
The practical takeaway: match your rails to how each corridor actually pays instead of shipping the same checkout everywhere. Wallet-first markets reward top-up-friendly flows and wallet-first ordering; bank-first markets reward clean hand-offs into the bank's own confirmation screens and sensible handling of basket size — instant rails for everyday amounts, batch or online-banking rails for larger ones.
Settlement and treasury: fiat, stablecoin, or both.
Collections land in local currency. The real decision is where that money needs to be next.
If your costs are local — payroll, ads, hosting bought in the same market — settling in local fiat keeps the treasury simple: no extra conversion, no extra exposure, money already where it is spent. Ask any prospective gateway three questions and write the answers down: where funds land, in which currency, and on what schedule. Those three answers determine how predictable your cash flow is.
If the money's next stop is another country — suppliers, licensors, a central treasury — moving value across borders is where stablecoin settlement earns its keep. ApeX settles locally and can convert to USDC or USDT when you want the money on-chain the same day, so the same collections can fund local operations and international payables at once. Because you decide per withdrawal, a mixed policy is practical rather than theoretical: local fiat for local costs, stablecoins for cross-border ones.
Whatever split you choose, make it explicit before launch: which currencies settle where, on what schedule, and who is allowed to instruct a conversion. A settlement policy designed on purpose is easy to audit; one discovered later in the ledger is not. Teams that write this down early also onboard finance staff faster, because the rules live in a document instead of in someone's head.
Step by step: start collecting with local rails.
From a market list to your first settled transaction — the path most teams follow with ApeX, which covers local collections in 40+ markets through one API.
- Map your markets. List the countries and buyer segments you serve, and note which rails dominate in each: national QR standards, consumer wallets, or real-time bank transfers.
- Talk to sales and complete KYB. Share your markets and product mix with our team, then complete KYB under the relevant locally licensed ApeX entity — no local incorporation required.
- Integrate in sandbox. Connect your checkout to the sandbox first and confirm that each payment method returns success, pending and failure callbacks exactly as documented.
- Test every rail end to end. Run test transactions across wallets, QR and bank-transfer rails, including a retry path for a failed authorization.
- Configure settlement. Choose where funds land: local fiat on an agreed schedule, or USDC or USDT when you want value on-chain the same day.
- Go live and monitor. Switch to production credentials, watch completion by method in the dashboard, and add rails market by market as volume grows.
Most of these steps happen once — after that, adding a market is a configuration change, not a second integration. Talk to our team to map your specific mix, or read the API docs first.
Frequently asked questions.
Which method should I launch first in Thailand?
PromptPay, paired with cards for international customers. It is the rail most Thai shoppers already use daily, and QR display works on any device with a banking app.
Do I need a local entity to accept local payments?
Not with ApeX — merchants onboard under our locally licensed entities in Singapore, the Philippines and Thailand. KYB is still required; a local company is not.
How do wallet payments settle?
Wallets and QR rails collect into local accounts, then settle to you on an agreed schedule in an agreed currency — local fiat, or stablecoins if you prefer on-chain settlement.
What is the difference between InstaPay and PESONet?
Both are Philippine bank-transfer rails: InstaPay moves funds in near real time for smaller, everyday amounts; PESONet batches larger credits. Consumers use both without thinking about the plumbing.
Can I combine app-store billing with local rails?
Yes — many apps keep Google Play / Apple billing for in-app purchases and route web top-ups through a local gateway, which typically costs less per transaction and unlocks wallet payers.
How fast can we go live?
After KYB, integration is a sandbox first (see Developers), then production credentials. Timelines depend on your markets and review — talk to sales for a concrete plan.
How do chargebacks and disputes differ on local rails?
Card payments carry a formal chargeback process where funds can be reversed after delivery. Wallet and real-time bank transfers are approved by the customer in their own app, and formal dispute mechanisms are far less common — so prevention (clear descriptors, confirmation screens, sensible risk rules) matters more than after-the-fact recovery.
Should I settle in local fiat or convert to stablecoins?
Follow the money's next stop. Local costs argue for settling in local fiat; cross-border suppliers and a central treasury argue for USDC or USDT. With ApeX you decide per withdrawal, so a mixed settlement policy is normal rather than exceptional.
Do international cards still have a role?
Yes — for customers outside the region, cards are often the most convenient method available. Many teams route international buyers to cards and domestic buyers to local rails, letting routing logic choose per transaction rather than forcing one method on everyone.