How Oracle Connects Tokenized Deposits to Swift’s Blockchain Ledger

Oracle’s integration with Swift’s blockchain-based ledger is intended to help banks use tokenized deposits in cross-bank payment flows without replacing their established payment operations. The design connects a bank’s own digital-asset infrastructure with Swift’s coordination layer and existing ISO 20022-based processing. Oracle announced the integration at Sibos in Miami on September 28, 2026. 32

How the connection is designed to work

The approach links three parts of the payment process: a bank’s tokenized-deposit infrastructure, Swift’s ledger for coordinating cross-bank activity, and the bank’s existing payment operations. Oracle says the integration is intended to let financial institutions extend existing payment services with interoperable tokenized deposits and manage traditional and digital-asset payment flows through a unified operating model. 32

That makes the integration a connection between systems, rather than a proposal to move every deposit or payment onto one blockchain. Oracle’s announcement describes banks using their own tokenized-deposit infrastructure in payment flows coordinated through Swift’s ledger. 2132

What each Oracle product contributes

• Oracle Blockchain Platform: Provides part of the technical foundation for connecting a financial institution’s digital-asset infrastructure to Swift’s ledger. Oracle’s announcement describes the integration as a way for institutions to participate in payment flows coordinated through Swift. 1632
• Oracle Digital Assets Data Nexus: Connects digital-asset transactions with existing payment operations. Oracle’s announced capabilities include integration with ISO 20022-based payment systems and coordination with Swift’s ledger. 1929
• Oracle Banking Payments: Offers a prebuilt integration path for banks using Oracle’s payment platform. The aim is to bring digital-money flows into existing payment processing and orchestration, rather than require a separate payment workflow. 1929

In practical terms, Data Nexus is the link between digital-asset activity and payment operations; Banking Payments is the existing payment hub the integration is designed to work with. Oracle says its Banking Payments application is built on the ISO 20022 framework. 1934

Where it fits in Swift’s ledger rollout

Oracle’s announcement is part of a broader Swift initiative. Swift says it is working with more than 40 financial institutions on its blockchain-based ledger. 5 For the initial use case, 17 banks were preparing to pilot live transactions using tokenized deposits, with 24/7 cross-border payments as the focus. 9

Those figures describe different stages and groups: more than 40 institutions have been involved in the wider effort, while 17 banks were preparing the initial pilot transactions. They do not establish that all those institutions are already processing tokenized-deposit payments in production. 59

What the integration does—and does not—mean

The intended benefit is interoperability: banks can connect digital-asset activity to payment infrastructure they already use, while Swift’s ledger coordinates cross-bank flows. Oracle presents the integration as a way to manage traditional and digital-asset payments through a unified operating model. 2132

The public announcements describe planned capabilities and pilot activity, not universal availability. Swift’s initial focus is 24/7 cross-border payments, while the broader aim is to make digital assets work across institutions and alongside traditional payment infrastructure. 921