Why it matters now
The tokenised deposit category has moved from "interesting bank pilot" to "named regulatory perimeter" across major APAC and global jurisdictions in the last two years.
The HKMA's Project Ensemble runs a tiered architecture of tokenised deposits and tokenised assets against a wholesale CBDC. The Hong Kong Stablecoins Ordinance, which commenced 1 August 2025, explicitly excludes tokenised deposits from the stablecoin licensing perimeter, leaving them under existing banking supervision. The MAS in Singapore has framed parts of Project Orchid around purpose-bound money use cases that look operationally like tokenised deposit applications. The FSA Japan in japan has a Payment Services Act bank-issuance route for stablecoins that is essentially a tokenised deposit framework, with megabank consortia running the trust route in production via Progmat alongside.
Globally, OCC Interpretive Letter 1183 (March 2025) reaffirmed and extended the path for nationally-chartered US banks to engage in tokenised deposit and bank-issued stablecoin activity, building on Letter 1174 from 2023. EU jurisdictions treat tokenised deposits under existing CRD/CRR (Capital Requirements Directive and Regulation) bank supervision; they are not in MiCA scope. The UK treats them as bank deposits under existing supervision rather than under the stablecoin perimeter.
The convergent regulatory message: a tokenised deposit is a deposit, supervised under existing banking rules, with the chain treated as a feature of the product rather than a separate regulated activity. This is why tokenised deposits have shipped faster than novel stablecoin perimeters in several markets. The legal heavy-lifting was done forty years ago.
The macro framing in the BIS Annual Economic Report 2024 chapter on tokenisation is consistent with this. Tokenised deposits are the commercial-bank-money leg of the unified-ledger architecture, paired with a wholesale-CBDC settlement layer; the policy preference across major central banks has been to ship them under existing perimeters rather than to invent a new one. That is the durable signal for any operator picking which jurisdiction to ship in.
Common confusions
A tokenised deposit is not a stablecoin. Stablecoin types covered this. The deposit-context repeat: a stablecoin is a redeemable claim on a non-bank issuer (or a narrow-bank subsidiary), backed by segregated reserves, designed for bearer-style transferability with credible 1:1 redemption. A tokenised deposit is a representation of a customer's claim on a specific bank, single-name credit risk, settled across the bank's own ledger or a consortium ledger, supervised under banking law. Same chart shape, different instrument. Calling Kinexys "a JPMorgan stablecoin" in front of a treasury team invites a long correction.
A single-bank token is not the same as a multi-bank consortium token. A Kinexys deposit token is a claim on JPMorgan; a Partior token represents one of three banks' deposit liabilities depending on which bank issued the leg. Treating them as interchangeable misses the credit-risk allocation entirely. For a counterparty risk team, the issuing-bank field is the load-bearing column on the tokenised deposit position blotter.
A tokenised deposit is not a wholesale CBDC. A wCBDC is central bank money. A tokenised deposit is commercial bank money with single-name credit risk. The two sit at different layers and are typically intended to coexist in a tiered architecture rather than to substitute. Chapter VIII covers the comparison directly; see 08 wcbdc vs tokenized deposits. The Fnality construction is the partial exception; even there, the legal characterisation is genuinely hybrid.
A tokenised deposit is not a programmable stablecoin with extra steps. The programmability is a property of the chain, not of the underlying instrument. A stablecoin on the same chain has the same programmability surface. The differentiator is the legal nature of the issuer's liability, the supervisory perimeter, and the credit-risk profile, not the on-chain feature set.
The depositor does not own the chain. The depositor owns a claim on the bank, represented on the chain. If the chain freezes due to a bug or governance dispute, the depositor's claim on the bank is unaffected; the transfer mechanism is paused. Conversely, if the bank fails, the chain entry does not protect the depositor; the deposit insurance regime does, on the same terms as for a non-tokenised deposit at the same bank.
A tokenised deposit and a tokenised money-market fund balance are not interchangeable cash positions. The MMF tokens covered in Stablecoin types are fund interests, with NAV mechanics, distribution policy, and a fund regulator in the room. The tokenised deposit is a deposit, with a single bank as counterparty and a deposit-insurance overlay where the structure preserves it. Both might trade near par on-chain. They sit on different lines of the policy and different lines of the insolvency waterfall.
The chain operator is not the issuer. JPMorgan operates the Kinexys chain and also issues the tokens; the dual role is a coincidence of business model, not an architectural requirement. In a consortium ledger like Partior, the chain operator and the token issuers are different entities, and the legal claim runs to the issuing bank rather than to the operator. Designs that treat the operator as a backstop for a failed bank are misreading the legal stack.
The takeaway across all of these. The vocabulary of the four flavours of stablecoin from Chapter II does not map onto tokenised deposits. A tokenised deposit is a fifth instrument, sitting in commercial bank money, supervised under banking law, transferable on a chain that the bank or a consortium operates. Holding the distinction steady is most of the work.