How Do Tokenized Bank Deposits Work for Institutions?
A tokenized bank deposit is a commercial-bank deposit liability recorded as a transferable token on a blockchain — it settles wholesale payments in seconds, stays a bank claim on the issuing bank's balance sheet, and differs structurally from a reserve-backed stablecoin.
TL;DR — Key Takeaways
- ✓What it is: A deposit token is a commercial-bank deposit recorded on-chain as a transferable token. The holder is a creditor of the bank — the token is a bank liability, not an RWA-collateralized stablecoin.
- ✓Deposit token vs stablecoin: A deposit token sits on a bank's balance sheet and only a supervised bank can issue it. A stablecoin is a non-bank claim on a segregated reserve. The distinction drives capital, insurance, and which regulator applies.
- ✓Who ships it: JPMorgan's Kinexys (ex-Onyx) reports $2B+ in daily deposit-token volume. Citi Token Services runs cross-border cash and trade. The Regulated Liability Network has piloted multi-bank settlement.
- ✓Where it breaks: Single-bank tokens settle instantly and finally; cross-bank finality needs a shared network or a central-bank leg. Deposit-insurance treatment and retail classification remain unresolved.
- ✓Who it's for: Wholesale settlement between institutions, treasury cash mobility, and DvP against tokenized securities — not retail payments or unbanked-user wallets.
What Is a Tokenized Bank Deposit, and Why Banks Built One
A tokenized bank deposit — a deposit token — is a commercial-bank deposit recorded as a transferable token on a blockchain, where the holder remains a creditor of the issuing bank. It is a bank liability wearing a new wrapper, not a new asset class. When a corporate treasury holds $10 million of a bank's deposit token, it holds a $10 million claim on that bank, the same claim it would hold as a balance in a checking account, now movable in seconds and around the clock.
Banks built deposit tokens because their existing cash rails are slow and closed. A wire moves during business hours, clears in batches, and stops at borders. A deposit token moves on a programmable ledger that runs 24/7, settles atomically, and can be attached to conditions — pay only when the tokenized bond is delivered, release funds only after a KYC check passes. This is the same programmability that makes real-world asset tokenization attractive across every asset class, applied to the most basic instrument on a bank's books: money it owes its customers.
“Tokenized deposits let commercial banks keep the two-tier monetary system intact: central-bank money settles between banks, and tokenized deposits settle between the customers of those banks. This preserves the singleness of money in a way that non-bank stablecoins do not guarantee.”
— Bank for International Settlements, Annual Economic Report: The Next-Generation Monetary System, 2023
That framing matters because it explains why regulators are far more comfortable with deposit tokens than with privately issued stablecoins. A deposit token does not create new money or a new class of issuer. It re-expresses money that already exists inside the regulated banking system. The rest of this article covers how it differs from a stablecoin, how banks issue one compliantly, where it settles well, and — most usefully — where the model breaks.
Deposit Token vs Stablecoin: The Difference Is the Balance Sheet
A deposit token is a liability of a commercial bank; a stablecoin is a claim on a reserve held by a non-bank issuer. That single structural fact — whose balance sheet the money lives on — determines the regulator, the capital treatment, the insurance question, and the credit risk the holder actually carries. They look identical in a wallet and behave differently in a crisis.
When you hold a stablecoin, you own a claim on a pool of cash and short-dated securities segregated from the issuer. The issuer is typically a payments or e-money firm, and your protection comes from reserve quality and the bankruptcy-remoteness of that pool. When you hold a deposit token, you are an unsecured creditor of a bank, and your protection comes from bank supervision, capital rules, and — where it applies — deposit insurance. This is a different risk than the reserve model behind an RWA-collateralized stablecoin, where the backing is an explicitly ring-fenced asset pool rather than a bank's general obligations.
| Property | Deposit Token | Stablecoin |
|---|---|---|
| Who can issue | Supervised commercial bank only | Non-bank issuer (e-money / payments firm) |
| What the holder owns | A deposit claim on the bank | A claim on a segregated reserve pool |
| Balance-sheet location | On the bank's balance sheet as a liability | Off the issuer's balance sheet, reserve-backed |
| Deposit insurance | Possible if mapped to a named account holder | Generally not insured |
| EU classification (MiCA) | Bank deposit — outside MiCA crypto regime | E-money token — inside MiCA |
| Primary use today | Wholesale / institutional settlement | Retail and crypto-market payments |
“Deposit tokens and stablecoins are not interchangeable. A deposit token is a bank's own deposit made programmable; it inherits the bank's regulatory perimeter. A stablecoin sits outside that perimeter and must earn trust through reserve transparency instead.”
— Oliver Wyman & Onyx by JPMorgan, Deposit Tokens: A Foundation for Stable Digital Money, 2023
How a Bank Issues a Deposit Token Compliantly
A compliant deposit token is minted only when the issuing bank debits a customer's deposit account by the same amount, so the token and the underlying deposit stay a single one-to-one claim. Every mint is backed by an existing deposit, every transfer moves a bank liability between identified account holders, and every burn credits a deposit account — the token never becomes a free-floating instrument detached from the bank's books.
The mechanics that make this work in a supervised environment are the same identity and control primitives used across institutional RWA issuance:
- Permissioned transfer: only wallets tied to KYC-verified, onboarded account holders can hold or receive the token; transfers to unknown wallets are rejected at the ledger level
- One-to-one deposit mapping: each token in circulation corresponds to a booked deposit liability, reconciled continuously against the core banking ledger
- Real-time AML screening: sanctions and transaction-monitoring checks run inline before a transfer settles, not in an overnight batch
- Auditable mint/burn trail: an immutable record links every token event to a core-banking entry so supervisors and auditors can reconcile the token supply to the deposit book
- Legal classification opinion: a jurisdiction-specific opinion confirms the token is a deposit, not e-money or a security, before launch
This is where a compliance-native settlement layer earns its place. Enforcing identity and transfer rules in application code is fragile — a bug or a bypass route can let a bank liability land in an unverified wallet. Blockmaze enforces these constraints at the protocol level, so a deposit token cannot be transferred to a wallet outside the bank's onboarded registry regardless of the application routing it. The same protocol-level enforcement that governs a tokenized deposit also governs the CBDC and wholesale settlement rails a central bank might sit above it, which is what lets the two tiers of money interoperate cleanly.
Key Insight
The hard part of a deposit token is not minting it — it is keeping the token supply and the deposit book reconciled in real time while enforcing that the token can only ever move between verified account holders. Get the reconciliation wrong and the bank has issued phantom liabilities; get the transfer control wrong and it has issued an uninsured, unmonitored payment instrument by accident.
Which Banks Run Deposit-Token Programs Today
The largest live program is JPMorgan's Kinexys platform, formerly Onyx, which JPMorgan reports has processed over $1.5 trillion in cumulative volume since 2019 and handles more than $2 billion in transactions on a typical day. Citi, Standard Chartered, and a bank consortium behind the Regulated Liability Network run parallel efforts, each targeting wholesale settlement rather than retail payments.
JPMorgan Kinexys (JPM Coin / ex-Onyx)
Kinexys is the deposit-token rail JPMorgan uses to move dollars and euros between the accounts of its institutional clients. A treasurer can fund an account and sweep cash across time zones outside normal cut-off windows, because the token settles on JPMorgan's own ledger 24/7. It is a single-bank system by design: both sides of every transfer are JPMorgan account holders, which is exactly why settlement is instant and final — the bank controls both legs of the ledger.
Citi Token Services
Citi Token Services applies the same model to cross-border cash management and trade finance. In pilots, Citi has used tokenized deposits to replace paper letters of credit with programmable payment guarantees that release funds when shipping conditions are met, compressing a settlement that took days into minutes. Like Kinexys, it operates within Citi's own regulated perimeter for Citi's institutional clients.
The Regulated Liability Network (multi-bank)
The Regulated Liability Network is the attempt to solve the single-bank limitation. It is a proof-of-concept for a shared ledger where multiple banks issue their own deposit tokens on common infrastructure, with a central-bank settlement leg to make cross-bank transfers final. It is the piece most banks agree is missing, and — as the failure-modes section explains — the piece that is hardest to ship.
“Since inception, our blockchain-based accounts have processed more than $1.5 trillion in notional value, with average daily volumes exceeding $2 billion. Kinexys Digital Payments now operates across multiple currencies for institutional clients.”
— JPMorgan Kinexys (formerly Onyx), Platform Disclosures, 2025
One use case ties every program together: delivery-versus-payment against tokenized securities. When the cash leg is a deposit token and the asset leg is a tokenized bond or a tokenized US Treasury, both legs can settle atomically on the same ledger — either both move or neither does. That removes settlement risk that traditional systems paper over with T+1 or T+2 windows.
Who Deposit Tokens Are For, Who They Are Not For, and When They Break
Deposit tokens fit wholesale settlement between institutions that already bank with the issuer; they do not fit retail payments, unbanked users, or open-network use where the counterparty is not an onboarded account holder. The model breaks precisely at the boundary of the issuing bank — the moment money must move to someone the bank does not carry as a customer.
Who it is for
- Corporate treasuries moving cash 24/7 across accounts and time zones without cut-off windows
- Institutions settling securities that need an on-chain cash leg for atomic DvP against tokenized bonds and funds
- Cross-border and trade finance where programmable release conditions replace manual, multi-day settlement
Who it is NOT for
- Retail consumer payments — a single-bank token only works if both parties bank with the issuer, which almost no retail flow satisfies
- Unbanked or permissionless users — the token cannot leave the onboarded, KYC-verified registry by design
- Open DeFi composability — a bank liability with hard transfer restrictions cannot circulate freely through permissionless protocols the way a stablecoin can
When the model breaks
Four failure modes recur across every program:
- Multi-bank interoperability: a token issued by Bank A is Bank A's liability. Moving value to a Bank B customer means A's token must be redeemed and B's issued, which requires a shared network and a settlement leg. Without it, every bank builds an island.
- Settlement finality across banks: one bank cannot make another bank's liability final. True cross-bank finality needs central-bank money to settle the interbank leg — the exact gap the Regulated Liability Network is trying to close.
- Deposit-insurance treatment: whether a deposit token is insured depends on it mapping cleanly to a named, identifiable account holder. Pooled or bearer-style designs can fall outside insurance, and regulators have not fully settled the retail case.
- Regulatory classification drift: a token structured slightly wrong can be reclassified from a bank deposit into e-money or a security, moving it under a different regulator with different capital and disclosure rules. This is why issuers structure custody and records and obtain a legal opinion before minting a single token.
Key Insight
The strength of a deposit token — that it stays inside one bank's regulated perimeter — is also its ceiling. Instant, final, insured settlement is easy inside that perimeter and hard the moment you cross it. Every serious question about deposit tokens is ultimately a question about how to settle between two different banks' liabilities without giving up finality.
Wholesale vs Retail: Why Deposit Tokens Stay Institutional
Deposit tokens are almost entirely wholesale today because institutional flows involve identified counterparties inside a bank's existing relationships, while retail flows demand reach to arbitrary recipients the bank does not onboard. The wholesale market fits the single-bank, permissioned model exactly; the retail market fights it at every step.
A wholesale deposit token settles a $50 million interbank cash leg between two identified institutions in seconds — a clean fit. A retail deposit token would need to reach any merchant or person, most of whom bank elsewhere, which reintroduces the multi-bank finality problem for every $20 payment. That is why regulators and banks alike treat the retail case as a later, harder problem, and why McKinsey's tokenization work puts near-term deposit-token adoption squarely in cash management, securities settlement, and trade rather than consumer payments.
“The most tangible near-term value from tokenized deposits and cash lies in wholesale flows — intraday liquidity, cross-border payments, and on-chain settlement of tokenized securities — where counterparties are known and finality can be engineered.”
— McKinsey & Company, From Ripples to Waves: The Transformational Power of Tokenizing Assets, 2024
According to the BIS, the endgame most central banks favor is a two-tier system: wholesale central-bank money settling between banks, and tokenized deposits settling between those banks' customers on shared infrastructure. According to JPMorgan, that shared infrastructure is already commercially live for single-bank flows and processing billions of dollars a day — the remaining work is connecting the islands. A compliance-native settlement layer that enforces identity and transfer rules at the protocol level, rather than in fragile application code, is what makes cross-bank deposit-token settlement viable without sacrificing the finality that makes the single-bank version work.
Building a Deposit-Token or Wholesale Settlement Rail?
Blockmaze enforces identity, transfer restrictions, and mint/burn reconciliation at the protocol level — the invariants a bank liability needs to stay compliant across single-bank and multi-bank settlement.
The Bottom Line on Tokenized Bank Deposits
A deposit token is the most conservative form of on-chain money: a regular bank deposit made programmable, still a liability of a supervised bank, still inside the regulatory perimeter. That is why banks reached for it before they reached for stablecoins, and why JPMorgan and Citi have live programs moving billions a day while the retail stablecoin debate rages on.
The unsolved problem is not the token — it is settlement between banks. Until a shared network with a central-bank settlement leg is production-grade, deposit tokens will keep delivering instant, final settlement inside single banks and stumbling at the boundary between them. The banks that win the next phase will be the ones whose deposit tokens can cross that boundary without losing finality, insurance clarity, or their classification as a deposit.
Frequently Asked Questions
What is the difference between a deposit token and a stablecoin?
A deposit token is a claim on a commercial bank — it sits on the bank's balance sheet as a deposit liability and earns the same treatment as the deposit it represents. A stablecoin is issued by a non-bank against a reserve of cash and short-dated assets held in segregated accounts. The holder of a deposit token is a bank creditor; the holder of a stablecoin is a claimant on a reserve pool. That distinction drives capital treatment, deposit insurance eligibility, and which regulator supervises the issuer.
Are tokenized bank deposits covered by deposit insurance?
It depends on structure and jurisdiction, and it is not automatic. A deposit token can, in principle, represent an insured deposit if it maps one-to-one to a named account holder that the bank can identify for insurance purposes. Most live wholesale programs, including JPMorgan's Kinexys, operate as institutional settlement rails where insurance coverage is not the design goal. Retail-facing deposit tokens raise unresolved questions about pass-through insurance that regulators in the US and EU have not fully settled.
Who actually issues tokenized bank deposits today?
Regulated commercial banks issue them. JPMorgan runs the largest program under its Kinexys platform (formerly Onyx), which JPMorgan reports processes over $2 billion in daily transaction volume. Citi operates Citi Token Services for cross-border cash and trade. A consortium of banks including the Regulated Liability Network has piloted shared multi-bank deposit-token settlement. Issuance is restricted to supervised banks because the token is a bank deposit liability, not a payment token any entity can mint.
Do deposit tokens settle instantly and finally?
Within a single bank's closed system, yes — transfers between two accounts at the same issuing bank settle atomically and with immediate finality because the bank controls both sides of the ledger. Across banks it is harder. Multi-bank settlement finality requires a shared arrangement or a central-bank settlement leg, because one bank cannot unilaterally make another bank's liability final. This interoperability gap is the main reason most programs remain single-bank today.
How are deposit tokens classified under MiCA and US law?
Under the EU's MiCA regulation, a token that is a bank deposit liability generally falls outside the crypto-asset regime and stays under existing banking and payment-services law, unlike e-money tokens which MiCA covers directly. In the US, banking regulators have signaled that a deposit token issued by a bank is treated as a deposit rather than a security or a new instrument. Classification still turns on exact structure, and issuers obtain a legal opinion before launch.
Related Articles
What Is RWA Tokenization? A Complete Guide
The pillar guide to how real-world assets — including bank liabilities — move on-chain compliantly.
Stablecoin RWA Collateral and Compliance
The reserve-backed alternative to deposit tokens, and how RWA collateral backs a non-bank on-chain dollar.
How Asset Managers Launch Compliant Tokenized Money Market Funds
The yield-bearing cash instrument that competes with deposit tokens for institutional treasury allocations.
Institutional RWA Custody Solutions and Compliance
How the balance-sheet and account records behind a deposit token are held and attested.