Moving money across borders is still slow and expensive. Central Bank Digital Currency, or CBDC, tries to fix this. Think of it as digital cash issued by a country's central bank, designed to work smoothly with other digital currencies around the world.
Instead of routing payments through many banks, CBDC systems aim for direct connections. The goal is to make sending money as easy as sending a text message.
CBDC cross-border projects target three big wins: lower fees, faster settlement, and wider access.
They replace old correspondent banking chains with shared platforms or direct links.
| Problem Area | Traditional System | CBDC Promise |
|---|---|---|
| Speed | Takes 2-5 business days | Near-instant, 24/7 settlement |
| Cost | Average 6.3% fee per transfer | Target below 1% in total fees |
| Transparency | Hidden fees, unclear routing | Full fee breakdown upfront |
| Access | Requires bank accounts | Potential for wallet-based access |
| Middlemen | Multiple correspondent banks | Direct central bank links |
To fix these problems, central banks are testing different designs. The big question is whether they build a shared network, or simply connect their own domestic systems.
Imagine sending $100 from France to a friend in Singapore. Today, the money might pass through three different banks before arriving, and $6 disappears in fees.
With a shared CBDC platform, the central bank of France and the central bank of Singapore could settle the transfer directly in seconds, and your friend gets nearly the full $100.
Major Wholesale CBDC Interoperability Projects
Central banks started with wholesale projects—tests between institutions, not everyday people. Four major projects are leading the way, each trying a different technical approach.
Project mBridge is the largest and most watched. It connects China, Thailand, Hong Kong, and the UAE on a single shared ledger.
| Project Name | Participants | Technical Model | Status (Early 2026) |
|---|---|---|---|
| mBridge | China, Thailand, Hong Kong, UAE, Saudi Arabia | Shared single ledger (mBridge Ledger) | MVP launched, real-value transactions started |
| Project Icebreaker | Israel, Norway, Sweden (BIS hub) | Hub-and-spoke with retail focus | Completed proof of concept |
| Project Jura | France, Switzerland | Sub-networks on a single platform | Completed experiment |
| Project Dunbar | Australia, Singapore, Malaysia, South Africa | Shared multi-CBDC platform | Completed prototype, lessons published |
| Project Mariana | France, Singapore, Switzerland | Automated market makers for FX | Completed proof of concept |
mBridge proves that direct central bank money can move in real time. But it also raises big questions about governance.
Think of mBridge like a group chat where four countries share one ledger. If one country adds a new payment rule, all four must agree.
That is hard. And in Project Dunbar, the designers learned that a shared platform works technically, but getting banks to agree on legal rules was the real challenge.
Shared ledger models (like mBridge) pool liquidity and speed, but need strong shared governance.
Interlinked domestic systems keep each country in control, but can be slower to build and connect.
Technical Models for Making CBDCs Talk to Each Other
There are three main ways to connect CBDC systems. Each has different trade-offs between control, speed, and complexity.
The BIS calls these models compatible, interlinked, and single system. Here's how they stack up in practice.
| Model Type | How It Works | Speed | Complexity | Example |
|---|---|---|---|---|
| Compatible | Each country keeps its own system; common standards allow basic exchange | Medium | High (needs massive coordination) | Early SWIFT-style linking |
| Interlinked | Shared technical interfaces, but separate ledgers with a bridge | Fast | Medium | Project Icebreaker |
| Single System | One shared ledger for all participants; smart contracts handle rules | Fastest | Highest (governance, privacy) | mBridge (shared ledger) |
The single system model is tempting because it cuts out all the middle layers. But sharing one ledger means sharing control, and no central bank wants to lose its monetary independence.
It is like choosing between a house with roommates and your own apartment. The shared house (single system) is cheaper and more social.
But you have to follow house rules. Your own apartment (compatible model) costs more to connect to utilities, but you make all the decisions.
Retail CBDC Cross-Border Challenges
Wholesale CBDC is for banks. Retail CBDC is for people like you and me. Making retail CBDCs work across borders is much harder.
If a traveler wants to use their digital euro in Thailand, the systems must handle currency exchange, identity checks, and privacy rules all at once.
| Factor | Wholesale CBDC | Retail CBDC |
|---|---|---|
| User Base | Limited to banks and institutions | General public, millions of users |
| Transaction Volume | Fewer, high-value transactions | Massive, low-value daily payments |
| Primary Risk | Settlement finality, liquidity | Privacy, fraud, data leakage |
| Identity (ID) Rules | Clear institutional KYC (Know Your Customer) | Varies wildly by country; tourist vs citizen rights |
| Offline Capability | Rarely needed | Often required for inclusion |
Tourist payments remain the classic test case. A person from the euro area visiting Singapore wants to pay with digital euros, but the merchant wants Singapore dollars instantly.
You are at a Singapore hawker stall, hungry for chicken rice. You tap your phone with a digital euro wallet.
The system must check your identity, convert EUR to SGD at a fair rate, settle the payment into the merchant's account, and keep your personal data safe. All in under two seconds.
Retail cross-border CBDC needs real-time FX conversion, privacy-preserving identity, and offline fallbacks.
No single project has fully solved all three yet, but Project Icebreaker came closest.
Governance, Privacy, and the Rules of the Road
Even if the tech works, people will not use CBDCs if they do not trust them. Two issues stand out: who governs the shared system, and who can see your transactions?
In a shared ledger like mBridge, all participant central banks can potentially observe cross-border flows. This creates tension between transparency for regulators and privacy for users.
| Issue | Current Challenge | Possible Solution |
|---|---|---|
| Data Visibility | Which central bank sees what data? | Privacy-enhancing tech, zero-knowledge proofs |
| Dispute Resolution | Which country's law applies to a failed payment? | Pre-agreed rulebooks and smart contract escrow |
| Access Rights | Who gets to use the system? Only licensed banks? | Tiered access: full for banks, limited for fintechs |
| FX Rate Setting | Who provides the exchange rate? Market or central bank? | Automated market makers pulling from live forex feeds |
| Exit and Interruption | What if a country leaves the shared system abruptly? | Clear wind-down procedures in smart contracts |
These are not just tech problems. They are legal and political problems that need treaties and agreements. Until these rules are clear, many central banks will stay in experiment mode.
A payment from Bank A to Bank B fails because of a software bug at midnight. Who pays for the lost interest during the six hours it took to fix?
Without a shared rulebook, the banks might argue for months. With smart contracts and pre-agreed rules, a small penalty fee could be paid automatically, and everyone moves on.
Key Takeaways
| Key Point | What It Means | Action Item |
|---|---|---|
| mBridge is the frontrunner | A shared ledger with real money is already live in Asia | Watch mBridge expansion; test small cross-border remittance use cases |
| Three technical models exist | Choice between compatible, interlinked, or single system shapes speed and control | Evaluate which model fits your country's legal and monetary policy |
| Retail CBDC is much harder | Millions of users, strong privacy needs, and offline payments create huge complexity | Study Project Icebreaker results for retail cross-border design patterns |
| Governance is the real bottleneck | Tech works; legal harmonization and shared rulebooks are still missing | Draft bilateral or multilateral agreements on data, disputes, and FX rules |
| Privacy tech is advancing fast | Zero-knowledge proofs can hide transaction details while proving compliance | Invest in privacy R&D; pilot with privacy-preserving cross-border prototypes |