Swift, the Belgium-based cooperative that underpins the messaging layer of global interbank finance, has taken a concrete step toward round-the-clock tokenized settlement — but the architecture of that step reveals as much about the enduring constraints of legacy banking infrastructure as it does about the promise of digital assets. The cooperative has launched a pilot program in which 17 global banks can transfer tokenized deposits continuously, including across weekends, using a dedicated ledger. The catch, and it is a consequential one, is that true final settlement still flows through the same aging rails that have defined correspondent banking for decades.
The significance of 24/7 operability should not be understated. Traditional interbank settlement has always been a creature of business hours and calendar conventions — payments initiated on a Friday afternoon can languish in a state of uncertainty until Monday morning, sometimes longer when public holidays intersect across jurisdictions. For corporate treasurers managing liquidity, for financial institutions squaring books across time zones, and for markets increasingly conditioned to instantaneous digital transactions, that temporal gap represents real cost and real risk. A ledger that can move tokenized deposits at midnight on a Sunday is, on its face, a meaningful operational advance.
Yet the architecture of Swift's pilot immediately surfaces a structural tension that has quietly shadowed nearly every institutional tokenization initiative of the past several years. The ability to transfer a tokenized representation of a deposit is not the same as settling that deposit in finality. Settlement — the irrevocable transfer of value from one party to another — remains tethered to the legacy systems that process it: central bank money, correspondent accounts, and the batch-cycle infrastructure of national real-time gross settlement systems. Until those systems run continuously, any tokenized layer built above them inherits their temporal and operational limitations at the moment of truth.
The 17 banks participating in this pilot represent a meaningful cross-section of global institutional finance. Their involvement signals that the demand for tokenized deposit infrastructure is no longer hypothetical or experimental in a narrow sense — it is being stress-tested at the network level by institutions with real balance sheets and real operational stakes. Swift's role as coordinator is equally telling. Rather than ceding this territory to blockchain-native protocols or permissioned distributed ledger consortia operating outside traditional finance, the cooperative is asserting itself as the connective tissue for institutional tokenization, much as it has been for messaging since the 1970s.
This positioning is strategically rational for Swift. The organization has spent the past several years exploring interoperability between blockchain networks and traditional payment systems, including extensive work on connecting central bank digital currency pilots across jurisdictions. A tokenized deposit ledger that plugs into its existing network of over 11,000 financial institutions gives Swift a credible on-ramp to the tokenized asset economy without requiring a wholesale replacement of correspondent banking infrastructure — the very infrastructure on which its relevance depends.
But the pilot also crystallizes a debate that regulators, central banks, and market infrastructure operators have been navigating with increasing urgency. If tokenized deposits can move continuously but only settle through legacy systems on business days, the apparent efficiency gain is partially illusory. A tokenized transfer confirmed at 2 a.m. on a Saturday may still carry counterparty exposure — a form of settlement risk — until the underlying funds are formally transferred through the relevant real-time gross settlement system when it reopens. The Bank for International Settlements and the European Central Bank have both flagged this gap in their respective analyses of tokenized money, noting that achieving genuine delivery-versus-payment finality in a tokenized environment requires reform at the central bank money layer, not merely at the commercial bank layer above it.
The European dimension is particularly relevant. The European Banking Authority and the ECB are actively developing frameworks under which tokenized commercial bank money could eventually settle against wholesale central bank digital currency — a model that would, in theory, close the finality gap that Swift's pilot currently leaves open. Several of the 17 participating banks are almost certainly European institutions operating within this regulatory perimeter, which means the pilot is unfolding alongside, and in dialogue with, those broader policy experiments.
What This Means for the Future of Institutional Settlement
Swift's tokenized deposit pilot is best understood not as a finished solution but as proof of institutional intent at scale. The cooperative has demonstrated that a network of 17 global banks can operate a shared ledger for weekend and after-hours token transfers — a non-trivial coordination achievement. What the pilot has not resolved, and cannot resolve unilaterally, is the deeper infrastructure question: whether central bank settlement systems will eventually extend their operating hours, adopt tokenized formats, or integrate directly with commercial bank ledgers to deliver true 24/7 finality. That question belongs to central banks and to the political economies that govern them. Until it is answered, the tokenized deposit layer — however sophisticated its ledger — will remain a fast road that ends at an old toll booth. The banks, the regulators, and Swift itself know this. The pilot is their way of building up to the gate, and waiting for it to open.
Written by the editorial team — independent journalism powered by Codego Press.