Tokenized Deposit Issuance
Issue bank money on-chain — permissioned, core-ledger settled, on the balance sheet.
Represent a bank's own deposit liability as a permissioned on-chain token, so institutional clients move on-us bank money 24/7 with same-second finality. It changes the rail, not the money: the token stays a deposit on the balance sheet, reconciled 1:1 to core banking — the institutional counterpart to a reserve-backed stablecoin.
What you get.
Bank-issued liability
The token is the bank's own deposit — a senior liability on its balance sheet, not a reserve-backed bearer instrument. The issuer of record is a chartered bank.
Permissioned transfer
ERC-1400-style controlled transfer — only KYB-verified, sanctions-screened, jurisdiction-cleared holders can receive. No bearer, no anonymous transfer.
Core-ledger settlement
Mint and redeem bind atomically to a posting on the core deposit ledger — a two-phase commit across the two ledgers, reconciled 1:1 so supply never diverges.
Shared platform spine
Reuses the same identity, custody, registry, and on-chain AccessManager as every other asset class — one platform, a new product declaration.
The lifecycle.
Define the token
Configure the deposit token — currency, decimals, permissioned transfer policy, and the core-ledger control account.
Permission holders
Allowlist KYB-verified, jurisdiction-cleared holders in the identity registry; sanctioned addresses are blocked.
Issue & settle
Mint and redeem against the core ledger, atomically reconciled 1:1 with same-second on-chain finality.
A tokenized deposit stays a bank deposit for capital, liquidity, and insurance purposes (OSFI / CDIC in Canada), with full AML and sanctions controls (FINTRAC, SEMA). QBridge provides the rails; the banking license and core-ledger integration sit with the issuer.
Ready to launch tokenized deposits?
Start in the issuer workspace, or talk to us about embedding QBridge as infrastructure.