IBM connects Digital Asset Haven to Swift tokenised deposit ledger in dual beta release

IBM announced on 24 September 2026 that clients of its Digital Asset Haven platform can now access beta connectivity to Swift's blockchain-based shared ledger for tokenised deposit transactions — a pairing that places the company at the intersection of legacy financial messaging infrastructure and emerging tokenised payment rails.

The announcement, made from Armonk, New York, also confirmed that IBM is extending Digital Asset Haven to an on-premises beta deployment option, allowing institutions to run digital asset operations within their own data centres on OpenShift environments. Both capabilities remain in beta; neither is a generally available product.

Swift Ledger Connectivity

The beta integration gives Digital Asset Haven clients a pathway to participate in Swift's blockchain-based shared ledger programme for tokenised deposits. Financial institutions already participating in that programme have tested tokenised deposits on the ledger using the IBM platform, according to IBM's announcement materials. No individual participating institutions are named in the announcement.

IBM said Digital Asset Haven now includes a messaging adapter that enables institutions to instruct tokenised deposit transactions using ISO 20022 — a standard widely adopted in high-value payment systems. The adapter is positioned as a means of routing tokenised asset instructions through the same messaging layer many institutions already use for conventional payment flows, rather than requiring entirely separate operational infrastructure.

IBM's Digital Asset Haven is designed to connect tokenised deposit workflows to the Swift shared ledger through existing financial messaging standards, according to the company's announcement.

Tom McPherson, general manager of IBM Z and LinuxONE, is cited in the announcement in connection with the release.

On-Premises Deployment

The on-premises option extends Digital Asset Haven beyond its existing deployment model, allowing institutions to manage digital asset operations within their own data centres on Red Hat OpenShift environments. The beta designation means the feature is not yet in full production release.

The on-premises option may appeal to institutions facing regulatory scrutiny over data residency — though IBM's announcement does not cite any specific regulatory authority or ruling in that context.

Market Context

IBM's announcement cited a J.P. Morgan Payments statistic that 93% of financial institutions are modernising their payments infrastructure, using the figure to contextualise demand for updated digital asset tooling. The statistic is attributed to J.P. Morgan Payments in IBM's own materials.

The combination of Swift connectivity and ISO 20022 compatibility suggests IBM is positioning Digital Asset Haven within existing financial messaging workflows rather than alongside them — an approach that may lower the operational friction for institutions already embedded in Swift's network.

Why It Matters

The dual announcement carries two distinct implications for financial institutions evaluating tokenised deposit infrastructure.

First, the Swift ledger integration provides a route for institutions to participate in tokenised interbank settlement using infrastructure tied to an established global messaging network. The beta framing is a meaningful qualifier: institutions cannot treat this as a production-grade capability yet, and the absence of named participants limits independent verification of real-world performance at this stage.

Second, the on-premises beta addresses a structural question that has grown more prominent as institutions weigh tokenisation strategies: whether digital asset infrastructure must be hosted externally, or whether it can be brought inside existing data-centre perimeters. The OpenShift-based deployment path gives institutions at least a provisional answer, subject to beta limitations.

Taken together, the two announcements reflect a pattern in which incumbent technology vendors are building connectivity layers between tokenised asset platforms and established payment networks, rather than positioning those platforms as replacements for existing rails. Whether beta integrations of this kind mature into production deployments — and at what pace — will be a key variable for institutions assessing their tokenised payments roadmaps.