IMF CBDC Handbook: The International Blueprint for Central Bank Digital Currencies

When a central bank decides to develop a digital currency, where does it begin? The technology choices are numerous and contested. The legal framework for a CBDC may require primary legislation in some jurisdictions. The policy questions — who can access a CBDC, under what conditions, for what purposes — touch fundamental questions about monetary sovereignty, financial inclusion, and the relationship between the state and citizens’ financial lives. And the interaction effects with commercial banking, monetary policy transmission, and financial stability are incompletely understood even by the world’s most sophisticated central banks.

For most of the 130-plus central banks currently developing or researching CBDCs, the internal expertise to navigate all of this from first principles does not exist. Central banks in small developing economies may have a handful of economists working on monetary policy research and a technology department focused primarily on maintaining existing payment system infrastructure. The task of designing a national digital currency from scratch would overwhelm these teams without external analytical support.

The IMF’s CBDC Handbook is the most comprehensive response to this capacity gap in the international system.

Structure and Scope

The Handbook is not a single document but a modular series of chapters addressing distinct aspects of CBDC design and policy — a deliberate architectural choice that allows central banks to engage with the portions most relevant to their circumstances without needing to process the entire body of work sequentially.

The design principles module addresses the foundational architecture questions: token-based versus account-based design, retail versus wholesale versus hybrid models, the role of intermediaries (whether CBDCs flow directly from the central bank to citizens or through commercial banks), and the programmability of the currency itself. Each design choice has policy implications — a retail CBDC that flows directly to citizens without commercial bank intermediaries has very different financial stability implications than a wholesale CBDC used only for interbank settlements.

The legal framework module addresses what many central banks discover late in the design process: that issuing a CBDC may require legal authority that current central bank legislation does not provide. In many jurisdictions, the legal tender framework defines currency in physical terms. Whether a digital token is legally equivalent to a banknote, whether CBDC holdings would be protected in a commercial bank insolvency, and whether the central bank could impose conditions on CBDC use (holding limits, expiry dates, geographic restrictions) are all questions that require legislative answers before technical implementation can proceed.

Retail vs. Wholesale: The Key Design Choice

The Handbook treats the retail versus wholesale distinction as the most consequential design decision a central bank makes, because it determines who the CBDC is for and what problem it is solving.

Retail CBDCs — accessible to households and businesses as a general-purpose payment instrument — have the potential to transform financial inclusion, reduce payment system costs, and provide a public digital payment infrastructure that does not depend on private sector intermediaries. They also raise the most complex policy questions: about privacy (a retail CBDC could give the central bank visibility into every citizen’s financial transactions), about financial stability (if citizens can instantly convert bank deposits into CBDC, runs on commercial banks become faster and more severe), and about the appropriate role of the state in retail financial services.

Wholesale CBDCs — accessible only to financial institutions for interbank settlement — raise fewer consumer protection and privacy concerns but have a more limited policy impact. They improve settlement efficiency for financial institutions and enable cross-border central bank digital money flows, but they do not directly address financial inclusion or retail payment system modernisation.

The Handbook provides analytical frameworks for assessing which model fits a given country’s circumstances, rather than prescribing a universal approach. For a country with high financial exclusion and an underdeveloped banking system, the retail model may offer transformative benefits. For a country with a sophisticated banking system but inefficient wholesale settlement infrastructure, the wholesale model may be more appropriate.

Privacy, Programmability, and the Limits of Design

Two policy dimensions in the Handbook have attracted the most attention from privacy advocates and civil liberties organisations: transaction privacy and programmability.

On privacy, the Handbook is honest about the fundamental tension. Any CBDC that is not fully anonymous creates a record of transactions that is, in principle, accessible to the central bank or to law enforcement through appropriate legal process. The Handbook discusses various privacy-preserving architectures — including zero-knowledge proof approaches that allow transaction validation without revealing transaction details — but acknowledges that no current CBDC design fully replicates the anonymity of physical cash. This is not merely a technical limitation: many CBDC designs intentionally preserve law enforcement access to transaction records for AML and sanctions compliance purposes, treating privacy as a value to be balanced against other legitimate public interests rather than as an absolute requirement.

On programmability — the ability to embed conditions in CBDC that constrain how it can be used — the Handbook again offers a balanced framework rather than a prescription. Programmability enables potentially valuable policy interventions: time-limited stimulus payments that must be spent rather than saved, earmarked social benefits that can only be used for specified categories of goods, automatic tax withholding. It also raises serious concerns about government overreach, financial autonomy, and the risk that programmability features could be weaponised by authoritarian governments against their populations.

Developing Country Applications

The Handbook’s most significant intellectual contribution may be its serious engagement with the different circumstances of developing economies. Advanced economy CBDC discussions tend to focus on efficiency improvements within already sophisticated financial systems — faster settlement, lower payment costs, competitive responses to private stablecoin development. These are meaningful but incremental improvements.

In many developing economies, the stakes are different in kind. High unbanked populations, expensive informal remittance channels, currency instability that drives dollarisation, and limited physical banking infrastructure mean that a well-designed retail CBDC could provide meaningful financial access to populations currently excluded from the formal financial system. The Bahamas’ Sand Dollar, Nigeria’s eNaira, Jamaica’s JAM-DEX, and several African CBDC experiments have all engaged with these possibilities — with mixed results that the Handbook incorporates as empirical reference points.

The financial stability risks also manifest differently in developing economies. In a country where banking system confidence is fragile, the option to convert deposits into CBDC at the click of a button could accelerate bank runs that in an advanced economy would unfold more slowly. The Handbook discusses holding limits, conversion rate limits, and non-remuneration of CBDC balances as tools for managing this risk — design choices specifically relevant to economies where banking system fragility is a genuine concern.

For central banks in Africa, Latin America, and Southeast Asia, the CBDC Handbook is not academic reading but practical policy infrastructure.