Oracle bridges bank systems to Swift’s blockchain tokenized deposit ledger

Oracle has built a technical bridge connecting bank payment infrastructure to Swift’s blockchain-based shared ledger for tokenized deposits, letting banks route digital-asset transactions through systems they already run. The integration, unveiled at Sibos in Miami, lets institutions plug into cross-bank tokenized payment flows without replacing core banking infrastructure or handing custody of customer deposits to a third party.

• Oracle announced the Swift ledger integration at the Sibos conference in Miami on Sept. 28.
• Oracle Blockchain Platform hosts the smart contracts needed to interact with Swift’s ledger, while Digital Assets Data Nexus supplies supporting infrastructure.
• Oracle Banking Payments links tokenized-deposit transactions to existing ISO 20022 payment processing rather than requiring a separate system.

• Sept 28 day Oracle disclosed the Swift integration at Sibos Miami
• 20022 ISO messaging standard now wired to blockchain-based deposit flows

Oracle is positioning itself as the connective layer between the payment rails banks already operate and Swift’s emerging ledger for tokenized commercial bank money. Oracle’s move gives banks a route into blockchain-based deposit payments without forcing a rebuild of core systems that took decades to establish.

For institutional investors tracking how traditional finance adopts blockchain rails, the integration signals that tokenization is advancing through incumbent infrastructure providers rather than displacing them.

Oracle Splits the Work Across Three Platforms

Swift’s shared ledger was not built to hold every bank’s deposits in one place. Each institution keeps its own tokenized-deposit infrastructure, and the ledger coordinates payment commitments between them.

Oracle’s contribution sits on either side of that coordination layer. Oracle Blockchain Platform hosts the smart contracts that interact with Swift’s ledger, and the Digital Assets Data Nexus manages the surrounding digital-asset infrastructure, including custodial wallets and signing systems.

Oracle Banking Payments then ties those blockchain events back into conventional ISO 20022 message processing, the same standard banks use for routine wire and payment transactions.

Banks, Not Swift, Keep Control of the Tokens

The design choice that matters most to banks is custody. Oracle says institutions retain control of their own tokenized-deposit systems rather than ceding that role to Swift, which functions strictly as a coordination layer across institutions.

That distinction is what makes the integration viable for compliance-conscious banks. Faster settlement is only attractive if it does not require surrendering control of customer deposits or the surrounding compliance framework.

A bank-issued deposit token that cannot move cleanly to another institution has limited value on its own, which is why interoperability has become the central design question for bank-issued digital money. Swift is attacking that problem from the network side; Oracle is attacking it from inside each bank’s existing technology stack.

The Trend Points Away From Stablecoin-Only Rails

The broader pattern Oracle’s move fits into is banks building programmable versions of their own regulated money rather than waiting for stablecoins to take over payment flows.

Oracle is not issuing money in this arrangement. It is making legacy payment rails and new blockchain-based ones talk to each other.

The CCS read. This is less about Swift launching a ledger and more about core-banking vendors deciding who controls the plumbing under tokenized deposits. If Oracle’s model holds, banks gain blockchain settlement without ceding custody or compliance authority to Swift or any outside network, which strengthens the case for bank money over stablecoins in regulated cross-border flows.

Oracle has not disclosed which banks will pilot the Swift integration first or when live transactions will begin moving through the connected systems, leaving the pace of institutional adoption as the open question coming out of Sibos.

Original reporting: newsbtc.com