CBDC vs Tokenization: Competing or Complementary Visions for Digital Money?
CBDC and tokenized asset programmes are often framed as rivals. They are better understood as distinct layers of a digital financial system that will need to interoperate — with significant compliance implications for the interface between them.
The CBDC debate has generated more regulatory and policy energy than almost any other topic in digital finance, while the tokenized asset market has grown from nothing to $18.9 billion with relatively less attention. This asymmetry reflects their different political saliences — CBDCs raise questions about monetary sovereignty, surveillance, and financial system structure that tokenized assets do not — rather than their relative importance for the practical operation of the tokenized financial system.
The compliance-relevant question is not which model “wins” — it is what the coexistence of CBDCs, tokenized deposits, and tokenized assets looks like in the 2027-2030 time frame, and what compliance and interoperability obligations arise at the boundaries.
The CBDC Landscape: Where Things Actually Stand
China: e-CNY — The Most Advanced Mass-Market CBDC
China’s digital yuan (e-CNY) is the most advanced CBDC programme globally by transaction volume and adoption breadth. Cumulative trial transaction value has exceeded $250 billion across more than 17 cities. The People’s Bank of China has distributed e-CNY through commercial banks, integrated it with major payment platforms (Alipay, WeChat Pay), and required its acceptance at the 2022 Beijing Winter Olympics.
The e-CNY’s technical design is a two-tier system: the PBoC issues e-CNY to commercial banks, which distribute it to consumers and businesses. This preserves the role of commercial banks as intermediaries — a politically and systemically important choice — while providing the PBoC with direct visibility into aggregate transaction flows.
Compliance and surveillance implications: The e-CNY includes programmable features that allow conditional spending — restrictions on where specific e-CNY allocations can be used, or time limits after which unspent e-CNY expires. It also provides the PBoC with transaction monitoring capabilities that cash does not. This has attracted significant attention from privacy advocates and from governments considering the surveillance implications of CBDC adoption.
For global tokenization programmes, the e-CNY’s significance is primarily as a signal that large-scale CBDC deployment is technically feasible and that governments are willing to deploy it. The e-CNY itself is not directly relevant to most global institutional tokenization programmes because China’s capital controls prevent most cross-border integration, but it provides empirical validation of the CBDC model.
European Union: Digital Euro — In Design Phase
The European Central Bank has been conducting its investigation and preparation phase for a digital euro since October 2021, transitioning to a preparation phase in November 2023. As of early 2026, the digital euro has not been issued and its issuance date is not confirmed. European legislation enabling digital euro issuance is progressing through the EU legislative process.
The ECB’s design choices for the digital euro are oriented toward preserving financial stability (no disintermediation of banks) and privacy (transaction privacy for retail payments, subject to AML requirements). The digital euro would be a liability of the Eurosystem — a claim on the ECB — with distribution through commercial banks and payment service providers.
Key design features relevant to tokenization:
The digital euro is designed for retail payments, not for securities settlement. It is not, in its current design phase, intended to serve as the settlement layer for tokenized securities. Wholesale CBDC — a separate concept designed for large-value securities settlement between financial institutions — is being explored by the ECB through Project Agorá and related BIS initiatives, but is not the same instrument as the retail digital euro.
For tokenization compliance teams, the digital euro’s relevance is indirect: if issued, it would be the most credible euro-denominated settlement instrument for retail-accessible tokenized payment products. The compliance architecture for any product that interfaces between tokenized assets and digital euro would need to navigate both the MiCA framework (for the tokenized asset) and the digital euro legal framework (when enacted).
United States: No Federal CBDC Announced
The United States has no announced plan to issue a federal retail CBDC. The Federal Reserve has been explicit that it would not issue a CBDC without Congressional authorisation and that it does not currently have a mandate to do so. The current administration has been publicly sceptical of retail CBDCs, with executive communications indicating opposition to a government-issued digital dollar that could be used for financial surveillance.
The Federal Reserve has conducted Project Hamilton (in collaboration with MIT) and Project Cedar (in collaboration with the New York Fed) as research exercises, and participates in BIS wholesale CBDC research. These are research programmes, not precursors to issuance.
The tokenized deposit alternative: In the absence of a US CBDC, the most likely US digital dollar for institutional markets is the tokenized deposit — a bank deposit represented as a token, issued by a regulated commercial bank, representing a claim on that bank rather than on the Federal Reserve. Citigroup’s Token Services, JPMorgan’s Kinexys digital currency, and other bank-issued tokenized payment instruments are all tokenized deposits, not CBDCs.
Tokenized deposits and CBDCs have different compliance profiles. A tokenized deposit is a bank liability, subject to deposit insurance (up to applicable limits), bank regulation, and AML requirements applied to the issuing bank. A CBDC is a central bank liability, subject to whatever specific legal framework governs it. The compliance architecture for products that use tokenized deposits as settlement currency is more immediately navigable than for hypothetical CBDC settlement, because the regulatory framework for bank deposits is well-established.
How CBDCs and Tokenized Deposits Actually Differ
The distinction between CBDCs and tokenized deposits is frequently blurred in policy discussion and occasionally in compliance analysis. The distinction matters because the two instruments have different issuers, different legal frameworks, and different compliance obligations:
| Dimension | CBDC | Tokenized Deposit |
|---|---|---|
| Issuer | Central bank | Commercial bank |
| Legal nature | Central bank liability | Bank deposit (bank liability) |
| Deposit insurance | Not applicable | Yes (up to limit) |
| Credit risk | Sovereign | Bank credit risk |
| AML obligations | Central bank framework | Bank AML (BSA, MLD, etc.) |
| Monetary policy transmission | Direct | Indirect (through banking system) |
| Programmability | Government-defined | Bank-defined (within regulatory limits) |
For settlement of tokenized securities transactions, both can function as the “cash leg” of a delivery-versus-payment transaction. The compliance difference is in who performs the AML/KYC obligations for the payment leg — the central bank (for CBDC) or the commercial bank (for tokenized deposits). Most existing tokenized securities programmes use tokenized deposits or regulated stablecoins (e.g., USDC) as the settlement currency, not CBDCs, because CBDC infrastructure is not yet available in most markets.
BIS Project mBridge: Cross-Border CBDC Settlement
BIS Project mBridge is the most advanced multi-central-bank CBDC project in the world, connecting the central banks of China, Hong Kong, the UAE, Thailand, and Saudi Arabia (as observer). Project mBridge enables instant cross-border payments between participating central banks using a shared DLT platform (mBridge ledger), settling transactions in each participating central bank’s digital currency.
For international tokenization programmes, mBridge’s significance is as a proof of concept for multi-currency, DLT-based settlement between regulated financial institutions across jurisdictions. If mBridge expands to additional participating central banks — or if similar multi-CBDC platforms develop between major economies — the compliance architecture for cross-border tokenized asset settlement would shift: real-time cross-border settlement in central bank money would become available.
The compliance implications of multi-CBDC settlement platforms are not trivial. A transaction settled on mBridge involves the central banks of multiple jurisdictions; AML obligations apply under the frameworks of all participating jurisdictions simultaneously. The BIS and FATF have been engaged on how AML and sanctions screening obligations apply to multi-CBDC settlement, but the framework is not yet finalised.
mBridge's significance for tokenization is not its current scale but its architecture: it proves that multi-jurisdiction, central-bank-money DLT settlement is technically achievable. The compliance framework for operating on it is the next challenge.
What CBDC Adoption Means for Tokenization Platforms
The most practical question for tokenization compliance teams is: as CBDCs are issued and adopted, what changes in the compliance obligations for tokenized asset platforms that wish to use CBDC as the settlement currency?
New KYC/AML interface requirements: If a CBDC is used to settle a tokenized securities transaction, the CBDC leg of the transaction passes through the central bank’s (or its designated agent’s) compliance checks, in addition to the securities platform’s own checks. The compliance architecture must accommodate dual-layer compliance — the tokenized asset platform’s investor eligibility and AML controls, and the CBDC settlement layer’s transaction monitoring.
Programmability compliance: CBDCs may include programmable features — restrictions on use, time limits, sectoral limitations — imposed by the issuing central bank. Tokenized asset platforms that use programmed CBDCs as settlement currency need to ensure that the CBDC’s programmatic restrictions do not inadvertently limit the settlement of legitimate tokenized securities transactions. A digital euro with retail spending limits would need to be distinguished from institutional-use digital euro for securities settlement.
Regulatory reporting at the CBDC interface: Central banks issuing CBDCs will likely require or receive transaction reporting that provides visibility into how their digital currency is being used. Tokenized asset platforms using CBDC settlement currency may be required to provide transaction data to the central bank in a format compatible with the CBDC’s reporting infrastructure — an additional regulatory reporting obligation on top of existing securities and AML reporting.
The Complementarity Conclusion
CBDCs and tokenized assets are best understood as addressing different layers of the digital financial system. CBDCs address the money layer — the settlement currency for financial transactions. Tokenized assets address the asset layer — the securities, funds, real estate, and credit instruments that are owned, transferred, and used as collateral.
A fully functional tokenized financial market needs both: the asset layer (tokenized securities, funds, derivatives) and the money layer (CBDC or regulated tokenized deposits) must be able to interact in atomic delivery-versus-payment settlement. The compliance architecture for this interaction — the point where tokenized assets and digital money meet in a single transaction — is the next frontier for tokenization compliance design.
The institutions and jurisdictions that develop coherent compliance frameworks for this interface will have a significant structural advantage in attracting institutional tokenization activity. Switzerland (SDX settlement integrated with SIX conventional infrastructure), Singapore (MAS Project Guardian with multi-asset, multi-currency scope), and the EU (wholesale CBDC exploration via BIS Project Agorá) are furthest along in addressing this challenge.
For related analysis, see /analysis/why-banks-are-tokenizing/ and /jurisdictions/.
Subscribe for full access to compliance intelligence across all 7 analytical lenses, including licensing guides, jurisdiction benchmarks, and enforcement trackers.
Subscribe from $29/month →