IBM is expanding its digital-asset infrastructure for banks. The company is connecting IBM Digital Asset Haven to Swift’s blockchain-based shared ledger, giving financial institutions a way to use existing payment messaging standards for tokenized deposit transactions.
IBM announced the integration on September 24, alongside a new beta option that lets regulated organizations run Digital Asset Haven entirely within their own data centers. These moves aim to give banks more flexibility as they begin incorporating tokenized deposits and other digital assets into existing financial infrastructure.
Connecting to Swift’s shared ledger
Under the new beta capability, IBM Digital Asset Haven clients can connect to permissioned blockchain networks, including Swift’s shared ledger. IBM has also introduced an ISO 20022 Messaging Adapter, which lets institutions instruct tokenized deposit transactions through standard ISO 20022 messages.
This is an important part of the integration. Rather than forcing banks to build completely separate workflows for blockchain-based transactions, the system lets them build on payment messaging standards and operational processes they already use. Swift’s ledger supports bank-issued tokenized deposits and 24/7 digital-asset transactions, while final settlement continues through existing banking systems.
As a result, this approach could make it easier for banks to experiment with tokenized money without replacing their existing payment infrastructure.
Swift’s tokenized deposit network keeps expanding.
Swift introduced its blockchain-based ledger at Sibos 2025 and developed the initial system with more than 40 financial institutions. In July, Swift said 17 banks across six continents were preparing to pilot live transactions using tokenized deposits. The ledger aims to support 24/7 cross-border payments while improving the movement and management of liquidity.
According to IBM, financial institutions already participating in Swift’s tokenized-deposit program have tested tokenized deposits through Digital Asset Haven. This means the integration moves beyond a standalone blockchain experiment. Instead, it connects digital-asset infrastructure with an established global financial messaging environment. Swift itself connects more than 12,500 financial institutions across more than 200 markets, according to IBM.
Why ISO 20022 matters here
The use of ISO 20022 could be one of the most important elements of the IBM-Swift integration. Banks already use this messaging standard across modern payment systems. Letting tokenized deposit instructions move through familiar message formats can reduce the need for institutions to develop entirely new operational processes for blockchain transactions.
This matters because financial institutions must manage more than just the underlying technology when introducing digital assets. They also need compliance controls, operational procedures, security systems, and connections to existing payment infrastructure. IBM’s approach brings tokenized transactions closer to those established banking workflows, which could help institutions test digital assets without treating blockchain as a completely separate financial system.
An on-premises option for digital assets
IBM is also expanding Digital Asset Haven with an on-premises beta deployment. Under this model, banks and other regulated organizations can operate the platform inside their own data centers, rather than relying on public cloud infrastructure.
The system runs on IBM Z and IBM LinuxONE environments. According to IBM, this deployment lets both the solution layer and key-management layer stay within the client’s own environment. The platform supports digital assets, including stablecoins and tokenized deposits.
For regulated financial institutions, keeping infrastructure and cryptographic keys within their own environments can provide greater control over security, governance, and operational processes. IBM launched Digital Asset Haven’s SaaS and hybrid deployment options back in October 2025. This new on-premises option now gives institutions another deployment model as they evaluate digital-asset use cases.
Tokenized deposits move closer to existing banking infrastructure.
The IBM-Swift integration arrives as banks explore how tokenized deposits can improve the movement of money across markets. Unlike privately issued cryptocurrencies, tokenized deposits represent bank money in digital form. They can potentially support programmable and always-on payment processes while remaining connected to regulated financial institutions.
Swift is developing its ledger specifically around bank-issued tokenized deposits and regulated financial infrastructure. The company has said the platform could eventually support applications such as programmable money and agentic commerce. That direction also connects with the broader development of digital financial infrastructure more generally. As tokenized deposits, stablecoins, and other forms of digital value become more widely tested, banks need systems that can connect these assets to existing payment networks. IBM is positioning Digital Asset Haven as one such infrastructure layer.
A broader strategy than blockchain alone
This latest announcement also shows how IBM is approaching institutional digital assets more broadly. Rather than focusing only on blockchain networks, Digital Asset Haven aims to provide a wider environment for managing digital assets across different deployment models.
IBM developed the platform for banks, governments, and other regulated organizations. Its infrastructure can support assets such as stablecoins and tokenized deposits while providing controls around key management and security. The new Swift connection expands that role into payment infrastructure directly. The on-premises option, meanwhile, addresses institutions that want to retain greater control over where they manage digital-asset operations and cryptographic keys.
What comes next for tokenized payments?
The immediate IBM-Swift integration remains a beta capability, while Swift’s broader tokenized-deposit initiative is still moving through pilot activity. That means this technology hasn’t yet become a universal replacement for conventional payment infrastructure.
Still, the direction is becoming clearer. Financial institutions are testing ways to move tokenized forms of money through infrastructure that still connects with established banking standards and controls. IBM’s integration with Swift’s shared ledger illustrates that approach well: banks can introduce blockchain-based transactions while continuing to use familiar messaging standards and existing operational processes.
As tokenized deposits move toward real-world use, the challenge will shift. It becomes less about proving that blockchain can move digital value and more about integrating that capability into the systems banks already depend on. IBM’s latest move puts that integration at the center of its digital-asset strategy, connecting tokenized deposits, Swift’s global payment infrastructure, and enterprise-controlled technology within a single banking workflow.
IBM Boosts Digital Asset Security with Swift Ledger Integration and On-Premises Deployment


Comments
No comments yet. Be the first to share your thoughts.
Leave a comment