A Central Bank Digital Currency is a digital liability of a central bank recorded in accounts, tokens or another ledger under the issuer's rules; it differs from a bank deposit in its counterparty, from cash in its form, and from Bitcoin in its centralised issuance, access governance and monetary policy.
CBDC is not a generic name for all electronic money. It is a direct digital liability of a central bank in its unit of account, so the holder does not bear the credit risk of a private issuer of that liability. An ordinary commercial-bank balance is instead a claim on that bank, even where the state protects it through deposit insurance. [2]
A retail CBDC is intended for the public and businesses in everyday payments; a wholesale CBDC is aimed at banks and other authorised institutions settling large payments or tokenised assets. The distinction is more than technical: commercial-bank reserves at the central bank are already digital, so a wholesale project must be examined for the genuinely new function it adds. [2]
The architecture can be direct, intermediated or two-tier. A central bank may maintain the core ledger and bear the ultimate liability while banks or payment companies open wallets, identify customers, process payments and provide support. An intermediary's failure therefore need not extinguish the claim itself, but it can block access or recovery. [3]
A CBDC need not use a blockchain or a public token. A design can use accounts, tokens, a central database or a distributed ledger; the choice affects verification, finality, recovery, scaling and offline payments. The word token alone proves neither anonymity, account-free possession nor transfer without the system operator's permission. [3]
Privacy is a property of a particular legal and technical design, not a consequence of the CBDC label. A system must determine which data the central bank, intermediaries and the state can see, how long they retain it, who can link it to an identity and what happens offline; the same design must also address AML, sanctions, fraud, cyber incidents and access recovery. [4]
Programmable payments are not the same as programmable money. A user may voluntarily set a conditional or automatic payment without the issuer changing the fungibility of units; restrictions on what, where or until when a unit may be spent instead alter the properties of the money. The IMF therefore recommends separating these layers explicitly and assessing them under the applicable mandate and law. [4]
A large migration of deposits into a safer central-bank liability can make commercial-bank funding more expensive and accelerate a digital bank run in a crisis. Designs therefore consider holding limits, no remuneration or tiered remuneration, and sweeping excess balances into bank accounts; those constraints reduce some systemic risks but also change the CBDC's utility and accessibility. [1]
An announced pilot or preparation phase is not an issued currency. The BIS survey for 2024 covered 93 central banks and found that 91 % were exploring a retail CBDC, a wholesale CBDC or both, but projects differ in purpose and commitment. The ECB would decide on any digital euro issuance only after adoption of the legal framework, so the date, law, issuer, intended users and operational status of every project must be checked separately. [5]
For the clearest picture, read this entry together with Fiat money, Monetary Base, Broad Money, Legal Tender, Sound money, Bitcoin Privacy.
01Is a CBDC the same as Bitcoin or a stablecoin?+
No. A CBDC is a central-bank liability whose issuance and rules are set by a public institution. Bitcoin has no central issuer and an open network verifies its supply and transfers under consensus rules; a private stablecoin is a liability or token of another issuer and carries different reserve, legal and counterparty risks.
02Does a CBDC automatically mean the state can see and program every purchase?+
Not automatically, but every design must answer that question. Architecture and law determine visibility, identification, offline use, official access and conditional features. A privacy claim in marketing is insufficient: the legal safeguards, data flows, intermediary powers and actual implementation must be examined.