Tokenized deposits vs. stablecoins: a banker's decision guide

A tokenized deposit and a stablecoin are both digital representations of cash on a ledger, but the issuer and the underlying liability are different. A tokenized deposit is a claim on a commercial bank deposit: the bank is the issuer, the token sits on the bank’s balance sheet, and it may be deposit-insured up to the local cap. A stablecoin is issued by a separate entity, often a nonbank, against a reserve of cash and equivalents it holds.

That distinction sounds technical, but it is the whole decision. It determines who regulates the instrument, whether holders have insurance, who is allowed to hold it, and what happens if the issuer fails.

For a bank weighing how to put cash on-chain, the choice is usually tokenized deposits first. Here is why, and where each instrument fits.

The two instruments look similar on a screen. Underneath, they are different financial objects.

Issuer and liability.A tokenized deposit is a liability of the issuing bank, recorded on the bank’s balance sheet and redeemable at par as a deposit. A stablecoin is a liability of its issuer, backed by a reserve the issuer manages. If the stablecoin issuer’s reserve is impaired, the token can break its peg. If a bank’s deposit is at risk, deposit insurance and bank resolution regimes come into play.

Regulation. Tokenized deposits sit inside the existing banking perimeter and are supervised by bank regulators such as the OCC in the US, BaFin in Germany, or MAS in Singapore. Stablecoins are increasingly governed by dedicated frameworks, including the GENIUS Act in the US and MiCA in the EU, which set reserve, disclosure, and licensing rules for issuers.

Insurance. A tokenized deposit can carry deposit insurance up to the local cap, because it is a deposit. A stablecoin is generally not deposit-insured; its safety depends on the quality and segregation of its reserve.

Settlement. Both can settle on-chain in near real time. The difference is whose books the settlement moves on. A tokenized deposit transfer is a movement of bank-money; a stablecoin transfer moves a reserve-backed token.

Who can hold it.Tokenized deposits are often restricted to a bank’s onboarded, KYC’d clients, which makes them well suited to controlled wholesale and institutional use. Stablecoins are frequently designed for open, permissionless circulation.

Neither instrument is strictly better. They solve different problems.

• Tokenized deposits fit bank clients who want on-chain settlement while staying inside the regulated deposit relationship: wholesale payments, intraday liquidity, treasury operations, and DvP settlement between known counterparties.
• Stablecoins fit open ecosystems where broad, permissionless transferability matters more than a direct banking relationship: payments across many counterparties, on-chain trading, and reaching holders a single bank does not serve.

A useful test: if the use case lives inside your client base and benefits from deposit treatment, a tokenized deposit is the natural fit. If it needs to circulate widely beyond your clients, a stablecoin model fits better.

For a bank, tokenized deposits are the path of least regulatory resistance. The instrument is already understood by supervisors, it stays on the balance sheet the bank already manages, and it preserves the deposit relationship and its protections. The bank is not creating a new kind of money so much as putting existing deposits on a faster settlement rail.

That lets a bank capture the operational benefits of on-chain settlement without stepping outside its existing supervisory framework. A stablecoin program, by contrast, usually means standing up issuance under a newer regime and managing a reserve as a distinct undertaking.

The underlying mechanics are similar for either instrument. The Liquid Network is an open-source Bitcoin sidechain, in production since 2018 and run by a federation of more than 80 members. Blocks arrive about once a minute, two confirmations give deterministic finality in roughly two minutes with no reorganizations, fees are sub-cent, and settlement runs 24/7.

Blockstream’s Asset Management Platform handles the lifecycle for both:

• Mint on deposit, burn on redemption. The issuer mints tokens when value enters and burns them when it leaves, keeping circulating supply tied to backing.
• Confidential Transactions. Amounts and asset types are hidden by default, which matters for institutional balances, while blinding keys allow selective disclosure to an auditor or regulator.
• Atomic FX and DvP.Liquid’s native multi-asset model lets two assets swap in a single atomic transaction, so a currency exchange or a delivery-versus-payment settlement either completes fully or not at all.
• Enforced holder rules.AMP’s Transfer-Restricted model uses per-asset whitelists and 2-of-2 HSM cosigning, which suits a tokenized deposit that should only sit with onboarded clients.

Tether’s USDt has been issued on Liquid since 2019, so the network has carried digital cash at scale for years. The same rails support a bank-issued tokenized deposit with the holder controls a regulated issuer requires.

Tokenized deposits and stablecoins are both digital cash, but a tokenized deposit is bank-money inside the banking perimeter, while a stablecoin is a reserve-backed token from a separate issuer. For a regulated bank, deposits are usually the cleaner starting point. Either way, the issuance and settlement layer should give you deterministic finality, native confidentiality, and enforced holder rules.