RWA · BANKS · POLICY SIGNALS
Why banks prefer deposits over stablecoins (RWA context)
In institutional tokenization, the relevant comparison is not “crypto versus TradFi”.
It is bank money versus third-party money — and what each implies for governance, liquidity, and enforceability.
Banks often prefer tokenized deposits (or deposit-like structures) because they align more naturally with existing prudential frameworks,
balance-sheet control, and regulated settlement responsibilities. Stablecoins can still play critical roles, but they introduce different
liability, reserve, and operational dependencies that banks must price and govern.
The core idea in one line
Banks tend to prefer deposits because deposits are native to bank regulation and balance sheets,
while stablecoins are typically issued liabilities of a separate entity — which changes risk ownership,
reserve governance, redemption mechanics, and supervisory treatment.
Deposits vs stablecoins: what banks optimize for
| Control & governance | Deposits are governed within a bank’s supervised perimeter (internal controls, risk committees, audit, supervisory dialogue). Stablecoins add an external issuer/reserve governance layer that a bank must diligence and monitor continuously. |
|---|---|
| Liquidity & backstops | Deposit-based money is designed to interact with bank liquidity tooling and prudential expectations. Stablecoins typically rely on reserve portfolios and redemption operations that sit outside the banking balance sheet. |
| Settlement finality & enforceability | Banks anchor finality in regulated market infrastructure and legal enforceability. Stablecoin transfers may be technically final on-chain, but operational enforceability depends on issuer policies, wallet controls, and jurisdiction-specific legal interpretations. |
| Regulatory clarity | Bank deposits are a familiar object for supervisors. Stablecoins often require new classification, rulemaking, and supervisory interpretation (issuer standards, reserve rules, custody rules, and operational resilience). |
Why tokenized deposits keep reappearing in RWA pilots
RWA tokenization programs usually need a settlement asset that is predictable under supervision.
Tokenized deposits can act like a “digitally delivered” form of bank money that still inherits the governance and liability structure
institutions already understand. This makes tokenized deposits especially attractive for wholesale settlement, treasury movements,
and permissioned transfer contexts where counterparties, eligibility rules, and compliance obligations are explicit.
BIS framing: bank money and tokenised deposits as “inside-the-perimeter” rails
A useful way to read the debate is to separate technology (tokenization) from money form (who issues the claim and who is regulated).
BIS-style framing typically pulls attention back to the banking perimeter: commercial bank money and tokenised deposits are designed to preserve
supervisory visibility, governance, and the legal structure of claims — even if the record/transfer layer becomes more programmable.
In practice, this is why banks treat tokenised deposits as a natural baseline for RWA settlement loops.
Bank-led execution: why “rails” matter as much as the instrument
When banks operationalize tokenization, they often do it through bank-led networks and controlled operating models
(permissioning, eligibility, compliance controls, and integration with treasury and custody).
Initiatives like Kinexys / Project Epic (and bank-issued token models such as EURCV structures) help illustrate a simple point:
for institutions, the preferred path is usually to modernize settlement while keeping money and governance anchored in regulated entities.
Stablecoins are not “bad” — they are structurally different
Stablecoins can be excellent interoperability and distribution rails, particularly for cross-border settlement, 24/7 transferability,
and programmable payment contexts. But for a bank-led RWA workflow, stablecoins create a dependency triangle:
(1) issuer governance, (2) reserve composition and transparency, and (3) redemption operations under stress.
Even when those are strong, the bank still must map them into internal risk ownership and supervisory expectations.
EU posture signals (MiCA + tokenized deposits conversation)
In the EU, the policy direction is to make stablecoin usage compatible with regulatory perimeter constraints via structured issuer regimes,
while also exploring institution-native forms of money for settlement. Practically, this pushes banks to treat stablecoins as regulated instruments
(issuer standards, reserve expectations, operational requirements) and to prefer bank-native constructs for core settlement where possible.
US posture signals (NYDFS + OCC interpretive authority)
In the US, a key signal is supervisory guidance and interpretive authority that clarifies what banks may do around custody, reserves-related activities,
and participation in blockchain networks. The market implication is not “stablecoins win” or “deposits win” — it is that banks will adopt what can be
defended in governance, audited in controls, and explained to supervisors under stress scenarios.
Decision frame you can reuse in calls
| If the goal is… | Then banks typically prefer… |
|---|---|
| Wholesale settlement between known regulated entities | Tokenized deposits / bank money constructs |
| Core treasury movements, internal liquidity, controlled settlement loops | Bank-native money with explicit governance and eligibility |
| Interoperability, distribution, 24/7 cross-border mobility | Stablecoins (with heavy due diligence + controls) |
| Retail-facing payment use at scale | Hybrid approaches (bank rails + stablecoin rails depending on jurisdiction) |
CryptoWisely Insight:
The practical question is rarely “deposits or stablecoins?”
It is: where does the liability sit, who governs redemption under stress, and what does the supervisor expect you to prove.
In RWA workflows, banks choose the instrument that minimizes unpriced external dependencies.
Sources (PDF)
These PDFs are provided for reference and context. Always validate jurisdiction-specific applicability before operational decisions.
| EU — MiCA (Level 1 core text) | Open PDF |
|---|---|
| EU — MiCA (Level 2 RTS/ITS measures) | Open PDF |
| EU — DLT Pilot Regime (Reg. 2022/858) | Open PDF |
| EU — EBA report on tokenised deposits | Open PDF |
| EU — ECB tokenisation: bank money settlement framework | Open PDF |
| US — NYDFS guidance (USD-backed stablecoins) | Open PDF |
| US — OCC IL 1170 (crypto custody authority) | Open PDF |
| US — OCC IL 1172 (stablecoin reserves authority) | Open PDF |
| US — OCC IL 1174 (independent node validation) | Open PDF |
| Global — BIS: tokenised deposits & commercial bank money | Open PDF |
| US — JPMorgan Kinexys / Project Epic (whitepaper) | Open PDF |
| EU — SG-Forge: CoinVertible EURCV product & operating model | Open PDF |
Disclaimer: This content is informational and does not constitute legal, regulatory, or investment advice.
← Back to RWA & Tokenization Hub