IBM (NYSE: IBM) is expanding its Digital Asset Haven platform with an on-premises beta that lets banks operate tokenized-asset infrastructure inside their own data centers. The move gives regulated institutions a more direct choice over where the platform, data and key-management processes reside as they test new payment and custody models.
The company also introduced a beta connector to the Swift shared ledger. Through an ISO 20022 Messaging Adapter, participating Digital Asset Haven clients can use familiar payment messages to instruct tokenized-deposit transactions on the permissioned network, according to IBM. Together, the two additions address a practical enterprise question: whether a bank can adopt digital-asset workflows without replacing the operating standards and deployment controls it already uses.
Why On-Premises Control Matters for Regulated Banks
IBM said the on-premises beta runs entirely in a client environment on IBM Z or IBM LinuxONE, with no dependency on public-cloud infrastructure. That positioning is important for institutions that must set their own boundaries for data residency, administrative access, key custody and recovery procedures. A SaaS product can reduce the work of standing up a new service, but it may not fit every bank’s control model or regulator expectations.
The company said the on-premises option retains the same architecture, APIs and workflows used by the platform’s SaaS and hybrid-SaaS deployments. In principle, that gives teams a common operating model while allowing them to select a deployment pattern suited to a particular workload. IBM described hardware-backed key protection through Crypto Express hardware security modules, confidential computing and isolation between production, test and development environments.
Those features do not remove the governance work. Banks still need to define who can authorize transactions, how exceptions are handled and what records auditors require. But an on-premises model changes the allocation of responsibility: the customer gains more control over the operating environment while taking on more of the work of running it.
Swift Integration Preserves a Familiar Payment Language
The ledger connector is designed to reduce a separate integration hurdle. IBM said clients can use ISO 20022 messages—already a core format in bank payment operations—to instruct tokenized-deposit transactions rather than build workflows around blockchain-specific message formats. That could make the technology easier to evaluate alongside existing payment controls, reconciliation processes and compliance operations.
Swift says it is working with more than 40 financial institutions on its blockchain-based ledger, whose initial use case is 24/7 cross-border payments with tokenized deposits. IBM said 17 first-mover institutions are piloting tokenized-deposit transactions through the ledger. The beta status matters: neither company has presented the capability as broad production availability, and institutions will need to test interoperability, controls and operational ownership before treating it as a replacement for established settlement infrastructure.
IBM’s strategy is less about asking banks to choose between traditional controls and digital-asset services than about making the newer model fit inside a controlled enterprise stack. Legacy platforms often force institutions to bolt digital-asset pilots onto separate infrastructure and unfamiliar operating procedures. By pairing an on-premises option with standard payment messaging, IBM is raising the competitive expectation that digital-asset infrastructure should adapt to bank control models rather than require banks to loosen them.