The first live interbank transaction on Swift’s blockchain-based ledger did not settle on the ledger. HSBC and Standard Chartered announced on 19 August 2026 that they had completed the first live cross-border transaction using tokenised deposits over Swift’s ledger, and the same release explains why that headline needs qualifying: the ledger “acted as a secure orchestration layer, enabling the obligations to be matched and netted between the two banks prior to final settlement through existing systems.” Netting is not settlement. What went live is a bilateral obligation-matching service with a distributed ledger underneath it, and correspondent banking still moving the money.
The mechanics are plain. Payment messages were exchanged between the two banks across Swift’s ledger, and the resulting obligations were recorded as tokenised deposit obligations on HSBC’s Tokenised Deposit Service (TDS) and on Standard Chartered’s own tokenised-deposit infrastructure — two separate, bank-proprietary systems that do not share a chain. The deposits never left the issuing bank’s books. Neither bank disclosed an amount, a currency or a corridor, an unusual omission for a transaction presented as live rather than as a pilot. HSBC’s TDS is live in six markets and seven currencies.
The orchestration layer was always the design
None of this contradicts what Swift said at launch. Reporting the ledger going live on 9 July 2026, Ledger Insights described it as “an orchestration layer rather than a payments platform in its own right”: deposits are issued on the banks’ own ledgers, the shared ledger records and validates their payment commitments to one another, and “interbank settlement between the payer and payee banks happens separately through conventional channels such as RTGS systems or correspondent banking relationships.” It runs on Besu, the open-source Ethereum-compatible framework. Because it is purely an orchestration layer, every participant must have built its own deposit-token capability first.
That constraint explains the arithmetic here. Swift said the ledger was ready for initial use with 17 banks across six continents preparing to pilot, Citi, HSBC and UBS among those named. One month on, two have transacted — and they are two of the few that already had the hard part built. Both sit inside the Hong Kong Monetary Authority’s EnsembleX work and the BIS Project Agorá; HSBC is also in the UK’s GBTD effort and The Clearing House initiative, while Standard Chartered is involved in Partior. The other 15 are not slow; they are waiting on deposit-token infrastructure of their own.
Lewis Sun, Head of Digital Currencies at HSBC, called it “a landmark moment for the promise of tokenised deposits,” showing “how digital money issued by banks can be interoperable across institutions.” Mark Willis, Head of Emerging Payments, Transaction Services and Digital Assets at Standard Chartered, called tokenised deposits “a key pillar” of the bank’s digital assets strategy and the transaction “an important step towards more seamless, always-on financial services.” Both formulations are careful: neither claims settlement finality on the ledger.
What a deposit token is, and what it is not
The open question is what was actually transferred. If HSBC issues a token recording a claim on HSBC, and that token cannot leave HSBC’s own service, it is a book entry with a better interface rather than a transferable instrument a third party can hold. The release does not say whether these tokens move outside the issuing bank. Nor can there be atomic Delivery versus Payment (DvP) or Payment versus Payment (PvP), because there is no cash leg on the ledger to settle against — the contrast with designs that do put a tokenised cash leg on-chain is the whole distinction.
Set that against Project Agorá, which convenes eight central banks and more than 40 financial institutions. Its prototype achieves “atomic, multi-currency settlement of wholesale cross-border payments” precisely because it records tokenised central bank reserves alongside tokenised commercial bank deposits on one platform. The BIS is equally explicit that Agorá “is not about building a finished product.” So the architecture that can settle atomically is a prototype, and the one that is live cannot settle at all. That is a defensible engineering choice, but it sits awkwardly beside the release’s own claim that banks can now “issue, transfer, record and settle tokenised deposits through Swift’s blockchain-based ledger.”
Three things are worth watching: whether banks three through 17 transact; whether anyone discloses a value or corridor, which would turn a milestone into measurable volume; and whether Swift moves a cash leg onto the ledger, the only change that converts netting into settlement. Until then the 24/7 promise of tokenised deposits is a liquidity and reconciliation optimisation layered on correspondent banking — useful to treasurers chasing weekend liquidity, and to the data-standards work tokenisation still needs — but not a new settlement asset.
This article is informational analysis only and is not financial, investment, or trading advice. Cryptocurrencies are highly volatile and can lose substantial value rapidly. Past performance and historical patterns do not guarantee future results. Do your own research and consult a regulated financial adviser before making any investment decision.
Image: “Telex machine” by Alan & Flora Botting, licensed under CC BY-SA 2.0, via Wikimedia Commons. Colour-corrected.
