Two banks move a tokenized deposit across Swift's ledger

What happened

Standard Chartered and HSBC said on 19 August that they had executed the first live tokenized deposit transaction on Swift's blockchain-based ledger. The release calls it 'a milestone in the use of tokenised deposits by regulated financial institutions to issue, transfer, record and settle tokenised deposits through Swift's blockchain-based ledger, not only demonstrating interbank interoperability, but helping advance industry progress on 24/7 cross-border payments'. Lewis Sun, head of digital currencies at HSBC, and Mark Willis, head of emerging payments, transaction services and digital assets at Standard Chartered, are quoted. The release names no currency, no value and no corridor. Global Finance and PYMNTS describe the mechanism in more detail than the banks do, reporting that obligations were recorded on each bank's own tokenization platform and reconciled through the shared ledger before settling over existing rails.

Why it matters

Two banks moving tokenized deposits between their own separate platforms is the interoperability problem being solved rather than described. A tokenized deposit is only useful if it can leave the bank that issued it, and until it can, each bank's ledger is a private ledger with a blockchain inside it. Doing it across Swift matters more than doing it at all, because Swift is the layer nearly every bank already speaks, which makes this a plausible route to the many rather than a bilateral arrangement between two.

What is not settled

The banks call it a first and a demonstration, and give none of the figures that would show what was actually moved. Nothing is said about when this becomes something other Swift members can use, or on what terms. Nor is it clear how it would meet the rival tokenized deposit systems that large banks have built in-house, which have the same problem in the other direction: they work, and they do not reach beyond their owner.