Swift’s Tokenised Deposit Ledger Reaches Live Cross-Border Use
- 12 minutes ago
- 3 min read
Swift’s blockchain-based ledger has moved beyond infrastructure readiness and into live interbank use.
On 9 July, Swift announced that the ledger was ready for initial use, with 17 banks across six continents preparing to pilot transactions using tokenised deposits. The more consequential milestone came on 19 August, when Standard Chartered and HSBC announced the first live cross-border interbank transaction executed on the infrastructure.
For the cross-border payments industry, the significance is less about blockchain itself and more about interoperability between different forms of regulated bank money.
Swift is adding an orchestration layer, not replacing bank ledgers
Tokenised deposits are digital representations of commercial-bank deposits. They remain liabilities of the bank that issues them rather than becoming a separate form of privately issued money outside the banking system. Swift’s model is therefore different from creating one shared digital currency or moving every participating bank onto the same balance-sheet infrastructure.
In the HSBC–Standard Chartered transaction, payment obligations were recorded on HSBC’s Tokenised Deposit Service and Standard Chartered’s own tokenised-deposit infrastructure. Swift’s blockchain-based ledger acted between them, matching and netting the obligations before final settlement occurred through existing systems.
That architecture could be important because banks have already developed numerous digital-asset and tokenisation platforms. The harder problem is increasingly not creating another tokenised deposit system, but enabling independently operated systems to transact with each other. Swift is attempting to make that interoperability a shared infrastructure function.
The opportunity is not simply payment speed
Swift already reports that 75% of payments travelling over its existing network reach the beneficiary bank within ten minutes, with many arriving in seconds. That makes the case for the new ledger more nuanced than “blockchain makes cross-border payments faster”.
Availability may be more important.
The ledger is designed to support transactions overnight and at weekends, potentially reducing the operational constraints created by banking hours, time zones and payment cut-offs. Swift also identifies improved liquidity efficiency as one of the objectives of the project. For corporate treasury operations, a system capable of coordinating bank-issued digital money across institutions on a 24/7 basis could eventually improve cash visibility and make liquidity movement less dependent on conventional operating windows.
There is an important limitation, however. The current architecture still completes final settlement through existing systems. A continuously available orchestration layer therefore does not automatically mean every underlying settlement process becomes instant and available around the clock.
What could this mean for correspondent banking?
The development should not yet be interpreted as the disappearance of correspondent banking. Instead, it may change some of the technical and operational expectations surrounding cross-border banking relationships.
If tokenised deposits become more widely used, banks may need to evaluate not only who their counterparties and correspondent partners are, but also whether their digital-money infrastructures can interoperate, how liquidity is made available outside conventional operating hours, where settlement finality occurs and how existing risk and compliance controls operate across the different layers.
That is an important distinction. Tokenisation can modernise the representation and movement of bank money without removing the institutional relationships, regulatory controls and settlement arrangements on which international banking depends. For banks and payment companies reviewing their cross-border operating models, this means tokenisation should increasingly be considered alongside broader correspondent-banking strategy rather than treated only as a digital-assets experiment.
From individual platforms to network effects
The potential scale of the Swift initiative is another reason to watch it closely. Its initial group includes 17 banks from six continents, among them BNP Paribas, Citi, DBS, HSBC, Lloyds Bank, MUFG, Standard Chartered, UBS and Wells Fargo. Swift says the ledger was developed with industry input in approximately nine months and intends to expand its functionality after the initial controlled rollout But participation alone will not determine whether tokenised deposits become meaningful cross-border infrastructure.
The next questions concern repeatability and scale: whether more institutions can connect different tokenised-deposit platforms under consistent operational standards; whether liquidity advantages appear in real corporate use cases; and how smoothly always-on transaction workflows can interact with existing settlement, compliance and control frameworks.
The first live HSBC–Standard Chartered transaction is therefore better viewed as the beginning of an infrastructure test than the conclusion of one.
If that model scales, the next stage of cross-border payments may not require choosing between traditional banking infrastructure and tokenisation. It may instead depend on making the two interoperable.
Suorces:
