Tokenized Deposits: How Programmable Bank Money Works in 2026

While stablecoins have dominated the headlines in 2026 thanks to the GENIUS Act, which gave them a major boost and laid the foundation for dollar-pegged tokens to become massively more widespread, there is another asset type that is also rapidly gaining momentum – tokenized deposits.

These innovative assets give banks a way to enhance their existing operations by turning traditional deposit money into digital tokens on a shared, programmable blockchain or distributed ledger. September alone has marked two major breakthroughs in this field, moving the concept another step closer to practical application.

First, the "Great British Tokenised Deposit" (GBTD) initiative, which brings together seven UK lenders – Barclays, HSBC UK, Lloyds, NatWest, Monzo, Nationwide Building Society and Santander – ran live retail pilots in which real customer payments moved between participating institutions using tokenized sterling deposits. These tests included two remortgage completions (funds were locked and released automatically) and a consumer “marketplace” transaction.

On September 22, Canada's Big Six banks – RBC, TD, BMO, Scotiabank, CIBC, and National Bank – announced a joint initiative to explore a shared Canadian dollar (CAD) tokenized deposit network “to drive responsible innovation and facilitate broad participation in the digital money ecosystem.”

This article aims to help payment processors, fintechs, corporate treasurers, and merchants navigate these new financial waters and explain what tokenized deposits are, how far interoperability has come, and what changes for businesses when they receive tokenized deposits as payments.

What Are Tokenized Deposits?

Unlike the concept of Central Bank Digital Currencies (CBDCs) or stablecoins, tokenized deposits put standard bank account balances on a distributed ledger. They stay inside the banking system, and depending on the jurisdiction and how the product is structured, they can keep the same regulatory treatment and deposit insurance as an ordinary deposit. 

This allows banks to issue tokenized deposits that act as a digital representation of traditional commercial-bank deposits, recorded and transferred on a distributed ledger. The terminology isn't settled yet. Some sources use "deposit tokens" for claims that can move between holders, and "tokenized deposits" for models where the bank keeps the record and settles between banks in the usual way. In this article, we use "tokenized deposits" for both unless the difference matters. 

While tokenized deposits are technically still “ordinary bank money,” they leverage a number of innovative, blockchain-native features aimed at solving some critical friction points in modern finance, such as programmability, near-instant settlement, and 24/7 availability.

Programmable Money via Smart Contracts: Banks can attach conditions to a payment, so funds are released to a supplier once an accepted confirmation arrives, for example, that a shipment has cleared the port. That can shorten escrow-style delays. It doesn't remove every risk, though: the contract is only as reliable as the data it receives, and disputes over delivery, credit risk and technical failures still need ordinary handling.

Faster, Around-the-Clock Settlement: Cross-border wires and correspondent payments can still take days. Tokenized deposits can settle within seconds and outside banking hours, at least inside one bank's system or a working multi-bank network. Where both sides of a trade sit on compatible infrastructure, they also make delivery-versus-payment (DvP) possible, with the asset and the payment changing hands at the same moment. Instant domestic schemes such as FedNow already run 24/7 without tokens, so the real gain is programmability and cross-border reach rather than speed alone.

Cash Leg for Tokenized Assets: On networks where other assets are tokenized too, such as bonds, fund units or gold, a tokenized deposit can serve as the payment side of the trade. The fractional ownership and liquidity come from the asset being traded, not from the deposit.

Still, at their core, these assets are not a new form of money creation but rather a technological upgrade of existing deposits. Legally, they're treated as deposits under existing banking law, as long as they meet the legal definition of a deposit. The GENIUS Act confirmed this from the other side: it excludes deposits, including those recorded on a distributed ledger, from its definition of a payment stablecoin.

How Do Tokenized Deposits Work?

Generally, tokenized deposits’ lifecycles can be divided into three main stages.

 

• Mint: When a customer tokenizes part of a balance, the bank records the same amount on the ledger and, under the product's rules, moves, mirrors or locks that amount in the ordinary account, so the customer can't spend it twice. One token unit corresponds to one unit of the deposit claim. That's a nominal match, not a separate 100% reserve: the bank funds itself in the usual way, as with any deposit.
• Transfer: Deposit tokens can be moved peer-to-peer or according to smart contract rules. Transfers can be instantaneous, 24/7, and programmable. For instance, funds can be locked until a condition such as delivery confirmation or land registry update is met.
• Burn / Redeem: The holder redeems tokens back into an ordinary balance at the bank, under the product's rules. If the money then needs to go to another bank, that's a separate payment. A USD deposit token is already denominated in dollars, so there's nothing to "convert to fiat".

Additionally, while tokens are inside the issuing bank’s controlled environment, the economic claim never leaves the regulated banking system. Examples of such assets include JPM Coin (JPMD), live on Base since November 2025 and on Ethereum since October 2026, for approved institutional clients, as well as Citi Token Services and HSBC's Tokenised Deposit Service. 

Hybrid Designs and the "Shape-Shifting" Question

Some products are built to behave differently depending on where the token sits. Custodia's Avit is one example: inside its network it's designed to work as a deposit, and outside it the product is being developed to fit the GENIUS Act's payment stablecoin regime. That's a design choice of one product, not a rule for the whole asset class.

For most tokenized deposits, what a holder owns depends on the legal structure, not on the wallet address. In some models, the token is a transferable claim, and the same bank stays the debtor whoever holds it. In others, the sender's position is cancelled and the recipient's bank credits a new deposit on its own books. In many products, transfers outside an approved list simply aren't allowed.

Deposit insurance follows the same logic. It depends on the jurisdiction, the bank, the nature of the claim and the holder's eligibility. In the US, the standard FDIC limit is $250,000 per depositor, per insured bank, per ownership category, and tokenized and ordinary deposits in the same category share that limit rather than adding up. FDIC rules don't extend to other countries: the UK and Canada have their own schemes, and deposits at a US bank's foreign branch aren't FDIC-insured just because of the brand. The FDIC's April 2026 proposal on the topic takes a technology-neutral approach, but it isn't a final rule yet.

For a business receiving a tokenized deposit, the useful question isn't where the token is, but which institution it now has a claim on, under which rules, and which insurance scheme covers it.

Tokenized Deposits vs Stablecoins vs Wholesale CBDCs

While tokenized deposits might seem functionally similar to CBDCs and stablecoins, there are a number of key technical and legal distinctions that set them apart. Namely, tokenized deposits are full-fledged bank deposits: they stay on the bank's balance sheet and may carry insurance and pay interest. 

Payment stablecoins under the GENIUS Act are 1:1 reserve-backed tokens. Their issuers can't pay interest or yield for holding them, they sit outside deposit insurance, and a bank that wants to issue one generally needs a separate approved subsidiary. A wholesale CBDC is a direct liability of a central bank, available to banks and other financial institutions and used mainly for interbank settlement. Retail CBDCs, by contrast, are designed for the public, and a CBDC doesn't have to run on a distributed ledger at all.

How the GENIUS Act Shapes Bank Incentives 

Signed into law on July 18, 2025, and officially coming into effect on January 18, 2027 (a date the OCC confirmed in its final rule on October 21, 2026), the GENIUS Act has introduced a critical new legal mechanism that explicitly excludes deposits – including blockchain-based – from the definition of a “payment stablecoin.”

For banks, this means they can issue deposit tokens that will retain the legal status of ordinary deposits, including eligibility for deposit insurance, the ability to pay interest, on-balance-sheet treatment, and existing supervisory regime. Meanwhile, issuing a payment stablecoin would generally require a separate subsidiary, 1:1 liquid reserves, and a ban on paying interest.

That gives US banks a practical reason to prefer tokenized deposits: the deposit model keeps their usual funding and accounting. Many programs predate the law, though. Citi Token Services has been a commercial service since October 2024, and the UK and Canadian initiatives follow their own national frameworks. The Act didn't start the trend, but it gave US banks legal clarity at a time when launches from JPMorgan, Citi, HSBC, BNY and Wells Fargo were already picking up.

Current Interoperability Landscape

Most tokenized deposit activity in 2026 still happens inside single banks. For example, a corporate client of JPMorgan can pay another JPMorgan client with JPM Coin, and a Citi client can pay another Citi client through Citi Token Services. Citi has also connected the service to its 24/7 USD Clearing, though that doesn't mean a Citi token can be sent to any outside wallet: crediting the end recipient depends on the receiving institution. Moving a tokenized deposit between customers of different banks is currently only possible on a handful of networks, and even then such capability is limited.

Launched for initial use in July 2026, Swift’s shared ledger is so far the most expansive initiative that aims to enable cross-bank transfers of tokenized deposits. It includes 17 participating banks across six continents, among them Citi, HSBC, DBS, BNP Paribas, Standard Chartered, UBS and Wells Fargo, which were preparing pilots when it launched. Since then, Standard Chartered and HSBC have announced a cross-border transaction (August 19, 2026), UOB and HSBC have completed HKD transactions (August 26, 2026), and DBS, OCBC and UOB have tested Singapore-dollar payments.

The ledger itself does not hold the deposits, with each bank continuing to issue and manage its own tokenized deposits on its own systems. Instead, Swift’s ledger simply records and validates the interbank payment commitments, allowing them to be moved 24/7, including overnight and on weekends. Final settlement between banks still takes place on existing rails such as RTGS systems or correspondent banking, with Swift acting as an orchestration layer – not a shared token that any customer can freely receive.

In the United States, The Clearing House is building the On-Chain Money Initiative that leverages Quant’s technology. The goal is to create a network where participating banks can clear and settle tokenized deposits with one another and connect those movements to existing RTP and CHIPS rails. While it’s not live for customers yet, institutions are expected to get access to the network in the first half of 2027.

Meanwhile, JPMorgan's Kinexys platform, which includes JPM Coin, processes roughly $7 billion a day and more than $4 trillion in cumulative volume, per J.P. Morgan (October 2026). These are platform-wide figures, not the volume of JPMD on public chains. Access, however, is restricted to approved institutional clients of JPMorgan, and it’s not an open interbank network.

Project Agorá, convened by the Bank for International Settlements, tests a more ambitious model: a shared multi-currency platform that combines tokenized commercial-bank deposits with tokenized central-bank reserves for atomic wholesale settlement. In July 2026, real-value testing involved 28 financial institutions and central banks, about CHF 800,000 and 17 scenarios across six currencies. The project remains experimental and is not available for everyday payments.

The latest breakthrough in terms of actual customer-to-customer transfers between different banks was achieved in the UK via the aforementioned GBTD in September 2026. The platform, built by Quant, allows the tokens to move between customers of the participating banks while each bank continues to issue its own deposits.

Still, production-grade interoperability remains limited in late 2026. Earlier live trials, such as those under Singapore's Project Guardian in 2022 and the Swiss Deposit Token proof of concept in 2025, showed it could work. Today, real customer value moves between different banks mainly in the UK GBTD pilots and in selected corridors on Swift's ledger. Most other activity is still confined to single-bank systems or tightly controlled allow-lists, and interoperability may widen within specific networks in 2027 if planned services such as The Clearing House network launch on schedule – but it is not yet the default way money moves between banks.

What Tokenized Deposits Mean for Businesses

By design, payments with tokenized deposits are different from both traditional bank transfers and stablecoin transfers, which raises several practical questions. 

First of all, such settlements can become final within seconds and are available around the clock inside a single bank’s system or a working multi-bank network such as the UK’s GBTD. On orchestration layers like Swift’s ledger, the token commitment may move quickly, but the underlying interbank settlement still follows traditional rails and can be subject to cut-off times. In any case, it is crucial to know exactly when the funds become irrevocable and usable in your account.

The redemption path is equally important. While the receiving bank can simply credit a regular deposit account in some networks, others would require the token to be redeemed or burned at the original issuing bank, which can add steps, delays or fees. This is why it needs to be confirmed in advance whether a particular bank can accept the specific token and convert it cleanly.

Deposit insurance depends on which institution you end up with a claim on, the jurisdiction and the product's legal structure. When a payment comes through an interbank arrangement, your claim is usually on your own bank, so your protection follows your own bank's scheme.

One of the biggest advantages is programmability, which allows, for example, funds to be locked until a condition is met – goods are delivered, a registry is updated, or a milestone is certified – and then released automatically. This can reduce the need for traditional escrow in marketplace or trade transactions. The UK pilots already demonstrated this in remortgage and consumer purchase scenarios.

Summarizing, here is a short checklist any business or payment processor should keep in mind:

• Which bank issued the token and on which network?
• Is my bank a participant in that network?
• When does the payment become final and available?
• Can the token be credited directly to my operating account?
• Which institution do I hold a claim on, and which deposit insurance scheme covers it?
• What integration work is required with my current systems?

What a business actually receives: three scenarios

Whether a tokenized deposit behaves like a fast bank payment or like a headache depends less on the token than on how the payer and the merchant are connected. Here are the three situations a business is most likely to run into.

Scenario 1: both businesses use the same product or network

Say the buyer and the supplier are both approved clients of the same bank's token service, such as JPM Coin or Citi Token Services. Here the payment moves a claim on one bank from one client to another. The supplier ends up holding a claim on that same bank, recorded on the product's ledger. Depending on the product, it shows up either as a token balance or directly as a credit in the supplier's account.

That distinction is worth checking before the first invoice goes out. A token balance and an ordinary account balance can come with different rules on what you can do with them and when. Finality is set by the product terms, too: inside a single bank's system, a transfer is often irrevocable within seconds and available around the clock, but only the bank's documentation tells you the exact moment.

Withdrawing is a separate question. Moving funds from the token balance into an ordinary account follows the product's redemption terms. And paying a supplier who banks somewhere else takes you back to wires or instant payments, with their usual hours and fees. Within one product, a tokenized deposit is close to an instant internal transfer; the moment money needs to leave it, ordinary banking rules apply again.

Scenario 2: different banks connected by a compatible interbank arrangement

This is the model behind initiatives like the UK's GBTD and Swift's shared ledger, and the one The Clearing House is building for 2027. It's tempting to picture one token travelling from Bank A to Bank B. That isn't how these arrangements are designed.

In practice, the payer's bank reduces the payer's position, and the merchant's bank credits the merchant on its own books, as a tokenized or an ordinary deposit depending on the setup. The merchant now holds a claim on its own bank, not on the payer's. What Bank A owes Bank B is settled separately between the two banks, under the arrangement's rules: through central bank reserves, an RTGS system, correspondent accounts or netting. On Swift's ledger, for example, payment commitments can move 24/7, while final settlement between banks still runs on existing rails.

For the merchant, the practical question is when your own bank treats the credit as final. Some arrangements let the receiving bank credit you as soon as the commitment is recorded. Others wait until the interbank leg settles, which can mean cut-off times and weekend gaps. Ask your bank which one applies before you release goods against an incoming payment.

Scenario 3: the merchant only accepts USDT, USDC or a regular bank transfer

There's no automatic compatibility here. A deposit token can't be sent to a USDT address, and it doesn't arrive in an ordinary account just because both are dollars.

To pay, the buyer has to convert first. They can redeem the token into an ordinary balance at their bank and send a wire or an instant payment. Or they can use the funds to buy USDC or USDT and send that. Either way, the merchant receives something else: a bank transfer or a stablecoin, with that instrument's own finality, fees and risks. The tokenized deposit never reaches the merchant, and any conversion cost or delay sits with the buyer, unless it's built into the price.

For a merchant already taking crypto, this is the familiar case. A processor such as 0xProcessing accepts the stablecoin leg (USDT and USDC across 20+ networks, screened for AML before crediting) and doesn't need to know where the buyer's money sat before conversion. Until your bank joins a network, a tokenized deposit is simply one more way for a buyer to fund a payment you receive in a form you already support.

The three scenarios side by side

Conclusion

Overall, tokenized deposits give banks a regulated route to programmable money that stays inside the banking system. In the US, the GENIUS Act made that route legally clearer. And 2026 brought live payments between banks in the UK pilots and on Swift's ledger, building on trials that go back to 2022.

As it stands today, a tokenized deposit works like a faster, programmable bank transfer when both sides use the same product, or when their banks share a compatible arrangement. When they don't, the buyer converts first, and the merchant receives an ordinary transfer or a stablecoin instead.

 

Most importantly, it is also a practical question of which exact rails the payer and the receiver decide to use, and understanding these new instruments is now necessary for anyone designing or receiving modern payment flows.

FAQ