CBDC vs Stablecoin vs Deposit Token in 2026: A Practical Map of Digital Money

Digital money in 2026 comes in three distinct flavours, and the differences between them matter more than most coverage acknowledges. Central bank digital currencies, privately issued stablecoins, and commercial bank deposit tokens all represent "digital dollars" (or euros, or yen) -- but their issuance models, settlement characteristics, regulatory treatment, privacy properties, and risk profiles are fundamentally different.

The casual conflation of these three categories leads to confused policy debates, misguided investment theses, and a general public that does not understand what is actually being proposed when politicians, central bankers, and technology executives talk about "the future of money." This piece lays out the structural differences and evaluates where each model stands in practical terms.

Issuance Models: Who Creates the Money​

The most fundamental difference between CBDCs, stablecoins, and deposit tokens is who issues them and what backs them.

CBDCs are issued by central banks. A central bank digital currency is a direct liability of the central bank, just like physical cash. When you hold a CBDC, you have a claim against the central bank itself -- the most creditworthy entity in a sovereign monetary system. The central bank creates CBDCs in the same way it creates reserves: by expanding its balance sheet. No private entity is involved in the issuance.

Stablecoins are issued by private companies. USDC is issued by Circle. USDT is issued by Tether. Each stablecoin represents a claim against the issuer, who is supposed to hold reserves sufficient to honour redemptions at par. The stablecoin is a liability of the private issuer, not the central bank. This means the credit risk is different -- you are trusting Circle or Tether to maintain adequate reserves and remain solvent, not the Federal Reserve.

Deposit tokens are issued by commercial banks. When JPMorgan creates JPM Coin (now rebranded as part of their Kinexys platform) or when a consortium of European banks creates a shared deposit token, the token represents a commercial bank deposit. It is a liability of the issuing bank, backed by the bank's assets and covered by deposit insurance up to applicable limits. This is the same credit relationship as a regular bank account, just represented as a blockchain token.

These differences in issuance model cascade through every other aspect of how these instruments function.

Settlement Finality and Mechanics​

Settlement finality -- the point at which a payment is irrevocable and the recipient has unconditional access to the funds -- works differently for each model.

CBDC settlement is final in the same way that central bank reserve settlement is final. When a CBDC transaction completes, the recipient has central bank money. There is no counterparty risk, no possibility of clawback (absent a legal process), and no settlement delay. The finality is absolute because the money is created by the entity that defines finality for the entire monetary system.

Stablecoin settlement is final at the blockchain level -- once a transaction is confirmed on-chain, it cannot be reversed through the blockchain itself. But economic finality is more nuanced. If a stablecoin issuer freezes an address or blacklists tokens (which both Circle and Tether have the technical ability to do, and have done), the recipient's access to the value can be restricted post-settlement. And if the issuer becomes insolvent, the stablecoin's value is impaired regardless of on-chain settlement status.

Deposit token settlement depends on the interbank settlement mechanism. If both parties bank with the same institution, settlement can be instant and final within that bank's ledger. If the parties bank with different institutions, the deposit tokens need to be settled through interbank channels -- potentially through central bank reserves, which introduces the same settlement timing as traditional interbank payments. The promise of deposit tokens is that they can speed up intrabank settlement and enable programmable payments, but cross-bank settlement remains dependent on existing infrastructure.

Regulatory Treatment in 2026​

The regulatory landscape for each type of digital money differs substantially.

CBDCs are regulated by definition -- they are created by regulators. The policy questions around CBDCs are about design choices (wholesale vs retail, account-based vs token-based, privacy protections) rather than whether they should be permitted. In practice, most CBDC projects are governed by new enabling legislation specific to the CBDC program.

Stablecoins are the subject of active regulatory development. In the US, the GENIUS Act establishes a federal framework requiring stablecoin issuers to maintain reserves in high-quality liquid assets, submit to regular audits, and comply with AML/KYC requirements. In Europe, MiCA creates a licensing framework for stablecoin issuers (called "asset-referenced tokens" and "e-money tokens" in MiCA's taxonomy). As we detailed in our analysis of the GENIUS Act's reserve requirements, the regulatory frameworks are substantive but differ meaningfully across jurisdictions.

Deposit tokens fall under existing banking regulation. A deposit token issued by a licensed bank is regulated as a bank deposit -- subject to capital adequacy requirements, deposit insurance, and banking supervision. This gives deposit tokens a regulatory advantage: they operate within a well-understood framework. The regulatory question for deposit tokens is whether existing banking rules adequately address the specific risks of tokenised deposits, such as the potential for faster bank runs if depositors can move tokens instantly.

Privacy Characteristics​

Privacy is one of the most politically charged differences between the three models.

CBDCs have the worst privacy profile from the user's perspective. Because a CBDC is a direct central bank liability, the central bank has the ability -- and, in most proposed designs, the architecture -- to observe all transactions. The digital euro pilot, for example, includes a "privacy threshold" below which transactions are anonymous and above which they are reported to authorities. But the central bank could technically observe all transactions if the design permitted it. This has generated significant political opposition, particularly in the US, where CBDC skeptics cite surveillance concerns.

Stablecoins on public blockchains offer pseudonymous transactions. The blockchain records transactions between addresses, not named individuals. However, the connection between addresses and identities is increasingly mapped by compliance firms, and stablecoin issuers maintain blacklists that require identity linkage. In practice, stablecoin privacy is moderate -- better than a CBDC with full transaction visibility, worse than physical cash.

Deposit tokens have the same privacy characteristics as existing bank accounts. The bank knows your identity, observes your transactions, and reports to authorities as required by law. This is the privacy model that most people already operate under, and deposit tokens do not change it meaningfully.

The privacy question is critical because it shapes public acceptance. The political backlash against CBDCs in the US -- which has effectively halted retail CBDC development -- was driven primarily by privacy concerns. Stablecoins and deposit tokens face less privacy-related opposition because they operate within existing privacy frameworks that the public already tolerates.

Programmability​

All three forms of digital money can be programmable -- meaning that transactions can be conditional, automated, or subject to smart contract logic. But the practical programmability differs.

CBDCs can be programmed by the central bank or by approved intermediaries. The digital euro pilot includes basic programmability for conditional payments. But central bank programmability raises the spectre of policy-driven restrictions on spending -- the concern that a government could program CBDCs to expire, or restrict purchases of certain goods. Whether this concern is realistic or paranoid depends on your view of government, but it is a genuine feature of CBDC architecture that does not exist with physical cash.

Stablecoins on public blockchains inherit the full programmability of the underlying smart contract platform. USDC on Ethereum can interact with any smart contract -- lending protocols, decentralised exchanges, automated treasury management, conditional escrow. This composability is the primary technical advantage stablecoins hold over CBDCs and deposit tokens. It enables an ecosystem of financial applications that can be built without permission from the issuer.

Deposit tokens have programmability defined by the issuing bank and the platform they operate on. JPMorgan's Kinexys platform, for example, supports programmable payments for institutional clients. But the programmability is bounded by the bank's approved use cases and the platform's architecture. A deposit token on a permissioned bank platform is not composable with DeFi protocols in the way that a stablecoin on Ethereum is.

The Digital Euro Pilot: Status Check​

The European Central Bank's digital euro project is the most advanced retail CBDC effort in a major developed economy. As of early 2026, it remains in pilot phase, with a launch decision expected by late 2026 or 2027.

The proposed design uses a two-tier model: the ECB issues the CBDC, but commercial banks distribute it. Users hold digital euros in bank-provided wallets, with holding limits (currently 3,000 euros per person) to prevent deposit disintermediation. The pilot has revealed low consumer interest -- most Europeans see no clear advantage over existing cards and bank transfers. The privacy debate remains politically sensitive, and the holding limit constrains utility beyond small retail payments.

JPM Coin and Bank Deposit Tokens​

JPMorgan's tokenised deposit platform (now operating under the Kinexys brand) is the most prominent deposit token in production, processing billions in daily institutional transactions for cross-border settlement and corporate treasury management.

The use case is strongest in wholesale markets where traditional correspondent banking is slow and expensive. Several European banks have piloted deposit token platforms on shared infrastructure, and the Swiss National Bank's Project Helvetia explored wholesale CBDC settlement using deposit tokens as an intermediary. The common thread is that deposit tokens enhance rather than disrupt existing banking infrastructure -- the least revolutionary but most immediately practical form of digital money.

Which Model Wins for Which Use Case​

The three models are not competing for the same use cases. Stablecoins lead in cross-border remittances (as we covered in our analysis of stablecoin payment adoption) and emerging market adoption where currency instability drives demand. Deposit tokens and wholesale CBDCs are best positioned for interbank settlement, avoiding the privacy concerns of retail CBDCs. Stablecoins on public blockchains are the only option with meaningful DeFi composability. For corporate treasury, the choice depends on whether a firm prioritises operating within banking rails (deposit tokens) or accessing the broader crypto ecosystem (stablecoins). In developed markets with efficient existing payment systems, none of the three offers a dramatic retail improvement.

The Interoperability Question​

For any of these models to reach full potential, they need to interoperate with each other and with existing financial systems. A world where CBDCs, stablecoins, and deposit tokens exist in separate silos is worse than the status quo.

Efforts are underway but early-stage. The BIS's Project mBridge explored CBDC-to-CBDC interoperability. Swift's experiments (discussed in our tokenisation coverage) focused on connecting tokenised assets across networks. But true cross-model interoperability -- atomic settlement between a CBDC, a stablecoin, and a deposit token -- does not exist and requires technical standards and legal frameworks that are years away.

Risks Unique to Each Model​

Each model carries distinctive risks that users and policymakers should understand.

CBDC risks: Central point of failure in sovereign infrastructure. Political risk of surveillance or spending restrictions. Disintermediation of commercial banks. Technology risk in government-operated systems.

Stablecoin risks: Issuer credit risk if reserves are mismanaged. Regulatory risk as frameworks evolve. Concentration risk with two issuers (Tether and Circle) dominating. Depegging risk during market stress.

Deposit token risks: Bank credit risk mitigated by deposit insurance up to limits. Technology risk on untested platforms. Fragmentation if banks operate incompatible systems. Faster bank run potential with instant token transfers.

The Practical Outlook​

The most likely trajectory is coexistence, not winner-take-all. Stablecoins will continue to dominate crypto-native use cases and emerging market adoption. Deposit tokens will gradually expand as an infrastructure upgrade for institutional settlement. CBDCs will develop unevenly -- wholesale variants for interbank settlement are likely, while retail CBDCs face political opposition in the US and unclear consumer value propositions in Europe.

For researchers and analysts following digital money development, the key is to evaluate each model on its actual merits rather than through ideological lenses. The practical outcome will be determined by infrastructure quality, regulatory design, and user behaviour -- not by the preferences of central bankers or crypto advocates.

Frequently Asked Questions​

What is the main difference between a CBDC, a stablecoin, and a deposit token?

The key difference is the issuer and the credit risk. A CBDC is issued by a central bank (sovereign credit risk). A stablecoin is issued by a private company (corporate credit risk, backed by reserves). A deposit token is issued by a commercial bank (bank credit risk, partially covered by deposit insurance). Each model has different settlement mechanics, regulatory treatment, and privacy characteristics.

Which form of digital money is safest?

From a credit risk perspective, CBDCs are safest because they are backed by the full faith of the sovereign. Deposit tokens carry bank credit risk mitigated by deposit insurance. Stablecoins carry issuer credit risk dependent on reserve management. From a privacy perspective, stablecoins on public blockchains offer more anonymity, while CBDCs potentially offer the least.

Why is the US opposed to a retail CBDC?

Political opposition centres on privacy and surveillance concerns -- the fear that a government-operated digital currency would enable transaction monitoring and spending restrictions. Legislation has been introduced to prohibit a retail Federal Reserve CBDC. The US approach favours regulated private stablecoins (through the GENIUS Act) over a government-issued alternative.

Can CBDCs and stablecoins interoperate?

Not currently at any meaningful scale. Projects like the BIS's mBridge are exploring CBDC-to-CBDC interoperability. True cross-model interoperability -- where a CBDC, stablecoin, and deposit token settle atomically -- requires technical standards and legal frameworks that do not yet exist.

What are deposit tokens used for?

Primarily wholesale institutional settlement -- cross-border interbank transfers, corporate treasury management, and institutional payment automation. JPMorgan's Kinexys platform is the most prominent example, processing billions in daily institutional transactions. Deposit tokens are not widely used for retail payments.

Will one model replace the others?

Unlikely. Each model serves different use cases and operates under different regulatory frameworks. The most probable outcome is coexistence, with stablecoins dominating crypto-native and cross-border retail corridors, deposit tokens serving institutional wholesale settlement, and CBDCs developing unevenly based on jurisdiction-specific conditions.