Caribbean CBDC Progress Shows the Constraint Is Ecosystem Readiness, Not Technical Readiness

Introduction

The debate over central bank digital currency has moved from technical feasibility to ecosystem adoption. The Caribbean makes that shift visible. Sand Dollar, DCash, and Jam-Dex have all shown that launching a retail CBDC is not the same as making it part of daily economic life. The BIS has framed retail CBDCs and fast payment systems as contextual choices that may fulfil different policy goals and complement one another. That distinction matters: IPS moves private money in real time, while CBDC introduces a digital form of public money.

The strategic question for central banks is therefore not which rail should win. It is how CBDC, IPS, RTGS, commercial-bank channels, wallets, and merchant acceptance should work together. A CBDC can be technically sound and legally issued, but still struggle if users cannot load it easily, merchants cannot accept it through familiar channels, and banks do not see a practical business case for distribution and support.

Adoption Data Shows the Ecosystem Constraint (It’s Not a Ledger Problem)

The Kansas City Fed’s review of Caribbean retail CBDCs is the strongest independent evidence for this argument. Sand Dollar, DCash, and Jam-Dex used different technology foundations, but all struggled to achieve expected consumer and merchant adoption. The lesson is not that CBDC technology is impossible. It is that a CBDC platform must be integrated into the wider payments ecosystem that consumers, merchants, banks, and wallet providers already use.

Jamaica is a strong example of that distinction. Wallet registrations rose quickly after launch, helped by incentive programs, but circulation remained small relative to total currency in circulation and merchant adoption stayed difficult. More recent reporting suggests the product itself is functional and transaction values have grown sharply, but scale is still constrained by the practical issue of everyday acceptance. In other words, registration is not the same as habitual usage. The gap between those two is exactly where payment infrastructure matters. The bottleneck is not minting. It is the practical loop of wallet reach, merchant acceptance, bank integration, POS readiness, and repeat use.

CBDC adoption does not fail because digital money is impossible. It stalls when the new instrument is not deeply connected to the systems, merchants, wallets, and institutions that already move money every day.

CBDC and IPS Are Complements, Not Competing Rails

The BIS framework helps clarify why coexistence is the more useful model. IPS solves speed and interoperability for private money moving between banks, payment service providers, and end users. CBDC addresses a different policy objective: a digital form of central bank money that may support inclusion, resilience, programmability, and monetary sovereignty. The two rails can serve different purposes while sharing participant connectivity, settlement logic, directory services, QR standards, fraud controls, and operating rules.

Treating CBDC and IPS as substitutes creates a false choice. A country can modernize instant payments and still want a public digital-money instrument. A country can launch CBDC and still need instant payments, RTGS, ACH, bank channels, merchant rails, and wallet providers to make the national ecosystem function. The strongest architecture is not standalone CBDC; it is CBDC designed to coexist with the commercial rails that already shape user behavior.

Jamaica also shows why back-office integration matters. In 2022, Montran and eCurrency announced the successful integration of Montran’s RTGS with eCurrency’s CBDC platform for the Bank of Jamaica. The integration connects CBDC to central bank currency-management operations, allowing participating institutions to order CBDC and settle issuance and redemption through RTGS. That is a real interoperability proof point. It also makes the adoption lesson sharper: even when the settlement layer is integrated, retail scale still depends on bank participation, wallet reach, POS readiness, and merchant acceptance.

The most effective national architecture is not CBDC instead of IPS, or IPS instead of CBDC. It is CBDC connected to the payment, wallet, merchant, and settlement rails that make digital money usable at scale.

The Strategic Lesson for Central Banks

The lesson from Jamaica and the wider Caribbean is not that CBDCs cannot work. It is that standalone deployments face an ecosystem problem. Merchant acceptance, wallet usability, bank and non-bank participation, POS and QR interoperability, settlement certainty, and integration with existing payment flows all determine whether adoption moves beyond incentives and pilot behavior.

That is why central banks evaluating CBDC should think in layers. RTGS provides settlement finality and currency-management control. IPS and ACH provide commercial reach across institutions. Wallets and merchant rails provide user distribution and acceptance. CBDC extends sovereign money into digital usage. When those layers are designed together, the system becomes coherent and scalable. When they are procured and governed in isolation, CBDC risks becoming a parallel wallet experiment rather than part of everyday payments.

Supporting Context: India, BIS, and Tokenised Money

India offers a useful contrast. RBI’s Digital Rupee FAQs describe e-rupee wallets offered by participating banks and non-banks for P2P and P2M payments, and state that merchant payments can be made by scanning either a CBDC QR code or a UPI QR code. The same FAQs distinguish e-rupee from UPI: e-rupee is digital central bank money and a store of value, while UPI is a payment method; when a UPI QR is scanned from an e-rupee app, settlement follows UPI timelines rather than CBDC wallet-to-wallet settlement.

For Caribbean CBDC programs, the relevant lesson is interoperability and acceptance reuse: CBDC is more likely to scale when it connects to the wallets, merchants, banks, and payment rails users already trust. Public Montran India material states that Montran’s CBDC solution is operational at one of India’s top ten public sector banks, supporting digital wallet management, token lifecycle management, UPI interoperability, and integration with existing bank infrastructure.

BIS Innovation Hub work also keeps the CBDC conversation connected to future tokenised money architecture. Project Aurum explored a two-tier retail CBDC system and a narrow model of CBDC-backed stablecoins where the token is a bank liability backed by assets held at the central bank. Project Agora and the BIS unified-ledger work point toward tokenised central bank money and commercial-bank money as wholesale settlement infrastructure. For this article, the stablecoin point should remain a sidebar: relevant to future architecture, but not the primary adoption lesson from the Caribbean.

Strategic Imperatives

1. Design CBDC and IPS for coexistence. These rails solve different problems and should share ecosystem components where practical: participant connectivity, directory services, QR acceptance, fraud controls, reporting, and settlement integration.
2. Judge success by everyday ecosystem usage, not sign-ups alone. Wallet registrations matter less than active usage, merchant acceptance, circulation depth, POS/QR reach, and repeat transactions.
3. Anchor wholesale CBDC (wCBDC) into proven settlement infrastructure. Interoperability with RTGS, for issuance and redemption operation, and with wider payment rails, gives sovereign digital money a practical operating base rather than leaving it as a standalone wallet experiment.
4. Make merchant acceptance and bank participation explicit design workstreams. Caribbean evidence shows that CBDC adoption depends on wallet providers, POS readiness, bank incentives, merchant economics, and user value propositions, not only central bank issuance.

The bottom line: CBDC and IPS are not rival answers to the same question. CBDC is a form of money. IPS is a movement rail for private money. RTGS is the settlement backbone. Wallets and merchant rails are the adoption layer. The jurisdictions that connect these layers well will get more value from all of them.

Interoperability Is the Real Proof Point

The strongest evidence in this debate comes from markets where sovereign digital money and settlement infrastructure already work together in practice. Jamaica is relevant because Montran operates the JamClear-RTGS backbone alongside which Jam-Dex was rolled out, and the 2022 Montran-eCurrency announcement framed this as a fully integrated RTGS-CBDC implementation with the Bank of Jamaica.

That kind of interoperability is more informative than abstract policy positioning because it shows what coexistence looks like in operation: central bank money can be issued and redeemed through controlled settlement processes, while adoption still depends on the commercial ecosystem that puts CBDC into users’ hands and merchants’ tills.

Reach Out To Learn More Here.