IBM links banks to Swift's tokenized deposit ledger through ISO 20022

Banks that want to move tokenized deposits no longer have to learn blockchain plumbing. IBM said on Thursday that its Digital Asset Haven platform can now instruct those transfers on Swift's blockchain ledger using ISO 20022, the messaging standard banks already use for ordinary payments, and that they can run the platform inside their own data centres.

What IBM added

IBM shipped two beta features at once. A messaging adapter lets an institution instruct tokenized deposit transactions in existing payment formats, with existing compliance processes, instead of building blockchain-specific workflows. The second option runs Digital Asset Haven on IBM Z and LinuxONE hardware on the bank's own premises, with no public cloud, so key management stays inside the institution. Financial institutions in Swift's programme have tested tokenized deposits on the ledger through the platform, IBM said.

ISO 20022 describes a payment the way a bank already thinks about it: who pays, who receives, how much, on what grounds. An instruction for a tokenized deposit in that same format means the bank avoids running a second payment pipeline beside its first one. The on-premises option answers a different worry. Keys to a tokenized deposit are the right to move it, and a bank that leaves those keys in someone else's cloud answers to its regulator for a function it does not control.

“The financial services industry is entering a new era where tokenized and traditional assets will need to move side by side”

— Tom McPherson, general manager of IBM Z and LinuxONE, IBM statement, via Cointelegraph, 24 September 2026

Quote source: Cointelegraph, 24 September 2026.

Swift's ledger already carries 17 banks

Swift built the ledger with more than 40 financial institutions and launched it in July with 17 banks in the first pilot group, among them HSBC, Citi, BNP Paribas, UBS and Standard Chartered. HSBC and Standard Chartered completed the first live cross-border transaction on it in August.

Two answers on tokenized deposits

Earlier today we wrote about the Solana Foundation hiring a payments manager whose stated priority is stablecoins and tokenized deposits. Solana and Swift aim at the same product and disagree about the rails. Solana wants banks to issue on a public network that anyone can read. Swift and IBM offer banks the same instrument without leaving the messaging system they already run, and without handing key custody to a cloud provider. For a compliance officer, the second option needs a shorter memo.

In August the Dallas Fed estimated that tokenized deposits could cost banks $700 billion in lending capacity. IBM answered the operational objection and left that one alone. A bank can now send a tokenized deposit with the message format it already uses, and it still has to decide what holding deposits in tokenized form does to its lending book.

Watch whether any of the 17 pilot banks moves from testing to a published volume figure. For now this is a working adapter, and the deposits still have to settle on someone's rails.

This article is for informational purposes only and does not constitute investment advice.