Legal and Regulatory Foundations | CBDC Architecture & Design | XRP Academy - XRP Academy
XRPAcademy
Course Progress0/20
3 free lessons remaining this month

Free preview access resets monthly

Upgrade for Unlimited
Skip to main content
beginner•55 min

Legal and Regulatory Foundations

Learning Objectives

Identify the core legal questions that CBDCs must address

Explain why legal tender status matters and how jurisdictions differ

Describe AML/CFT requirements and their impact on CBDC design

Analyze the regulatory models different countries are adopting

Recognize cross-border legal complexities in CBDC implementation

Every line of CBDC code sits atop layers of legal foundation. The central bank's authority to issue CBDC. The currency's legal status. Consumer protections. Liability frameworks. Privacy regulations. Anti-money laundering requirements.

These legal foundations aren't afterthoughts—they shape what's possible from the start. A CBDC design that would be illegal can't be built, no matter how elegant the technology. A CBDC that doesn't comply with international AML standards will be isolated from global finance.

More fundamentally, law determines power. Who can freeze accounts? Who can access transaction data? Who bears the loss when fraud occurs? These questions are answered by legal frameworks, not technical specifications.

This lesson maps the legal landscape that CBDC architects must navigate.

ESSENTIAL LEGAL QUESTIONS FOR CBDC
  • Some: Yes, under existing currency powers
  • Others: New legislation required
  • Constitutional questions in some jurisdictions
  • Legal tender?
  • Central bank liability?
  • Deposit or currency?
  • Property or claim?
  • Consumer protections?
  • Privacy rights?
  • Recovery rights?
  • Transaction finality?
  • System failures?
  • Fraud losses?
  • Unauthorized transactions?
  • Intermediary failures?
  • AML/CFT?
  • Sanctions?
  • Data protection?
  • Financial supervision?
WHERE DOES CBDC AUTHORITY COME FROM?
  • Government/central bank authority over currency
  • Legal tender provisions
  • Monetary system framework
  • US Constitution: Congress has power to "coin Money"
  • EU Treaties: ECB authority over monetary policy
  • Most countries: Constitutional monetary provisions
  • Exclusive right to issue currency
  • Management of monetary policy
  • Payment system oversight
  • Some: Yes, digital is just new form
  • Others: Cash only, legislation needed
  • Digital Euro Regulation (EU - proposed)
  • Specific CBDC laws (various)
  • Amendments to existing banking acts
  • Explicitly authorized CBDC issuance
  • Defined legal status
  • Set regulatory framework
WHAT IS CBDC LEGALLY?
  • Must be accepted for debts
  • Settles obligations
  • Highest legal status
  • Form of money
  • Not necessarily legal tender
  • Central bank liability
  • Like a bank account
  • Deposit protections apply
  • Different regulatory framework
  • Electronic value
  • E-money regulations apply
  • May have limitations
  • Legal tender status (or equivalent)
  • Central bank liability
  • Currency, not deposit

WHY THIS MATTERS:

  • Forced acceptance controversies

  • Central bank balance sheet impact

  • Different from cash conceptually

LEGAL TENDER EXPLAINED

DEFINITION:
Money that must be accepted to settle debts
(in most legal systems)

  • Creates acceptance obligation
  • Settles legal payment obligations
  • Provides payment finality
  • Force private parties to accept for all transactions
  • Eliminate all payment disputes
  • Apply to all countries universally

COMMON MISCONCEPTIONS:

  • Not true in most jurisdictions

  • Applies to debt settlement

  • Merchants can refuse for purchases

  • Not true

  • Private agreements can use other means

  • Contracts can specify payment method

  • Forcing acceptance is controversial

  • Digital divide concerns

LEGAL TENDER APPROACHES BY JURISDICTION

APPROACH 1: EXPLICIT CBDC LEGAL TENDER
Jamaica: JAM-DEX is legal tender
Bahamas: Sand Dollar designated legal tender
Nigeria: eNaira has legal tender status (with caveats)

  • Legal tender status proposed
  • With offline capability requirement
  • Accessibility requirements
  • Not forced acceptance for all
  • Valid payment if accepted
  • Not required to accept
  • Parallel to cash
  • Research phase
  • Legal status undetermined
  • Future legislation planned

KEY DEBATES:

  • Pro: Ensures universal usability

  • Con: Burdens merchants without digital capability

  • Some people can't use digital payments

  • Legal tender status could discriminate

  • Cash must remain alternative

  • Integration costs

  • Technical requirements

  • Compliance burden

CBDC, CASH, AND LEGAL TENDER

THE QUESTION:
If CBDC is legal tender, what about cash?

APPROACHES:

  • Citizens choose

  • No elimination of cash

  • Maximum flexibility

  • Most common approach

  • Discourage cash

  • Eventually phase out

  • Controversial

  • Sweden discussions

  • CBDC as convenience

  • Not mandatory acceptance

  • Lower CBDC status

  • Some proposals

  • Eliminating cash is extremely unpopular

  • "Cash preservation" is explicitly stated by ECB

  • Most CBDCs designed to complement, not replace cash

  • Legal frameworks reflect this

CONSUMER PROTECTION QUESTIONS

FUNDAMENTAL RIGHTS:

  1. RIGHT TO ACCESS

  2. RIGHT TO INFORMATION

  3. RIGHT TO ERROR CORRECTION

  4. RIGHT TO RECOVERY

  5. RIGHT TO PRIVACY

  6. RIGHT TO EXIT

WHO'S LIABLE WHEN THINGS GO WRONG?

SCENARIO 1: SYSTEM FAILURE
CBDC system goes down; users can't access money

  • Central bank liable for unavailability
  • Force majeure exceptions
  • Intermediary responsible for their systems
  • Limited liability caps

Typical: Central bank liability with exceptions

SCENARIO 2: FRAUD LOSS
User is scammed; sends CBDC to fraudster

  • User bears loss (like cash)
  • Bank/intermediary liable (like cards)
  • Shared responsibility
  • Depends on circumstances

Typical: User bears loss (more like cash than cards)

SCENARIO 3: UNAUTHORIZED TRANSACTION
Someone hacks wallet and sends CBDC

  • User liable if negligent
  • Intermediary liable for security failure
  • Depends on how breach occurred
  • Similar to electronic funds transfer rules

Typical: Depends on fault; rules developing

SCENARIO 4: INTERMEDIARY FAILURE
Bank/PSP distributing CBDC goes bankrupt

  • CBDC protected (unlike bank deposits)
  • Users can access via central bank
  • Orderly transfer to other provider

Typical: CBDC should be safe (not intermediary asset)

KEY PRINCIPLE:
CBDC itself (central bank liability) should be safe
Risks relate to access, not underlying value
```

WHICH EXISTING LAWS APPLY?
  • Transaction rules
  • Dispute resolution
  • Unauthorized transaction protections
  • May need modification for CBDC
  • Issuance rules
  • Safeguarding requirements
  • Redemption rights
  • CBDC is different (central bank vs. private)
  • If CBDC through banks
  • Consumer protection rules
  • Disclosure requirements
  • Supervision framework
  • GDPR in EU, various others
  • Personal data handling
  • Purpose limitations
  • User rights
  • Unfair practices
  • Advertising rules
  • Contract terms
  • Applies to CBDC services
  • Some existing rules apply
  • Some modification needed
  • Some new CBDC-specific rules
  • Comprehensive framework developing

Anti-money laundering and counter-terrorism financing rules fundamentally shape CBDC design.

AML/CFT FRAMEWORK FOR CBDC

FATF STANDARDS:
Financial Action Task Force sets global standards
CBDCs must comply like any other financial product

CORE REQUIREMENTS:

  1. CUSTOMER IDENTIFICATION (KYC)

  2. TRANSACTION MONITORING

  3. SUSPICIOUS ACTIVITY REPORTING

  4. RECORD KEEPING

  5. SANCTIONS SCREENING

  6. TRAVEL RULE

HOW AML/CFT SHAPES CBDC DESIGN
  • Above certain thresholds
  • For AML/CFT compliance
  • International standard requirement
  • No country can opt out and participate in global finance

TIERED KYC IS THE SOLUTION:
┌─────────────────────────────────────────┐
│ TIER 1: ANONYMOUS/LOW KYC │
│ - Very low limits (€50-150/transaction) │
│ - Minimal/no identification │
│ - Basic functionality only │
│ - For small transactions │
├─────────────────────────────────────────┤
│ TIER 2: BASIC KYC │
│ - Medium limits (€1,000-3,000) │
│ - Phone number/basic ID │
│ - Standard features │
├─────────────────────────────────────────┤
│ TIER 3: FULL KYC │
│ - High/no limits │
│ - Complete identity verification │
│ - All features available │
└─────────────────────────────────────────┘

  • System must detect suspicious patterns
  • Even if individual transactions are small
  • Aggregate monitoring
  • Someone must be able to investigate
  • Transactions must be recordable
  • Even if not routinely accessed
  • Available for law enforcement with process
  • Duration requirements apply

THE HONEST TRUTH:
CBDC cannot be as anonymous as cash above trivial amounts
This is legal requirement, not technical choice
Privacy advocates may not accept this
```

THE FUNDAMENTAL TENSION
  • Cash-like anonymity
  • No government surveillance
  • Transaction privacy
  • No tracking
  • Identification for significant transactions
  • Transaction monitoring capability
  • Record keeping
  • Law enforcement access

THIS CANNOT BE FULLY RECONCILED

COMPROMISE APPROACHES:

  • Small = more private

  • Large = fully identified

  • Trade-off, not solution

  • Selective disclosure

  • Zero-knowledge proofs

  • Hide from some, visible to others

  • Complex, still developing

  • Below €X: No monitoring

  • Above €X: Full compliance

  • Where to set X is political

  • Real-time privacy

  • Historical access with warrant

  • Balances surveillance and investigation

THE REALITY:
No CBDC achieves cash-level privacy for significant amounts
Legal requirements prevent it
This is a feature/bug depending on perspective


---

REGULATORY MODEL OPTIONS
  • Modify central bank act
  • Adjust payment regulations
  • Quick but incomplete
  • Example: Jamaica

Advantages:

  • Faster implementation
  • Uses familiar frameworks
  • Lower legislative burden
  • May leave gaps
  • Unclear authority
  • Potential conflicts
  • Dedicated CBDC law
  • Complete framework
  • Takes longer
  • Example: EU Digital Euro Regulation (proposed)

Advantages:

  • Comprehensive coverage
  • Clear authority
  • Addresses all issues
  • Years to develop
  • Political challenges
  • May be outdated by technology
  • Central bank issues rules
  • Administrative action
  • Fastest but legally weakest
  • Example: Some pilot programs

Advantages:

  • Very fast
  • Flexible
  • Can adapt quickly
  • Legal challenges possible
  • Limited scope
  • May need legislation eventually
  • Framework law (basics)
  • Central bank regulations (details)
  • Industry standards (technical)
  • Most comprehensive

Advantages:

  • Appropriate level for each issue
  • Flexibility where needed
  • Certainty where needed
  • Complex
  • Coordination required
  • Multiple updates needed
CASE STUDY: DIGITAL EURO REGULATION

PROPOSED FRAMEWORK:

  1. Digital Euro Regulation (main law)
  2. Legal tender regulation
  3. Possible ECB regulation amendments

KEY PROVISIONS (Proposed):

  • Digital Euro as legal tender

  • Mandatory acceptance with exceptions

  • Coexistence with cash

  • Banks and PSPs as intermediaries

  • Central bank holds liabilities

  • Intermediary obligations

  • Strong privacy for small offline transactions

  • Progressive identification for larger amounts

  • ECB cannot see individual transactions (design goal)

  • To be set by ECB

  • ~€3,000 discussed

  • To protect bank deposits

  • Free basic services

  • Commercial services may be charged

  • Limits on merchant fees

  • Rights framework

  • Dispute resolution

  • Accessibility requirements

  • Proposal: 2023

  • Legislative process: 2024-2026

  • Earliest launch: 2027-2028

WHO SUPERVISES CBDC?
  • System operation
  • Monetary policy aspects
  • Overall CBDC governance
  • Intermediary supervision
  • Consumer protection
  • Market conduct
  • Bank stability
  • Capital requirements
  • Operational resilience
  • Privacy compliance
  • Data handling
  • User rights
  • Anti-money laundering compliance
  • Suspicious activity
  • Sanctions enforcement
  • Multiple regulators
  • Different mandates
  • Potential conflicts
  • Information sharing
  • Central bank leads on CBDC core
  • Existing regulators handle their domains
  • MOUs for coordination
  • New oversight committees
CROSS-BORDER CBDC LEGAL ISSUES
  • Sender's country?
  • Receiver's country?
  • Intermediary's country?
  • Settlement location?
  • Generally: No
  • But: May be acceptable by agreement
  • International conventions needed
  • Both countries?
  • Higher standard?
  • Mutual recognition?
  • Travel rule complexity
  • Home country?
  • Receiving country?
  • International standards?
  • Court jurisdiction?
  • Arbitration?
  • Which rules apply?
  • Different sanctions lists
  • Compliance with multiple regimes
  • Screening requirements
LEGAL FRAMEWORKS FOR MULTI-CBDC

PROJECT mBRIDGE APPROACH:

  • Participant agreement

  • Common rulebook

  • Shared standards

  • BIS (formerly) coordinated

  • Each central bank retains authority

  • Common platform, separate currencies

  • Bilateral/multilateral agreements

  • Dispute resolution mechanism

CHALLENGES:

  • Countries don't want to cede control

  • Common platform = shared governance

  • Who decides disputes?

  • Different national rules

  • Participants may seek lowest standard

  • Harmonization difficult

  • mBridge involves China

  • US sanctions considerations

  • BIS withdrew (2024)

  • Geopolitical dimensions

  • Early stage

  • Highly complex

  • Politically sensitive

  • Not fully developed

WHO'S SETTING INTERNATIONAL CBDC STANDARDS?
  • Committee on Payments and Market Infrastructures
  • Principles for financial infrastructures
  • CBDC guidance development
  • AML/CFT standards
  • Travel rule for virtual assets
  • Applying to CBDCs
  • Capacity development
  • Policy guidance
  • Technical assistance
  • Financial Stability Board
  • Systemic risk considerations
  • Cross-border coordination
  • Technical standards
  • Messaging formats
  • Interoperability
  • Standards emerging
  • Not yet comprehensive
  • Country-by-country variation
  • Harmonization years away

IMPLICATION:
Early CBDC projects navigate uncertain legal terrain
Standardization will come but slowly
```

✅ Legal frameworks are essential—CBDCs cannot launch without legal authority and status clarity.

✅ AML/CFT requirements constrain design—full anonymity is legally impossible above trivial amounts in any jurisdiction participating in global finance.

✅ Consumer protection frameworks are developing—existing regulations apply partially; new rules are being created.

✅ Cross-border complexity is significant—international CBDC use raises unresolved legal questions.

⚠️ How legal tender status will work in practice—forced acceptance debates are ongoing.

⚠️ Where privacy thresholds will settle—the anonymous tier limits vary and remain contested.

⚠️ How liability will be allocated—new situations will create new legal questions.

⚠️ Whether international harmonization will occur—or whether CBDC legal frameworks will fragment.

📌 Assuming technology drives legal outcomes—law constrains what technology can do, not vice versa.

📌 Expecting full privacy in CBDCs—AML/CFT requirements make this legally impossible for significant transactions.

📌 Ignoring cross-border complexity—domestic-only thinking misses global legal constraints.

Legal frameworks are the often-invisible foundation that determines what CBDCs can actually be. Privacy limitations aren't technical—they're legal requirements. Consumer protections aren't features—they're legal mandates. The two-tier model isn't just practical—it's often legally required. Understanding law is essential for understanding why CBDCs are designed the way they are.

Assignment: Analyze the legal framework for a specific CBDC, documenting authority, status, consumer protections, AML/CFT compliance, and identifying gaps.

Requirements:

Part 1: Select a CBDC
Choose: Digital Euro (proposed), Jamaica JAM-DEX, Nigeria eNaira, or another CBDC with available legal documentation.

  • What legal authority enables this CBDC?

  • Was new legislation required?

  • What constitutional/statutory provisions apply?

  • Are there any legal challenges or uncertainties?

  • Is the CBDC legal tender? How is this defined?

  • Is it a central bank liability?

  • How does it relate to cash legally?

  • What are acceptance obligations?

  • What consumer rights are established?

  • What dispute resolution mechanisms exist?

  • How is liability allocated (system failure, fraud, unauthorized transactions)?

  • What existing regulations apply?

  • What KYC requirements exist by tier?

  • How does the design address AML requirements?

  • What transaction monitoring is required?

  • What privacy protections exist within legal constraints?

  • Accuracy of legal analysis (30%)

  • Comprehensiveness of coverage (25%)

  • Identification of gaps/uncertainties (25%)

  • Clarity of presentation (20%)

Time Investment: 3-4 hours
Value: Understanding legal frameworks is essential for realistic CBDC assessment.

Knowledge Check

Question 1 of 1

If a CBDC intermediary (distributing bank) fails, what typically happens to user CBDC holdings?

  • BIS: "Central Bank Digital Currencies: Legal Frameworks"
  • IMF: "Legal Aspects of Central Bank Digital Currency" (Fintech Note)
  • European Commission: Digital Euro Regulation proposal
  • FATF: Updated Guidance for Virtual Assets
  • Financial Crimes Enforcement Network (FinCEN): Virtual currency guidance
  • Relevant national AML regulations
  • Consumer protection authority publications
  • Payment services regulations by jurisdiction
  • E-money regulations

For Next Lesson:
Having completed Phase 1 (Foundations), we now move to Phase 2 (Architecture). Lesson 8 examines ledger technology options—centralized databases, distributed ledgers, and hybrid approaches—evaluating the trade-offs for CBDC implementation.

End of Lesson 7

END OF PHASE 1: FOUNDATIONS

Total words: ~5,400
Estimated completion time: 55 minutes reading + 3-4 hours for deliverable

Course 58: CBDC Architecture & Design
Lesson 7 of 20
XRP Academy - The Khan Academy of Digital Finance

Key Takeaways

1

Legal authority must exist before CBDC can launch

: Constitutional and statutory authority questions must be answered—some countries need new legislation, others can proceed under existing central bank powers.

2

Legal tender status is significant but not universal acceptance

: Legal tender means debts can be settled, not that all merchants must accept. Most CBDCs aim for legal tender status with nuanced obligations.

3

AML/CFT requirements prevent full anonymity

: International standards require customer identification and transaction monitoring above low thresholds. This is legal reality, not design choice.

4

Liability frameworks are developing

: Who bears loss from fraud, system failure, and unauthorized transactions is being defined through new regulations and will likely resemble a hybrid of cash and electronic payment rules.

5

Cross-border CBDCs face unresolved legal complexity

: Jurisdiction, applicable law, and international standards for multi-CBDC arrangements are early-stage and politically sensitive. ---