CBDC Risks and Challenges: Adoption, Security, Privacy, and Banking Impact

CBDC risks and challenges are no longer theoretical. Central banks have moved from white papers to pilots, yet the first live retail CBDCs teach a clear lesson: issuing digital central bank money is easier than getting people, merchants, banks, and regulators to trust it at scale.

The Bank for International Settlements, in its 2024 survey of 93 central banks, found that 91 percent were exploring retail CBDCs, wholesale CBDCs, or both. Those institutions cover roughly 94 percent of global GDP. A separate 2024 global tracker counted 134 countries studying CBDCs, with every G20 economy involved and 44 countries in active pilots. Even so, only a handful of jurisdictions had live retail CBDCs by late 2024, including the Bahamas, Nigeria, and Jamaica. The IMF has noted that usage in these live systems remains modest.

That gap between policy interest and public adoption is the real CBDC story. The technology matters. But design choices around privacy, cybersecurity, banking stability, and incentives probably matter more.

What Makes CBDC Risks and Challenges Different?

A central bank digital currency is a digital form of sovereign money issued by a central bank. It can be designed for retail users, such as households and businesses, or for wholesale use between financial institutions.

People often compare CBDCs with stablecoins, bank deposits, or mobile money. That comparison helps, but it is incomplete. A CBDC can sit at the core of a national payment system. If it fails, leaks data, or triggers deposit flight during stress, the effects reach far beyond a single payment app.

To be blunt, a CBDC is not just another wallet. It can become critical national infrastructure.

CBDC Adoption Challenges: Why Launch Does Not Equal Use

The Bahamas Sand Dollar, Nigeria's eNaira, and Jamaica's Jam-Dex all show that adoption stays hard even after an official launch. IMF analysis of these systems points to limited usage compared with cash, cards, bank transfers, and mobile payments.

Low public awareness

Many users still do not understand why they need a CBDC. If a debit card, instant payment app, or mobile wallet already works, a new government-issued option has to offer a real reason to switch.

That reason cannot be vague. Users ask simple questions:

• Where can I spend it?
• Is it cheaper than my current payment app?
• Will refunds work?
• Who sees my transactions?
• What happens if I lose my phone?

Weak answers stall adoption.

The merchant acceptance problem

CBDCs face the classic two-sided market problem. Consumers will not use a CBDC unless merchants accept it. Merchants will not invest in acceptance unless enough consumers use it.

Anyone who has worked on payment integrations knows the ugly edge cases. A transaction can look successful in the wallet, fail at the merchant terminal, then sit in a reconciliation queue because the payment reference and refund reference do not match. In real deployments, those operational details decide whether merchants trust a payment rail.

Privacy drives trust, but not the way policymakers expect

A 2024 Reserve Bank of Australia study found that average Australian consumers would not pay extra for the added safety of a CBDC over bank deposits. They did place modest value on privacy. The study estimated that consumers would pay about 5 Australian dollars per year to avoid sharing transaction data with the central bank, a commercial bank, or a financial intelligence authority.

That number is small. The signal is not. People may not describe privacy in technical terms, yet they notice when a payment system feels like surveillance.

CBDC Privacy Risks: Data, Surveillance, and Civil Liberties

CBDC privacy is one of the hardest design problems. Digital payments already generate data. A CBDC can raise the sensitivity of that data because it may connect identity, transaction history, wallet balances, geolocation signals, device information, and compliance records.

Key CBDC privacy risks

• Data leakage: Personal transaction data or identity records may leak through breaches, misconfiguration, or third-party failure.
• Data abuse: Lawfully collected data may later be used for profiling, commercial targeting, tax fishing expeditions, or broad law enforcement access beyond the original purpose.
• Centralized visibility: A poorly designed direct CBDC model may give public authorities too much access to transaction-level information.
• Cross-border data exposure: International CBDC payments may move user data into jurisdictions with weaker legal protections.

Germany's federal data protection authority has warned that CBDCs could give governments, central banks, and participating financial entities unprecedented access to citizens' financial information. The OECD has raised similar concerns that CBDCs could let governments monitor transaction-level data and exert greater control over private payments when safeguards are weak.

The AML and privacy trade-off

Central banks cannot ignore anti-money-laundering and counter-terrorist financing obligations. At the same time, a CBDC with full traceability for every small purchase will be hard to defend in democratic societies.

Common design responses include:

• Tiered privacy: Small-value transactions get stronger privacy, while larger transfers trigger standard checks.
• Role separation: Private intermediaries manage customer identity and front-end services, while the central bank avoids direct access to all user-level details.
• Privacy-preserving cryptography: Techniques such as zero-knowledge proofs can support compliance checks without exposing every underlying data point, though production deployment is complex.

No model removes every risk. Direct models can concentrate data. Hybrid models still need careful data retention rules. Intermediated models add operational complexity and vendor risk.

CBDC Cybersecurity and Operational Risk

CBDC cybersecurity deserves a higher bar than most fintech projects. A retail CBDC may serve millions of people and depend on banks, wallet providers, telecom networks, merchants, and government systems.

The BIS has described CBDC platforms as critical national infrastructure that nation states and criminal actors could target. The Federal Reserve has also warned that CBDC designs would need strong controls for storing, processing, and transmitting sensitive transaction and identity data.

Main security threats

• Core ledger compromise: Attackers may target the central ledger, validation layer, or settlement logic.
• Wallet attacks: Malware, phishing, SIM swap attacks, and device compromise put users at risk.
• Intermediary breaches: Banks and payment service providers can become weak points if their controls lag behind the central infrastructure.
• Insider threats: Privileged access to transaction data or operational tools can be abused.
• Ransomware and outages: A payment outage during a salary cycle, holiday season, or crisis can turn into a public confidence problem fast.

Concentration risk is serious. If a CBDC replaces diverse private payment options instead of complementing them, one failure can hit a larger share of national payments. Resilience planning should include offline payments, fallback rails, incident drills, independent audits, and strict access controls.

CBDC Banking Impact: Deposits, Lending, and Stability

The banking impact of CBDCs worries commercial banks, community banks, and financial stability teams alike. A retail CBDC may let households and firms hold central bank money directly or near-directly. That can change how deposits move.

Disintermediation risk

If users shift large balances from bank deposits into CBDC wallets, banks may lose a stable funding source. In normal periods, the shift may be gradual. During a panic, it could be fast. A bank run that once required branch visits or wire instructions could become a few taps on a phone.

That is why many central banks are weighing safeguards such as:

• Caps on individual CBDC holdings
• Non-interest-bearing CBDCs
• Tiered remuneration, where larger balances earn less or nothing
• Intermediated models that keep banks involved in customer relationships

These controls are not cosmetic. They decide whether a CBDC complements bank deposits or competes with them.

Pressure on payment revenue

Banks and card networks earn revenue from payments, float, account services, and merchant relationships. A public digital money system could squeeze some of those economics. That may improve competition in concentrated payment markets, but smaller institutions could struggle if compliance costs rise while payment income falls.

The right policy question is not whether banks deserve protection from competition. It is whether CBDC design weakens credit creation, regional banking, or operational diversity in ways that harm the broader economy.

Lessons From Live CBDCs and Global Pilots

The Sand Dollar, eNaira, and Jam-Dex offer early evidence. All three work for payments, but none has displaced existing instruments at scale. The common barriers repeat: awareness, merchant acceptance, wallet usability, trust, and integration with existing financial habits.

Global pilots are now testing different models, including wholesale settlement, cross-border corridors, and securities settlement. Wholesale CBDCs may prove easier to justify in some markets because the user base is smaller, compliance is clearer, and the operational environment is more controlled. Retail CBDCs face a tougher test. They must work for ordinary people on ordinary days.

Governance: The Missing Layer in Many CBDC Debates

Good CBDC design is not only technical. Legal and institutional safeguards matter just as much.

Regulators and data protection authorities increasingly call for privacy by design, data minimization, strict retention limits, independent oversight, and transparent rules for government access. Write these controls before launch, not after public backlash.

Governance should also cover programmability. If a CBDC can support programmable payments, policymakers must define who can set conditions, under what law, and with what appeal rights. Otherwise, programmable money can slide from useful automation into excessive control.

How Professionals Should Prepare

If you work in banking, compliance, cybersecurity, digital assets, or public policy, CBDC risks and challenges are becoming part of the job. You do not need to become a central banker, but you should understand payment architecture, wallet security, privacy engineering, and financial stability trade-offs.

For structured learning, you can connect this topic with training paths such as Certified Blockchain Expert™, Certified Blockchain Developer™, Certified Cryptocurrency Expert™, and Certified Cybersecurity Expert™. If your role is technical, start by mapping how a CBDC wallet, identity provider, ledger, and bank core would exchange data. If your role is policy or risk, build a checklist covering privacy, AML/CFT, outage response, bank funding impact, and user redress.

The next step is simple. Take one live CBDC case, such as the eNaira or Sand Dollar, and grade it against four criteria: adoption, privacy, cybersecurity, and banking impact. That exercise teaches more than another abstract debate about whether CBDCs are good or bad.