Tokenized deposits vs. stablecoins

From a distance, tokenized bank deposits and fiat-backed stablecoins look similar: a digital token, redeemable 1:1 for fiat, transferable on a blockchain or similar rail. Up close, the differences are substantial and matter for merchants and platforms deciding which to accept.

Written December 2024 from a comparative analysis.

The claim relationship

• Stablecoin. The holder has a claim against the issuer for redemption. The issuer holds reserves; the holder is a creditor.
• Tokenized deposit. The holder has a bank deposit that happens to have a tokenized representation. The claim is on the bank; the token is a form factor.

Regulatory posture

• Stablecoin (fiat-backed). Regulated as e-money or under MiCA in the EU; various frameworks elsewhere. Reserve composition, redemption rights, disclosure requirements.
• Tokenized deposit. Regulated as a bank deposit. Deposit insurance may apply (subject to jurisdictional details). Bank regulatory oversight applies to the underlying deposit.

Operational implications

• Interoperability. Stablecoins are widely accepted across many wallets and platforms. Tokenized deposits are usually walled-garden — usable within a specific institution's ecosystem.
• Cross-border. Stablecoins move easily across borders. Tokenized deposits are more constrained by the underlying bank's cross-border footprint.
• Credit risk. Stablecoin holders face issuer risk. Tokenized deposit holders face bank credit risk, mitigated by deposit insurance for retail.

When each makes sense

• Stablecoins for cross-border transfers, DeFi integration, agent-controlled wallets.
• Tokenized deposits for institutional flows within a banking network, programmable corporate payments, treasury operations.

The two aren't competitors so much as complements. Payment platforms accepting one should think about accepting both, with clear understanding of the different risk profiles.