Skip to main content
Skip to content
Guides

CBDCs, Privacy and Programmable Payments: What the Rules Actually Say

Compare digital euro, digital pound and SandDollar evidence. Separate payment conditions, privacy layers, wallet limits and proposed rules from live requirements.

CBDCs, Privacy and Programmable Payments: What the Rules Actually Say
Reading options: audio, text size & sections

What Matters

A CBDC’s label does not tell you who can see a payment or restrict it. The digital euro and digital pound proposals distinguish user-authorised conditional payments from issuer restrictions on money. Assess the actual jurisdiction, legal status, wallet layer and offline design. This evidence ledger replaces this page’s earlier blanket claims about surveillance and programmable control.

The useful question is specific: which actor can do what to which payment, under which rule? A central bank’s liability, a wallet provider’s identification process and a merchant’s payment condition are different parts of a system. Combining them into one claim that “money controls everyone” obscures both genuine risks and meaningful safeguards.

The same care is needed with reassurance. A promise that a central bank cannot identify online users does not establish that the customer’s wallet provider cannot identify them. An offline privacy design does not establish unlimited anonymous value transfer. A prohibition in a proposal is not proof that legislation has been enacted. Good scrutiny follows those boundaries.

Claim versus the documentary record

ClaimWhat the source supportsPractical consequence
Every CBDC is programmable money.The Commission’s digital euro proposal, Article 24, distinguishes conditional payments and prohibits programmable money. It remains a proposal in the cited text. [1]Read the actual currency restrictions and payment-service rules separately.
A pilot means issuance has been approved.The ECB’s pilot FAQ expressly separates pilot preparation from an issuance decision. [2]Record pilot, legislation and issuance as separate milestones.
Privacy means no intermediary knows the customer.The ECB distinguishes online intermediary identification from Eurosystem visibility, and describes a different offline model. [3]Ask whose visibility a privacy statement addresses.
All CBDC wallets use identical onboarding.SandDollar publishes different individual wallet tiers, including different identification requirements and limits. [4]Compare the actual tier, not just the product name.

Programmable payment or programmable money?

Consider two hypothetical instructions. In the first, a buyer authorises payment after a verified delivery. In the second, a currency issuer makes the received units unusable outside an approved category. Both involve software. Only the second imposes a restriction that travels with the money in this comparison.

The distinction matters for an autonomous agent. A household might authorise an agent to settle an electricity bill within a monthly cap. That cap is a delegated payment permission. It need not alter what the electricity supplier can do with the funds after receipt. The review should therefore identify the authorising party, the trigger, the ability to revoke the instruction and what happens when the trigger is disputed.

The Bank of England’s March 2026 design-phase update describes payments under conditions set and approved by users, while rejecting programmable money in its proposed architecture and legislative approach. That is a statement about the proposed digital pound, not a guarantee about every central bank project. [5]

A holding limit is another distinct control. It constrains the amount held in an account or wallet, not necessarily the categories in which money can circulate. Likewise, a sanctions-related account restriction, an anti-fraud pause and an expiring voucher have different legal bases and consequences. A useful assessment records them individually rather than using “programmable” as a catch-all.

Three cases, three evidence boundaries

Digital euro: a proposed retail design

The ECB’s current FAQ describes a potential digital euro, online and offline functionality, and an issuance decision that follows the legislative process. Its stated offline model would limit personal transaction details to payer and payee, while funding and defunding would involve anti-money-laundering checks. Its online model allows payment service providers to identify users while limiting identification by the Eurosystem. These are official design statements, not measurements made by DN. [3]

The operational questions follow directly. What happens when an offline device is lost? Which information is shared during funding? What are the value limits? Who handles a complaint? Those questions require implementation documents and final rules. A high-level privacy commitment cannot answer all of them.

Digital pound: distinguish the central ledger from the wallet provider

The Bank of England’s project page says no decision to introduce a digital pound has been made. Its proposed public-private structure gives intermediaries user-facing responsibilities, including identification and personal-data handling, while separating the Bank’s core infrastructure from those personal records. [6] [7]

That distinction changes the privacy audit. A reviewer needs to inspect wallet-provider retention, access controls, lawful disclosure and data sharing, as well as the central bank’s role. The proposed absence of personal data in one layer is valuable, but does not make the complete customer relationship anonymous. The scheme’s eventual law, rulebook and deployed technology would need to agree.

SandDollar: operational wallet rules are more concrete

SandDollar’s individual-wallet page publishes a Tier I holding limit of B$500 and a B$1,500 monthly transaction limit, with no government-issued identification requirement for enrolment. Tier II lists B$8,000 and B$10,000 respectively and requires government-issued identification. “No government-issued ID required” should not be rewritten as “no customer information collected.” These are the stated product rules reviewed on this date, not a universal CBDC template. [4]

The comparison demonstrates why project status matters. A live wallet’s published limits can be checked against a user’s intended transaction. A proposed future wallet requires a different conclusion: design evidence exists, but operational availability and final conditions remain unconfirmed.

DN CBDC Control Evidence Ledger

This instrument is a review table, not a numerical freedom or surveillance score. Complete one record for one jurisdiction, one wallet tier and one dated version. Its output is a set of supported statements and open questions. An unknown field remains unknown.

Record fieldEvidence to captureDecision the field supports
Issuer and liabilityStatute, terms or official architecture identifying the claim holder and issuer.Distinguishes central bank money from a deposit, stablecoin or payment message.
Current statusProposal, enacted framework, pilot, issuance decision or operating service, each dated.Prevents proposed features from becoming asserted current rights.
Visibility by actorData accessible to central bank, wallet provider, merchant and authorised authorities.Locates privacy exposure instead of assigning a single anonymity label.
Payment conditionsWho sets them, consent, revocation and dispute handling.Separates a user instruction from an issuer restriction.
Limits and interruptionHolding, transfer and offline limits; suspension powers; recovery and appeal route.Shows whether a particular payment remains possible during an incident.
Evidence maturityOfficial commitment, proposed law, binding rule, implementation test or observed incident.Stops a design promise being mistaken for an independently verified outcome.

Worked review: for an agent paying a supplier after delivery, the first decision is whether the agent has the customer’s authority. The next is whether the payment service supports the condition. The third is whether the supplier receives normally usable money. A documented answer to the first two does not establish the third. This sequence is original DN decision support; it does not assign a legal conclusion to any untested implementation.

What financial optionality actually requires

Optionality is a practical capability: another lawful way to pay, recover access or obtain help when one service fails. It depends on the recipient accepting the alternative, the user being able to access it, and the alternative’s own failure modes. Merely opening more trading accounts does not demonstrate those conditions.

Crypto also needs a precise privacy description. Bitcoin’s own guidance explains that transactions are public and persistent; identities can become linked to addresses through other information. Self-custody changes who controls signing authority. It does not make a public ledger invisible or remove an exchange’s identification requirements. [8]

For a business, the more useful contingency test is concrete: can payroll or a supplier payment be completed if a particular wallet provider is unavailable? Who can revoke an agent’s payment authority? Is a manual approval route documented? Can accounting records reconcile a delayed or duplicated instruction? Those questions apply to bank payments, CBDCs and crypto rails alike.

Methodology and limitations

DN compared primary documents by jurisdiction and by the actor each statement concerns. We have not audited code, tested offline privacy, measured user adoption or verified an enacted legal framework beyond the exact documents cited. The ledger deliberately avoids scoring incomparable designs. Its rows are prompts for evidence collection, not a certification that a system meets them.

The BIS survey is useful context for this restraint: its 2024 survey reports that design features, use cases and development stages vary across jurisdictions. Exploration cannot be counted as issuance. [9] The ledger should be refreshed when legislation, an issuance decision, a rulebook, wallet terms or a material operational incident changes the evidence.

Frequently asked questions

Can a CBDC be designed with intrusive controls?

Its controls must be assessed from the specific law and architecture. The fact that a technical capability is possible does not prove that every implementation enables it or gives every institution the same authority.

Does a ban on programmable money prohibit automatic payments?

Not in the distinction used by the cited European and UK documents. A user-authorised conditional payment is treated separately from restrictions embedded in the money itself. The relevant service still needs clear consent and dispute rules.

Does offline mean fully anonymous?

No universal conclusion follows. Examine the offline payment record, funding and defunding checks, device security, limits and recovery design. A privacy statement about one stage does not describe every stage.

Is this page predicting a global CBDC rollout?

No. It records specific documentary evidence as of 12 November 2026. No worldwide adoption forecast or inevitability claim is supported by this review.

Corrections and change log

12 November 2026: replaced the earlier universal surveillance and programmable-control framing; separated proposed designs from operational wallet rules; added the control-evidence ledger; corrected the claim that crypto is private by default. The canonical URL is retained. Send corrections with the jurisdiction, document version and relevant passage through the DN contact page.

Machine-readable review record

The record below is a bounded illustrative example. It is not a wallet scan, current-chain dataset or assessment of a deployed service. The schema identifier is an identifier, not a promised API endpoint. Downloads are local snapshots; no schedule or automatic refresh is active.

Primary sources

  1. European Commission digital euro proposal, Article 24 — Proposed distinction between conditional payment transactions and programmable money.
  2. ECB digital euro pilot FAQ — Pilot preparation does not constitute issuance approval.
  3. ECB digital euro FAQ — Project status and distinct online/offline privacy designs; official commitments, not DN measurement.
  4. SandDollar individual wallets — Published Tier I/II identification and holding/transaction limits.
  5. Bank of England design-phase update — User-authorised conditions versus programmable money; proposed architecture and legislation.
  6. Bank of England digital pound project — Current project page states no decision to introduce the digital pound.
  7. Bank of England intermediary roles design note — Proposed intermediary KYC and personal-data role distinct from core infrastructure.
  8. Bitcoin privacy guidance — Public persistent transactions and identity-linkage risk.
  9. BIS 2024 CBDC survey results — Jurisdictions differ in CBDC stage, design and use cases.

Get the most talked about stories directly in your inbox

Join the Decentralised News briefing for independent crypto, DeFi and AI analysis. No spam, unsubscribe anytime.