CBDCs: A Central Bank Liability That Happens to Be Digital

Concept-level article, and one correction belongs at the top: a central-bank digital currency is not a cryptocurrency. It is issued by a central bank, denominated in the national currency, and is a liability of the state's monetary authority. It is not decentralised, not scarce by protocol, not permissionless, and not an investment — there is nothing to buy, hold for appreciation, or trade. A CBDC is closer to cash than to anything else in this pillar, and it appears here because readers meet the term in the same conversations and because the confusion is actively exploited: fraudulent schemes have solicited money for "early access" to central-bank currencies that no member of the public can pre-purchase. No CBDC is or will be sold to the public in advance.

Bank deposits are digital and are a claim on a commercial bank. Physical cash is a claim on the central bank. A retail CBDC would be a central-bank claim held directly by the public — digital cash rather than a digital deposit — and that single change is what the entire policy debate is about.

What it is, and the two forms

Wholesale CBDCs would be used between financial institutions for settlement, which is closer to an upgrade of existing plumbing than a change to anything a household encounters — central banks already provide digital settlement to banks, and this modernises it. This form attracts little controversy. Retail CBDCs would be available to the public, and this is where the argument sits. Four design questions determine what a retail CBDC actually is, and they are unsettled everywhere it is being considered. Is it interest-bearing? A remunerated CBDC competes with bank deposits; an unremunerated one behaves more like cash. Are there holding limits? Caps exist in most proposals precisely to limit that competition. Is it intermediated? Most designs route access through banks and payment firms rather than the central bank serving the public directly, so the central bank issues while others handle onboarding and service. And what is the privacy architecture? This is the contested one, taken up below. Two things a CBDC is not, stated because both are widely assumed. It is not a blockchain project — some designs use distributed-ledger components and many do not, and the technology choice is incidental to the policy question rather than central to it. And it is not new money in the sense of monetary expansion: issuing a CBDC converts one form of central-bank liability into another rather than creating additional purchasing power.

The arguments, reported as a live policy debate

The case made for them. Payments could be cheaper and faster, particularly cross-border, where cost and delay remain high. Physical cash use has declined in many economies, and a public digital option would preserve access to a form of money that is not a claim on a commercial firm. A public payment rail could reduce dependence on a small number of private payment networks. Financial inclusion is cited, though critics note that access barriers are rarely primarily technological. And several central banks have said explicitly that a domestic option is partly a response to private payment systems and foreign currencies gaining ground. The case made against them. Privacy is the objection raised most forcefully: a central-bank-issued instrument could in principle create a record of individual transactions in a way physical cash does not, and while most published designs propose privacy protections and some propose offline low-value anonymity, critics argue that architectural safeguards can be changed by later decisions and that the capability, once built, exists. Programmability is the second: money that can carry conditions could in principle be restricted by purpose, by date, or by recipient. Proponents point to legitimate uses and note that no major central bank has proposed spending restrictions on general-purpose retail money; opponents reply that the objection is to the capability rather than to any current stated intention. Bank disintermediation is the third and most technical: if households move deposits into central-bank money, particularly during stress, banks lose the funding base from which they lend — and a CBDC could make a bank run faster and frictionless. Holding limits and unremunerated designs are the standard mitigations. And operational concentration: a national payment system is a national point of failure and a target. This portal reports these positions and adjudicates none of them. The privacy and programmability questions in particular are genuine political disagreements about the relationship between citizens and the state, not technical questions with technical answers — and a financial-education portal has no standing to settle them. What a reader can usefully hold onto: the design choices above are where the substance is, so any specific claim about what a CBDC will do should be checked against the actual published design of the actual proposal in question. And since implementation status differs by jurisdiction and has been moving — some in research, some piloting, some issued, some abandoned — this article deliberately describes structures rather than a current state of play, because the structures age far more slowly than the status does.