Oracle connects bank payment systems to Swift shared ledger for tokenized deposits

Oracle announced integration between its banking and blockchain infrastructure and Swift’s shared ledger for tokenized deposits, providing banks a path to interoperable tokenized-deposit payments without replacing core systems.

Key facts

• Oracle is connecting bank payment systems to Swift’s shared ledger for tokenized deposits: banks keep custody of deposits while enabling cross-bank tokenized transfers.
• Oracle Banking Payments links blockchain events to existing ISO 20022 processing to unify traditional and tokenized payment flows under one operating model.
• Oracle Blockchain Platform hosts smart contracts that interact with Swift’s ledger. Digital Assets Data Nexus supplies supporting digital-asset infrastructure, including payment orchestration, custodial wallets, signing, and integration to bank payment stacks.

How the model works

• Swift’s ledger coordinates payment commitments across institutions rather than centralizing balances. Each bank maintains its own tokenized-deposit infrastructure and compliance controls.
• Oracle’s integration bridges internal bank systems with Swift’s coordination layer, enabling interoperability for commercial bank money across bank boundaries.
• Banks can process ordinary and tokenized-deposit payments through the same ISO 20022-aligned workflows.

Implications

• Interoperability: tokenized deposits gain utility when they move across banks. Swift provides the coordination layer; Oracle connects internal systems to that layer.
• Control and compliance: banks retain control of customer deposits, signing, wallets, and compliance frameworks instead of ceding roles to Swift.
• Industry trajectory: banks are upgrading regulated money to be programmable and interoperable rather than adopting external stablecoins. Oracle’s role: enable communication between legacy and blockchain systems, not issue money.