Asia-Pacific's B2B payment infrastructure is in a period of structural change that is moving faster than most treasury teams' knowledge of it. The developments are not merely incremental improvements to existing rails — they represent a genuine reordering of how value moves between businesses across the region. This article covers five shifts that are materially changing the corridor map, with analysis of what each means for B2B operators in Singapore.
1. Real-Time Retail Rails Expanding Into B2B Settlement
The most significant structural shift is the expansion of domestic real-time payment rails — originally built for consumer P2P use cases — into B2B settlement infrastructure. This is happening simultaneously across multiple APAC markets.
BI-FAST in Indonesia: Bank Indonesia launched BI-FAST in December 2021 as the successor to the older retail transfer infrastructure. By late 2024, BI-FAST had achieved near-universal coverage among Indonesian banks and had become the default domestic routing for B2B transfers below the IDR 250 million per transaction cap. For Singapore operators disbursing to Indonesian counterparties — e-commerce marketplace payouts, contractor payments, smaller supplier payments — BI-FAST has cut expected settlement time from 1–2 business days (SKN/LLG era) to near-real-time during banking hours, with 24/7 availability being phased in.
PromptPay cross-border expansion in Thailand: Thailand's PromptPay, managed by National ITMX, has moved beyond domestic P2P into cross-border settlement. The Bank of Thailand and MAS have bilateral real-time payment linkage arrangements in development, building on the existing PayNow-PromptPay framework for person-to-person transfers. B2B applications of cross-border PromptPay settlement are emerging for lower-value supplier payments and payroll — with the caveat that BOT FX regulations on purpose documentation still apply to inbound international payments regardless of rail.
InstaPay and PESONet maturation in the Philippines: The BSP's National Retail Payment System framework has driven InstaPay to near-universal coverage among Philippine banks and e-money issuers. PESONet clearing cycles have increased, with some periods seeing three or four clearing windows per day. For BPO sector payroll — a significant component of SGD-PHP B2B flows — the combination of PESONet for same-day batch and InstaPay for smaller disbursements has effectively eliminated the 2–3 day SWIFT settlement timeline for most operational payment types.
2. The PayNow Bilateral Linkage Architecture
Singapore's MAS has been the most active central bank in APAC in building bilateral real-time payment linkages. The PayNow-PromptPay linkage with Thailand and the PayNow-UPI linkage with India are the most mature, but the programme extends further: linkages with Malaysia (PayNow-DuitNow), and exploration of linkages with Indonesia and the Philippines are in various stages of development or operational testing.
For B2B operators, the current iteration of these linkages has a critical limitation: they are designed and calibrated for person-to-person transfers, with transaction limits (typically SGD 1,000–3,000 per transfer) that are far below typical B2B invoice or payroll disbursement sizes. A SGD 500,000 monthly payroll to Philippine employees cannot be routed via the PayNow-PESONet linkage with individual transaction caps — it requires PESONet direct submission through a licensed Philippine payment institution.
We are not saying the bilateral linkage architecture is irrelevant for B2B — the infrastructure being built now will likely evolve to accommodate commercial payment volumes. What we are saying is that current transaction limits mean the PayNow linkage ecosystem supplements, rather than replaces, the local-rail direct settlement paths for most B2B use cases. Monitor MAS and partner central bank announcements on transaction limit increases — those will signal when the bilateral linkage paths become primary for B2B.
3. ASEAN Cross-Border QR and the Project Nexus Framework
The Bank for International Settlements' Project Nexus — which Singapore's MAS has participated in — proposes a multilateral instant payment linkage model where national real-time systems connect through a standardised hub rather than through bilateral arrangements. If deployed at scale, Nexus would reduce the number of bilateral arrangements needed to connect ASEAN's payment systems from O(n²) to O(n), which is the underlying problem with the current bilateral architecture.
For B2B operators, Project Nexus is medium-term infrastructure — operational timelines for multilateral rollout remain in the 3–5 year range. But it represents the logical end state that the current bilateral linkage investments are pointing toward. Understanding that the current bilateral fragmentation is intentionally transitional helps frame investment decisions: building payment infrastructure on a bilateral-linkage-only assumption may require rearchitecting when multilateral connectivity matures.
4. MAS PSA Implementation Reshaping the Provider Landscape
Singapore's Payment Services Act, now in full implementation, has created a clearer two-tier structure among payment service providers. Major Payment Institution licence holders — operating above the SGD 3M monthly volume threshold — face enhanced safeguarding requirements, MAS technology risk management obligations, and more rigorous AML/CFT programme requirements. Standard Payment Institution licence holders have lighter compliance requirements but are volume-constrained.
The practical effect for B2B treasury teams: the number of PSA-licensed providers has grown, but the quality distribution has widened. The post-PSA landscape has more credentialed operators, but also more operators whose compliance programmes were designed to obtain a licence rather than to run a genuinely robust AML and operational risk programme. Due diligence on payment providers now requires reviewing not just whether a PSA licence is held, but whether the provider's KYB/AML programme is substantive, whether client monies are properly safeguarded, and whether the technical infrastructure supports reliable settlement across the APAC corridors relevant to the business.
5. ISO 20022 Migration and Structured Payment Data
The global migration from SWIFT MT message format to ISO 20022 (MX format) is underway, with SWIFT's cross-border MT/MX coexistence period running through November 2025. ISO 20022 messages carry significantly richer structured data — including remittance information, purpose codes, beneficiary details, and compliance screening fields — than MT messages.
For APAC B2B operators, this matters in two ways. First, ISO 20022-compliant payment instructions are more likely to pass through AML screening at correspondent and receiving banks without delays, because the structured data fields allow automated purpose-code and beneficiary verification that MT messages cannot support. Second, for businesses that reconcile payments against ERP systems, ISO 20022's structured remittance information makes automated reconciliation significantly more accurate — reducing the manual reconciliation overhead that plagues businesses with high-volume APAC payment flows.
The practical implication for treasury teams: ensure your payment service provider supports ISO 20022 MX formatting for cross-border payment instructions, and ensure your ERP or finance system can ingest ISO 20022 payment status and remittance data. This is not an immediate operational crisis — MT and MX coexist through the transition period — but it is an infrastructure debt that will need to be addressed.
Reading the Map
The five shifts described above share a common direction: APAC's B2B payment infrastructure is moving toward real-time settlement, structured data, lower intermediary costs, and regulatory clarity. The pace is uneven — Indonesia's BI-FAST deployment moved faster than many expected, while the Project Nexus multilateral timeline remains aspirational. For Singapore-based B2B operators, the practical near-term implication is that local rail settlement via licensed payment service providers already outperforms SWIFT for the five core APAC corridors on cost and speed, and that gap will likely widen as real-time infrastructure matures and bilateral linkage transaction limits increase.
Treasury teams that wait for "the infrastructure to settle" before optimising their corridor routing will continue paying correspondent banking costs on flows that already have better alternatives. The infrastructure for better APAC B2B settlement is not coming — it is already here, across most of the corridors that matter.