Project Nexus and the AI-Ready Infrastructure Imperative
What Is Project Nexus?
Project Nexus is a BIS Innovation Hub initiative to connect domestic instant payment systems (IPS) globally through a single multilateral hub. Rather than each IPS operator building bespoke bilateral connections to every new country — each requiring its own legal, FX, compliance, and operational framework — an operator connects once to Nexus and reaches all other participating networks.
Conceived in 2021 and progressing through four phases of development, Nexus completed a comprehensive blueprint in July 2024. In March 2025, the five founding central banks — Bank Negara Malaysia, Bank of Thailand, Bangko Sentral ng Pilipinas, the Monetary Authority of Singapore, and the Reserve Bank of India — incorporated Nexus Global Payments (NGP) as the scheme's not-for-profit governing organisation, registered in Singapore.
The five founding payment systems are India's UPI, Malaysia's DuitNow, the Philippines' InstaPay, Singapore's PayNow / FAST, and Thailand's PromptPay. Bank Indonesia and the European Central Bank (Eurosystem/TIPS) are special observers. In a significant signal of global intent, NGP has also signed a Memorandum of Understanding with FLAR — the Latin American Reserve Fund — to explore future connectivity with Latin American countries.
The Bilateral Ceiling: Why Corridors Alone Cannot Scale
ASEAN has proven that bilateral IPS connectivity works. The PayNow-PromptPay linkage cut Singapore-Thailand transfer times from days to seconds and reduced costs dramatically. As of mid-2024, the region had established 13 person-to-merchant QR linkages and four person-to-person payment links.
But each of these connections is bespoke. Every new bilateral corridor requires tailored agreement on scheme rules, participant reachability, FX handling, compliance responsibilities, operating hours, dispute handling, and data-sharing boundaries. As the number of countries grows, the number of required bilateral connections scales as n×(n-1) — exponential complexity with every addition.
The IMF's 2026 analysis of ASEAN digital payment integration identifies cross-border payments as a driver of local-currency usage and regional economic integration, while highlighting interoperability, operational risk, cyber risk, and policy-coordination challenges as the primary constraints on scale. Nexus is designed precisely to resolve the structural, not just technical, constraints.
The Architecture: How Nexus Actually Works
Nexus standardises the connection layer between domestic IPS. Each operator connects once via published API specifications and ISO 20022 message profiles, gaining the ability to originate and receive payments to and from all other connected systems.
A Nexus payment is technically structured as two domestic instant payments linked by the scheme — one in the sending country, one in the receiving country — bridged by the Nexus hub. This seemingly simple architecture creates a specific set of roles and responsibilities:
What Readiness Actually Demands: A Bank-Level View
This is where most analysis stops short. The Nexus platform will be built. The question for participant banks and IPS operators is whether their internal infrastructure can meet the certification requirements before 2027 — and sustain the operational demands after go-live.
Message and Data Readiness
Domestic message profiles must be mapped to Nexus-specific ISO 20022 requirements. This is not a one-time translation task — it encompasses verification messages, status messages, exceptions, rejects, returns, and a class of "future-use" messages for which frameworks must exist before production traffic arrives. The November 2026 ISO 20022 CBPR+ deadline (which removes MT message coexistence in SWIFT cross-border flows) creates a converging pressure point: banks facing both SWIFT's native MX mandate and Nexus certification simultaneously.
Settlement and Liquidity
Settlement certainty is the hardest part of the user experience. A Nexus payment commits to completing within 60 seconds. That commitment is only as strong as the liquidity and pre-funding arrangements behind it. Banks and settlement-access providers must maintain continuous liquidity positions across time zones, with playbooks for FX quote expiry, payment failure, and beneficiary unreachability — all within the scheme's timing window.
Compliance: The Unsolvable Problem with Legacy Systems
Nexus can standardise connectivity. It cannot standardise jurisdiction. Every participating country brings its own AML/CFT obligations, sanctions lists, consumer protection rules, data residency requirements, and dispute resolution frameworks. A Nexus payment crossing three jurisdictions must satisfy all three compliance regimes simultaneously — in under 60 seconds.
Operational Posture: 24/7 Is Not Enough
Nexus will operate continuously. But 24/7 availability and 24/7 operational maturity are different things. Participant banks need cross-scheme monitoring (different IPS do not share telemetry), structured playbooks for reject and exception handling, fraud and sanctions escalation paths that fit inside tight timelines, and business continuity arrangements that can absorb asymmetric incidents — such as a domestic IPS outage in one jurisdiction while inbound payments from others continue.
Why Artificial Intelligence Is Not Optional in a Nexus World
The infrastructure and compliance demands described above share one characteristic: they require decisions to be made at machine speed, at machine scale, across machine-quantity data — while remaining defensible to human regulators. That is the definition of an AI problem.
Real-Time Compliance Decisioning
Compliance teams operating with legacy rule-based systems face an impossible equation: more transaction volume, higher transaction values, tighter decisioning windows, more jurisdictions, and regulators who have explicitly stated that faster payments do not reduce AML and sanctions obligations. AI-native systems — with sub-second API response times, context-aware semantic screening, and explainable audit trails — are the only architecture that resolves this equation without sacrificing accuracy or customer experience.
Fraud Pattern Detection Across Borders
Cross-border fraud patterns are structurally different from domestic ones. Authorised push payment (APP) fraud, layering across multiple IPS, and sanctions evasion using multi-hop routing all exploit the seams between national compliance frameworks. Machine learning models trained on cross-border transaction behaviour can identify these patterns in real time; static rules cannot. The transition from retrospective transaction monitoring to predictive, lifecycle-based risk management is not a preference — it is the operational requirement of a multilateral instant payment scheme.
FX and Liquidity Intelligence
FX providers and settlement-access providers in the Nexus model must maintain rate validity and liquidity positions across multiple currencies simultaneously. AI-assisted liquidity forecasting — using transaction intent signals embedded in ISO 20022 structured data — enables institutions to anticipate positions before they materialise, reducing the cost and risk of pre-funding arrangements.
Data as the Network Effect
ISO 20022's structured data fields — purpose codes, remittance information, counterparty identifiers — represent a step-change in the quality of information accompanying each payment. Organisations that invest in AI infrastructure to extract, normalise, and act on this data in real time will operate at a fundamentally different level of efficiency and insight from those treating it as a compliance overhead. The payments industry has talked about "payments as a data service" for a decade. Nexus, combined with mature AI infrastructure, is the first architecture that makes that phrase operationally true.
The Nexus Readiness Checklist for Participant Banks
Based on published Nexus scheme documentation, ISO 20022 implementation guides, and operational requirements from comparable multilateral payment networks, the following areas represent the minimum readiness scope for participant banks preparing for Nexus certification:
Technical Integration
-
Map domestic message profiles to Nexus-specific ISO 20022 schemas (pacs.008, pacs.002, camt.056, and future-use classes)
-
Implement Nexus API specifications for payment initiation, status queries, and exception flows
-
Validate end-to-end message flows including verification, confirmation, rejection, and return scenarios
-
Test structured address and identifier fields under CBPR+ SR2026 rules (effective November 2026)
Compliance Infrastructure
-
Deploy real-time sanctions screening capable of operating within Nexus payment timing requirements
-
Implement AI-assisted AML transaction monitoring with cross-border pattern libraries
-
Establish unified fraud and AML workflow to eliminate siloed team structures
-
Build explainable risk-scoring architecture that produces audit-ready reports per-decision
-
Configure jurisdiction-specific rule sets for each corridor (AML, CFT, data residency, consumer protection)
Liquidity and Settlement
-
Establish FX provider relationships and define quote-validity protocols
-
Configure pre-funding or settlement-access arrangements with designated providers
-
Implement intraday liquidity monitoring with 24/7 visibility across all active corridors
-
Define playbooks for FX expiry, payment failure, and beneficiary unreachability within scheme timing
Operational Maturity
-
Deploy cross-scheme monitoring dashboards (not reliant on individual IPS telemetry)
-
Maintain exception and reject playbooks for each participating corridor
-
Document and test business continuity scenarios including partial-network incidents
-
Complete Nexus technical certification process and rulebook compliance documentation
-
Train operations, compliance, and customer service teams on Nexus-specific flows
Frequently Asked Questions
What is Project Nexus in simple terms?
Project Nexus is a BIS Innovation Hub project that connects domestic instant payment systems — like India's UPI, Singapore's PayNow, and Thailand's PromptPay — through a single shared hub. Instead of each country needing a separate connection to every other country, all participants connect once to Nexus and can instantly reach all others. The goal is to make cross-border payments as fast and cheap as sending a text message, targeting a 2027 go-live.
Who owns and operates Project Nexus?
Nexus Global Payments (NGP) is the not-for-profit organisation incorporated in Singapore in March 2025 that governs the Nexus scheme. The Nexus Technical Operator (NTO) is a joint venture between PayNet (Malaysia) and NETS (Singapore), supported by Amazon Web Services and Endava. The BIS Innovation Hub plays a technical advisory role but does not own or operate any part of NGP.
How does Nexus handle compliance across different countries?
Nexus standardises the technical connectivity and scheme rules but does not override national compliance requirements. Each participating IPS operator and participant bank remains responsible for satisfying its own jurisdiction's AML, CFT, sanctions, consumer protection, and data residency obligations. In practice, this means compliance controls must operate in real time within each payment's processing window, which requires AI-driven screening tools rather than traditional batch-mode compliance systems.
Will Project Nexus expand beyond ASEAN and India?
Yes. The European Central Bank confirmed its Governing Council's decision to continue feasibility work on connecting the Eurosystem's TIPS to Nexus. NGP has also signed an MOU with FLAR (Latin American Reserve Fund) to explore connectivity with Latin American countries. The ECB's eventual participation alone would add over 450 million people to the reachable network. Nexus is designed from the outset to be globally extensible — any country with a domestic instant payment system can apply to connect.
What is the difference between Nexus and SWIFT GPI?
SWIFT GPI enhances the existing correspondent banking model — improving transparency, speed, and traceability within a network that still relies on intermediary banks and nostro/vostro accounts. Nexus is a fundamentally different architecture: it connects domestic instant payment systems directly, removing the need for correspondent banking relationships in Nexus-connected corridors. Nexus payments are designed to complete in under 60 seconds using existing domestic rails; SWIFT GPI payments remain subject to correspondent bank processing and typically settle in hours.