IBM Launches Beta Integration Connecting Digital Asset Haven to Swift Ledger

Beta Integration Links IBM Platform to Swift Infrastructure

IBM has launched a beta integration connecting its Digital Asset Haven platform to Swift’s blockchain-based shared ledger. According to the IBM Newsroom, this capability allows financial institutions to instruct tokenized-deposit transactions using existing ISO 20022 payment messages. The move is designed to streamline the adoption of digital asset models by leveraging payment infrastructure that banks already utilize.

The integration relies on a new adapter that translates standard payment instructions into commands for Swift’s tokenized-deposit ledger. This technical design prevents bank staff and legacy systems from needing to interact directly with blockchain-specific interfaces. Instead, the architecture places the blockchain technology underneath, while maintaining ISO 20022 messaging, existing compliance processes, and bank-controlled infrastructure on top. IBM stated that the goal is to make the transition to tokenized deposits look operationally familiar to banking professionals.

17 Institutions Test Swift’s Tokenized Deposit Ledger

Swift’s shared ledger is currently being tested by 17 first-mover institutions. The ledger is designed specifically around bank-issued tokenized deposits, distinguishing it from public blockchain networks that support decentralized tokens. Transactions on this ledger can move around the clock before final settlement is executed through established banking systems. This 24/7 capability aims to address the limitations of traditional batch settlement cycles while maintaining the legal and regulatory frameworks of commercial banking.

Swift currently connects more than 12,500 financial institutions across over 200 markets globally. By linking its platform to this extensive network, IBM positions Digital Asset Haven as a bridge between traditional banking operations and emerging digital asset standards. The company’s approach focuses on reducing friction in the adoption of new digital asset models by minimizing the operational changes required for banks to begin processing tokenized deposits.

On-Premises Option Expands Deployment Choices

In addition to the cloud-based integration, IBM introduced an on-premises beta version of Digital Asset Haven. This version allows financial institutions to run the platform inside their own data centers rather than relying on public-cloud deployment. The on-premises solution utilizes IBM Z and LinuxONE infrastructure, providing banks with direct control over their data and hardware.

This deployment option addresses specific concerns regarding data sovereignty and infrastructure control, which are often cited in enterprise adoption discussions for sensitive financial systems. By offering an on-premises version, IBM caters to institutions that may have strict requirements for keeping financial data within their own physical perimeter.

Tokenized Deposits as a Banking Response to Stablecoins

Tokenized deposits are emerging as a banking industry response to the rise of stablecoins. Unlike stablecoins, which are typically issued by non-bank entities, tokenized deposits retain the status of liabilities of regulated commercial banks. This structure allows them to gain the programmability and settlement advantages associated with blockchain technology while remaining within the traditional banking regulatory perimeter.

The beta phase involves testing the integration across various components of the banking stack. IBM and Swift are working to ensure that the underlying blockchain processes do not disrupt existing compliance workflows or settlement finality protocols. As the beta continues, the focus remains on validating the stability and compatibility of the ISO 20022 adapter with Swift’s ledger. The broader banking industry is watching these developments as tokenized deposits move from conceptual frameworks to operational pilots.