corridors

ASEAN Payment Corridors 2026: State of the Market

A corridor-by-corridor breakdown of how ASEAN cross-border payments actually flow today — from MY-SG QR linkage to the IDR-PHP backwater. What's working, what's broken, and what's worth integrating.

April 22, 20267 min readBy Kaadxpay Team

If you've spent any time inside ASEAN payment infrastructure, you know the official narrative — "10 countries, harmonized real-time payments, ASEAN-5 QR linkage by 2025" — barely survives contact with reality. The corridors are real. So is the friction.

This is our 2026 view from inside the orchestration layer. We process payments across most of the ASEAN-6 plus Hong Kong, and what follows is what the corridor map actually looks like, not the press-release version.

The actual corridor map

We measure corridors along five dimensions:

  1. Real-time availability — can a transfer settle in seconds?
  2. FX liquidity — is the local-to-local pair traded directly, or routed through USD?
  3. Regulatory simplicity — how many forms, how much KYC re-collection?
  4. Fee transparency — is the all-in cost knowable in advance?
  5. Reliability — what's the production failure rate?

Here's the 2026 scorecard for the corridors we touch most:

CorridorReal-timeFX directnessReg simplicityFee transparencyReliabilityOverall
MY → SGAA (direct MYR/SGD)AAAA
SG → IDAB (via USD)BBAB+
HK → PHBB (via USD)BBAB
MY → IDB+C (via USD)BCBB-
TH → VNCC (via USD)CCCC
ID → PHDD (via USD x2)DDCD

The headline: corridors involving Singapore are uniformly best. Indonesia is mixed. Vietnam, Cambodia, Myanmar are still legacy SWIFT territory for most flows.

MY → SG: the gold standard

The MY-SG corridor is the closest ASEAN gets to "it just works":

  • DuitNow ⇋ PayNow QR linkage went live in 2024 and is genuinely real-time
  • Direct MYR/SGD FX with tight spreads (typically 5-15 bps over interbank for retail-size flows)
  • Single AML regime in practice — both BNM and MAS accept each other's CDD as starting points
  • Reliability is bank-grade — both sides publish uptime, both deliver

Average all-in cost for SME-sized flows (MYR 10K–500K): 0.4–0.8% depending on volume tier and channel. That's competitive globally.

SG → ID: the workhorse corridor

Singapore-to-Indonesia is volume-heavy because of trade and remittance, but technically rougher:

  • PayNow ⇋ BI-FAST linkage is announced but not yet live for general access (slated for late 2026)
  • FX is USD-routed by default — you pay 2 spreads (SGD/USD + USD/IDR), often 30-60 bps total
  • AML re-collection is required for non-resident IDR exposure; Indonesia's enforcement of the foreign currency restrictions (Rupiah Mandatory Use) adds friction
  • Reliability is good once you're set up — BI-FAST itself is excellent

What works in 2026: Wise + locally-licensed partners; a few orchestrators (us included) bypass the USD leg via direct MAS-licensed FX counterparties paired with BI-licensed remittance partners.

Practical tip

For SGD → IDR over USD 50K, the all-in fee gap between "naïve route via correspondent bank" and "optimized route via licensed FX + RPP partner" is often 80–120 bps. That's USD 400-600 per USD 50K transfer. Worth shopping carefully.

HK → PH: the diaspora corridor

Hong Kong to the Philippines has unique dynamics driven by the OFW (Overseas Filipino Workers) flow — over USD 30B/year:

  • Receive-side rails are excellent: InstaPay and PESONet are both reliable and same-day
  • Send-side in HK has deep bank competition keeping fees down
  • FX is USD-routed but spreads are tight because of corridor depth
  • The genuine pain is KYC for the recipient — many Filipino recipients still lack permanent ID; orchestrators that integrate eKYC over PhilSys gain a real advantage

Typical retail remittance fee in 2026: HKD 25–60 flat plus 0.5-1% FX margin for amounts under HKD 50K.

MY → ID: the underserved trade corridor

This is where orchestration genuinely creates value. The MY-ID corridor is heavily used by Malaysian SMEs trading with Indonesian counterparts (palm oil, textiles, electronics), but:

  • No QR linkage live as of mid-2026
  • FX requires USD routing in 95% of cases
  • BNM and BI both impose paperwork (LHDN forms on the MY side, RPP onboarding on the ID side)

What's working: B2B platforms that pre-onboard both parties as merchants, run KYC once, and net flows so the per-transaction FX cost amortizes.

ID → PH: the broken corridor

This one's worth flagging because it shows up on every "ASEAN integration" deck and is broken in practice:

  • No direct IDR/PHP FX market with retail liquidity
  • Both directions go via USD, paying 2 sets of spreads
  • Both regulators require local-currency settlement, which means double the AML overhead
  • Remittance volume is low (under USD 200M/year) so no orchestrator has invested in optimization

If you have a use case here, you'll likely route via Singapore or Hong Kong as a hub — adding a leg, but cleaning up the FX path.

What the press releases miss

Three realities the integration narratives gloss over:

1. QR linkage is consumer-side only. "ASEAN QR" connects the consumer payment moment, but the underlying B2B settlement still uses correspondent banking. For merchants, the experience often feels worse, not better, because they now reconcile multiple FX-adjusted settlements where they previously had a single domestic flow.

2. The middle 6 countries' rails are uneven. Vietnam's 24/7 NAPAS clears domestic instantly but cross-border is still SWIFT-dependent. Cambodia's KHQR is excellent intra-Cambodia but largely opaque to non-Khmer banks. Myanmar's situation is heavily affected by sanctions overlay.

3. AML harmonization is a press release, not a reality. Each ASEAN regulator runs its own CDD playbook. We've not yet seen a single CDD packet move untouched from one regulator's licensee to another's; the operator always re-collects.

What we'd watch in 2026-27

  • PayNow ↔ BI-FAST live launch — should compress SG-ID corridor cost by ~25-40 bps if it lands
  • Project Nexus rollout — the BIS-led inter-RTPS bridge has Singapore live and Malaysia close; if Indonesia and the Philippines join, it materially changes the corridor graph
  • CBDC pilots — Singapore's Project Orchid and Hong Kong's e-HKD are both advancing; production cross-border CBDC use is at least 2-3 years away but worth tracking
  • AML packet portability — quietly, a few of the larger banks have started accepting upstream CDD from regulated counterparts. If this becomes consistent, orchestrator economics improve materially

What this means for builders

If you're building anything cross-border in ASEAN in 2026:

  1. Don't believe the ASEAN-5 marketing. Map each corridor on its actual merit.
  2. Build for routing, not for a single rail. What's optimal for MY-SG is wrong for ID-PH.
  3. Invest in your AML/KYC stack early. You'll re-run CDD more than you'd like; cost-effective recollection beats ineffective harmonization.
  4. License where you must, partner where you can. The Labuan FSA PSO + 3-4 local partners model is currently the leanest path to coverage. (We wrote about the PSO license in detail here.)
  5. Measure corridor reliability empirically. Press-release uptime is not real uptime.

We'll publish corridor-by-corridor deep dives over the coming months. If you have a specific corridor you'd like us to break down, send us a note.

Author
Kaadxpay Team
Cross-Border Payments Research

Engineering, compliance, and corridor research from the team building Kaadxpay — a Labuan FSA-licensed cross-border payment orchestrator for ASEAN and beyond.

Related Reading

Labuan FSA PSO License Explained: Why It Matters for ASEAN Cross-Border Payments

Labuan FSA PSO License Explained: Why It Matters for ASEAN Cross-Border Payments

A practical guide to the Labuan Financial Services Authority Payment System Operator license — what it permits, who needs it, and how it compares to BNM, MAS, and offshore alternatives.

Apr 28, 20266 min read
Stripe vs Airwallex vs Kaadxpay: ASEAN Payments Comparison (2026)

Stripe vs Airwallex vs Kaadxpay: ASEAN Payments Comparison (2026)

An honest, opinionated comparison of three cross-border payment platforms serving ASEAN merchants. Pricing, coverage, settlement speed, FX margin, and where each one actually shines.

Mar 25, 20268 min read
Idempotency for Payment APIs: The Engineering Playbook

Idempotency for Payment APIs: The Engineering Playbook

How to design idempotency keys that survive retries, network partitions, and creative client behavior. The patterns we use in production at Kaadxpay, written for engineers who actually have to debug double-charge tickets.

Apr 15, 20268 min read

Subscribe to Kaadxpay Insights

Monthly insights on cross-border payment corridors, regulation, and engineering practice.