IBM Links Traditional Banking to Blockchain as Swift Ledger Integration and On-Premises Digital Asset Haven Enter Beta
Key Takeaways
- •IBM's Digital Asset Haven now supports tokenized deposit transactions on Swift's blockchain-based shared ledger through a beta ISO 200 message adapter that relies on standard banking payment messaging rather than blockchain-specific workflows.
- •Swift's shared ledger, first presented at Sibos 2025 and built on a prototype developed with Consensys using input from more than 40 financial institutions, went from concept to activation in nine months and is now piloting tokenized deposits with 17 institutions.
- •Participating IBM clients can move bank-issued tokenized deposits around the clock on the Swift ledger, with final settlement still completing through existing systems while banks retain established Swift standards and their own compliance processes.
- •IBM's new on-premises beta of Digital Asset Haven allows regulated institutions to manage assets such as stablecoins and tokenized deposits entirely within their own data centers on IBM Z and LinuxONE hardware, with no dependency on public cloud infrastructure.
- •The on-premises edition shares the same architecture, APIs, and workflows as the SaaS and hybrid editions available since October 2025, enabling clients to switch deployment models without rewriting their applications.

IBM announced two developments aimed at connecting traditional banking infrastructure with blockchain technology: an integration between its digital asset platform and Swift's blockchain-based shared ledger, and an on-premises beta of the same platform for regulated institutions.
With the Swift integration, IBM Digital Asset Haven — the company's digital asset management platform — can support tokenized deposit transactions executed through standard payment messaging. A beta release of an ISO 20022 message adapter — the global standard for financial messaging that banks already rely on for cross-border payments — allows banks to initiate such transactions with the message formats and operational processes they already use, removing the need to adopt blockchain-specific workflows.
The announcement lands as banks broadly modernize their payments infrastructure, looking for faster cross-border money movement and better tools to handle a widening array of digital assets. Swift — the cooperative whose network links more than 12,500 financial institutions across over 200 markets first presented the shared ledger at Sibos 2025, its annual financial industry conference. Built on a prototype developed together with Consensys, and shaped by input from more than 40 financial institutions worldwide, the platform went from concept to activation in nine months. Seventeen institutions are now piloting tokenized deposit transactions on it.
The ledger carries bankissued tokenized deposits — blockchain-based representations of deposits held at the issuing bank — which means participating IBM clients can move digital assets around the clock, ahead of final settlement that still completes through existing systems. Banks keep relying on established Swift standards and their own compliance processes. Financial institutions already taking part in the program have successfully tested tokenized deposits on the Swift ledger using Digital Asset Haven.
On-Premises Deployment Brings Digital Asset Operations In-House
Alongside the Swift integration, IBM is extending Digital Asset Haven into an on-premises beta deployment, letting regulated organizations manage digital assets such as stablecoins and tokenized deposits entirely within their own data centers. The platform's SaaS and hybrid editions have been available since October 2025, and banking and payment institutions across several continents have since started implementing digital asset use cases on them.
The on-premises edition runs on IBM Z and IBM LinuxONE systems with no dependency on public cloud infrastructure, either on hardware that clients already run or on newly added capacity. It features client-controlled deployment, with both the solution layer and the key management layer kept inside the client's own environment in configurations designed to reach 99.999999% availability. Keys are protected by IBM Crypto Express hardware security modules, while confidential computing and environment partitioning separate production, test, and development workloads. That design reflects constraints familiar to regulated banks, where data-residency rules and internal risk policies can require that sensitive systems and cryptographic key material stay under the institution's direct control.
Formal, auditable key ceremonies govern the generation of root certificate authority keys, producing documentation suitable for regulatory review, and cold storage operations are supported through the IBM Offline Signing Orchestrator.
Because the on-premises edition shares the same architecture, APIs, and workflows as the SaaS and hybrid options, clients can switch between deployment models without rewriting their applications — a setup aimed at institutions that want to expand into digital assets while keeping control of their technology stack.
With both developments still in beta, the next milestone to watch is how the pilots — such as the 17 institutions testing tokenized deposits on the Swift ledger — and the early implementations underway on the SaaS and hybrid editions move from testing toward production use.
Source: Metaverse Post