Swift’s 17-bank ledger pilot is a bet that tokenized deposits can extend banking hours without replacing banks

Swift’s new digital-assets ledger marks an important shift in the tokenization story because it is trying to solve a very traditional financial problem with onchain-style infrastructure: how to keep cross-border money moving when the banking day is effectively closed. The bank-owned messaging network said on July 9 that a blockchain-based ledger is ready for initial use and that 17 large banks are preparing to pilot tokenized-deposit transactions on top of it. Participating institutions reported across coverage include HSBC, Citi, BNP Paribas, UBS, ANZ, DBS, Standard Chartered, BNY and Wells Fargo, giving the initiative more weight than a laboratory proof of concept. This is no longer just a white-paper exercise about digital cash; it is an attempt to insert tokenized bank liabilities into real payment operations.

The core proposition is straightforward. Tokenized deposits are digital representations of commercial-bank money, and Swift’s ledger is designed to let participating institutions coordinate those liabilities across a shared network while still relying on existing payment systems for final settlement. That architecture is significant because it preserves the institutional controls banks care about most: compliance screening, credit governance, operational resilience and clearly assigned legal responsibility. Rather than asking banks to migrate wholesale into a public-token model, the pilot gives them a way to offer round-the-clock transfer capabilities within a framework they already understand and supervise.

That is why the 24/7 angle matters more than the blockchain label itself. Cross-border payments still run into practical dead zones tied to banking hours, local market cutoffs and weekend processing windows. Stablecoins have shown that internet-native value transfer can keep moving outside those constraints, but many regulated institutions remain uncomfortable with relying directly on third-party issuer models for large-scale treasury and payment activity. Swift’s answer is to bring the operational availability of digital tokens into a bank-led environment where the liability remains a deposit claim and the governance stack remains familiar. In other words, the project is designed to modernize availability without forcing banks to give up the legal and supervisory framework that underpins their existing payment business.

The initiative also fits a broader pattern in financial-market infrastructure. Over the past year, tokenization has moved from isolated asset pilots toward shared utility layers that coordinate issuance, settlement and recordkeeping across multiple institutions. Swift first outlined this ledger direction last year, and the current pilot suggests the design has moved from concept into controlled implementation. The company says more than 11,500 financial institutions already connect through its messaging network, and it has highlighted that most payments on the existing system already reach beneficiary banks within minutes. The new piece is not about fixing a broken network as much as it is about extending that network into always-on digital-money workflows.

For RWA builders, the most interesting part is what Swift is choosing to prioritize. The company is not starting with tokenized equities, funds or exotic market structure. It is starting with tokenized deposits because cash-like instruments are where interoperability, settlement finality and treasury movement become immediately valuable. If banks can coordinate deposit tokens across jurisdictions and systems, the same operational rails can eventually support broader classes of tokenized assets that need dependable cash legs. That makes this pilot less of a narrow payments update and more of a foundational move for institutional onchain finance.

The project also sharpens the strategic contrast between stablecoins and bank-issued tokenized deposits. Both promise faster settlement and programmability, but they sit on different liability structures and different regulatory assumptions. Stablecoins usually rely on a dedicated issuer and reserve pool; tokenized deposits rely on the commercial bank balance sheet and the deposit relationship itself. Swift is clearly betting that many large institutions would rather extend deposit-based money onto shared digital rails than outsource a meaningful share of their payment future to external token issuers. That does not eliminate stablecoins, but it does suggest banks are building a parallel model aimed at preserving their role in the settlement stack.

The commercial question now is whether controlled pilots can become a scaled network effect. Banks will need interoperability, legal certainty across jurisdictions, operational standards and enough client demand to justify integrating tokenized-deposit flows into existing treasury and transaction-banking products. But the headline takeaway is already clear: one of the most important pieces of global payment plumbing has moved tokenized deposits closer to production. If that momentum holds, the next phase of RWA adoption may be shaped less by headline token launches and more by whether institutional cash infrastructure can run continuously, compliantly and across borders.