Hybrid CBDC models are becoming the practical middle path for central bank digital currency design. Users hold a direct claim on the central bank, while banks, fintechs, and payment service providers handle wallets, onboarding, compliance, and customer-facing payment services. That split matters. It keeps sovereign money at the core, but it does not ask a central bank to become a national retail bank.

The Bank for International Settlements describes this approach as an intermediate model between direct CBDC and indirect CBDC. In plain terms: the central bank issues and backs the money, private firms build the front end, and the system includes a fallback path if a provider fails.

What Is a Hybrid CBDC Model?

A hybrid CBDC is a retail central bank digital currency where the user's balance is a legal claim on the central bank, not on a commercial bank or wallet provider. Private intermediaries still play a major role. They verify users, run mobile apps, process payment messages, provide customer support, and meet AML/CFT obligations.

Think of it as a two-tier CBDC architecture with a safety rail. The central bank controls issuance and final settlement. Private providers compete on usability, merchant tools, programmable payment features, analytics, and integrations.

Core features of hybrid CBDC models

Direct central bank liability: CBDC balances are claims on the central bank.
Private distribution: Banks and payment service providers manage wallets, KYC, apps, and user support.
Central bank ledger or synchronized records: The central bank maintains full or periodically updated retail balance data so it can preserve funds if an intermediary fails.
Segregated customer funds: CBDC holdings are kept off the balance sheet of the wallet provider, which protects users in insolvency.
Portability: Users should be able to move CBDC wallets or accounts between providers without losing access to funds.

That last point is easy to underestimate. In real payment systems, migration is where designs get tested. If a wallet provider exits the market on a Friday night, the central bank's backup ledger must know the customer's balance, the latest transaction state, and which pending payments are still valid. A vague recovery promise is not enough.

Direct, Indirect, Intermediated, and Hybrid CBDC Architectures

CBDC architecture usually falls into four broad designs. The labels vary across central banks, but the distinction is mostly about who owes money to the user and who stores retail payment data.

1. Direct CBDC

In a direct CBDC, the central bank manages customer accounts or wallets and processes every retail transaction. Users have a direct claim on the central bank. The downside is obvious: huge operational load, customer service demands, and a large concentration of sensitive data inside the central bank.

2. Indirect CBDC

In an indirect model, users hold claims on intermediaries, similar to bank deposits or stored value accounts. The central bank tracks wholesale balances of those intermediaries, not every retail balance. This keeps the private sector in charge of retail records, but the user's claim is not directly on the central bank.

3. Hybrid CBDC

In a hybrid model, users hold central bank money, but private firms run the payment interface. The central bank maintains a central ledger or synchronized retail balances. If a payment service provider fails, the central bank can help restart access and preserve balances.

4. Intermediated CBDC

An intermediated CBDC is close to hybrid, but the central bank may maintain only wholesale PSP balances while detailed retail transaction data stays with intermediaries. This can reduce central bank access to personal transaction data, but it requires tight rules for auditability, reconciliation, and recovery.

Why Central Banks Prefer Hybrid CBDC Models

Central banks do not want to break the two-tier monetary system unless they must. Commercial banks and payment firms already handle onboarding, fraud monitoring, merchant acceptance, dispute workflows, and app development. A hybrid CBDC keeps those functions in the market.

At the same time, central banks want the public to have access to risk-free digital money. Cash provides that today, but cash use is declining in many markets. A hybrid retail CBDC can offer a digital version of public money without turning the central bank into the only wallet provider.

To be blunt, a fully direct CBDC is usually the wrong choice for a large retail economy. It places too much operational and data responsibility on the central bank. Hybrid CBDC models are more realistic because they share the work.

Current State of Hybrid CBDC Development

CBDC work has moved from theory to pilots. A 2024 BIS survey reported three live retail CBDCs: the Bahamas Sand Dollar, Jamaica's Jam-Dex, and Nigeria's eNaira. The same survey found that roughly half of the central banks polled were experimenting with retail CBDCs, and a smaller share were running pilots.

Wholesale CBDC activity is also growing. According to the Atlantic Council CBDC tracker, well over 100 jurisdictions were researching, piloting, or launching CBDCs as of mid-2025. That count keeps shifting, so treat any exact figure as a snapshot rather than a fixed number.

Examples from major CBDC projects

China's e-CNY: Often described as a two-tier hybrid design, with the People's Bank of China issuing the digital yuan while commercial institutions support retail wallets and payment services.
India's e₹ pilots: The Reserve Bank of India has reported several million retail CBDC users across its pilots, involving multiple banks. The pilots include person-to-person, person-to-merchant, offline, and programmable payment features.
Japan's CBDC experiments: The Bank of Japan has tested multi-phase CBDC designs focused on operational feasibility in a two-tier system.
South Africa's retail CBDC research: The South African Reserve Bank has explored a model where CBDC remains a claim on the central bank while intermediaries execute payments.
Hong Kong's Aurum project: This BIS Innovation Hub and Hong Kong Monetary Authority project tested a two-tier retail CBDC system with wholesale CBDC and CBDC-backed stablecoins.

Technical Design Patterns in Hybrid CBDC

Hybrid CBDC models are not just policy diagrams. They come with real engineering choices.

Two-layer core and interface design

The first layer is the central bank-operated CBDC core. It handles issuance, redemption, settlement, and ledger integrity. The second layer consists of banks and PSPs that build wallets, merchant tools, APIs, and extra services.

For developers, this means most application work happens at the edge. You are not issuing money. You are integrating with the money layer.

Account-based and token-based access

Some research designs combine account-based systems with token or UTXO-style subsystems. Account-based models fit KYC-heavy retail and wholesale payments. Token-style designs can support offline payments and stronger privacy, although they introduce hard questions around double-spending and device security.

A practical detail: offline CBDC is not just a QR code problem. The hard part is reconciling value after devices reconnect. If two offline transactions try to spend the same balance, the system needs deterministic rules for finality, risk limits, and user messaging. Otherwise, your wallet app becomes a dispute machine.

Permissioned ledger and smart contract patterns

Some prototypes use permissioned distributed ledgers where the central bank initializes the network and approved institutions operate nodes or services. Others use conventional centralized ledgers with cryptographic audit logs. Both can work.

Blockchain is useful when multiple regulated parties need shared state and auditability. It is overhyped when teams use it only to make a wallet database sound modern. If the central bank is the only writer and every intermediary trusts its API, a well-designed centralized system may be simpler.

Privacy, Compliance, and Legal Design

Hybrid CBDC models sit in a sensitive place. They must support AML/CFT controls without creating a central database of everyone's spending habits.

European policy discussions, including work connected to the European Data Protection Supervisor, have stressed data minimization, role-based access, and privacy by design. Academic research has also explored asymmetric privacy, where receiving funds may carry stronger privacy than sending funds, while still allowing lawful traceability under defined conditions.

The legal structure matters as much as the code. Laws and regulations must define:

Whether CBDC balances are direct claims on the central bank.
How CBDC funds are segregated from PSP assets.
What happens if a PSP becomes insolvent.
Who performs KYC, transaction monitoring, and sanctions screening.
How users can switch wallet providers.
Which authority can access transaction data, and under what legal threshold.

Without this clarity, a hybrid CBDC can create confusion during stress. Users need to know who is responsible when a payment fails. Regulators need to know who holds the audit trail.

Impact on Banks, Fintechs, and Enterprises

Hybrid CBDC models affect more than central banks. Banks may see some deposits move into CBDC, especially if CBDC is highly convenient or interest-bearing. The IMF has warned that CBDC design can influence bank funding, credit supply, and monetary policy transmission.

Most central banks are likely to manage that risk with holding limits, transaction limits, or tiered remuneration. For example, a CBDC wallet could be useful for daily payments but unattractive as a large savings account.

For fintechs and enterprises, the opportunity is in services around the CBDC core:

Wallet design and identity integration.
Merchant acceptance and point-of-sale tools.
Programmable payment flows, such as conditional disbursements.
Compliance automation and transaction monitoring.
Interoperability with instant payments, card networks, tokenized deposits, and regulated stablecoins.
Cross-border settlement interfaces for wholesale and multi-CBDC networks.

If you work in payments architecture, expect ISO 20022-style messaging, API idempotency, reconciliation, and settlement finality to matter more than flashy wallet screens. A duplicate payment request after a mobile retry is boring until it credits twice. Good CBDC infrastructure must treat that as a first-class design issue.

Hybrid CBDC and Stablecoins

Hybrid CBDC models may also coexist with regulated stablecoins and tokenized deposits. Projects such as Aurum explored a structure where stablecoins are backed by CBDC in the interbank system. Recent policy proposals imagine private issuers offering user-facing tokens fully backed by central bank reserves or CBDC.

This could preserve the uniformity of money while allowing private products at the edge. But it only works with strict redemption rights, reserve rules, operational standards, and supervision. Otherwise, stablecoins can fragment liquidity and create run risk.

What Professionals Should Learn Next

If you are building a CBDC or digital asset skill set, focus on the intersection of money, architecture, and regulation. Learn how central bank money differs from commercial bank money. Study wallet custody, identity, settlement, privacy engineering, and payment message flows.

Blockchain Council readers can connect this topic with related learning paths such as Certified Blockchain Expert™, Certified Blockchain Developer™, and Certified Cryptocurrency Expert™. Developers should also practice with permissioned ledger concepts, smart contract security basics, API reconciliation, and digital identity patterns.

Final Takeaway

Hybrid CBDC models are likely to shape the next phase of digital money because they make a practical trade-off: central banks keep control of issuance and settlement, while private providers compete on access, usability, compliance, and programmable services.

Your next step is concrete: map one retail payment journey from wallet opening to merchant settlement, then identify which parts belong to the central bank core and which parts belong to a PSP. That exercise will teach you more about hybrid CBDC architecture than another abstract policy diagram.

Hybrid CBDC Models Explained: Central Bank Control with Private Innovation