Central Bank Digital Currency Policy Training Course

Participants can assess CBDC use cases against evidence-based policy criteria.

• Use-case inventory separates domestic retail, wholesale and cross-border payments
• Theory of change links CBDC features to intended public outcomes
• Multi-criteria decision analysis scores benefits, costs, risks and feasibility
• Payment pain points evidenced through transaction data and user research
• Counterfactual analysis compares CBDC proposals with existing payment reforms
• Success metrics define adoption, access, resilience, cost and trust

Participants can recommend a retail CBDC design aligned with stated policy objectives.

• Account-based and token-based claims compared for authentication and recovery
• Direct, intermediated and hybrid models allocate customer-facing responsibilities
• Two-tier distribution model assesses central-bank and private-sector roles
• CBDC wallet functions specify onboarding, transfers, limits and customer support
• Offline payment design considers device security, settlement and loss allocation
• Remuneration, holding limits and transaction caps address policy trade-offs

Participants can evaluate wholesale CBDC applications for interbank and securities settlement.

• Wholesale CBDC use cases cover RTGS, securities settlement and collateral
• Delivery-versus-payment models analyse atomic settlement and liquidity requirements
• Programmable settlement conditions distinguish automation from monetary programmability
• Tokenised deposits and wholesale CBDC compared through claim and settlement finality
• RTGS integration identifies messaging, account management and operational dependencies
• Cross-border wholesale corridors assess correspondent banking and foreign-exchange settlement

Participants can analyse how CBDC design affects money demand and monetary-policy transmission.

• Central-bank balance sheet effects traced through CBDC issuance and redemption
• Money demand analysis considers convenience yield, interest and confidence
• Interest-bearing CBDC scenarios test policy-rate pass-through and substitution
• Tiered remuneration models assess holdings incentives and monetary-control objectives
• Bank deposit migration channels identify funding, pricing and credit effects
• Stress-period conversion risks estimate flight-to-safety and liquidity pressures

Participants can prepare a financial-stability assessment for a proposed CBDC design.

• Bank funding profiles analysed using deposit concentration and liquidity metrics
• Scenario analysis models deposit outflows under normal and stressed conditions
• Liquidity Coverage Ratio implications assessed for CBDC-related deposit migration
• Credit supply effects traced from funding costs to lending capacity
• Holding limits and conversion frictions test disintermediation mitigants
• Systemic-risk register records contagion channels, triggers and control owners

Participants can set proportionate privacy and identity requirements for a CBDC service.

• Privacy-by-design principles translate into data minimisation and purpose limitation
• Identity assurance levels align onboarding controls with transaction risk
• Tiered KYC models set evidence requirements and transaction permissions
• Data lifecycle mapping identifies collection, storage, access, retention and deletion
• Pseudonymisation and encryption protect payment data while permitting lawful controls
• Lawful-access governance defines authority, thresholds, logging and independent oversight

Participants can define a CBDC control model for financial crime and consumer harm.

• FATF risk-based approach determines CBDC customer and transaction controls
• AML transaction monitoring scenarios identify typologies, alerts and escalation paths
• Sanctions screening design addresses parties, wallets, intermediaries and updates
• Travel Rule considerations distinguish CBDC transfers from virtual-asset transfers
• Consumer-protection rules cover disclosure, errors, fraud, complaints and redress
• Financial inclusion safeguards address access barriers, fees and assisted channels

Participants can identify legal changes and institutional authorities required for CBDC issuance.

• Legal-gap analysis tests currency law, central-bank powers and legal tender
• Claim structure defines holder rights, redemption obligations and insolvency treatment
• Delegated service arrangements allocate liability among public and private parties
• Electronic transactions law assessed for signatures, records and evidentiary status
• Data-protection obligations mapped to CBDC roles and processing activities
• Legislative roadmap sequences consultation, drafting, enactment and subordinate rules

Participants can establish governance arrangements for CBDC policy, delivery and oversight.

• Target operating model assigns policy, issuance, operations and supervisory responsibilities
• RACI matrix clarifies decision rights, accountabilities and escalation routes
• Three-lines model separates operational management, risk oversight and assurance
• Programme board terms define mandate, membership, quorum and reserved decisions
• Risk appetite statements set tolerances for availability, fraud and privacy
• Independent review arrangements cover audit, model validation and public reporting

Participants can evaluate CBDC architecture choices without treating technology as the policy driver.

• Centralised and distributed architectures compared through control and resilience requirements
• Permissioned ledger design assesses validator roles, governance and performance
• Core ledger, wallet and gateway components mapped to service responsibilities
• Application programming interfaces define participant access and interoperability boundaries
• Scalability metrics cover throughput, latency, peak demand and settlement finality
• Technology due diligence tests vendor dependency, portability and exit arrangements

Participants can define cyber and operational-resilience requirements for a CBDC service.

• NIST Cybersecurity Framework profiles identify CBDC protection and recovery priorities
• Threat modelling identifies fraud, insider, supply-chain and nation-state scenarios
• Zero-trust principles govern identity, device, network and privileged access
• Operational-resilience mapping identifies important business services and impact tolerances
• Business continuity plans address ledger failure, telecom outages and cyber incidents
• Security testing strategy covers penetration tests, red teaming and crisis rehearsals

Participants can specify interoperability requirements for domestic and cross-border CBDC payments.

• ISO 20022 message flows map initiation, clearing, settlement and exception handling
• Interoperability layers distinguish technical, semantic, legal and business alignment
• Alias directories support account discovery while protecting personal data
• Payment-system access rules define participation, settlement and liquidity obligations
• Open API standards govern consent, authentication, throttling and audit trails
• Exception management covers rejected payments, reversals, disputes and investigations

Participants can assess cross-border CBDC arrangements and associated policy dependencies.

• Cross-border payment frictions measured through cost, speed, transparency and access
• Jurisdictional analysis compares capital controls, exchange rules and data localisation
• Multi-CBDC platform models assess governance, settlement and foreign-exchange mechanisms
• Correspondent banking alternatives test liquidity, compliance and operational consequences
• Currency substitution risks assess domestic monetary autonomy and payment preferences
• Memoranda of understanding define supervisory cooperation and crisis communication

Participants can structure market engagement and supplier decisions for a CBDC programme.

• Make-buy-partner assessment compares capabilities, control, cost and delivery risk
• Request for information documents test market maturity and supplier assumptions
• Evaluation criteria weight security, interoperability, ownership and service continuity
• Contractual controls address intellectual property, data access and source-code escrow
• Service-level agreements define availability, incident response and performance reporting
• Industry consultation plan gathers evidence without pre-committing policy choices

Participants can develop a controlled CBDC pilot plan with evidence-based decision gates.

• Pilot charter defines policy hypotheses, scope, population and operating assumptions
• Minimum viable product boundaries separate learning priorities from production requirements
• Sampling strategy selects users, merchants, banks and geographic locations
• Test scenarios cover onboarding, payments, outages, fraud and dispute resolution
• Key performance indicators measure usability, uptime, cost and policy outcomes
• Stage-gate criteria determine iteration, expansion, pause or termination decisions

Participants can prepare a stakeholder engagement strategy for a CBDC policy programme.

• Stakeholder segmentation distinguishes citizens, banks, merchants, legislators and media
• Message architecture explains purpose, safeguards, choices and known limitations
• Public consultation design gathers evidence through questions, submissions and hearings
• Trust-risk analysis addresses surveillance concerns, exclusion and system reliability
• Disclosure protocols define publication of pilots, incidents, metrics and evaluations
• Crisis communication playbooks assign spokespeople, approvals and response timelines

Participants can build, review and present a complete CBDC policy and implementation dossier.

• Policy objective statement connects public need, mandate and measurable outcomes
• Design recommendation justifies access, distribution, privacy and remuneration choices
• Financial-stability assessment documents scenarios, mitigants and residual risk
• Legal and governance analysis assigns authority, accountability and required changes
• Pilot roadmap sequences scope, controls, metrics, decision gates and resources
• Executive decision paper presents options, recommendation, trade-offs and approvals