CBDC Interoperability Explained: Connecting Banks, Wallets, and Blockchains

CBDC interoperability is the ability of central bank digital currency systems to work with banks, retail wallets, payment networks, and blockchain platforms without trapping value in isolated systems. That sounds simple. It is not. The hard part is making legal finality, identity, compliance, liquidity, and data standards line up across systems built by different central banks, vendors, and market participants.

The topic has moved from policy papers to live pilots. The BIS, IMF, World Economic Forum, SWIFT, HKMA, and several central banks are now testing how CBDCs can connect to RTGS systems, fast payment rails, FX markets, and tokenized assets. If you work in payments, digital assets, banking technology, or blockchain infrastructure, CBDC interoperability is a core design question now, not a side topic.

What CBDC Interoperability Means

CBDC interoperability means that one CBDC system can communicate, transact, and settle with another system. That other system may be a domestic payment rail, a commercial bank ledger, a retail wallet, a foreign CBDC platform, or a blockchain-based securities network.

In practice, it covers four layers:

• Domestic payment integration: CBDCs connect with RTGS, instant payment systems, card rails, and bank account infrastructure.
• Cross-border CBDC links: Multiple central bank digital currencies support payment versus payment, also called PvP, for FX settlement.
• Bank and wallet access: Commercial banks, payment service providers, and wallet operators use shared standards for identity, messaging, security, and compliance.
• Blockchain and tokenized asset settlement: CBDCs support delivery versus payment, or DvP, for securities, tokenized deposits, trade finance, and other digital assets.

The BIS has argued that CBDCs without interoperability could create new digital islands. That is the right warning. A retail CBDC wallet that cannot pay into existing bank and merchant systems is just another closed-loop app. A wholesale CBDC that cannot settle FX or securities against external systems is a narrow settlement tool, not market infrastructure.

Why Banks, Wallets, and Blockchains Need Interoperability

Banks need settlement access and liquidity control

Banks care about final settlement, liquidity, balance sheet treatment, and operational risk. In a wholesale CBDC model, banks may connect as direct participants through nodes, APIs, or regulated gateways. They need to move value between central bank money, commercial bank money, FX positions, and securities accounts.

One practical detail gets missed in high-level diagrams: the message mapping is often where projects stall. In ISO 20022 payment flows, a pacs.009 financial institution credit transfer carries different data expectations than a pacs.008 customer credit transfer. If a CBDC gateway maps the wrong party identifier, or drops a UETR used for payment tracking, reconciliation can fail even though the ledger transaction technically settled. That is not theoretical plumbing. It is the boring, costly part of payment integration.

Wallets need shared identity and payment rules

Retail wallets need common standards for onboarding, identity verification, fraud controls, device security, and transaction messaging. The BIS 2024 survey found that 56 percent of advanced economies and 79 percent of emerging market and developing economies considering retail CBDCs expect them to be interoperable with domestic payment systems.

That matters for adoption. Users should not need to know whether a merchant accepts CBDC, instant payment, or card settlement in the background. The wallet should route the payment, apply compliance checks, and confirm settlement in a format both sides understand.

Blockchains need atomic settlement

Blockchain-based asset markets need trusted cash legs. Tokenized bonds, fund units, invoices, carbon credits, and collateral transfers all need settlement assets that can move with legal finality. CBDCs could provide that cash leg, especially in wholesale markets.

The key mechanism is atomic settlement: both sides of a transaction happen together, or neither happens. For securities, that is DvP. For currency exchange, that is PvP. Smart contracts can coordinate the workflow, but governance and legal finality still come from regulated institutions.

The Three Main Models of CBDC Interoperability

The BIS and IMF often describe three broad models for multi-CBDC interoperability. You will see these models in most serious CBDC architecture discussions.

1. Compatibility model

CBDC systems remain separate, but they use compatible standards. Think shared messaging formats, similar identification schemes, aligned compliance data, and coordinated operating rules.

This is the lowest-disruption model. It fits jurisdictions that want autonomy and limited technical dependency. The trade-off is clear: payments may still pass through multiple intermediaries, so speed and cost gains can be modest.

2. Interlinking model

Separate systems connect through technical interfaces, gateways, or a common clearing mechanism. SWIFT has tested this approach through CBDC sandbox work that linked CBDC networks built on different distributed ledger technologies, including Corda and Quorum, as well as existing RTGS systems.

This model is practical because it does not force every central bank onto one platform. It also fits the real world, where old payment systems rarely disappear quickly. The downside is connector complexity. Gateways must handle message conversion, identity mapping, compliance checks, routing, and settlement status across multiple networks.

3. Single platform model

Multiple CBDCs operate on one shared platform, usually with separate governance rules for each currency. BIS Innovation Hub projects such as mBridge, Dunbar, and Jura have tested this model for wholesale CBDCs.

mBridge is the best-known example. It involves the central banks of Hong Kong SAR, Mainland China, Thailand, and the United Arab Emirates. In a 2022 pilot, 20 commercial banks executed payment and FX PvP transactions for corporate clients using CBDCs issued on the platform. HKMA reported that the trial reduced cross-border payment times from several days to near real time and lowered costs.

This model can deliver strong efficiency gains. It is also politically and legally harder, because shared governance, access rules, data visibility, and dispute processes must be agreed upfront.

Real Use Cases Already Being Tested

CBDC interoperability is not only about sending money from one wallet to another. The higher-value use cases sit in institutional finance and cross-border commerce.

• International trade settlement: CBDCs can settle invoices, trade documents, and letters of credit with fewer correspondent banking steps.
• FX payment versus payment: Two currencies settle at the same time, reducing Herstatt risk.
• Tokenized bond issuance: A bond token and CBDC payment can exchange atomically across borders.
• Digital trade workflows: SWIFT sandbox phase 2 tested digital trade, FX settlement, DvP for securities, and a liquidity saving mechanism.
• Insurance and wealth product settlement: mBridge participants identified cross-boundary insurance payments and wealth management settlement as possible use cases.
• Tokenized institutional cash: Cambridge Centre for Alternative Finance has discussed Fnality, a UK regulated payment operator using an omnibus account at the Bank of England to support tokenized PvP and DvP settlement.

To be blunt, wholesale CBDC interoperability will likely mature before broad retail cross-border CBDC use. The user group is smaller, compliance controls are clearer, and the economic case is stronger in FX, securities, and trade settlement.

Standards That Make CBDC Interoperability Work

Interoperability depends on standards. Not slogans. Actual standards and rulebooks.

• ISO 20022: Used for structured financial messaging across payment systems.
• BIC and LEI identifiers: Help identify financial institutions and legal entities.
• Common identity frameworks: Needed for wallet access, AML/CFT screening, sanctions controls, and transaction limits.
• APIs and gateways: Connect CBDC platforms with RTGS systems, fast payment systems, bank ledgers, and blockchain networks.
• Legal finality rules: Define when settlement is irrevocable and enforceable.

The World Economic Forum has emphasized that CBDC interoperability is institutional as much as technical. That view is correct. A gateway can translate a message, but it cannot solve a conflict between capital controls, data localization laws, or different definitions of settlement finality.

Risks and Design Trade-Offs

Interoperability brings efficiency, but it also concentrates operational and governance risk. You should watch five problem areas.

1. Cyber and operational resilience: A shared platform or major gateway can become critical infrastructure.
2. Data privacy: Cross-border CBDC flows may expose sensitive payment and identity data.
3. Monetary sovereignty: Retail cross-border CBDCs can raise concerns about currency substitution.
4. Compliance fragmentation: AML/CFT, sanctions, and capital controls vary across jurisdictions.
5. Liquidity management: Faster settlement can increase intraday liquidity pressure if not designed with liquidity saving tools.

There is no perfect architecture. Compatibility protects autonomy but gives fewer gains. Interlinking is realistic but complex. A single platform is powerful but hard to govern. Pick the model based on the policy goal, not the technology fashion.

What Comes Next for CBDC Interoperability

The direction is clear. Wholesale multi-CBDC platforms will keep advancing. Domestic CBDC designs will increasingly connect to instant payment systems and bank infrastructure. Interoperability gateways will become a specialized market, with one study by Stratistics MRC estimating growth from about 2.2 billion US dollars in 2025 to 14.8 billion US dollars by 2032.

Integration with tokenized assets is the area to watch. If CBDCs can settle tokenized bonds, FX trades, and trade finance obligations with finality, they become part of a broader digital market structure. If they cannot interoperate, they risk becoming isolated central bank databases with limited market impact.

For professionals, the best next step is to build literacy across both payment systems and blockchain architecture. If you are focused on digital assets strategy, explore Blockchain Council resources such as Certified Blockchain Expert™ and Certified Cryptocurrency Expert™. If you build smart contract or tokenization systems, pair that with Certified Blockchain Developer™ or Certified Smart Contract Developer™. CBDC interoperability sits exactly at that intersection: regulated money, programmable assets, and production-grade payment infrastructure.