HSBC and Standard Chartered Complete First Live Tokenised Deposit Transaction on Swift Ledger

HSBC and Standard Chartered have completed what they described as the first live cross-border tokenised deposit transaction on Swift’s blockchain-based ledger, moving the technology from a controlled launch phase into a real interbank payment use case.

The transaction linked HSBC’s Tokenised Deposit Service with Standard Chartered’s tokenised-deposit infrastructure. Payment messages were exchanged through Swift’s ledger, while the resulting obligations were recorded on the banks’ respective tokenised-deposit systems. Swift said in July that its ledger was designed to act as an orchestration layer connecting bank-issued tokenised deposits rather than replacing banks’ own ledgers or the existing systems used for final settlement.

Neither bank disclosed the value, currency, customer identities or the jurisdictions involved in the transaction. That limits what can be concluded about commercial scale, but the operation demonstrates that tokenised deposits issued on separate bank platforms can be coordinated through shared infrastructure and then settled using existing financial rails.

How the transaction worked

The mechanics are important because the payment was not a simple transfer of a single token from one shared bank wallet to another. In their joint announcement, Standard Chartered and HSBC said the transaction involved an exchange of payment messages using Swift’s ledger. The obligations created by those messages were recorded as tokenised deposit obligations on HSBC’s Tokenised Deposit Service and Standard Chartered’s own tokenised-deposit infrastructure.

Swift’s ledger then acted as the secure orchestration layer. According to the banks, it enabled the obligations to be matched and netted between them before final settlement through existing systems. That structure combines a blockchain-based coordination layer with conventional settlement infrastructure rather than moving the entire payment lifecycle onto one blockchain.

The distinction matters for banks trying to introduce digital money without abandoning the controls, credit processes and settlement systems already embedded in global payments. Swift described that model when it announced on July 9 that its blockchain-based ledger was ready for initial use. The cooperative said participating banks would be able to move tokenised value for customers, including overnight and on weekends, while still completing final settlement through existing systems.

The transaction announced Wednesday is the first interbank transaction executed on that ledger, according to the joint bank announcement. It follows Swift’s July launch, when 17 banks across six continents, including HSBC and Standard Chartered, were preparing to pilot live transactions.

Tokenised deposits stay within regulated banking

Tokenised deposits are digital representations of commercial bank deposits rather than cryptocurrencies issued outside the banking system. HSBC describes the tokens in its service as digital records of underlying cash deposits in customer bank accounts. Its Tokenised Deposit Service converts deposits into digital tokens on a one-for-one basis and allows participating clients to transfer them through HSBC’s private blockchain.

That means the claim represented by the token remains a claim on the issuing bank. HSBC also distinguishes tokenised deposits from stablecoins, which can be designed for broader use on public blockchains, and from central bank digital currencies, which would be liabilities of a central bank.

The interoperability problem appears when tokenised deposits are created on separate bank platforms. A corporate treasurer may be able to move tokenised money instantly within one bank’s network, but that benefit becomes more limited if another bank uses a different ledger and the two systems cannot communicate. The Swift initiative is intended to provide a common coordination layer without requiring participating banks to issue the same token or move their customer deposits onto one common bank ledger.

HSBC’s Tokenised Deposit Service was already operating in six markets at the time of the transaction: Hong Kong, Singapore, Luxembourg, the United Kingdom, the United States and the United Arab Emirates. The bank said the service supports CNH, HKD, SGD, EUR, GBP, USD and AED. Its commercial product materials say the service is designed for 24/7 movement of funds across participating HSBC locations and for corporate customers with complex treasury needs.

Standard Chartered said its tokenised-deposit capabilities sit within a broader digital-assets and payments business that also includes custody, tokenisation and stablecoin settlement. The bank did not disclose further technical details about the specific infrastructure used for Wednesday’s transaction.

Swift moves from pilot infrastructure to live use

Swift first announced plans to add a blockchain-based shared ledger to its infrastructure in September 2025, initially focusing on real-time, 24/7 cross-border payments. By July 2026, it said the ledger was ready for initial use after nine months of development with input from international financial institutions.

In its July launch announcement, Swift named 17 banks preparing for initial live transactions: ANZ, BNP Paribas, BNY, Citi, DBS, First Abu Dhabi Bank, FirstRand, HSBC, Itaú Unibanco, Lloyds Bank, Mashreq, MUFG Bank, OCBC, Standard Chartered, UBS, UOB and Wells Fargo. Swift said the initial use case was designed to connect bank-issued tokenised deposits on banks’ own ledgers and improve payment availability and liquidity efficiency.

The cooperative is positioning the ledger as an extension of its role in financial messaging rather than as a replacement for the existing banking system. Its own materials say the shared ledger is intended to provide a real-time record of transactions between financial institutions and to interoperate with both traditional payment rails and emerging digital systems.

For HSBC and Standard Chartered, the immediate significance is narrower but concrete. The banks have now shown that separate tokenised-deposit platforms can create and reconcile interbank obligations through Swift’s ledger in a live transaction. The announcement does not establish the transaction’s scale, economics or performance relative to conventional cross-border payments because the banks did not disclose the amount, currency, timing or fee data.

The next test is repetition at broader scale. Swift said in July that the ledger would expand in functionality and availability after its initial controlled go-live phase, while the other participating banks prepared their own live pilots. Further transactions will show whether the same model can work across more institutions, currencies and payment corridors while retaining the compliance and settlement controls banks require.