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 move builds on an earlier milestone: Oracle’s Swift Compatible Application certification for payments, announced earlier in 2026.
The timing wasn’t accidental. Oracle unveiled the integration at Sibos 2026 in Miami, the annual gathering that ran from September 28 through October 1 and drew the usual crowd of banks, vendors, and payment infrastructure players. Oracle isn’t alone in chasing this connection, either — IBM and Cosmos are also building their own routes into Swift’s ledger, which frames this less as a singular Oracle breakthrough and more as a wider vendor race to plug into the same coordination layer.
Keeping Existing Payment Systems and Wallets Running
The practical detail that matters most for banks weighing this integration is what they don’t have to change. Institutions can keep running their current payment applications, wallets, and settlement infrastructure while linking into Swift’s ledger for cross-bank coordination. That’s a deliberate design choice — asking banks to abandon systems they’ve spent years building would have made adoption a much harder sell.
Swift’s Ledger as a Shared Coordination Layer
Swift’s ledger functions as the common ground where tokenized deposits from different banks can meet for cross-institution payments. Banks can manage tokenized deposits on their own systems just fine, but those assets still need somewhere shared to coordinate payments between institutions — that’s the gap Swift’s ledger is built to fill, and it’s the gap Oracle’s integration connects to.
In practice, this means an institution’s tokenized deposit infrastructure doesn’t have to talk directly to every counterparty’s system. It talks to the ledger, and the ledger handles the coordination.
A Network Spanning 11,500-Plus Institutions
Scale is the reason this matters beyond one vendor’s product sheet. Already linking more than 11,500 institutions across 200-plus countries, Swift’s network ensures 75% of payments arrive at the destination bank within 10 minutes. That existing footprint — comparable in spirit to the interoperability questions raised around XRP and Swift in other contexts — gives Oracle’s integration a potential distribution path that a standalone blockchain network would take years to build from scratch. Swift itself said in July that 17 banks from six continents were preparing to pilot live transactions on the ledger, a signal that the coordination layer is moving from concept toward real testing.
Inside Oracle’s Technology and Compliance Stack
Oracle’s answer to interoperability rests on a stack of components that each handle a different piece of the tokenized deposit workflow. The Blockchain Platform supplies enterprise-grade infrastructure, the Digital Assets Data Nexus manages digital-asset operations, and Oracle Banking Payments ties tokenized activity back into standard payment processing — while bank infrastructure retains control over deposits, wallets, and settlement.
Custodial Wallets, Smart Contracts, and ISO 20022
According to Oracle, its Blockchain Platform and Digital Assets Data Nexus provide support for Swift commitment contracts, custodial wallets, signing, smart contracts, and event orchestration. That combination lets tokenized deposits move through existing bank payment infrastructure without requiring a separate system for every blockchain or counterparty a bank happens to work with.
Oracle is also connecting that tokenized-deposit workflow to ISO 20022-based payment processing, mapping payment instructions and accounts to digital wallets and routing payment status back to existing systems. The practical upshot: banks don’t need to build a parallel process just to handle tokenized money — the standard ISO 20022 pipes they already use for everyday payments carry the status updates too.
AI Oversight and Compliance Through Digital Assets Data Nexus
The Swift integration lands on top of an earlier expansion Oracle made to its Digital Assets Data Nexus on September 23, which added payment integrations, configurable wallet and smart-contract controls, and AI-enabled oversight, along with 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.
This is where the story moves from plumbing to governance. Compliance tooling built into the same stack that handles custody and smart contracts means banks aren’t bolting on a separate risk layer after the fact — at least in theory. Whether that holds up once live volumes grow is a different question than what a product announcement can answer.
Settlement Still Runs on Traditional Rails
Coordinating tokenized payments across banks doesn’t mean the blockchain itself finalizes the money movement. Swift’s ledger synchronizes interbank payment commitments using tokenized deposits, but final settlement still happens on existing RTGS or correspondent-banking rails. Oracle’s integration follows that same hybrid model, syncing events between the ledger, tokenized-deposit infrastructure, and existing bank systems before settlement occurs — a structure that echoes broader arguments about why stablecoin rails are gradually chipping away at traditional wire transfers elsewhere in the payments world.
Why does this matter for the wider adoption debate? Because it lowers the risk profile for banks. Nobody is asking institutions to trust a new settlement mechanism outright; they’re being asked to add a coordination layer on top of systems that already work, with the money still landing through rails regulators and risk teams understand.
What’s Planned — and What Remains Uncertain
Not everything Oracle described is live today. Some capabilities are planned for fiscal year 2027 and remain subject to change, according to the company. That caveat matters because the real test isn’t the announcement — it’s which banks actually connect their tokenized-deposit systems, how the ledger gets adopted for live transactions, and how institutions balance blockchain-based coordination against the settlement rails they’re not giving up anytime soon.
Oracle’s integration is built to help banks step into Swift’s blockchain-based payment environment without walking away from the payment applications and settlement infrastructure they’ve already invested in. The model stitches together tokenized deposits, ISO 20022 payment processing, bank-managed wallets, and Swift’s shared coordination layer, with settlement continuing through established RTGS or correspondent-banking systems. Swift’s existing footprint of more than 11,500 institutions gives the approach a plausible route into a banking network that’s already global — the open question is how many of those institutions actually turn the connection on.
FAQ
What does Oracle’s integration with Swift’s ledger enable for banks?
It enables banks to connect their tokenized deposit infrastructure to cross-bank payment flows while continuing to operate existing payment systems and wallets.
How does Swift’s ledger function in cross-bank tokenized payments?
Swift’s ledger acts as a shared coordination layer for interbank payment commitments among banks.
Does the integration mean settlement occurs on blockchain?
No, final settlement remains on traditional rails like RTGS and correspondent banking, not on blockchain.
What compliance features does Oracle provide with this integration?
Oracle’s Digital Assets Data Nexus includes AI oversight, KYC/KYB checks, and AML screening to support compliance.
Article produced with the assistance of artificial intelligence and reviewed by the editorial team.