How Central Bank Digital Currencies Are Reshaping Global Financial Inclusion Strategies

More than 1.4 billion adults globally remain outside the formal financial system. Cash is still king in many regions, but digital payments are growing fast. Central bank digital currencies—digital versions of a country's fiat money—promise to bridge this gap. But promises alone don't open bank accounts. This article is for policymakers, fintech builders, and financial inclusion teams who need a practical, no-hype look at how CBDCs can actually expand access, and where they often fall short.

Why Financial Inclusion Needs a New Approach

Traditional banking relies on physical branches, credit history, and stable identity documents. For a farmer in rural Kenya, a street vendor in India, or a refugee in Jordan, those prerequisites are often out of reach. Mobile money services like M-Pesa have shown that digital channels can work, but they remain fragmented, expensive for small transactions, and tied to private platforms that may not prioritize public welfare.

The limits of cash and mobile money

Cash is universal but costly to distribute and manage. Mobile money reduces some friction but introduces new ones: interoperability gaps, agent liquidity issues, and fees that eat into tiny balances. Neither solution scales well for cross-border remittances or government benefit distribution. A central bank digital currency, by contrast, is designed as a public good—a liability of the central bank, not a private company. That distinction matters for trust.

What CBDCs can do differently

A well-designed CBDC can offer free or low-cost transactions, work offline for areas with patchy connectivity, and be accessed through simple feature phones. Because it's legal tender, it cannot be refused for payments. This shifts the inclusion conversation from "can we reach them?" to "how do we design for their reality?"

Many central banks are now piloting CBDCs with inclusion as a primary goal. The Bahamas' Sand Dollar, Nigeria's eNaira, and China's digital yuan all aim to reach underserved populations. Early results are mixed, and the lessons are instructive.

Core Idea: Digital Cash That Works for Everyone

Think of a CBDC as digital cash—not a cryptocurrency, but a direct claim on the central bank, just like a banknote. The difference is it lives on a phone or a card. The core mechanism is simple: the central bank issues digital tokens or accounts, and citizens can hold and transfer them without needing a commercial bank account.

Two-tier vs. direct models

Most CBDC designs use a two-tier model: the central bank issues the digital currency to commercial banks or payment providers, who then distribute it to end users. This leverages existing infrastructure and keeps the central bank out of retail operations. A direct model, where the central bank manages all accounts, is rarer but can reduce intermediary costs. Each model has trade-offs for inclusion.

Why design decisions matter for inclusion

If a CBDC requires a smartphone and internet for every transaction, it excludes the very people it aims to serve. Offline capability, low-cost devices, and agent-assisted onboarding are not optional features—they are core requirements. Similarly, privacy protections must balance anti-money laundering rules with the reality that many unbanked individuals distrust formal systems due to surveillance concerns.

Practical inclusion means designing for the lowest common denominator: a basic phone, intermittent connectivity, low literacy, and limited digital skills. Every technical choice—from the ledger architecture to the authentication method—either widens or narrows the access gap.

How It Works Under the Hood

Behind a simple user interface, a CBDC system involves several layers: issuance, distribution, transaction processing, and compliance. Each layer has inclusion implications.

Issuance and digital wallets

The central bank creates the digital currency and makes it available through authorized intermediaries. End users hold it in digital wallets—either app-based or on a physical card. The wallet design is critical: tiered wallets with low KYC requirements for small balances can lower the entry barrier. For example, a basic wallet might require only a phone number and allow transactions up to $200 per month, while a full wallet needs a national ID and higher limits.

Offline transactions and NFC cards

For areas without reliable internet, offline capability is essential. Some CBDCs use near-field communication (NFC) cards that can be loaded with value and exchanged by tapping two cards together. The transaction settles later when the card connects to the network. This mimics cash's physical transfer while adding a digital trail. The catch is that offline systems are harder to secure against double-spending and require hardware that may be costly to produce.

Interoperability with existing systems

A CBDC that only works within its own app will fail. It must be interoperable with mobile money, bank transfers, and merchant payment terminals. This requires standardization of APIs and clearing protocols—a technical and political challenge that many pilots underestimate.

One common mistake is building a closed system that competes with existing private services rather than complementing them. Inclusion gains come from integration, not isolation.

Worked Example: Reaching Rural Communities

Imagine a central bank in a low-income country launching a CBDC pilot in three rural districts. The target population includes smallholder farmers, informal traders, and households receiving government subsidies. Here's how the strategy might unfold—and where it could go wrong.

Phase 1: Agent network and onboarding

The central bank partners with mobile network operators and local shops to become cash-in/cash-out agents. Farmers can exchange cash for CBDC at these agents, using a basic phone with USSD codes. No smartphone, no internet required. Each agent gets a digital wallet and a small float. The onboarding process uses a simplified KYC: name, phone number, and a self-declared address. Balance limits cap at $500 to manage risk.

Phase 2: Use cases that matter

The government starts distributing fertilizer subsidies via CBDC. Farmers receive a notification on their phone and can redeem the value at any agent or use it to pay for seeds directly. A local cooperative accepts CBDC for crop purchases, eliminating the need for cash transport. The system also supports person-to-person transfers—farmers can send money to family in the city without paying high remittance fees.

Common pitfalls in this scenario

First, agent liquidity: if agents run out of digital currency to sell or cash to buy, the system stalls. The central bank must manage float replenishment, which is harder than it sounds. Second, digital literacy: even with USSD, many farmers need assistance. Agents become de facto educators, but they are not trained for that role. Third, trust: if the system fails during a critical subsidy distribution, users may never come back. One technical glitch can undo months of adoption work.

A successful pilot requires robust offline fallback, agent training, and a clear escalation path for disputes. Without these, the inclusion promise collapses.

Edge Cases and Exceptions

Not everyone fits the typical unbanked profile. Special populations require tailored design.

Refugees and displaced people

Refugees often lack official IDs from their host country. A CBDC that requires a national ID excludes them entirely. Some pilots are experimenting with self-sovereign identity or biometric verification (iris scans, fingerprints) to onboard refugees. But biometrics raise privacy and security concerns, especially for vulnerable groups.

Elderly and disabled users

An elderly person with limited vision or mobility may struggle with even a simple phone interface. Voice-based interfaces, large-font displays, and assisted transactions through trusted relatives or agents can help. The design must accommodate cognitive and physical limitations without forcing users to rely on others who might exploit them.

Children and youth

Minors are often excluded from financial services. A CBDC could offer limited accounts for children—for example, a wallet that only receives payments and cannot be used for gambling or large withdrawals. This requires careful age-verification and parental consent mechanisms.

Each edge case forces a design trade-off. Simplicity for the majority may conflict with accessibility for the minority. The best approach is modular: a core system that allows add-on features for specific groups, rather than a one-size-fits-all solution.

Limits of the Approach

CBDCs are not a silver bullet for financial inclusion. They solve some problems but create others.

Technical and cost barriers

Building and maintaining a CBDC infrastructure is expensive. For a small central bank, the cost of development, security audits, and ongoing operations may outweigh the benefits. If the system is not reliable, users will not trust it. If it is not affordable, the poor will not use it.

Risk of financial exclusion by design

If a CBDC is designed primarily for efficiency or surveillance, it may alienate the very people it aims to include. High KYC requirements, complex interfaces, or reliance on smartphones can create new barriers. Some designs also risk crowding out private sector innovation, reducing the variety of services available to low-income users.

Monetary policy and privacy tensions

Central banks may be tempted to use CBDCs for monetary policy tools—like negative interest rates or programmable money that expires. These features could harm low-income savers or be perceived as coercive. Privacy is another fault line: too much privacy enables illicit finance; too little erodes trust. Finding the balance is politically charged and context-dependent.

What to do instead

For many countries, improving existing payment systems—like interoperable fast payments or mobile money—may be more effective than launching a CBDC. A CBDC should be considered only when there is a clear gap that cannot be filled by private or public alternatives. Inclusion strategies should start with user needs, not technology.

If you are evaluating a CBDC for inclusion, start by mapping the actual barriers your target population faces. Talk to unbanked individuals, not just experts. Pilot small, iterate fast, and be honest about what the data says. The goal is not to issue a digital currency—it is to give people a better way to save, pay, and build economic resilience. Keep that focus, and the technology will follow.