Oracle announced on September 28, 2026 an integration with Swift’s blockchain-based ledger, letting banks connect their own tokenized deposit infrastructure to cross-bank payment flows while continuing to operate existing payment systems, wallets, and settlement infrastructure.

Jamie Bullard, Oracle Financial Services VP of application software engineering for payments, said in the company’s announcement that institutions need a practical, trusted way to connect digital assets with established payment infrastructure while maintaining control and security. The integration builds on Oracle’s earlier Swift Compatible Application certification for payments, announced earlier in 2026.

The announcement came at Sibos 2026 in Miami, running September 28 through October 1. Oracle isn’t the only vendor building this connection: IBM and Cosmos are also developing routes into Swift’s ledger, positioning this as a wider vendor race rather than a unique Oracle capability.

What Oracle’s Bridge Between Bank Ledgers Does

The central challenge is interoperability. Banks can manage tokenized deposits on their own infrastructure, but those assets need a common coordination layer for payments between institutions. Swift’s ledger provides that shared layer, and Oracle’s integration lets institutions connect existing systems to it while retaining control over their own assets.

Table 1. Main components of Oracle’s integration with Swift’s blockchain ledger.

Oracle said its Blockchain Platform and Digital Assets Data Nexus support Swift commitment contracts, custodial wallets, signing, smart contracts, and event orchestration, letting tokenized deposits join bank payment infrastructure without a separate system per blockchain or counterparty.

The Scale Behind Swift’s Global Ledger

The potential scale comes from Swift’s existing network of more than 11,500 institutions across 200-plus countries, with 75% of payments reaching the destination bank within 10 minutes. 

The goal isn’t another isolated blockchain system, but connecting tokenized bank money with infrastructure already used worldwide, comparable to the interoperability challenges in XRP and Swift: can Ripple actually replace global bank transfers? In July, Swift said 17 banks from six continents were preparing to pilot live transactions.

Why Final Settlement Can Stay on Existing Rails

One important detail: tokenized payment coordination doesn’t necessarily mean final settlement occurs on the blockchain. Swift’s ledger synchronizes interbank payment commitments using tokenized deposits, while final settlement remains on existing RTGS or correspondent-banking rails. 

Oracle’s integration follows the same model, synchronizing events between the ledger, tokenized-deposit infrastructure, and existing bank systems before settlement, a hybrid structure reflected in why stablecoin rails are replacing wire transfers elsewhere.

How ISO 20022 Ties Digital and Traditional Payments Together

Oracle is also connecting the tokenized-deposit workflow to ISO 20022-based payment processing, mapping payment instructions and accounts to digital wallets while returning payment status to existing systems, meaning banks don’t need a separate process for tokenized money.

Governance, Risk Controls, and What’s Still Pending

The Swift integration follows Oracle’s September 23 expansion of Digital Assets Data Nexus, adding payment integrations, configurable wallet and smart-contract controls, and AI-enabled oversight, plus KYC/KYB checks and AML screening. 

Mark Rakhmilevich, Oracle’s VP of mission critical data platform technologies, said banks must support a growing range of assets and settlement models as tokenized deposits, stablecoins, and CBDCs become more widely used, while preserving control over liquidity and risk. Some capabilities are planned for fiscal year 2027 and remain subject to change.

What Comes Next for Bank Adoption

Oracle’s integration is intended to help banks participate in Swift’s blockchain-based payment environment without abandoning existing payment applications or settlement infrastructure. The practical impact will depend on which banks connect their tokenized-deposit systems, how the ledger is adopted for live transactions, and how participating institutions combine blockchain coordination with existing settlement rails.

What this means for you: Oracle is helping banks connect their own tokenized deposit systems to Swift’s emerging blockchain ledger while retaining existing payment and settlement infrastructure. 

The model combines tokenized deposits, ISO 20022 payment processing, bank-managed wallets, and Swift’s shared coordination layer, while final settlement can continue through established RTGS or correspondent-banking systems. Swift’s existing network of more than 11,500 institutions gives the initiative a potential route into the established global banking ecosystem.

This article is for informational purposes only and does not constitute financial or investment advice. Tokenized deposits, blockchain infrastructure, digital-money systems, and cross-border payments involve regulatory, technology, cybersecurity, operational, liquidity, and settlement risks. Some Oracle capabilities described in the source material are planned products and remain subject to change.