For fifty years, Swift has been the messaging layer of global banking: the network that tells banks a payment is coming, not the rail that moves the money itself. That distinction just narrowed. On July 9, Swift confirmed its blockchain based shared ledger is ready for initial use, with 17 banks across six continents preparing to pilot live transactions on it, the first time Swift’s own infrastructure will orchestrate the movement of tokenised, bank issued deposits rather than simply carry messages about them.
From messages to a shared settlement layer
The participating institutions, ANZ, BNP Paribas, BNY, Citi, DBS, First Abu Dhabi Bank, FirstRand, HSBC, Itau Unibanco, Lloyds Bank, Mashreq, MUFG Bank, OCBC, Standard Chartered, UBS, UOB, and Wells Fargo, span six continents, reflecting how broadly the largest correspondent banking players want a stake in whatever comes after SWIFT messaging alone. According to Swift, the ledger gives participating banks a secure orchestration layer for deposits they issue and tokenise on their own systems, letting them move funds for customers around the clock, including overnight and on weekends, before completing final settlement through the existing correspondent banking infrastructure banks already trust.
That hybrid design is the point. Banks get always on, near instant movement of value between institutions without abandoning the compliance, credit, and risk controls built into decades of settlement infrastructure. Thierry Chilosi, Swift’s chief business officer, framed the ledger as continuity rather than disruption: “With our new ledger capability, we’re extending the trust and stability of established finance into the frontiers of digital money.”
Nine months from announcement to pilot
Swift first announced the shared ledger initiative in 2025 and says it built the system in roughly nine months, with direct input from the international banks now piloting it. That timeline matters for an institution not known for moving fast: Swift’s core messaging standards evolve over years, not quarters. The compressed build cycle signals how much competitive pressure Swift is under from stablecoin issuers, tokenised deposit networks, and blockchain rails built outside the traditional correspondent banking system, all of which promise the 24/7 settlement that legacy SWIFT messaging cannot deliver on its own.
The scale Swift is defending is enormous. The network says roughly 75 percent of payments sent over Swift reach the beneficiary bank within 10 minutes, moves value equivalent to global GDP roughly every two to three days, and connects more than 11,500 banking organisations across over 200 markets. A shared ledger that keeps that network relevant as value itself becomes programmable is an existential project, not a side experiment.
Why banks are opting in rather than building around Swift
Standard Chartered was among the first to publicly frame its participation as a strategic bet rather than a compliance checkbox. “We are redefining cross-border payments with Swift’s new blockchain based ledger, combining tokenised deposits with our global network,” said Mahesh Kini of Standard Chartered. That framing, redefining rather than merely adopting, captures why global banks are choosing to build tokenisation capability inside the Swift network instead of routing around it through independent blockchain consortia: the orchestration layer inherits Swift’s existing reach into more than 11,500 institutions, sparing each bank from having to build bilateral tokenised settlement relationships one counterparty at a time.
It also lets banks tokenise deposits, rather than relying on stablecoins issued by non bank entities, keeping deposit taking, credit creation, and regulatory oversight inside the banking perimeter. For regulators wary of stablecoin run risk, a bank-issued tokenised deposit settling over Swift’s shared ledger is a materially different risk profile than a dollar stablecoin issued by a crypto native firm.
What the shared ledger means for the finance leader
For treasurers and payments executives, three practical implications follow from this launch. First, weekend and overnight liquidity gaps that have defined cross-border cash management for decades start to close, at least among the 17 pilot banks, meaning corporates banking with those institutions may see faster fund availability well before broader Swift rollout. Second, procurement and banking relationship decisions should start factoring in which correspondent banks are inside the pilot group, since early tokenised deposit capability will concentrate liquidity advantages among participating institutions first. Third, this is a signal to treasury and risk teams that tokenised deposits, not public stablecoins, are becoming the incumbent banking industry’s preferred instrument for programmable money, a distinction that matters for counterparty risk assessment and internal digital asset policy.
The rollout is deliberately staged. Swift describes this as a controlled go live phase focused on pilot transactions, with expanded functionality and broader bank availability to follow. Finance leaders should treat the current 17-bank cohort as the leading edge of a capability that will widen access gradually rather than all at once, and should ask their banking partners directly whether, and when, they plan to join.
What to watch next
The near-term test is whether pilot transactions move beyond controlled trials into meaningful transaction volume without incident. As bank-owned stablecoins and tokenised deposits increasingly compete for the same programmable-money use cases, Swift’s shared ledger is a bid to ensure that competition happens on infrastructure the incumbent banking system controls, rather than infrastructure built entirely outside it. Whether the other 11,500-plus institutions on Swift’s network follow the first 17 will determine whether this becomes the default settlement layer for tokenised value, or one of several competing rails banks now have to support.
The timing is not incidental. Stablecoin issuers have spent the past year operating under clearer US rules following the GENIUS Act’s regulatory deadline, giving non bank digital dollar issuers a compliance framework of their own to compete on. Swift’s answer is to make sure banks have a comparably credible, regulator friendly alternative before that competition fully matures, rather than ceding programmable money entirely to issuers outside the banking perimeter.
Source: Swift
