The Block's explainer lays out a comparison that comes up constantly as stablecoins — cryptocurrencies pegged to a reference asset like the US dollar or euro — move from crypto-native trading pairs into everyday payments. Both stablecoin issuers and banks take in cash and issue something back to the customer in exchange. That surface similarity is where most people stop, and it's also where the comparison gets misleading.
This article covers what stablecoins and banks actually have in common, where the regulatory and structural differences show up, and why those differences matter more than the surface-level similarity suggests.
The similarity: both hold money against a liability
A bank takes a customer's deposit and issues an account balance in return — a claim the customer can redeem on demand. A stablecoin issuer takes a customer's cash and issues a token in return — also a claim the holder can, in principle, redeem on demand. In both cases, the institution is holding assets to back liabilities it has issued to someone else.
Think of it like two different vaults that both promise "bring this piece of paper back and we'll hand you your money." One vault is a bank branch; the other is a smart contract or a token issuer's redemption desk. The promise looks the same from the outside. What differs is who checks that the vault actually has the money, how often, and what happens if it doesn't.
Where regulatory oversight diverges
Banks operate inside a dense, decades-old regulatory structure: capital requirements, reserve ratios, routine examinations, and — critically — deposit insurance from bodies like the FDIC in the US, which protects depositors up to a set limit even if the bank fails.
Stablecoin issuers do not have an equivalent safety net by default. Their obligation to hold high-quality, liquid reserves — and to prove it through attestations or audits — depends entirely on which jurisdiction's rules apply to them, and those rules vary widely. A stablecoin issued under a strict regime like the EU's MiCA framework faces different reserve and disclosure requirements than one operating with looser oversight elsewhere.
A bank deposit's safety comes partly from insurance that survives the bank's failure. A stablecoin's safety comes entirely from the quality of its reserves and the credibility of its issuer — there's usually no backstop behind that.
This is the detail that gets lost when stablecoins are described as "just digital dollars." The dollar peg is a promise about value; it says nothing about who backstops that promise if the issuer's reserves come up short.
Where the infrastructure diverges
The other major difference is the rail the money moves on. Bank balances live in each bank's own ledger, and moving money between banks requires interbank settlement systems — ACH, wire transfers, card networks — that can take anywhere from seconds to days and often layer on intermediary banks for cross-border transfers.
Stablecoins live on public or permissioned blockchains, where the ledger itself is the settlement layer. A transfer that changes who holds a token is the settlement event — there's no separate reconciliation step between banks because there's no separate bank-to-bank hop. That's the practical reason stablecoins keep showing up in cross-border payments and B2B settlement: fewer intermediaries between "sender sends" and "receiver has usable funds."
| Dimension | Traditional bank deposit | Stablecoin |
|---|---|---|
| Backing | Fractional reserve, capital requirements | Meant to be fully reserved, but varies by issuer |
| Depositor protection | Deposit insurance (e.g. FDIC) | Typically none |
| Settlement rail | Bank ledgers + interbank networks (ACH, wire, SWIFT) | Blockchain ledger; transfer is settlement |
| Oversight | Uniform, long-established banking regulation | Jurisdiction-dependent, still maturing |
| Redemption | Guaranteed by law up to insured limit | Contractual promise from the issuer |
Why this comparison matters right now
The comparison isn't academic. Regulatory frameworks like the GENIUS Act exist precisely because stablecoins are converging on bank-like functions — holding customer money, enabling payments — without having converged on bank-like oversight. Every rule under debate, from reserve composition to redemption guarantees, is an attempt to close some part of that gap.
Real-world adoption is already testing where the gap matters in practice. A Japanese logistics firm turning to the yen-pegged JPYC stablecoin to speed up contractor payments is betting that settlement speed matters more than deposit insurance for that use case — contractors want to get paid fast, not to have FDIC-style protection on a balance they hold for hours before moving it elsewhere. That calculus changes for a treasury desk parking idle cash for months.
What this means for builders
If you're building on top of stablecoin rails, don't inherit assumptions from banking APIs by default — deposit insurance, chargeback protections, and mandated reserve audits may not exist for the specific stablecoin you're integrating, and the guarantees differ issuer by issuer. Read the issuer's actual reserve attestations and redemption terms rather than assuming "pegged to the dollar" implies "as safe as a dollar in a bank." For payment-speed use cases where funds move and settle quickly, the settlement-rail advantage is real; for anything resembling long-term deposits, the missing insurance layer is the tradeoff you're accepting.
Conclusion
Stablecoins and banks both hold money against issued liabilities, but that's close to where the resemblance ends. Banks operate inside a mature regulatory perimeter with deposit insurance as a backstop; stablecoin issuers operate under fragmented, still-developing rules with no equivalent safety net, in exchange for a settlement rail that skips the interbank hops banking relies on. Neither structure is strictly better — they're built for different tradeoffs, and conflating them is where the confusion starts.