From Bilateral Corridors to Network Architecture: What Project Nexus Asks of Cross-Border Instant Payments

Introduction

Cross-border instant payments have reached an inflection point. Households and businesses in more than 100 jurisdictions now have access to fast payments. Yet the cross-border layer connecting them remains fragmented, expensive, and operationally complex. Project Nexus is the most important live-implementation test of a different model: a multilateral scheme that lets domestic instant payment systems connect once to reach every other participating country. Its founding partners are India, Malaysia, the Philippines, Singapore, and Thailand. Together, they represent the first wave potential market reach of roughly 1.7 billion people. Live operation is targeted for 2027 rather than already achieved.

The strategic opportunity is no longer in question. The operating model that carries it is.

ASEAN has already shown that bilateral cross-border payment connectivity can work. The Singapore-Thailand PayNow-PromptPay link, Malaysia-Indonesia QR connectivity, and other regional QR/account-to-account corridors prove demand and technical feasibility. The limitation is scalability. Each corridor still requires agreement on scheme rules, participant reachability, FX handling, compliance responsibilities, operating hours, dispute handling, and data-sharing boundaries. Nexus reframes the challenge from corridor-by-corridor construction to network architecture. That shift depends less on another payment switch and more on a common scheme layer. This includes ISO 20022 profiles, API specifications, reference data, proxy resolution, FX-provider and settlement-access roles, and operating rules that every IPS operator and participant can implement consistently.

This piece explores three things:

1. What bilateral connectivity reveals about the limits of corridor-first thinking
2. What cross-border integration actually demands at network scale
3. What that shift means strategically for the operators and infrastructure providers preparing for the next phase

The bilateral model is not failing. It is hitting a structural ceiling.

Existing ASEAN linkages show that domestic schemes can be connected across borders and that fast user confirmation is achievable. Their success also exposes the structural constraint. The IMF’s February 2026 analysis of ASEAN digital payment integration points to cross-border payments as a driver of local-currency usage and regional integration. It also highlights interoperability, operational-risk, cyber-risk, and policy-coordination challenges. In practice, every new bilateral connection adds another legal, FX, compliance, data, participant-certification, and operational construct. The stronger the bilateral network becomes, the more valuable a reusable multilateral layer becomes.

From Bilateral to Network: The Architectural Shift That Defines What Comes Next

Nexus is built on a different premise. BIS and Nexus Global Payments describe a connect-once model in which an IPS operator connects to Nexus rather than building a bespoke integration for every new country. The first-mover owners are the central banks and/or IPS operators of India, Malaysia, the Philippines, Singapore, and Thailand. Bank Indonesia and the Eurosystem are special observers. Their involvement follows earlier Nexus phases, including the 2022 proof of concept linking test versions of TIPS, Malaysia’s RPP, and Singapore’s FAST. That distinction matters. Nexus is not yet a global production network. However, it has moved from a BIS-led concept into an independently incorporated implementation vehicle with public technical documentation, ISO 20022 specifications, API specifications, and a targeted 2027 go-live.

The strategic implication is not that bilateral corridors disappear. Domestic IPS operators and participant banks now need to become network-ready. They must be schema-extensible, reference-data disciplined, settlement-aware, FX-integrated, compliance-configurable, and operationally prepared for 24/7 cross-border service levels.

What Cross-Border Integration Actually Demands

The challenge starts with a design reality. Most domestic instant payment systems were built first for national policy objectives, domestic settlement models, domestic compliance assumptions, and local participant rules. Cross-border interoperability changes the operating problem. Nexus payments require each connected IPS operator to adapt domestic or cross-border components. Operators must also maintain reference data, register PSP capabilities, support prescribed message flows, meet scheme timing requirements, and manage participant readiness through local rulebook addenda or cross-border agreements.

ISO 20022 helps, but it does not eliminate implementation variance. Nexus therefore matters because it publishes specific message and API specifications, not just a broad standards preference. For participant banks and IPS operators, the readiness work is practical. It includes mapping domestic message profiles to Nexus requirements, supporting verification and status messages, maintaining high-quality reference data, and testing exceptions, rejects, returns, and future-use messages before production volumes arrive.

Settlement certainty is the hard part behind the user experience. Nexus documentation frames a cross-border payment as two domestic instant payments linked by the scheme, with FX providers and settlement access providers playing explicit roles. That means readiness is not only about message translation. It is about liquidity, pre-funding or settlement-access arrangements, FX quote validity, reject handling, participant reachability, and assurance that the beneficiary receives final funds within the scheme’s timing expectations.

Compliance is equally operational. Nexus can standardise connectivity, but it cannot erase jurisdictional AML/CFT, sanctions, fraud, consumer-protection, data-residency, and dispute-resolution obligations. The practical question for each IPS operator and participant bank is whether those controls can run inside an instant-payment operating window without turning every exception into a manual corridor-specific process.

The integration demands of a multilateral hub are not simply domestic IPS demands at scale. They are a different operating discipline. This is where Montran’s adjacent experience is relevant if stated precisely: TIPS, RT1 and national IPS connectivity in Europe; central and participant-side instant payment deployments; and PAPSS-style cross-border readiness in Africa all involve the same underlying disciplines of certification, scheme adaptation, liquidity-aware operations, participant onboarding, and 24/7 support.

The Operator Mandate and What It Means for the Industry

In February 2026, Nexus Global Payments appointed a PayNet-NETS joint venture as the Nexus Technical Operator, with AWS and Endava supporting technical design and development. The appointment followed a competitive procurement process and marked the transition from scheme design to platform build. Public NGP materials state that technical development was scheduled to begin in early 2026 and that go-live is targeted for 2027.

The NTO mandate is broader than platform build. NGP describes responsibility for building, operating, and maintaining Nexus infrastructure. It also includes meeting global standards, supporting cybersecurity and operational resilience, and coordinating onboarding for entities that manage domestic instant payment schemes. For connected IPS operators, that means the critical path is not only the central Nexus platform. It is the readiness of each domestic scheme, participant bank, PSP, FX provider, settlement-access provider, certification process, and operating desk that will touch the transaction.

Compliance and scheme governance sit with the Nexus Scheme Organisation, but the NTO must support those obligations operationally — meaning the platform has to accommodate the rules and requirements of every participating jurisdiction from day one.

For infrastructure providers and participant banks, the lesson is immediate. Nexus will not remove the need for domestic readiness; it will expose it. Banks still need core and channel integration, sanctions and fraud controls, customer notifications, exception workflows, liquidity monitoring, reconciliation, operational dashboards, and certification evidence. IPS operators still need participant onboarding, scheme-rule enforcement, reference-data quality, uptime discipline, and business continuity.

The success of Nexus is in the broader payments industry’s interest. Multilateral cross-border instant payments will not be solved by a single vendor or a single central platform. It will depend on how quickly the ecosystem around each IPS can become certifiable, observable, compliant, liquid, and operationally resilient.

Strategic Imperatives

1. Treat domestic IPS rails as connection-ready, not connection-complete. Nexus readiness requires message mapping, API integration, reference-data discipline, participant capability registration, exception handling, certification, and rulebook alignment – not only a domestic real-time rail.
2. Plan for 24/7 operating posture, not only 24/7 availability. Cross-border IPS operations require monitoring across schemes that do not share telemetry, playbooks for rejects and exceptions, fraud and sanctions escalation inside tight timelines, and continuity arrangements that can withstand asymmetric incidents.
3. Build for the ecosystem the operator appointment has unlocked. With the NTO selected and 2027 go-live targeted, the bottleneck moves toward domestic scheme adaptation, PSP and bank readiness, FX/liquidity arrangements, settlement-access models, and operational certification. The network grows or stalls based on ecosystem mobilisation, not announcement momentum.

The bottom line: The architectural shift is underway. Operating maturity will determine the pace.

Reach Out To Learn More Here.