The Legal Boundary: Automate the Payment, Not the Currency

The legal question behind programmable payments is not whether code can execute a rule. It is whether the rule changes the legal and economic nature of the money that a person receives. This chapter uses the IMF’s analysis of retail and wholesale central bank digital currencies to examine that boundary: central-bank liability, currency status, legal tender, par convertibility, user rights, provider responsibility, and settlement finality. The result is not a universal legal answer, but a way to see why payment-level conditionality usually carries a different burden from asset-level restrictions.

The distinction matters because a central bank digital currency is not merely a new interface for an old balance. A legal system must decide what the instrument is, who may issue it, who may operate the platform, what rights users have, and how a transfer becomes final. Those decisions determine whether a digital payment can preserve the single, trusted monetary object that the programmable-payments framework treats as its starting point.

The legal identity of central-bank money

The IMF Note defines retail CBDC, or rCBDC, as a digital form of central bank money available to the general public. The definitions used by central banks and international institutions differ in wording, but the Note identifies four common traits: rCBDC is a liability of the central bank, available to the public, inherently digital, and designed to serve as money.

The first trait establishes the legal baseline. If rCBDC is a direct central-bank liability, users hold an asset linked to the monetary authority rather than a claim issued by the intermediary that provides the wallet or service account. In a two-tier model, private intermediaries handle customer-facing distribution and services, while the central bank handles issuance, redemption, and the core ledger in the background. The intermediary may fail, but that failure should not change the value of the central-bank liability held by the user.

That structure resembles the earlier distinction between an asset and a payment instruction. The wallet or front-end service is a way to access the asset; it is not necessarily the issuer of the asset. A programmable payment feature offered through that service may therefore determine when a central-bank liability moves without changing whose liability it is. By contrast, a condition that changes the permitted use, eligible holder, or expiry of the unit can alter the user’s rights in ways that go beyond operating a payment.

If rCBDC is intended to function as digital cash, legal treatment must address more than issuance. The IMF identifies currency features such as the State’s or its agent’s monopoly of issuance, nominal face-value treatment, legal tender, private-law privileges, and criminal-law protection. These features support the expectation that a unit of official money will be recognized and valued in a stable way. Their exact legal form varies by jurisdiction, and legal tender itself has no single globally established definition, but the underlying issue is consistent: can the instrument discharge a payment obligation and be accepted under the rules that give currency its public status?

Convertibility is central to that question.