IBM announced two Digital Asset Haven beta capabilities on September 24: a connection to permissioned networks including Swift’s shared ledger, and an on-premises deployment option for IBM Z and LinuxONE.
The messaging integration is designed to let institutions instruct tokenized-deposit transactions using ISO 20022 messages. The on-premises option lets participating customers run the digital-asset platform within their own data centers on supported IBM infrastructure.
Existing messages meet tokenized deposits
IBM’s announcement describes an ISO 20022 Messaging Adapter intended to preserve familiar operational formats while connecting to the ledger infrastructure.
The release says participating institutions have tested tokenized deposits using Digital Asset Haven and Swift’s shared ledger. It frames the capability as a way to use established messaging and bank processes for new digital-asset transactions.
There is an important timing distinction in IBM’s description: digital assets can move continuously ahead of final settlement through existing systems. Continuous ledger activity should therefore not be interpreted as proof that every associated settlement process is complete at the same moment.
A deployment choice for institutions
The on-premises beta extends deployment options beyond the service’s existing SaaS and hybrid arrangements. IBM says the new option keeps the solution and key-management layers in the customer’s IBM Z or LinuxONE environment.
That can address an institution’s requirements about where infrastructure runs and who operates it. It also leaves the institution with responsibilities associated with capacity, configuration and its own environment.
The announcement’s performance and availability descriptions are vendor claims tied to configurations. They are not independent measurements of every customer’s deployment.
Beta status limits the availability claim
Both capabilities are described as beta offerings. The announcement should not be read as unrestricted general availability or as confirmation that every Swift-connected institution is using tokenized deposits.
For readers, the development illustrates an integration approach: connect new asset records to existing financial messages and processes. It does not remove the need to understand the rights attached to a tokenized asset, or the distinction between a transfer instruction and final settlement.
