Swift Links Two Banks’ Tokenized Deposits in First Live Transaction
TL;DR
- HSBC and Standard Chartered completed the first live cross-border transaction between two banks using Swift tokenized deposits infrastructure.
- Swift’s ledger coordinated payment instructions while final settlement continued through the banks’ existing payment systems.
- The transaction does not yet show how the system performs at higher volumes, across more currencies, or with more participating banks.
On August 19, HSBC and Standard Chartered completed the first live cross-border transaction between two banks on Swift’s blockchain-based ledger, using tokenized deposits, digital versions of bank deposits. Swift is the messaging network banks use to move money internationally.
The banks did not disclose the amount, the currencies involved, the payment corridor, or how long settlement took.
How the two systems connected
HSBC and Standard Chartered each already run their own systems for issuing tokenized deposits, digital records that represent money customers hold in their bank accounts. Before this test, those two systems had no way to talk to each other, similar to two companies running incompatible accounting software.
Swift’s ledger gave the banks a shared space to exchange payment instructions and agree on what each owed the other. Once that agreement was recorded, the actual transfer of money still happened through the banks’ existing payment systems. So Swift added a coordination layer to the infrastructure. The ledger allows two different bank networks to confirm and reconcile a transaction before final settlement through existing payment systems.
Is a tokenized deposit the same as a stablecoin?
No. A tokenized deposit is a digital claim on money a customer already holds in a specific bank account. The bank issues it, tracks it, and remains responsible for the underlying deposit. HSBC converts eligible deposits into tokens at a one-to-one ratio. Clients can then move those balances between approved HSBC locations, subject to local rules.
A stablecoin works differently. It is typically issued by a company rather than a bank. It tracks a reference asset such as a currency, and often trades on public blockchain networks open to anyone. A tokenized deposit stays inside the issuing bank’s regulated system and does not circulate the same way.
>>> Read more: SWIFT Wraps Tokenized Bond Trial
Where this fits Swift’s wider pilot
Swift announced on July 9 that its blockchain-based ledger was ready for initial use. At that point, 17 banks across six continents were preparing to run their own live tests with tokenized deposits.
The goal behind the effort is to enable cross-border payments at any hour, including nights and weekends, when traditional transfers slow down or require banks to keep funds parked in multiple locations in advance. A shared ledger could reduce how much money banks need to hold in reserve just to cover timing gaps.
HSBC’s tokenized deposit service, called TDS, is already live in six markets: Hong Kong, Singapore, Luxembourg, the UK, the US and the UAE. That footprint gives the pilot a base to expand from if other bank pairs replicate what HSBC and Standard Chartered just completed.
Scaling beyond a single transaction
Two banks can now exchange and reconcile tokenized deposit obligations through Swift’s shared ledger. The banks did not name any corporate clients involved or say when the connection might become available for customer use.
Whether the system holds up at higher transaction volumes and across more currencies depends on getting more of Swift’s 17 pilot banks trading with each other across different markets, producing enough activity for a real stress test.
