IBM Digital Asset Haven Taps Swift's Shared Ledger in Beta

IBM added beta connectivity from its Digital Asset Haven platform to Swift's blockchain-based shared ledger on September 24, the company said from Armonk, New York. Banks can now use standard ISO 20022 payment messages to instruct tokenized deposit transactions on Swift's rail, without writing blockchain-specific workflows.

If your timeline is suddenly full of IBM-Swift posts, here is why. Swift is the cooperative that already connects 12,500 financial institutions across 200+ markets. It is now running a permissioned blockchain ledger for bank-issued tokenized deposits, and a Big Tech vendor with bank-grade tokenization software is the latest to plug in.

The IBM side: a messaging adapter, not a new chain

The new piece is the IBM Digital Asset Haven ISO 20022 Messaging Adapter, in beta. ISO 20022 is the global standard format banks already use to send payment instructions, and the adapter lets them send those same instructions across Swift's shared ledger while the underlying tokenized deposit moves on the chain.

In IBM's framing, the bank does not need to learn a new way of instructing payments. Tom McPherson, general manager of IBM Z and LinuxONE, said "the financial services industry is entering a new era where tokenized and traditional assets will need to move side by side," and that connecting to Swift's shared ledger lets clients do that without giving up control.

The Swift side: 17 banks, nine months from concept

Swift first announced the shared ledger at Sibos 2025, built from a prototype developed with Consensys. IBM's release says Swift designed it with more than 40 financial institutions and moved from concept to activation in nine months. As of the IBM post, 17 first-mover institutions are piloting tokenized deposit transactions on it. Banks in that program have already tested tokenized deposits using IBM Digital Asset Haven.

Two things to keep separate. The 17-bank pilot is the active group using Swift's ledger. The IBM messaging adapter is one vendor's beta connector into that ledger. The IBM release does not list which of the 17 are using the IBM adapter, and it does not say the connector is generally available to every Haven client. The 24/7 movement of digital assets ahead of final settlement is real, but final settlement still runs through the existing systems.

The on-premises Haven, and why some banks care

The second beta in the same IBM release is an on-premises version of Digital Asset Haven. It runs entirely inside a client's own data center on IBM Z or IBM LinuxONE hardware, with no public cloud dependency. Keys sit on IBM Crypto Express HSMs, embedded in the same LinuxONE box, with confidential computing isolating production, test, and development environments.

For a regulated bank, the practical point is that the key management layer does not leave the building. IBM also says configurations achieve 99.999999% availability, though the release qualifies that number with specific z/VM, GDPS, and ODF version requirements, so it is a benchmark on a particular stack, not a general uptime claim.

The on-premises Haven uses the same architecture, APIs, and workflows as the SaaS and Hybrid SaaS options IBM launched in October 2025. A bank can move between deployment models without rewriting applications, which removes one of the historical reasons IT teams slow-roll tokenization pilots.

What is actually confirmed

The primary source for all of this is IBM's own September 24 press release. A few items floating in other summaries, including a claim that the IBM-Swift work produced a first live cross-border transaction in August and the identity of the wallet infrastructure provider behind Haven, are not corroborated on the IBM press page.

IBM also cites J.P. Morgan Payments research that 93% of financial institutions are modernizing their payments infrastructure. That is one bank's survey, not a measurement of how many will actually move tokenized deposits through Swift's rail.

The honest read: a Big Tech vendor has a beta connector to a real cooperative ledger, and 17 named institutions are testing tokenized deposits on that ledger. The Swift ledger is moving faster than most expected, and IBM is now visibly on the rail.