1. Systemic Friction in Correspondent Banking and CBDC Foundations

Cross-border payments use several arrangements, including correspondent banking and links between domestic payment systems. SWIFT primarily carries financial messages; it is not itself a ledger that executes every settlement. Processing time, fees, and FX costs vary by currency, route, intermediary, and operating hours, so one average delay should not be applied to every transfer. A cross-border CBDC requires choices beyond domestic issuance, including foreign access, system connections, and legal finality.

2. Architectural Bifurcation: Retail vs Wholesale CBDC Paradigms

Central bank digital currency frameworks structurally bifurcate into retail and wholesale architectures. Retail CBDC serves as a direct digital liability of the central bank accessible to general households and commercial merchants, functioning as an electronic complement to physical legal-tender banknotes. To mitigate commercial banking disintermediation, retail designs vary: some use intermediaries for customer-facing services, while other arrangements are possible. Design choices can affect access and bank intermediation. In the report’s definition, wholesale CBDC is digital central bank money held by eligible financial institutions for financial-market payments. Eligibility and operating arrangements depend on the jurisdiction and design. DLT is one possible technology, not a universal requirement of wholesale CBDC. Specific designs or experiments may test PvP or DvP settlement; legal and technical arrangements determine finality.

3. Multi-CBDC connections: design choices and limits

The joint BIS-CPMI, BIS Innovation Hub, IMF, and World Bank report, “Options for access to and interoperability of CBDCs for cross-border payments,” analyzes access/interlinking choices and describes distinct projects. For example, its annex describes Project Jura, a specific experiment involving French and Swiss financial institutions, EUR and CHF wholesale CBDCs, and tokenised assets. The report documents design options and pilot boundaries; it does not show that all CBDCs use one shared ledger or eliminate intermediaries, prefunding, or legal settlement risk. Eligibility, FX liquidity, failure handling, and finality still need case-specific analysis.

4. What the policy sources establish

The joint BIS-CPMI-IMF-World Bank report analyzes options for cross-border CBDC access and interoperability. The CPMI’s 2026 ISO 20022 update concerns message-data consistency for existing cross-border payments and does not mandate CBDC adoption. These are policy and standardization discussions, not proof that a particular payment effect has occurred.

Use a hypothetical payment to compare interoperability choices

Suppose a company in Country A wants to pay a supplier in Country B the equivalent of $1,000. Decide whether a foreign bank can participate directly, whether CBDC connects to an existing rail, or whether central banks would govern a shared platform. Then specify the FX provider, whether both currencies move together (PvP), fees and FX liquidity, cross-border data access, failure recovery, and legal finality. The BIS/CPMI report describes different efficiency, resilience, inclusion, and implementation trade-offs, with no single best arrangement. This is a hypothetical, not a real transaction result.

Existing-rail improvements are alternatives. The CPMI’s 2026 ISO 20022 update encourages consistent payment-message data; it is not a regulation or CBDC mandate. PvP can reduce FX settlement risk but is not available for every currency or participant.

Sources and References: