HSBC and Standard Chartered have completed the first live cross-border transaction on Swift’s blockchain-based ledger, moving the network’s tokenized-deposit project from readiness into an executed interbank test.
The banks said they exchanged payment messages through Swift’s ledger. The resulting obligations were recorded on HSBC’s Tokenised Deposit Service and Standard Chartered’s tokenized-deposit infrastructure, demonstrating that two bank-operated systems could coordinate through a shared layer.
Swift’s ledger matched and netted the obligations between the banks before final settlement through existing payment systems. That distinction is important: the transaction tested interoperability and orchestration, not a new settlement asset or a replacement for the banking rails that ultimately discharge the payment.
A completed milestone after July’s controlled launch
Swift said in July that its ledger was ready for initial use and that 17 banks across six continents were preparing to pilot live transactions. The HSBC-Standard Chartered transaction is the first interbank execution disclosed under that program.
The status change is meaningful because the earlier announcement established technical readiness and participant intent, while the latest release establishes that two separate tokenized-deposit systems have completed a live workflow through the common ledger. The companies did not disclose the transaction’s amount, currencies, corridor, client, processing time or final-settlement rail.
Those omissions limit what can be concluded about production performance. One completed transaction does not establish throughput, service availability, liquidity savings or broad commercial access. It does, however, provide a concrete interoperability result for a model built around regulated commercial-bank money.
Swift coordinates while banks retain their own ledgers
The architecture leaves the deposit obligations on the participating banks’ systems. Swift provides the shared orchestration layer that carries messages and coordinates matching and netting across those separate environments.
For banks, that approach could reduce the need to build bespoke bilateral connections between every tokenized-deposit platform. A common layer may also allow institutions to preserve their own account structures, compliance processes and risk controls while testing round-the-clock payment coordination.
The operational questions now move beyond whether two systems can connect. Wider use would require clear rules for transaction finality, liquidity, sanctions screening, exception handling and responsibility when one leg cannot settle. The fact that final settlement still takes place through existing systems also means their operating windows and liquidity mechanics remain relevant to the end-to-end service.
What the test means for digital-money competition
Tokenized deposits are bank liabilities, unlike stablecoins issued by non-bank companies or central bank digital currency. Swift’s project therefore represents a bank-led route to always-on digital value transfer rather than a stablecoin network.
For corporate treasury users, the proposed benefit is the ability to move liquidity across institutions and time zones with fewer operating-hour constraints. HSBC said its Tokenised Deposit Service is already live in Hong Kong, Singapore, Luxembourg, the United Kingdom, the United States and the United Arab Emirates, supporting several currencies. The new transaction shows that the service can interact with another bank’s tokenized-deposit infrastructure through Swift, but it does not establish that the interbank capability is generally available to customers in those markets.
The next evidence to watch will be repeat transactions across additional banks, currencies and corridors, along with disclosure on settlement times, failure handling and commercial availability. Those results will determine whether the shared-ledger model can progress from a controlled first transaction to dependable cross-border payment infrastructure.