Advanced11 min readUpdated May 8, 2026

Stablecoins vs. CBDCs: Competition, Coexistence & Convergence

The key differences between private stablecoins and central bank digital currencies, and how they may evolve together.

Key Takeaways

  • CBDCs are central bank liabilities; stablecoins are private sector liabilities — a fundamental difference.
  • Wholesale CBDCs and regulated stablecoins are increasingly complementary, not competing.
  • The "two-tier" model may see central banks provide settlement rails while fintechs offer consumer-facing stablecoins.
S
By StablecoinHub Editorial

Understanding the CBDC–Stablecoin Spectrum

The financial world is debating whether central bank digital currencies (CBDCs) will replace stablecoins, complement them, or something in between. The answer depends heavily on the CBDC design choices made by each central bank.

Fundamental Difference: Liability Structure

StablecoinRetail CBDCWholesale CBDC
IssuerPrivate companyCentral bankCentral bank
Liability ofIssuer + custodianSovereign stateSovereign state
Default riskYesNoNo
ProgrammableYes (on-chain)VariesYes
PrivacyPseudonymousRegulatedTransaction-level

The Two-Tier Model

Most central banks exploring CBDCs are gravitating toward a two-tier distribution model:

  1. Tier 1: Central bank issues wholesale CBDC to licensed intermediaries (banks, fintechs).
  2. Tier 2: Intermediaries distribute to end users as retail wallets.

In this model, a fintech might issue a regulated, fiat-backed stablecoin that is 100% backed by wholesale CBDC — making it essentially a "wrapped CBDC" with better programmability and user experience.

Convergence Signals

  • The ECB is studying how the digital Euro can coexist with MiCA-compliant EMTs.
  • The BIS has published frameworks for CBDC-stablecoin interoperability.
  • Circle and other issuers have explicitly designed USDC to be CBDC-compatible.

The likely end state is a hybrid ecosystem where sovereign CBDCs provide settlement finality at the base layer, while regulated private stablecoins provide the programmability, composability, and user experience layer.