CBDC Interoperability

What specific challenges do the three layers of CBDC interoperability each face? Why is 'technical interoperability' easiest to solve while 'regulatory interoperability' is hardest?

Technical layer (difficulty: medium): different countries' CBDCs may be built on different underlying technologies (China's e-CNY uses centralized ledger; European Digital Euro may use distributed ledger; others may use third-party blockchains). Making these systems communicate requires cross-chain bridging technology or unified intermediate protocol. Technically feasible — mature solutions like cross-chain bridges and Hashed Timelock Contracts (HTLC) exist. Project mBridge's mBridge Ledger is a technical interoperability solution. Difficulty: getting countries to accept using a common technical platform (may trigger data sovereignty and backdoor concerns).

Legal layer (difficulty: high): if Taiwan's CBDC is to be used in Germany, needs resolving: does German law recognize Taiwan's central bank-issued digital currency as legal payment instrument? If disputes arise during settlement (like exchange rate disputes), which country's law applies? These require bilateral or multilateral treaties — complex diplomatic and legal negotiation processes.

Regulatory layer (difficulty: highest): each country's AML and KYC standards differ. If the US wants to accept a Saudi Arabian CBDC user, must confirm their KYC verification level meets US requirements (or has treaty exemptions). This involves mutual recognition of sovereign regulatory standards — one of the most difficult coordination problems in international financial regulation. Different countries have fundamentally different rules for 'suspicious transaction reporting obligations' and 'enforcement of sanction lists.'

Compared to DeFi's 'composability' concept, what are CBDC interoperability's similarities and differences?

Surface similarities: both are about the ability of 'different systems to mutually communicate and operate.' DeFi composability allows different protocols to stack on each other like blocks; CBDC interoperability allows different countries' digital currencies to mutually convert. Both pursue 'seamless integration' user experiences.

Fundamental difference 1: sovereignty vs openness. DeFi composability is built on 'open protocols where anyone can build' — Uniswap doesn't need Aave's permission to integrate Aave's protocol, and vice versa. CBDC interoperability is fundamentally 'negotiation between sovereign systems' — Taiwan's central bank CBDC interoperating with European Central Bank's CBDC requires formal intergovernmental agreements, not free technical connection.

Fundamental difference 2: immutable vs revocable. DeFi composability, once established (through smart contracts), is automatically executing and irrevocable (unless contracts have upgrade functions). CBDC interoperability can be terminated at any time by either government — if US-China relations worsen, the US could sever interoperability with China's e-CNY. This makes CBDC interoperability fundamentally political rather than purely technical.

Practical insight for users: DeFi composability allows users to permissionlessly interact USDC with any protocol. CBDC interoperability requires waiting for intergovernmental agreements to be reached, and may be interrupted by geopolitical changes. This is the fundamental difference in 'stability and openness' between the two systems.

If CBDC interoperability becomes widespread, what long-term impact does it have on the existing cross-border payment industry (like SWIFT, Western Union, Wise)?

SWIFT's potential impact: SWIFT's core business is interbank messaging — if CBDC interoperability allows central banks to directly settle peer-to-peer, SWIFT's 'message intermediary' role would be marginalized. But SWIFT has also actively begun positioning in CBDCs — conducting multiple CBDC integration tests in 2022-2024, exploring its role as a 'CBDC connection layer.' SWIFT may transform from 'messaging network' to 'standardized bridging protocol provider across CBDCs.'

Impact on Western Union and similar remittance services: Western Union's core business is 'allowing people without bank accounts to remit cross-border,' serving emerging market personal remittances. If widespread retail CBDC interoperability is achieved, allowing people without traditional accounts to hold CBDCs for cross-border transfers, Western Union's business model faces fundamental disruption. But this scenario is unlikely within 3-5 years (CBDC adoption rates are still low; retail interoperability is harder).

Role of Wise, Revolut, and similar fintechs: these companies are already actively integrating multiple payment channels (including crypto stablecoins). If CBDC interoperability becomes widespread, their most likely transformation is becoming 'CBDC aggregators' — helping users convert one country's CBDC to another's, bearing compliance, user experience, and exchange rate optimization roles. They're more flexible than SWIFT, more technical than Western Union — potentially better adapted to the CBDC era.

Conclusion: widespread CBDC interoperability would compress intermediary profit margins but won't immediately eliminate the cross-border payment industry. Needs for user experience, compliance services, exchange rate management still exist — only the implementation methods will change.

How do BIS's interoperability frameworks (like Nexus, Unified Ledger) differ from mBridge? What scenarios does each suit?

mBridge: multilateral wholesale CBDC platform allowing participating countries' central bank CBDCs to directly exchange on the mBridge Ledger. Design focus: speed (T+0), cost (near zero), suitable for large enterprise trade finance. Participants: China, Hong Kong, Thailand, UAE (expanding to more countries in 2026). Limitation: requires each country's central bank to 'deploy' its CBDC on the mBridge platform, raising data sovereignty and control concerns; only suitable for transactions between participants, not a universal solution.

BIS Nexus: Nexus is a different BIS direction — instead of creating a new common platform, building 'standardized connection protocols' between existing instant payment systems (like Singapore's PayNow, Europe's SEPA), allowing them to mutually transmit instructions and complete settlement. Nexus's advantage: countries don't need to abandon existing systems — just need a 'translation layer' added to current systems. Singapore, India, Malaysia, and other countries' fast payment systems have already participated in testing.

BIS Unified Ledger: a more ambitious BIS concept proposed in 2023 — putting central bank money, commercial bank deposits, and tokenized assets all on one unified programmable platform, allowing smart contracts to conduct complex atomic settlement across these three asset types. This concept is currently in research phase; if realized, would be a fundamental rebuild of monetary infrastructure.

Applicable scenarios: mBridge suits short-to-medium term large cross-border trade settlement (especially between participating countries); Nexus suits cross-border retail payments for individuals and small businesses (broader geographic coverage, lower cost); Unified Ledger is a long-term vision, not in near-term deployment discussion scope.