Top U.S. banks plan a tokenized deposit network for 2025, providing 24/7 on-chain settlement and competing directly with stablecoins. Regulatory stance from the Fed is the key catalyst.
A consortium of top U.S. banks is planning a tokenized deposit network for launch next year, The Wall Street Journal reported. The network would enable 24/7 on-chain settlement while keeping deposits inside the regulated banking system. For the payment infrastructure, this is a direct competitive response to stablecoins – and a potential inflection point for bank deposit retention and payment processor margins.
A tokenized deposit is a digital representation of a traditional bank deposit on a blockchain. It allows instant, around-the-clock settlement between participating banks and, eventually, between banks and their customers. Current payment rails – ACH, wire transfers, card networks – settle in batches or during business hours. Tokenized deposits would enable real-time gross settlement continuously.
The naive read: this is just a digital wrapper for existing deposits. The better market read: it changes the competitive dynamics of payment infrastructure. Banks can offer programmable money – smart-contract-enabled payments – without losing the deposit base to non-bank stablecoin issuers like Circle or Tether. That matters because stablecoins have been capturing payment volume in remittances, B2B payments, and crypto markets. A tokenized deposit network gives banks a regulated, insured alternative that can settle on the same rails.
Stablecoins grew by solving two problems: slow settlement and lack of programmability. They offer 24/7 transferability and can be integrated into DeFi protocols and payment apps. They carry counterparty risk – reserves may not be fully transparent – and they are not FDIC-insured. Tokenized deposits would be insured up to standard limits and subject to bank supervision.
The read-through for stablecoin issuers: banks may recapture some payment volume, especially in domestic transactions where deposit insurance matters. Stablecoins retain advantages in cross-border payments (no correspondent banking friction) and in DeFi (where tokenized deposits may not be composable with non-bank protocols). The outcome depends on interoperability: if banks build a closed network, stablecoins remain the default for open blockchain ecosystems.
Which parts of the financial sector feel the impact first?
A key uncertainty: interoperability. If the bank consortium builds a permissioned blockchain that does not connect to public chains, the network’s utility is limited to bank-to-bank settlement. If it bridges to public blockchains, it opens up composability with DeFi but introduces regulatory and security risks.
For traders tracking the shift in payment infrastructure, the initiative introduces a new variable for bank stock valuations. The sector read-through depends on which banks join the consortium and how open the network becomes.
The plan is still aspirational. Banks must agree on technical standards, governance, and liability rules. Regulatory clarity from the OCC, the Federal Reserve, and the FDIC is the single biggest catalyst. The Fed’s stance on tokenized deposits versus a central bank digital currency (CBDC) will shape the timeline. If the Fed views tokenized deposits as a private-sector CBDC substitute, it may encourage the initiative. If it sees them as a risk to monetary policy transmission, it may impose restrictions.
Other execution risks include anti-money laundering compliance on a 24/7 blockchain, settlement finality in a programmable environment, and consumer protection if smart contracts malfunction. Banks will need to solve these before the network goes live. The next catalyst is regulatory: a Fed statement on tokenized deposits or a consortium announcement with named participants. Until then, the plan is a concept, not a market event.
Prepared with AlphaScala research tooling and grounded in primary market data: live prices, fundamentals, SEC filings, hedge-fund holdings, and insider activity. Each story is checked against AlphaScala publishing rules before release. Educational coverage, not personalized advice.