Compliance & Enforcement

1. CBDC AML/CFT Framework

1.1 FATF Classification: CBDC as Fiat Currency

The foundational principle of CBDC compliance is the FATF's classification of CBDCs as digital representations of fiat currency, not virtual assets. This classification, articulated in the FATF's October 2021 Updated Guidance for a Risk-Based Approach to Virtual Assets and VASPs, has three critical regulatory consequences:

1. CBDCs fall under existing AML/CFT frameworks for traditional currency — Recommendations 10 through 21 (financial institution obligations), not the newer VASP regime under Recommendation 15 / Interpretive Note to R.15.
2. CBDC intermediaries are classified as financial institutions (FIs) or designated non-financial businesses and professions (DNFBPs), not as Virtual Asset Service Providers (VASPs). This means they must perform customer due diligence (CDD), record-keeping, suspicious transaction reporting (STR), and sanctions screening under the mature FI compliance framework.
3. The regulatory infrastructure is well-established — unlike the still-evolving VASP regime, FI obligations have decades of implementation history and supervisory practice.

However, the FATF notes that CBDCs may present different or higher AML/CFT risks than standard fiat currencies given their digital nature, and that these risks should be addressed by central banks prior to issuance. The FATF takes a technology-neutral stance: functionally equivalent products face the same risk-based standards regardless of underlying technology.

Source: FATF, "Updated Guidance for a Risk-Based Approach to Virtual Assets and VASPs," October 2021. https://www.fatf-gafi.org/en/publications/Fatfrecommendations/Guidance-rba-virtual-assets-2021.html

Note on the CBDC/VASP boundary in practice. While the retail CBDC itself sits under the FI regime, several jurisdictions have moved to bring the adjacent crypto/stablecoin ecosystem under a separate VASP regime — precisely because those instruments are NOT CBDCs and would otherwise escape AML/CFT cover. Ghana's Virtual Asset Service Providers Bill 2025 (passed by Parliament December 2025; jointly administered by the Bank of Ghana and the SEC; virtual assets are NOT legal tender) is the clearest 2025-26 example, and is distinct from the still-unlaunched eCedi. Brazil's BCB Resolutions 519/520/521 (effective 2 February 2026) operationalize an equivalent VASP/stablecoin framework alongside the (now-rebuilt) Drex pilot. China takes the opposite tack, banning the adjacent ecosystem outright (Yinfa No. 42, see §2.3). The lesson: a CBDC compliance regime is incomplete unless the jurisdiction has also decided how it treats the stablecoins and VASPs that will sit next to the CBDC.

1.2 How FATF Recommendations Apply to CBDC

The following FATF Recommendations are directly applicable to CBDC systems:

The February 2025 FATF Plenary approved amendments to Recommendation 1 and its Interpretive Note to better support financial inclusion, explicitly requiring countries to allow and encourage simplified measures in lower-risk scenarios — directly relevant to tiered KYC for CBDC wallets.

Source: FATF, "FATF updates Standards and consults on guidance to better promote financial inclusion," February 2025. https://www.fatf-gafi.org/en/publications/Fatfrecommendations/update-standards-promote-financial-conclusion-feb-2025.html

1.3 Travel Rule Applicability to CBDC

Because CBDCs are classified as fiat currency, cross-border CBDC transactions are subject to the travel rule under FATF Recommendation 16 (wire transfers), not the Interpretive Note to Recommendation 15 (VA transfers between VASPs).

Key requirements under R.16:

• Ordering financial institutions must include originator and beneficiary information with CBDC transfers
• Intermediary institutions must ensure originator information accompanies the transfer throughout the payment chain
• Beneficiary institutions must verify the identity of the beneficiary
• For cross-border CBDC transfers above applicable thresholds, full originator and beneficiary data must be transmitted

June 2025 Revision of R.16: The FATF Plenary agreed changes to Recommendation 16 in June 2025 that modernize the standard to cover all "payments or value transfers and related messages," not just traditional wire transfers. This expansion has direct implications for CBDC:

• More detailed and structured information is required for both originators and beneficiaries, especially for payments over EUR 1,000
• New fields include originator address, date of birth, and Legal Entity Identifiers (LEI) for legal persons
• Alignment with ISO 20022 messaging standard (already adopted by most CBDC platforms)
• Implementation deadline: end of 2030

Critically, CBDC intermediaries follow established wire transfer compliance procedures and can leverage existing SWIFT/ISO 20022 infrastructure. There is no need for the separate travel rule technology solutions (e.g., TRISA, Travel Rule Protocol) developed for VASP-to-VASP transfers.

Sources:

• FATF, "FATF updates Standards on Recommendation 16 on Payment Transparency," June 2025. https://www.fatf-gafi.org/en/publications/Fatfrecommendations/update-Recommendation-16-payment-transparency-june-2025.html
• Mayer Brown, "FATF Revises AML Standards For Certain Funds Transfers," August 2025. https://www.mayerbrown.com/en/insights/publications/2025/08/fatf-revises-aml-standards-for-certain-funds-transfers
• CGAP, "The FATF's Revised Travel Rule: Key Changes for Payment Transparency." https://www.cgap.org/blog/fatfs-revised-travel-rule-key-changes-for-payment-transparency

1.4 Tiered KYC Models for CBDC Wallets

The FATF's risk-based approach explicitly supports tiered customer due diligence for CBDC, enabling financial inclusion while maintaining AML/CFT safeguards. The July 2025 Financial Inclusion Guidance further reinforced that simplified CDD measures should be encouraged where risks are lower.

Standard three-tier framework:

Specific thresholds and requirements are set by national authorities based on country risk assessments — the FATF does not prescribe uniform numbers. This jurisdiction-specific calibration creates potential inconsistencies across borders and complicates cross-border CBDC interoperability. Among the 20 jurisdictions surveyed, observed tiers range from China's 4-category wallet system and Nigeria's Tier 0–3 ladder to the Bahamas' 3-tier KYC, India's basic/full-KYC split, and the Eastern Caribbean's two-tier Value-Based/Registered wallets — confirming convergence on the structure of tiered KYC but wide divergence on thresholds.

Source: FATF, "Guidance on Financial Inclusion and AML/CFT Measures," July 2025. https://www.fatf-gafi.org/en/publications/Financialinclusionandnpoissues/guidance-financial-inclusion-aml-tf-measures.html

2. Comparative Analysis

2.1 Where the 20 Jurisdictions Sit on the Deployment Spectrum

Compliance and enforcement frameworks only "bite" where a CBDC actually moves value. Of the 20 jurisdictions surveyed, the live/launched footprint is narrow, and precise classification matters because an unlaunched CBDC has no transactions to monitor:

• Launched / live (6): Bahamas (Sand Dollar), Nigeria (eNaira), Jamaica (JAM-DEX), Eastern Caribbean (DCash — pilot concluded Jan 2024, DCash 2.0 successor suspended Feb 2026), China (e-CNY — operational at pilot scale, not a formal nationwide legal-tender launch), and India (e₹ — pilot, retail + wholesale). Of these, only the Bahamas, Nigeria and Jamaica are unambiguously launched general-purpose retail CBDCs; DCash is suspended, and China/India remain formally pilots despite operating at scale.
• Anti-CBDC / opposed (1): the United States — the only major economy to formally bar CBDC development by executive action (EO 14178, in force). Statutory bans (H.R. 1919; the ROAD to Housing moratorium) passed both chambers in differing, unreconciled forms and are NOT enacted; the operative alternative is a stablecoin-first strategy under the GENIUS Act (S.1582 / Public Law 119-27). Fed Chair Kevin Warsh (sworn in 22 May 2026) reaffirmed opposition to a retail CBDC. For compliance purposes, there is no US CBDC to regulate.
• Pilot with mandated launch ahead (1): Russia — narrow live government/budget use since 1 Jan 2026; full large-scale launch legally mandated for 1 Sep 2026.
• Active pilot / advanced preparation, not launched (the remainder): EU (digital euro — preparation phase concluded Oct 2025, Governing Council moved to the next phase 30 Oct 2025; ECON Committee vote scheduled 23 Jun 2026), Brazil (Drex — Besu platform decommissioned 4 Nov 2025, rebuilding), Australia (Project Acacia final report 18 May 2026), South Korea, Singapore, Thailand, Japan, Canada, UK, Sweden, Ghana (pilot declared 'completed' 22 May 2026, designing wholesale/cross-border), and South Africa (Position Paper 27 Nov 2025 — 'no compelling immediate need' for a retail CBDC).

Aggregate read (N = 20): 6 launched/live (3 unambiguous retail launches + DCash suspended + 2 pilot-scale), 1 anti-CBDC, 1 pilot-with-mandated-launch, and the balance in active-pilot or pre-issuance research. Every one of the launched/live retail CBDCs operates a non-anonymous, tiered-KYC, intermediated distribution model — confirming that, in practice, no live CBDC offers cash-equivalent anonymity at scale.

2.2 Jurisdiction-by-Jurisdiction AML/CFT Compliance Matrix

The matrix below profiles the compliance-relevant design of the jurisdictions where a CBDC is live, mandated, or in advanced preparation (the cases where AML/KYC/sanctions framing is concrete), benchmarked against the FATF standard.

2.3 Notable AML/Sanctions/Enforcement Developments Across the Wider Set

Beyond the five profiled above, several 2025-26 developments sharpen the compliance picture across the full 20-jurisdiction set:

• China — Yinfa No. 42 (6 Feb 2026): the PBOC notice formalizes a ban on RMB-linked stablecoins and RWA tokenization with extraterritorial reach, deliberately channeling private digital-value activity through the e-CNY. Combined with the April 2026 doubling of authorized operators to 22 banks and the Jan 2026 reclassification toward a deposit-money model, this concentrates AML/CFT obligations on a tightly supervised operator set rather than an open ecosystem.
• Russia — non-anonymity is mandatory, not optional: the CBR explicitly states settlements "do not provide for the anonymity of payments," and on 6 Feb 2026 tightened ESIA registration and ID verification ahead of the 1 Sep 2026 large-scale launch. Compliance here is enforced structurally (one wallet per person on the CBR platform, unique identifiers) rather than via intermediary discretion.
• Ghana — VASP Bill 2025 (Dec 2025): Parliament passed the Virtual Asset Service Providers Bill, establishing crypto/VASP licensing jointly under the Bank of Ghana and the SEC (virtual assets are NOT legal tender). This is distinct from the eCedi, whose pilot was declared "completed" on 22 May 2026 with no enabling legislation passed — meaning Ghana's near-term AML/CFT enforcement surface is the VASP regime, not the (unlaunched) CBDC.
• Brazil — VASP/stablecoin operationalization: BCB Resolutions 519/520/521 (effective 2 Feb 2026) bring VASPs and fiat-referenced stablecoins (classified as FX under Resolution 521) into the AML/FX perimeter, even as the Drex CBDC platform itself was decommissioned (Besu shut down 4 Nov 2025) and is being rebuilt with a narrowed credit/collateral scope.
• South Africa — Position Paper (27 Nov 2025): SARB concluded there is "no compelling immediate need" for a retail CBDC; its compliance focus is wholesale (Project Khokha 2x, including bank-issued stablecoins for regional African settlement) under POPIA, not a retail AML/CFT regime that does not yet exist.
• South Korea — compliance over privacy by design: BOK Governor Rhee stated the deposit-token/wholesale design "chose to improve compliance at the sacrifice of privacy"; full anonymity was rejected specifically to preserve wallet-freezing/AML capability. PIPA amendments (Feb 2026) raise data-breach fines to up to 10% of revenue.
• Nigeria — enforcement pivot to the adjacent ecosystem: the CBN's 31 Mar 2026 VASP AML/CFT supervisory pilot covers cNGN and crypto exchanges (Flutterwave, KuCoin, Paystack and others) under FATF Travel Rule obligations — but explicitly NOT the eNaira, underscoring that the live CBDC has become largely dormant while the regulator's AML attention shifts to private stablecoins.

2.4 Key Observations from the Comparative Matrix

Privacy spectrum: The jurisdictions span a wide privacy range. The EU digital euro offers the strongest privacy protections (offline cash-like privacy, pseudonymised online settlement where the Eurosystem cannot identify users). Russia sits at the opposite extreme with explicitly non-anonymous design and no judicial oversight for account freezes — and has mandated that posture for its 1 Sep 2026 launch. China occupies a middle ground with "controllable anonymity" that provides technical privacy for small transactions but retains state surveillance capability. Among launched CBDCs specifically, none offers true cash-equivalent anonymity.

Tiered KYC convergence, threshold divergence: Every launched or preparing jurisdiction has adopted some form of tiered KYC, though thresholds vary dramatically. Nigeria's Tier 0 cap of N20,000/day (~USD 12) is among the lowest globally, while China's Category 4 wallet allows CNY 2,000/payment (~USD 275) — over 20 times higher. This inconsistency is a direct consequence of FATF delegating threshold-setting to national authorities (R.1, R.10).

Enforcement asymmetry: Russia and China embed enforcement mechanisms directly into the CBDC platform (programmable spending restrictions, centralized surveillance, operator scoring). South Korea makes the compliance-over-privacy trade-off explicit. The EU and Bahamas rely on intermediary-level compliance with regulatory oversight. Nigeria's enforcement is weakened by institutional capacity constraints despite a formal framework — and its regulator has in practice redirected AML/CFT supervisory energy toward private stablecoins/VASPs (cNGN pilot) rather than the dormant eNaira.

The adjacent-ecosystem question: A recurring 2025-26 pattern is that the consequential AML/CFT enforcement action is happening next to the CBDC rather than on it — China bans RMB stablecoins to protect e-CNY's monopoly; Ghana and Brazil stand up VASP regimes while their CBDCs stall; Nigeria supervises cNGN/exchanges while the eNaira idles. A CBDC compliance strategy that ignores the stablecoin/VASP perimeter is therefore structurally incomplete.

3. CBDC as AML Tool

3.1 How CBDC Can Enhance AML Compliance

CBDC platforms offer compliance capabilities that are technically superior to both physical cash and existing digital payment systems. These capabilities fall into four categories:

A. Programmable Compliance (Smart Contract Enforcement)

Smart contracts embedded in CBDC platforms can automate regulatory compliance in real-time, shifting AML from ex-post reporting to pre-settlement enforcement:

• Sanctions screening oracles — Smart contracts can check wallet addresses against sanctions lists before settling a transaction. Russia's digital ruble has demonstrated this with 17,000+ smart contract executions during its pilot (CBR self-reported), including conditional spending for targeted budget funds with the governments of Tatarstan and the Chuvash Republic.
• Transaction limit enforcement — Wallet-tier limits are automatically enforced at the platform level, making it technically impossible to exceed daily/monthly caps without upgrading KYC.
• Conditional spending ("coloured funds") — Funds can be programmatically restricted to approved use categories. This has been deployed in China's e-CNY (campus consumption, prepaid business management), in India's purpose-bound money welfare pilots (PMGKAY food currency, state subsidy schemes), and in South Korea's Project Hangang Phase 2 deposit-token government subsidies (EV charging, childcare, regional vouchers).

Sources:

• Bank of Russia, "Digital Ruble Current Status June 2025" (pilot figures CBR self-reported). https://www.cbr.ru/Content/Document/File/180336/digital_ruble_30062025_en.pdf
• BIS Papers No. 123, "E-CNY: main objectives, guiding principles and inclusion." https://www.bis.org/publ/bppdf/bispap123_e.pdf

B. Real-Time Transaction Monitoring

Unlike batch-processed card network data or post-hoc bank reconciliation, CBDC platforms provide the central bank with real-time visibility into transaction flows:

• Pattern detection algorithms can flag suspicious activity as it occurs, not days later
• Network analysis can identify structuring, smurfing, and layering patterns across the entire CBDC ecosystem simultaneously
• Threshold-based automatic reporting to FIUs can be embedded at the platform level

C. Enhanced Audit Trails

Every CBDC transaction creates an immutable, centrally recorded audit trail. This contrasts with the current system where banks maintain siloed records and FIUs must reconstruct transaction chains from multiple institutions:

• Law enforcement gains a single source of truth for financial investigations
• Cross-institutional tracing (following funds across intermediaries) becomes trivial rather than requiring months of subpoenas
• Record-keeping obligations (R.11) are satisfied by design rather than by intermediary compliance

D. Financial Intelligence Capabilities

CBDC data can enhance national financial intelligence capacity:

• Aggregate transaction flow data provides macro-level economic intelligence without identifying individuals
• Cross-referencing CBDC transaction patterns with external data (tax records, customs declarations) can identify discrepancies
• Real-time economic indicators derived from CBDC flows can inform monetary and fiscal policy

3.2 Risk: CBDC as Surveillance Instrument

The same technical capabilities that make CBDC an effective AML tool also create the risk of comprehensive state financial surveillance. This risk has materialized in practice:

Russia — The surveillance model:

• The CBR has explicitly stated that "digital ruble settlements do not provide for the anonymity of payments" and that "unique identifiers make it possible to track the circulation of digital rubles"
• Combined with a 2025 law allowing authorities to freeze bank accounts without court orders, the digital ruble enables direct state control over holdings without judicial oversight
• On 6 Feb 2026 Russia tightened ESIA registration and ID verification ahead of the legally-mandated 1 Sep 2026 large-scale launch — hardening, not softening, the non-anonymous posture
• The government has previously frozen accounts of opposition figures (e.g., Alexei Navalny's Anti-Corruption Foundation)
• Freedom House rates Russia at 16/100 for political freedom; the HRF CBDC Tracker raises significant financial-surveillance concerns and rates the digital ruble's privacy "Very Weak"

Source: Human Rights Foundation CBDC Tracker, "Russia." https://cbdctracker.hrf.org/currency/russian-federation (accessed March 2026)

China — The "controllable anonymity" model:

• The PBOC retains the technical capability to trace any transaction when deemed necessary through legal process
• Officials acknowledge that "big data analysis" can flag suspicious patterns even in phone-number-only wallets
• The system provides less privacy than physical cash despite marketing as "anonymous for small amounts"
• The interaction between PIPL (Personal Information Protection Law) obligations and PBOC data access capabilities has not been publicly clarified
• The Yinfa No. 42 ban on RMB-linked stablecoins (6 Feb 2026) removes a private alternative, narrowing the channels through which value can move outside the monitored e-CNY rails

Source: DigiChina (Stanford), "Lexicon: 'Controllable Anonymity' or 'Managed Anonymity' and China's Digital Yuan." https://digichina.stanford.edu/work/lexicon-controllable-anonymity-or-managed-anonymity-and-chinas-digital-yuan/

Nigeria — Coercion and distrust:

• The CBN's December 2022 naira redesign and cash-withdrawal limits, designed partly to force digital adoption including eNaira, triggered protests, bank attacks, and a severe liquidity crisis
• Cambridge University's Journal of African Law found the CBN "misapprehends the meaning and scope of informed consent to data processing, allows monitoring and tracking of users, and fails to protect children and other vulnerable groups"
• The HRF CBDC Tracker notes Nigeria's "corruption issues and track record of silencing dissent" heighten financial-control risks
• The compliance machinery proved moot in practice: with ~98.5% of wallets inactive after one year (IMF), there was little CBDC activity left to monitor — and by 2025-26 the CBN had pivoted supervisory attention to cNGN/VASPs

Source: Cambridge Core, "Assessing the Legal Status of the eNaira and Its Potential for Privacy and Inclusion." https://www.cambridge.org/core/journals/journal-of-african-law/article/same-naira-more-possibilities-assessing-the-legal-status-of-the-enaira-and-its-potential-for-privacy-and-inclusion/19189464219A6786DE28C68B5E28D67D

3.3 Balance Between Compliance Utility and Privacy Rights

The central design challenge for CBDC compliance is reconciling three competing objectives:

1. AML/CFT effectiveness — The state's legitimate interest in detecting and preventing illicit finance
2. Privacy protection — The individual's right to financial privacy, protected under constitutional law in most democracies and by instruments such as the GDPR, PIPL, POPIA, PIPA, LGPD, and the ICCPR
3. Financial inclusion — The need to serve unbanked populations who cannot meet stringent identity requirements

Privacy-preserving compliance technologies offer a partial resolution:

Sources:

• BIS, "Project Tourbillon: Exploring privacy, security and scalability for CBDCs." https://www.bis.org/publ/othp80.pdf
• BIS, "Project Aurum 2.0: Improving privacy for retail CBDC payment." https://www.bis.org/about/bisih/topics/cbdc/aurum2_0.htm
• ECB, "Preparation phase closing report," October 2025. https://www.ecb.europa.eu/euro/digital_euro/progress/html/ecb.deprp202510.en.html

The EDPB/EDPS recommendation (Joint Opinion 02/2023) is the most significant regulatory intervention on this tension to date. The European data protection authorities strongly recommended introducing a privacy threshold below which neither offline nor online low-value transactions are traced for AML/CFT purposes — effectively extending cash-like privacy into the digital domain for small amounts. With the ECB's preparation phase concluded (October 2025) and the European Parliament's ECON Committee vote on the draft Regulation scheduled for 23 June 2026, whether this recommendation is codified into the final digital euro Regulation will set the global benchmark for privacy-preserving CBDC compliance.

Source: EDPB, "Joint Opinion 02/2023 on the establishment of the digital euro," October 17, 2023. https://www.edpb.europa.eu/our-work-tools/our-documents/edpbedps-joint-opinion/edpb-edps-joint-opinion-022023-proposal_en

4. What Works and What Doesn't

4.1 What Works

A. Tiered KYC with Risk-Based Calibration

Every launched jurisdiction has adopted some form of tiered KYC, and the approach has proven both practically viable and FATF-compliant. China's 4-category wallet system is the most extensively tested at scale (2.25 billion wallets, 3.48 billion cumulative transactions as of late 2025 — PBOC self-reported aggregate data). The Bahamas' 3-tier model, while suffering from low adoption, demonstrates sound design for small island developing states with correspondent-banking dependencies.

The key success factor: calibrating tier thresholds to local economic conditions. China's Category 4 wallet (CNY 2,000/payment) is set at a level meaningful for daily commerce. Nigeria's Tier 0 (N20,000/day, ~USD 12) is too restrictive for practical use, contributing to the eNaira's failure as a financial-inclusion tool.

B. Two-Tier Distribution with Intermediary Compliance

All launched jurisdictions use a two-tier model where the central bank issues CBDC and commercial banks/PSPs handle end-user compliance (KYC, AML monitoring, STR filing). This model works because:

• It leverages existing compliance infrastructure at financial institutions
• It avoids the central bank becoming a retail service provider (a lesson Nigeria learned the hard way)
• It distributes compliance costs across the financial sector
• It creates competitive incentives for intermediaries to serve users efficiently

C. AML by Design (Embedding Compliance in Architecture)

The FATF recommends that CBDC systems embed AML/CFT compliance by design — "AML by design" — rather than retrofitting compliance as an afterthought. The EU digital euro's N-XT settlement engine exemplifies this: its UTXO model natively supports privacy at the settlement layer while enabling compliance at the intermediary layer. The architecture was designed from inception to make it technically impossible for the Eurosystem to identify users or infer payment patterns — privacy is structural, not policy-dependent.

D. Automated Transaction Monitoring at Platform Level

Platform-level monitoring (as opposed to institution-level monitoring) provides a single view of all CBDC transactions, enabling detection of patterns invisible to any single intermediary. The Bahamas' real-time AML/CFT engine and China's centralized ledger both enable cross-institutional pattern detection. Russia's unique-identifier system, while raising severe privacy concerns, demonstrates the technical capability for comprehensive transaction tracing.

4.2 What Doesn't Work

A. Coercive Adoption Strategies

Nigeria's naira redesign and cash-restriction policy (December 2022) is the definitive case study in failed CBDC-adjacent coercion. The attempt to force digital adoption by restricting cash triggered:

• Protests and attacks on bank branches
• A severe liquidity crisis devastating the large informal sector
• Deepened public distrust of both the CBN and the eNaira
• The government's eventual retreat (extending old-banknote validity by late 2023)

The lesson: mandatory merchant acceptance (as in Russia's 1 Sep 2026 mandate and the proposed EU regulation) is very different from restricting alternatives. The former expands the CBDC acceptance network; the latter destroys trust.

B. Full De-Anonymisation Without Judicial Safeguards

Russia's approach — explicit non-anonymity combined with account-freeze powers without court orders, now hardened via the Feb 2026 ESIA tightening — has produced the predictable result: polling indicates over 50% of Russians are unwilling to use the digital ruble for daily transactions, and roughly half view it as a tool for tighter state control (media-sourced, indicative only). Even senior banking figures (Sberbank CEO German Gref) have expressed doubts about consumer benefits.

Full de-anonymisation only "works" in the narrow sense of maximising state surveillance capability. It fails as a compliance strategy because it:

• Drives users to alternative, less regulated payment channels
• Reduces voluntary adoption, forcing reliance on mandates
• Creates an instrument of political control that undermines rule of law

C. Compliance Without Value Proposition

The eNaira's compliance framework (4-tier KYC, AML engine) was technically adequate but irrelevant because the underlying product had no value proposition. 98.5% of wallets were inactive after one year (IMF, May 2023; self-reported figures). Compliance infrastructure is necessary but not sufficient — if users do not adopt the CBDC, the compliance framework has nothing to monitor. Jamaica's JAM-DEX shows a milder version of the same pattern: growth (+550% transaction value YoY in 2025, BOJ self-reported) is concentrated among existing users at ~0.1% of currency in circulation, so the compliance surface remains thin.

D. Undefined Privacy-Compliance Boundaries

China's "controllable anonymity" model suffers from a fundamental legal ambiguity: the specific interplay between PIPL obligations and the PBOC's data access capabilities has not been publicly clarified. No public enforcement actions or regulatory guidance specifically address PIPL compliance in the context of e-CNY data collection. This ambiguity undermines both privacy claims and compliance certainty.

The EU's FDPM (Fraud Detection and Prevention Mechanism) faces a similar critique from the EDPB/EDPS: the processing of personal data within the FDPM "lacks foreseeability" — meaning the scope and conditions of data processing are not clearly defined, creating legal uncertainty for both operators and users. Brazil's Drex pivot is the starkest evidence of this boundary problem: privacy emerged as "the single most consequential obstacle," with ZKP approaches (Zether, Starlight, Rayls, Nova) all judged not production-mature, contributing to the decommissioning of the Besu platform in November 2025.

5. Recommended Framework

5.1 Structural Principles

A compliance-effective CBDC framework should be built on five structural principles derived from the evidence across the 20 jurisdictions:

Principle 1: AML by Design, Not Retrofit

Compliance capabilities must be embedded in the CBDC architecture from inception. The central bank and AML/CFT authorities should be engaged during the design phase, not after deployment. The legal framework should be enacted before or concurrent with pilot programs — a gap visible in Ghana (eCedi piloted with no enabling legislation) and China (digital RMB recognised only in a still-unenacted draft PBOC Law).

• Best practice: EU digital euro — N-XT settlement engine designed with privacy-at-settlement and compliance-at-intermediary from inception
• Anti-pattern: Nigeria eNaira — compliance framework bolted onto an account-based system with no clear differentiation from existing bank compliance

Principle 2: Privacy-Preserving Compliance by Default

The privacy architecture should minimise data exposure while maintaining legally mandated audit trails. Privacy should be a technical guarantee (structural), not merely a policy commitment (discretionary).

• Deploy blind signatures or zero-knowledge proofs for low-value transactions
• Use UTXO-based or token-based models to prevent the central bank from accessing individual transaction data
• Store offline transaction data in tamper-proof secure elements inaccessible to any party except law enforcement under lawful process
• Establish a clearly defined, legally enforceable privacy threshold below which transactions are not traced for AML/CFT purposes (the EDPB/EDPS recommendation for the digital euro)

Principle 3: Risk-Based Tiered KYC Calibrated to Local Conditions

Tier thresholds must reflect local economic realities (average daily transaction values, informal sector size, poverty levels) rather than arbitrary round numbers. The FATF's July 2025 Financial Inclusion Guidance reinforces that simplified measures should be encouraged — not merely permitted — for lower-risk scenarios.

Recommended tier structure:

Principle 4: Intermediary-Level Compliance with Platform-Level Intelligence

The two-tier model should assign compliance obligations as follows:

• Intermediaries (banks, PSPs): Customer onboarding, KYC verification, transaction-level AML monitoring, STR filing, sanctions screening of customers
• Platform (central bank): Aggregate analytics, cross-institutional pattern detection, sanctions list maintenance, regulatory data sharing with FIU, system-level fraud detection
• Clear data access rules: The central bank should not have access to individual user identity at the platform level. Identity data remains with intermediaries and is disclosed to law enforcement only under lawful process. (Russia's one-wallet-per-person CBR-platform model is the cautionary counter-example, concentrating identity at the central bank.)

Principle 5: Enforceable Legal Limits on State Access

Every CBDC system must include legally enforceable constraints on when and how government authorities can access individual transaction data. These constraints should be:

• Codified in statute (not merely policy or regulation)
• Subject to judicial review (court-order requirement for individual data access)
• Transparent (regular publication of aggregate access statistics)
• Time-limited (data-access warrants must specify scope and duration)

5.2 Transaction Monitoring Architecture

Recommended three-layer monitoring model:

Layer 1: Intermediary Monitoring (Real-Time)
  - KYC verification at onboarding
  - Transaction-level sanctions screening
  - Threshold-based STR triggering
  - Customer risk scoring

Layer 2: Platform Analytics (Near-Real-Time)
  - Cross-institutional pattern detection
  - Aggregate flow analysis (without individual identification)
  - Anomaly detection using machine learning
  - Network analysis for structuring/smurfing patterns

Layer 3: FIU Intelligence (Batch + On-Demand)
  - STR aggregation and analysis
  - Cross-referencing with external intelligence
  - International information sharing (Egmont Group)
  - Targeted investigation support (with judicial authorisation)

5.3 Cross-Border Compliance

For multi-CBDC platforms (e.g., mBridge, BRICS Bridge, future EU TIPS interlinking), the following compliance requirements apply:

• R.16 compliance for all cross-border CBDC transfers: full originator/beneficiary data in ISO 20022 format
• Jurisdictional conflict resolution: Participating central banks must agree ex ante on which country's AML/CFT framework governs each transaction type (originator jurisdiction, beneficiary jurisdiction, or platform rules)
• Sanctions screening at multiple points: Both originating and receiving intermediaries must screen against their respective national sanctions lists, plus the platform must screen against any platform-level restricted lists — a point of acute friction for sanctions-circumvention-oriented initiatives such as Russia's BRICS Bridge, which key partners (China, India, South Africa) have approached with limited enthusiasm
• Data sharing agreements: Bilateral or multilateral MOUs between participating FIUs for sharing suspicious activity information

6. Decision Matrix

6.1 Compliance Design Decision Matrix

Use this matrix to evaluate CBDC compliance architecture decisions. Each row represents a design choice; columns indicate the trade-off implications.

6.2 Jurisdictional Readiness Checklist

Before launching a CBDC, a jurisdiction should confirm the following compliance prerequisites:

6.3 Risk Assessment Framework

Sources

Primary Regulatory Sources

• FATF, "Updated Guidance for a Risk-Based Approach to Virtual Assets and VASPs," October 2021: https://www.fatf-gafi.org/en/publications/Fatfrecommendations/Guidance-rba-virtual-assets-2021.html
• FATF, "FATF updates Standards on Recommendation 16 on Payment Transparency," June 2025: https://www.fatf-gafi.org/en/publications/Fatfrecommendations/update-Recommendation-16-payment-transparency-june-2025.html
• FATF, "Guidance on Financial Inclusion and AML/CFT Measures," July 2025: https://www.fatf-gafi.org/en/publications/Financialinclusionandnpoissues/guidance-financial-inclusion-aml-tf-measures.html
• FATF, "FATF updates Standards and consults on guidance to better promote financial inclusion," February 2025: https://www.fatf-gafi.org/en/publications/Fatfrecommendations/update-standards-promote-financial-conclusion-feb-2025.html
• FATF, 2025 Targeted Update on VAs and VASPs: https://www.fatf-gafi.org/en/publications/Fatfrecommendations/targeted-update-virtual-assets-vasps-2025.html
• EUR-Lex, COM(2023) 369 (Digital Euro Regulation): https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex:52023PC0369
• EDPB/EDPS, Joint Opinion 02/2023: https://www.edpb.europa.eu/our-work-tools/our-documents/edpbedps-joint-opinion/edpb-edps-joint-opinion-022023-proposal_en
• Federal Law No. 340-FZ (Russia, August 2023): https://digitalpolicyalert.org/event/13503-implemented-federal-law-no-340-fz-establishing-the-legal-framework-for-the-introduction-of-the-digital-ruble
• CBN Regulatory Guidelines on the eNaira (October 2021): https://www.cbn.gov.ng/Out/2021/FPRD/eNairaCircularAndGuidelines%20FINAL.pdf
• Central Bank of The Bahamas Act, 2020: https://laws.bahamas.gov.bs/cms/images/LEGISLATION/PRINCIPAL/2000/2000-0037/2000-0037_2.pdf

Central Bank Sources

• PBOC, "Progress of Research & Development of E-CNY in China," July 2021: https://www.pbc.gov.cn/en/3688110/3688172/4157443/4293696/2021072014364791207.pdf
• PBOC, "Balancing Privacy and Security: Theory and Practice of the E-CNY's Managed Anonymity," November 2022: https://www.pbc.gov.cn/en/3935690/3935759/4696666/2022110110364344083.pdf
• ECB, "Preparation phase closing report," October 2025: https://www.ecb.europa.eu/euro/digital_euro/progress/html/ecb.deprp202510.en.html
• Bank of Russia, "Digital Ruble Current Status June 2025": https://www.cbr.ru/Content/Document/File/180336/digital_ruble_30062025_en.pdf
• Bank of Russia, "Large-scale introduction of digital ruble to begin on 1 September 2026": https://cbr.ru/eng/press/event/?id=25774

BIS and Academic Sources

• BIS, "Project Tourbillon: Exploring privacy, security and scalability for CBDCs": https://www.bis.org/publ/othp80.pdf
• BIS, "Project Aurum 2.0: Improving privacy for retail CBDC payment": https://www.bis.org/about/bisih/topics/cbdc/aurum2_0.htm
• BIS Working Papers No. 1242, "Privacy-enhancing technologies for digital payments": https://www.bis.org/publ/work1242.pdf
• IMF, "Nigeria's eNaira, One Year After" (WP/23/104), May 2023: https://www.imf.org/en/publications/wp/issues/2023/05/16/nigerias-enaira-one-year-after-533487
• IMF, "Central Bank Digital Currency: Progress and Further Considerations," 2024: https://www.imf.org/-/media/Files/Publications/PP/2024/English/PPEA2024052.ashx
• Carnegie Endowment, "Can the Digital Ruble Shield Russia From Western Sanctions?," October 2024: https://carnegieendowment.org/research/2024/10/russia-digital-ruble-development?lang=en
• Cambridge Core, "Assessing the Legal Status of the eNaira and Its Potential for Privacy and Inclusion," 2023: https://www.cambridge.org/core/journals/journal-of-african-law/article/same-naira-more-possibilities-assessing-the-legal-status-of-the-enaira-and-its-potential-for-privacy-and-inclusion/19189464219A6786DE28C68B5E28D67D

Surveillance and Civil Liberties Sources

• Human Rights Foundation CBDC Tracker — Russia: https://cbdctracker.hrf.org/currency/russian-federation
• Human Rights Foundation CBDC Tracker — Nigeria: https://cbdctracker.hrf.org/currency/nigeria
• DigiChina (Stanford), "Lexicon: 'Controllable Anonymity'": https://digichina.stanford.edu/work/lexicon-controllable-anonymity-or-managed-anonymity-and-chinas-digital-yuan/

Verification Notes

• Source of truth: This refresh mirrors .claude/cbdc-frameworks-fact-matrix.json (canonical per-jurisdiction facts) across all 20 jurisdictions. No fact has been introduced that is not present in the matrix or the prior version of this file; web search was not used.
• Aggregate (N = 20): 6 launched/live (Bahamas, Nigeria, Jamaica unambiguous retail; Eastern Caribbean DCash pilot concluded Jan 2024 / DCash 2.0 suspended Feb 2026; China e-CNY and India e₹ operating at pilot scale, not formal nationwide launches); 1 anti-CBDC (United States); 1 pilot with a legally-mandated large-scale launch (Russia, 1 Sep 2026); the remainder in active-pilot or pre-issuance research.
• United States: anti-CBDC. EO 14178 (in force) is the only binding prohibition; the GENIUS Act = S.1582 / Public Law 119-27; H.R. 1919 and the ROAD to Housing CBDC moratorium passed both chambers in differing, unreconciled forms and are NOT enacted; Kevin Warsh sworn in as Fed Chair 22 May 2026.
• China: 22 authorized operators after +12 banks added 2 Apr 2026; Yinfa No. 42 (6 Feb 2026) bans RMB-linked stablecoins/RWA tokenization with extraterritorial reach; revised AML Law effective 1 Jan 2025; aggregate adoption figures (2.25bn wallets, 3.48bn transactions) are PBOC self-reported.
• Russia: non-anonymity is mandatory by design; ESIA registration/ID verification tightened 6 Feb 2026; full large-scale launch mandated 1 Sep 2026; pilot metrics CBR self-reported; public-skepticism polling is media-sourced/indicative only.
• EU: ECB preparation phase concluded Oct 2025, Governing Council moved to next phase 30 Oct 2025; ECON Committee draft-report vote scheduled 23 Jun 2026; EDPB/EDPS Joint Opinion 02/2023 privacy-threshold recommendation not yet codified.
• Ghana: VASP Bill 2025 passed Parliament Dec 2025 (BoG + SEC; virtual assets NOT legal tender) — distinct from the eCedi, whose pilot was declared "completed" 22 May 2026 with enabling legislation still unpassed.
• Brazil: BCB Resolutions 519/520/521 effective 2 Feb 2026 (VASP/stablecoin); Drex Hyperledger Besu platform decommissioned 4 Nov 2025; no ZKP privacy solution deemed production-mature.
• South Africa: Position Paper 27 Nov 2025 ("no compelling immediate need" for retail CBDC); compliance focus is wholesale (Project Khokha 2x) under POPIA.
• Nigeria: 31 Mar 2026 VASP AML/CFT supervisory pilot covers cNGN/crypto (Flutterwave, KuCoin, Paystack et al.), NOT the eNaira; eNaira adoption figures IMF/CBN self-reported.
• Adoption/transaction figures are flagged as self-reported with their source where cited (e.g. China, Nigeria, Jamaica, Russia pilot, India e₹).
• NOT VERIFIED items (e.g. holding limits / data-access details for Ghana's eCedi, DCash merchant limits) are not asserted as facts here.
• Tags use only canonical parents: type/guidance, dimension/compliance, dimension/aml-cft.
• Wikilinks use the deep-research/cbdc-frameworks/ path prefix with correct file slugs (basenames are ambiguous across domains); region values map to the canonical 5-region set.

Last updated: 2026-06-04 </content> </invoke>