A tokenized bank deposit is a commercial bank liability recorded as a blockchain token. The holder's claim runs to the issuing bank, and the bank stays responsible for who may hold it and where it may settle.
This page explains what a tokenized bank deposit is, how it differs from adjacent instruments, and why banks issue them on more than one chain. To issue a deposit token across chains, reach out to our team.
What is a tokenized bank deposit?
A tokenized bank deposit is a deposit at a commercial bank whose holder record is kept as a token. How much authority that token carries varies by product. In some, a transfer of the token is a transfer of the deposit. In others an official book stays at the bank and is updated to follow the token.
The instrument is a bank liability. Tokenization changes how the claim is recorded and how it can move. The bank remains the obligor, and the rules that apply to its deposits still apply.
How they differ from adjacent instruments
The holder's claim is the difference that matters.
| Instrument | What the holder owns | Who the claim runs to | Typical eligibility |
|---|---|---|---|
| Tokenized bank deposit | A bank liability | The issuing bank | The bank's own customers |
| Issuer-managed, reserve-backed stablecoin | A claim on the issuer's reserves | The stablecoin issuer | Broad, with screening |
| Tokenized treasury | A claim on government debt | The note or bill issuer | Often qualified investors |
| Tokenized fund share | A unit in a fund | The fund | The fund's subscription terms |
An issuer-managed, reserve-backed stablecoin is a claim on reserves the issuer holds. A tokenized deposit is the bank's own liability. Both can be designed to stay near one unit of a currency. The obligor is different.
The holder redeems with the issuing bank under that bank's terms. Tokenized capital markets collect these instruments in one map.
What has to be true for the token to stay a deposit
These hold on every chain where the token exists.
- The obligor stays the bank. The destination token is the bank's own contract, so the holder's claim still runs to the bank.
- Eligibility travels with the token. Only addresses the bank has approved may receive it. Each deployment keeps its own list, so the bank maintains that list wherever supply sits.
- Outstanding units stay reconcilable. A transfer debits one chain and credits another, so the bank's liability stays the same when a customer changes chains.
Those three are why a cross-chain token standard is the fit for a deposit token. The OFT standard uses debit-and-credit accounting: burn or lock on the source, mint or unlock on the destination. Each deployment still holds its own state. The bank aggregates those balances and any units still in flight, and checks the total against its deposit book.
Why banks issue the token on several chains
Because the customers and the venues that use the deposit sit on more than one chain. Issuing there lets the same liability be used as payment or collateral on the networks those customers already run.
Several deployments are several places that liability can sit. Cross-chain compliance is how the bank keeps eligibility current on each of them. The work after issuance is multi-chain asset operations: reconciliation, list maintenance, and a transfer record.
FAQ
Is a tokenized bank deposit the same as a stablecoin?
An issuer-managed, reserve-backed stablecoin is a claim on the issuer's reserves. A tokenized bank deposit is a claim on the issuing bank. The obligor, the regulatory perimeter, and the redemption path are different.
Does tokenization change deposit insurance?
Insurance, where it applies, follows the bank product and the jurisdiction. The record being a token leaves that unchanged.
Can a tokenized deposit move between chains?
Yes, where the destination token is the bank's own contract and outstanding units stay constant as they move.
Who may hold a tokenized bank deposit?
Whoever the issuing bank has approved. Where that is enforced with an onchain allowlist, the bank maintains one list on every chain where the token exists.
How does a bank know how many units are outstanding?
By aggregating each chain's supply and adding units that have been debited but not yet credited. A canonical model keeps that total unchanged when a holder moves, which is what makes the aggregate checkable against the deposit book.
Issue a deposit token across chains
A tokenized bank deposit works across chains when every deployment is the bank's own contract, eligibility is maintained on each of them, and outstanding units can be aggregated against the bank's books.
To scope issuance or a chain expansion for a deposit token, reach out to our team, or start at Developers.