International Business Machines has expanded its digital asset infrastructure strategy with a new connection between IBM Digital Asset Haven and Swift’s blockchain-based shared ledger, while also testing an on-premises deployment option for regulated financial institutions.
The development is aimed at banks and other financial organizations exploring tokenized deposits, stablecoins, and blockchain-based settlement without requiring them to build separate technology stacks for each digital asset network.
According to IBM’s announcement, the new integration is being offered in beta and allows institutions using Digital Asset Haven to process tokenized deposit transactions through Swift’s shared ledger using standard ISO 20022 messaging. The approach is intended to reduce the need for financial institutions to adopt separate blockchain-specific transaction workflows.
The integration is designed to let banks use existing ISO 20022-based messaging processes to interact with tokenized deposits on Swift’s ledger, potentially simplifying the connection between conventional financial infrastructure and blockchain-based assets.
Swift expands tokenized deposit testing
Swift operates a global financial messaging network connecting more than 12,500 financial institutions across more than 200 markets. Its shared-ledger initiative is being tested as financial institutions examine how tokenized deposits could support faster and more programmable forms of settlement.
Seventeen institutions are currently participating in pilot transactions involving tokenized deposits on the ledger, according to the announcement.
Tokenized deposits are digital representations of commercial bank deposits. They differ from privately issued stablecoins because they represent claims on regulated financial institutions. Banks have been examining the technology as a potential way to combine the characteristics of traditional deposits with blockchain-based programmability and settlement capabilities.
IBM’s integration with Swift seeks to address one of the challenges facing institutional adoption: connecting emerging digital asset infrastructure with established payment and messaging systems.
Using ISO 20022 messaging could also provide institutions with a familiar framework for processing transactions. The standard is already used extensively across global financial systems and supports structured transaction information.
IBM tests on-premises digital asset infrastructure
IBM is also testing an on-premises version of Digital Asset Haven for organizations that need to manage digital assets within their own data centers.
The deployment is being designed for IBM Z and IBM LinuxONE systems, allowing regulated organizations to manage assets such as stablecoins and tokenized deposits without depending on public cloud infrastructure.
The on-premises option could give banks and other regulated institutions greater control over the infrastructure supporting digital assets, while addressing operational, security and data-management requirements that can influence technology decisions in highly regulated financial markets.
The approach is particularly relevant for institutions that maintain critical financial workloads on dedicated infrastructure and may face restrictions or internal policies concerning the use of public cloud services.
Digital Asset Haven is part of IBM’s broader effort to provide infrastructure for institutions entering the digital asset market. The company has been developing technology aimed at helping financial organizations manage tokenized assets while maintaining connections with established financial systems.
Banks move toward integrated digital asset systems
The latest developments come as financial institutions increasingly investigate tokenized deposits, stablecoins and other blockchain-based assets as part of broader payment modernization efforts.
For banks, the challenge is not simply issuing or managing a tokenized asset. They also need infrastructure capable of connecting those assets with existing payment networks, messaging standards, custody systems, and compliance processes.
IBM’s connection to Swift’s shared ledger addresses part of that interoperability challenge by combining Digital Asset Haven with a ledger designed for financial institutions.
The on-premises deployment provides another option for organizations that want to retain greater control over their digital asset infrastructure.
Together, the Swift integration and on-premises deployment expand IBM’s approach to institutional digital assets by addressing both interoperability and infrastructure-control requirements as banks evaluate tokenized deposits and blockchain-based settlement.
The beta stage means the technology remains under testing, and broader adoption will depend on how financial institutions evaluate performance, security, regulatory requirements, and operational costs. The participation of 17 institutions in Swift’s tokenized deposit pilot provides an early indication of institutional interest, while the planned infrastructure options could help determine how such systems develop as digital asset use moves toward larger-scale financial applications.







