Standard Chartered and HSBC complete the first real-time payment of Swift blockchain ledger

Standard Chartered Bank and HSBC completed the first real-time cross-border transaction based on Swift blockchain ledgers

Standard Chartered Bank and HSBC have successfully completed the first real-time cross-border transaction based on Swift blockchain ledgers, which marks that tokenized deposit systems issued by different banks can achieve real-time interoperability, providing early evidence for this concept. This demonstration came only about a month after Swift announced that its ledger was ready for initial use.

According to Swift's description of the method, this test relied on payment instructions exchanged by two banks through the ledger. The resulting debt obligations are recorded on HSBC's "tokenized deposit service" and Standard Chartered's "tokenized deposit infrastructure", while Swift's ledger serves as the orchestration layer-matching and net rounding of debt before settlement is completed through existing payment channels.

Key Points

HSBC and Standard Chartered performed the first real-time cross-border transaction on Swift's blockchain ledger. Swift's ledger is used to arrange, match and net balance debt between the tokenized deposit systems of different banks before final settlement is completed. The workflow is designed to preserve the bank's existing settlement, compliance and risk control mechanisms rather than replace them. The move follows a plan Swift announced in July: a pilot project involving 17 banks on six continents is preparing to use tokenized deposits for real-time transactions.

How does the ledger-based payment process work

The core concept behind Swift's blockchain ledger is interoperability: connecting tokenized deposits issued on different banking infrastructures, allowing cross-border payments to run more continuously. In this real-time transaction, payment orders are exchanged between HSBC and Standard Chartered through the ledger, and the two banks 'respective tokenization systems record the debt obligations arising from these orders.

Swift describes the ledger as an orchestration layer rather than a substitute for the settlement track. In the process described, ledgers help match and balance out the amounts that each party should pay to each other. Settlement is then carried out through existing payment systems, a hybrid design designed to reduce operational friction while maintaining existing governance and control mechanisms unchanged.

What this means for tokenized deposits

Banks have been testing tokenized bank deposits against multiple use cases, but interoperability remains a major obstacle. Tokenized deposits can speed settlement speeds and enable more flexible payment processes, but substantial progress depends on whether institutions can connect their systems between cross-border and counterparty networks.

Swift's ledger approach targets this gap by acting as an orchestration mechanism for sharing. If the pilot project continues to demonstrate large-scale reliability, the result will be a path to 7×24-hour cross-border payment capabilities without having to force each bank to abandon its existing settlement processes, compliance frameworks or risk management procedures.

This concept of "connecting without replacing everything" is a key difference from attempts to rebuild the entire payment stack end-to-end. It also helps explain why pilot projects focusing on interoperability can gain momentum alongside stablecoins and other digital settlement narratives: Regulators and risk teams may be more inclined to accept incremental changes that retain familiar guardrails.

Timeline: From Swift's pilot program to its first real-time operation

This transaction follows Swift's announcement in July that its blockchain ledger is ready for initial use, and 17 banks covering six continents are preparing to pilot real-time transfers. The pilot team includes Citibank, BNP Paribas, Bank of New York Mellon, Wells Fargo, UBS, Mitsubishi UFJ Financial Group, DBS Bank and ANZ Bank, as well as institutions participating in the first real-time cross-border transaction.

Swift also stated that the ledger is designed to support 7×24-hour cross-border payments while maintaining existing settlement, compliance and risk controls. With the first real-time cross-border transaction reported just weeks after the ledger readiness statement, Swift and participating banks are actually moving from the planning stage to operational verification-an important step for any distributed ledger plan designed for financial messaging.

Previous reports have emphasized that the ledger approach will allow banks to connect tokenized deposits issued on different infrastructures. The first execution between HSBC and Standard Chartered provides a concrete example of how this "connection" can work in practice: debt is recorded on the bank's tokenization services, while Swift's ledgers handle the orchestration required to achieve interoperability.

Industry's broad push for interoperable digital settlement

The Swift-led progress is part of a broader push by financial institutions towards tokenized bank currency and networked settlement. In November 2025, HSBC said it plans to expand its tokenized deposit services to corporate customers in the United States and United Arab Emirates in the first half of 2026. The bank has previously launched the service in the United States to provide qualified corporate and institutional customers with 7×24-hour domestic and cross-border transfer services using tokenized deposits.

Standard Chartered Bank has also participated in real-value settlement attempts. In July, it was included in the list of institutions and central banks participating in the Bank for International Settlements "Project Agora" experiment, which allegedly used tokenized commercial bank deposits and central bank reserves to settle approximately US$1 million in six currencies.

At the same time, other industry players are building parallel network concepts. The clearing house, owned by some of the largest U.S. banks, reportedly plans to launch a tokenized deposit network in the first half of 2027, aiming to connect traditional payment tracks with digital asset infrastructure to enable round-the-clock settlement.

Taken together, these efforts suggest that the industry is trying to standardize interoperability through multiple paths: shared orchestration layers such as Swift ledgers, institution-specific tokenized deposit platforms such as HSBC Services, and broader web initiatives discussed by payment operators. The question for the market is whether these paths will converge into interoperable standards or will remain scattered across their respective ecosystems.

For investors, traders and builders, the next step is performance and scale: whether further real-time transactions on the Swift ledger will exceed the scope of limited bilateral testing, and how quickly participating banks can expand interoperability of tokenized deposits over more paths while maintaining settlement and risk control in line with established regulatory expectations.