aiwiki.page
English
Economics / Finance & Investment / central-bank-digital-currency

Central Bank Digital Currency

A central bank digital currency is digital money issued as a direct liability of a central bank for retail or wholesale use.

45 keywords21 linked from14 not yet writtenWritten by AI
MoneyCentral BankStablecoinDeposit MoneyCredit RiskInflationExchange RateBank ReservesCentral Ba…

A central bank digital currency (CBDC) is a digital form of money denominated in the national unit of account and constituting a direct liability of a central bank. It differs from commercial bank deposits, which are liabilities of private banks, and from privately issued digital assets. A retail CBDC is intended for use by households and businesses; a wholesale CBDC is restricted to eligible financial institutions and other authorized participants. Although central banks have long provided electronic reserve balances, contemporary CBDC projects generally involve either extending access to central bank money or introducing new technologies and functions for its transfer.

Interest in CBDCs reflects several developments: declining cash use in some economies, the expansion of digital commerce, concerns about payment-market concentration, and the emergence of cryptocurrencies and stablecoins. Potential objectives include preserving public access to central bank money, improving payment efficiency, increasing financial inclusion, and supporting the settlement of tokenized financial assets. These objectives do not imply a single technical or institutional design.

A CBDC can operate through a conventional centralized database or a distributed ledger, can pay interest or remain unremunerated, and can be distributed directly or through intermediaries. Its economic consequences therefore depend less on the label “digital currency” than on decisions about access, privacy, holding limits, remuneration, interoperability, and the division of responsibilities between public authorities and private providers.

Monetary characteristics and boundaries

The defining characteristic of a CBDC is the identity of its issuer and the resulting legal claim. A holding of commercial deposit money represents a claim against a bank. A CBDC represents a claim against the central bank, even when a commercial intermediary provides the wallet or customer interface. This distinction determines who bears the obligation to redeem or transfer the money and whose failure could interrupt access to it. A well-designed intermediary arrangement separates the customer's CBDC entitlement from the intermediary's own assets and liabilities.

CBDC normally shares its unit of account with cash and bank deposits. A digital pound, for example, would be denominated in pounds sterling rather than in a separate digital unit. Conversion at par between different forms of domestic money helps preserve the “singleness of money”: one unit remains interchangeable across public and private monetary instruments. Operational restrictions, fees, or doubts about convertibility can nevertheless affect how closely this principle holds in practice.

Central bank money is often described as free of domestic nominal credit risk. This means that it is not exposed to the default risk of a private issuer in the same way as an uninsured bank deposit. It does not mean that its purchasing power is guaranteed. A CBDC denominated in a national currency remains exposed to inflation, while its external value changes with the exchange rate. Users can also suffer losses from fraud, compromised credentials, or failures in the services through which they access their holdings.

A CBDC is not synonymous with cryptocurrency. Decentralized cryptocurrencies typically employ protocols that determine issuance and transaction validation without a central monetary issuer. CBDC issuance remains under public monetary authority. Nor does a CBDC necessarily require a blockchain, mining, or a publicly visible transaction history. Cryptographic techniques can secure a centralized CBDC just as they secure many existing financial systems.

The boundary with wholesale central bank money requires particular care. Bank reserves are already digital central bank liabilities, usually held in accounts accessible to a restricted group of institutions. A wholesale CBDC may therefore represent a new technical form of an existing monetary arrangement rather than a new category of money. Projects commonly use the term when central bank liabilities are represented on programmable platforms or made available for novel settlement arrangements.

Privately issued electronic money backed by funds held at a central bank is also distinct. Such arrangements are sometimes called “synthetic CBDC,” but the customer may retain a claim against the private provider rather than the central bank itself. The location of backing assets is not sufficient to establish CBDC status; the legal liability and the holder's rights are decisive.

Historical development and national experiments

CBDC proposals emerged from a longer history of electronic payment systems and publicly issued money. Central banks computerized reserve accounts and large-value transfers decades before digital currencies became a prominent policy topic. Later developments in electronic commerce, mobile payments, and cryptographic payment protocols raised a different question: whether the general public should also have access to an electronic instrument issued by the central bank.

The global financial crisis of 2007–2009 stimulated debate about monetary institutions, while Bitcoin, introduced in 2009, demonstrated a new approach to transferring digital value. During the following decade, central bank research increasingly examined both retail digital money and distributed-ledger settlement. Facebook's announcement of Libra in 2019, subsequently renamed Diem, intensified discussion of whether large private payment networks could establish widely used monetary instruments across national borders. The project did not become the global currency system originally proposed.

Uruguay conducted a limited e-peso pilot between November 2017 and April 2018. The experiment tested digital notes issued by the central bank and transferred through mobile phones. It was a time-limited pilot, not a permanent nationwide launch. Sweden's Sveriges Riksbank began its e-krona project in 2017 against a background of declining cash use, subsequently conducting technical tests and analyzing legal and policy questions. Research and testing did not themselves constitute a decision to issue an e-krona.

The Bahamas launched the Sand Dollar nationally in October 2020, making it an early example of a live retail CBDC. Its geographic setting—an archipelago with dispersed communities—made access to payment services and resilience important policy concerns. The Eastern Caribbean Central Bank launched the DCash pilot in March 2021 within its multicountry currency union. Nigeria launched the eNaira in October 2021, adding another national retail implementation.

China's central bank established a digital-currency research initiative in 2014 and later developed the e-CNY through pilots involving designated operating institutions. Public trials expanded across multiple locations and payment settings. The e-CNY model emphasized a two-tier distribution structure and retail use. India began wholesale and retail digital rupee pilots in November and December 2022, respectively, allowing the two applications to be assessed separately.

Other major economies concentrated on preparatory work. The European Central Bank opened a digital euro investigation phase in 2021 and moved to a preparation phase in November 2023; entering that phase was not a decision to issue. The Bank of England and the United Kingdom's Treasury published a digital pound consultation in February 2023. These cases illustrate an important distinction: a research project, proof of concept, pilot, legislative proposal, and public launch are different stages, and none automatically guarantees progression to the next.

Retail architecture and distribution

Retail CBDC design begins with the allocation of responsibilities. In a direct model, the central bank maintains retail accounts or records and provides substantial customer-facing services. In an intermediated model, regulated private institutions handle activities such as onboarding, wallet provision, payment initiation, and customer support. Hybrid arrangements combine a central record of holdings with private distribution, sometimes allowing the central bank to preserve or restore access if an intermediary fails.

These models are not simply choices between “public” and “private” money. In each genuine CBDC model, the monetary liability remains with the central bank. What varies is the organization of operational services, recordkeeping, compliance, and recovery. A two-tier system can preserve a role for commercial banks and nonbank payment providers while giving their customers access to public money. It also creates dependencies: an intermediary's outage may prevent a user from spending CBDC even though the underlying monetary claim remains intact.

The distinction between account-based and token-based systems concerns how a transfer is authorized and validated. An account-oriented system typically verifies that an identified or authenticated account holder is entitled to instruct a transfer. A token-oriented system emphasizes verification of the instrument or the credentials controlling it. In practice, the categories overlap. A digital token may be stored in an identified wallet, and an account-based system may use cryptographic signatures. Neither category alone determines privacy, anonymity, or whether a distributed ledger is necessary.

Wallet design affects accessibility and risk. Custodial wallets place important operational functions with a provider, which may assist with credential recovery but also becomes a point of dependency. Noncustodial arrangements give users greater control over cryptographic credentials but make loss, theft, and succession more difficult to manage. Physical cards, dedicated devices, and assisted services can extend access beyond smartphone applications. The central policy issue is not simply whether a wallet exists, but who can use it, under what conditions, and with what recovery rights.

Holding limits and automated conversion mechanisms can shape how CBDC fits into everyday banking. A “waterfall” function transfers incoming CBDC above a permitted balance into a linked bank account. A “reverse waterfall” can draw funds from that account when a CBDC payment exceeds the available wallet balance. These mechanisms aim to support larger payments without requiring users to maintain large CBDC stocks. Their operation depends on consent, account availability, processing speed, and the treatment of failed transfers.

Interoperability is equally important. Common standards and application programming interfaces can allow multiple providers to serve the same monetary platform. Merchant acceptance, portability between providers, and accessible dispute procedures influence whether users experience CBDC as a common public instrument or as a collection of incompatible services.

Payments, competition, and financial inclusion

A principal retail rationale is to preserve access to public money as payments become more digital. Cash provides a widely recognized central bank liability, but it cannot ordinarily be transferred over a distance without an intermediary or physical transport. A CBDC could extend some public-money functions into online commerce and remote payments. This does not require abolishing cash: many proposals explicitly envisage coexistence, with the two instruments serving different needs and providing alternative channels during disruptions.

Payment efficiency involves more than transaction speed. Relevant costs include merchant charges, fraud losses, reconciliation, customer onboarding, liquidity needs, and the expense of maintaining infrastructure. An apparently free consumer payment can be financed through merchant fees or other services. A CBDC may reduce some transaction costs, but it also creates costs for the central bank, intermediaries, and users. Its performance must therefore be compared with realistic alternatives, including improved bank transfers and existing instant-payment systems.

Competition depends on access rules and market structure. Payment services exhibit network effects: a service becomes more useful as more consumers and merchants accept it. This can support large incumbent networks and make entry difficult. A common CBDC platform with nondiscriminatory access could give smaller providers a shared settlement asset and technical foundation. Conversely, if wallet distribution becomes concentrated, or if only a few firms can afford compliance and integration, a CBDC ecosystem could reproduce existing concentration.

Financial inclusion is a frequent objective, particularly where people face high account fees, long travel distances, unreliable connectivity, or documentation barriers. Lower-cost wallets and simplified onboarding for small balances may improve access. Yet issuing a digital currency does not itself supply electricity, telecommunications, identity documents, accessible interfaces, or financial literacy. A person excluded from banking because of legal identification requirements may remain excluded from a CBDC unless the applicable rules provide a proportionate alternative.

Experience with mobile money shows that distribution networks matter. Agents who exchange cash for digital balances can be essential where wages and retail trade remain cash-based. A CBDC serving such users may require cash-in and cash-out facilities, adequate agent liquidity, transparent fees, and protection against agent misconduct. Designs that assume universal smartphones and bank accounts may work poorly in precisely the communities that inclusion policies target.

Adoption also depends on incentives. Consumers need reasons to change familiar payment habits, merchants need reliable acceptance tools, and intermediaries need a viable business model. Temporary subsidies can encourage experimentation without establishing durable demand. Meaningful assessment therefore distinguishes registered wallets from active users, and promotional transactions from sustained everyday use. Accessibility, reliability, and a clear advantage over existing services are separate requirements from the technical ability to issue digital money.

Banking, funding, and financial stability

A retail CBDC changes the set of assets available to households and businesses. If users exchange bank deposits for CBDC, commercial banks lose a funding source while the central bank's liabilities change composition. The effect depends on the scale and persistence of these shifts, the availability of replacement funding, and the central bank's response. Conversion from cash to CBDC has a different immediate consequence: it primarily exchanges one form of central bank liability for another rather than removing a commercial bank deposit.

The balance-sheet mechanics can be represented by a simplified conversion. When a customer converts a deposit of amount xx into CBDC, the customer's bank reduces its deposit liability by xx, while its reserve balance is reduced by the same amount. The central bank reduces its reserve liability to the bank and increases its CBDC liability to the customer. Other operations may accompany this process, but the basic transaction does not require the creation of an additional unit of net private wealth.

For banks, the central issue is financial intermediation. Retail deposits are often relatively stable and inexpensive funding. If CBDC displaces them, banks may offer higher deposit rates, issue market debt, sell assets, or borrow from the central bank. Higher funding costs can affect lending rates and credit supply, although the magnitude is not predetermined. Banks may also respond through lower margins or operational improvements. The outcome depends on competition, existing liquidity, and the types of deposits that move.

The risk is more acute during stress. A CBDC can make it easier to move funds rapidly from a private bank into a public liability, potentially accelerating a bank run. Digital transfers between banks already permit rapid withdrawals, but a universally accessible central bank instrument could offer a particularly attractive destination when confidence in the banking system weakens. Deposit insurance, bank supervision, and emergency liquidity remain relevant; CBDC does not replace these protections.

Proposed safeguards include individual holding limits, transaction limits, and tiered remuneration that makes large balances less attractive. Each entails trade-offs. A strict holding cap can constrain routine transactions or complicate business use. A low or negative return on large balances may discourage accumulation in normal conditions without being sufficient during a severe confidence shock. Restrictions on conversion during stress could undermine expectations of ready exchange and require a clear legal basis.

The central bank can offset reserve outflows by lending to banks or purchasing assets, but this changes its own balance sheet and role in credit allocation. Lending generally requires suitable collateral and exposes the central bank to operational and financial risks. A CBDC framework therefore interacts with the lender-of-last-resort function and prudential regulation rather than operating as an isolated payment innovation.

Monetary policy and the central bank balance sheet

CBDC does not automatically establish a new monetary-policy regime. A non-interest-bearing retail instrument with modest holding limits may behave mainly as a digital counterpart to cash. An interest-bearing CBDC available in large quantities could have more substantial effects on portfolio choices, bank deposit pricing, and the transmission of policy rates. The decisive variables are remuneration, eligibility, convertibility, and the alternatives available to holders.

An interest-bearing CBDC could provide a public reference return for liquid household assets. If consumers can readily shift funds into it, banks may have to adjust deposit rates more closely when the central bank changes its policy stance. This could strengthen part of the monetary transmission mechanism. The effect would be weaker where access is limited, switching is difficult, or banks provide valuable bundled services that make deposits attractive despite a lower return.

CBDC remuneration is distinct from the rate paid on reserves. The central bank could set the same rate, a lower rate, or a tiered schedule. For example, small balances might receive one rate and balances above a threshold another. Such a structure could distinguish payment-oriented holdings from large-scale saving. It would also increase administrative complexity, especially where one person uses multiple wallets or where firms need substantial working balances.

Debate sometimes associates CBDC with removing the effective lower bound on interest rates. A digital instrument can technically carry a negative nominal return, but that does not establish that substantially negative rates would be feasible. If cash remains readily available at par, holders can shift into banknotes, subject to storage, security, and handling costs. Legal constraints, public acceptance, and substitution into other assets also matter. Negative-rate capability is therefore a design possibility, not an inherent purpose or inevitable consequence of CBDC.

Issuance can affect seigniorage, the income associated with issuing monetary liabilities. If CBDC replaces non-interest-bearing banknotes but itself pays interest, the central bank's net income may decline, other things equal. If it replaces bank deposits and the central bank acquires interest-bearing assets, its gross income may increase, although operating expenses, remuneration, and risk must also be considered. The fiscal consequences depend on profit-remittance arrangements and the central bank's accounting framework.

CBDC also remains separate from fiscal policy. A government could distribute a legally authorized transfer through CBDC wallets, just as it can use bank accounts or payment cards. The payment channel does not determine the spending authority, eligibility rules, or financing. Likewise, creating a CBDC is not equivalent to quantitative easing: the latter concerns asset purchases and monetary conditions, whereas CBDC primarily specifies the form and accessibility of a central bank liability.

Privacy, legal status, and public governance

Retail CBDC raises questions about what information is generated, who can access it, and for what purposes. Cash usually permits face-to-face payments without a centralized transaction record. Digital payments commonly create records at service providers, network operators, or settlement institutions. A CBDC's privacy properties depend on architecture, data separation, retention rules, access controls, and law; public issuance alone does not determine whether it is more or less private than existing electronic payments.

A system can separate identity information from transaction processing. For example, a wallet provider may verify a customer while the core platform processes transfers using identifiers that do not directly disclose the customer's name. Such separation can reduce routine visibility without guaranteeing anonymity. Transaction patterns, metadata, and information held elsewhere may permit reidentification. Claims of privacy must therefore specify protection against whom: merchants, intermediaries, the central bank, other public authorities, or external attackers.

Compliance requirements introduce further distinctions. Rules against money laundering and terrorist financing may require customer identification, transaction monitoring, and reporting. Some designs envisage simplified requirements for low-value wallets and stronger checks for higher limits. The permissible thresholds and procedures are jurisdiction-specific. Technical capacity for anonymous transfers does not by itself make such transfers legally authorized, while identification does not necessarily justify unrestricted use of payment data.

Legal foundations cover issuance authority, ownership, finality, redemption, and the consequences of intermediary insolvency. Whether a central bank may issue physical currency does not automatically settle whether it may provide digital money to the public. Legislation may be needed to define the instrument and allocate responsibilities. Legal-tender status is a separate question: an instrument may be central bank money without every merchant being obliged to accept it, and acceptance obligations can contain exceptions.

Data governance determines who is accountable for collecting, storing, sharing, and deleting information. Relevant protections include purpose limitation, independent oversight, access logging, and enforceable restrictions on disclosure. Privacy-enhancing cryptographic techniques can support these protections, but cannot replace institutional safeguards. Public authorities may have lawful investigatory powers, and the conditions governing their exercise must be distinguished from routine operational access.

“Programmable money” is another contested expression. Conditional payments can release funds when specified requirements are met, while restrictions embedded in the currency itself might limit where, when, or by whom it can be spent. These are different arrangements. A general-purpose CBDC can support conditional payment services without giving its issuer unrestricted control over lawful purchases. Decisions about expiration, permitted uses, account freezing, and redress are matters of legal authority and governance, not unavoidable features of digital currency.

Technology, offline use, and operational resilience

A CBDC platform must prevent unauthorized creation, ensure valid transfers, and maintain consistent ownership records. A conventional database can perform these functions under centralized administration. Distributed ledger technology instead distributes records and validation responsibilities among multiple nodes. In a central bank setting, participation is normally permissioned: recognized institutions operate the system under agreed rules. The choice concerns governance, performance, resilience, and integration rather than a requirement to imitate public cryptocurrency networks.

Transaction capacity cannot be assessed solely by a peak “transactions per second” figure. Relevant measures include end-to-end latency, availability, processing under exceptional loads, recovery time, and performance when fraud controls and compliance checks are active. A platform capable of rapid internal transfers may still deliver slow payments if wallet providers, telecommunications networks, or merchant systems are unavailable. National deployment also requires software updates, secure key management, monitoring, and workable incident procedures.

Offline payments seek to allow transfers when one or both parties lack network connectivity. A device may hold a limited quantity of value or a secure record of spending authority, with transactions synchronized later. The fundamental difficulty is preventing double spending when there is no immediate access to a common ledger. Secure hardware, transaction counters, restricted balances, and limits on consecutive offline transfers can reduce risk, but they introduce costs and assumptions about device integrity.

Different meanings of “offline” must be distinguished. A payer without internet access may still transact through a connected merchant. A more demanding arrangement allows both parties to exchange value without a network, while another question is whether recipients may spend that value again before reconnecting. Greater offline flexibility generally makes fraud detection, loss allocation, and reconciliation harder. Final acceptance and provisional acceptance are not economically equivalent, particularly for merchants.

Cybersecurity encompasses more than protection of the central ledger. Attacks can target wallet applications, credential recovery, merchant terminals, software suppliers, and customer-support procedures. Social engineering may induce a user to authorize a technically valid but fraudulent payment. Security therefore requires layered controls and clear liability rules, not merely strong cryptography. The possibility of freezing, reversing, or compensating a transfer must be specified rather than assumed.

Operational resilience also requires contingency arrangements for power failures, telecommunications outages, natural disasters, and institutional failures. Geographically separated facilities and independent service providers can reduce common points of failure, although shared software or infrastructure may still create correlated risks. Continued access to cash or alternative payment channels can provide an additional safeguard. A CBDC designed to complement existing systems offers different resilience benefits from one that becomes the sole practical means of everyday payment.

Wholesale settlement and cross-border applications

Wholesale CBDC projects focus on settlement among financial institutions rather than ordinary consumer purchases. One major application is tokenization: representing financial assets and their ownership records on programmable platforms. If securities circulate on such a platform but payment requires movement through a separate system, participants face coordination and reconciliation problems. A wholesale CBDC can provide central bank money within, or closely connected to, the asset platform.

Delivery versus payment links the transfer of a security to the corresponding payment so that one occurs only if the other occurs. This reduces principal risk, but it does not eliminate all transaction risks. Participants may still face replacement costs, liquidity shortages, operational failures, or uncertainty about the legal effectiveness of the transfer. Settlement finality requires a legally enforceable point after which a transfer is unconditional and irrevocable; technical confirmation alone is insufficient.

Programmable platforms can coordinate transfers through a smart contract, meaning software that executes specified transaction rules. Such software can support atomic settlement, where linked transfers succeed together or do not occur. Atomicity can reduce some exposures while increasing prefunding requirements if participants must have all assets available at once. Existing systems often economize on liquidity through netting or intraday credit, so a technically simpler transaction is not necessarily the most liquidity-efficient arrangement.

Switzerland's Project Helvetia examined the settlement of tokenized assets in central bank money. Its phases explored both issuing wholesale central bank money on a distributed-ledger platform and linking that platform to an existing payment system. The Swiss National Bank began the Helvetia III pilot in December 2023, providing wholesale CBDC for real transactions on a regulated infrastructure. The experiment concerned a restricted wholesale environment, not a general-purpose digital franc for the public.

Cross-border applications seek to improve payments that otherwise involve multiple intermediaries, separate operating hours, currency conversion, and repeated compliance checks. Payment versus payment makes the final transfer of one currency conditional on the final transfer of another, reducing foreign-exchange principal risk. Projects including mCBDC Bridge, commonly called mBridge, and Project Dunbar tested arrangements involving multiple central banks and currencies. Their technical demonstrations did not by themselves establish universal access or resolve all legal questions.

Cross-border CBDC use introduces issues of access, jurisdiction, and monetary sovereignty. Authorities must determine which foreign institutions or individuals may hold each currency, how disputes are resolved, and how capital-flow rules apply. Widespread foreign access to an attractive retail CBDC could facilitate currency substitution in another economy, while wholesale access may be more narrowly controlled. Interoperability also requires common messaging, compatible compliance processes, and agreement on governance. The principal obstacles are therefore not exclusively technological: they include the allocation of authority and risk across national monetary systems.