Oracle links banks’ payment systems to Swift’s tokenized-deposit blockchain

Oracle is building a direct link between banks’ existing payment infrastructure and Swift’s new blockchain ledger for tokenized deposits, giving financial institutions a route into digital-asset settlement without ripping out their core systems. The move signals that large banks intend to make regulated deposit money programmable on their own terms rather than ceding that ground to stablecoin issuers.

• Oracle announced the integration at Sibos in Miami on September 28.
• Oracle Blockchain Platform hosts the smart contracts needed to interact with Swift’s shared ledger.
• Oracle Banking Payments links tokenized-deposit blockchain events to existing ISO 20022 payment processing.

• Sept 28 date Oracle unveiled the Swift ledger link at Sibos Miami
• ISO 20022 existing bank messaging standard now tied to tokenized-deposit events

Oracle is positioning its technology as a bridge between the payment rails banks already run and Swift’s emerging blockchain ledger for tokenized deposits. The company disclosed the integration at Sibos in Miami on September 28. The design lets banks connect their own tokenized-deposit systems to cross-bank payment flows while continuing to hold and control the underlying assets themselves. The story was first reported by NewsBTC.

Banks, not Swift, keep custody of tokenized deposits

Swift’s shared ledger is not meant to consolidate bank balance sheets into one pool. Each institution keeps running its own tokenized-deposit infrastructure, with the ledger acting as a coordination layer between them.

Oracle’s integration sits across that divide. Oracle Blockchain Platform can host the smart contracts required to interact with the Swift ledger, while the company’s Digital Assets Data Nexus supplies the surrounding digital-asset infrastructure banks need to manage those tokens. Oracle Banking Payments then connects those blockchain events to the ISO 20022 messaging standard banks already use for conventional payments.

The intended outcome is a single operating model in which a bank processes ordinary payments and tokenized-deposit payments through the same systems. Oracle has said banks stay in control of their own tokenized-deposit infrastructure rather than transferring that function to Swift, a distinction the company is emphasizing to institutions wary of surrendering control over customer deposits or compliance obligations.

Interoperability is the problem Oracle says it is solving

A bank-issued deposit token that only functions inside one institution has limited value once it needs to move to another bank. That interoperability gap has become a central issue in discussions around bank-issued digital money, and it is the specific problem Swift’s ledger and Oracle’s integration are aimed at closing.

Swift is approaching the problem as a coordination layer between institutions. Oracle is approaching it from inside each bank’s own systems, covering payment orchestration, custodial wallets and signing infrastructure alongside the ISO 20022 link.

Oracle frames itself as connector, not deposit issuer

Oracle’s own description of its role draws a clear line: the company is not issuing tokenized deposits itself but building the connective layer between older payment infrastructure and newer blockchain-based settlement. That framing matters because banks moving into tokenized deposits are doing so on their own terms rather than waiting for stablecoins to displace existing rails.

Details about which banks have committed to using the Oracle integration or when live transactions on Swift’s ledger might begin remain open questions as the technology moves from announcement to deployment.

The BlockWest read. For bank treasurers and payment-ops teams, this is less about blockchain novelty than about avoiding a rebuild. Oracle is selling continuity: keep your ISO 20022 stack, your custody controls, your compliance sign-off chain, and bolt tokenized settlement on top. That pitch matters more to risk committees than to crypto markets, and it is the reason banks may move on deposit tokenization faster than they have on stablecoins.

Whether the integration moves from announcement to production hinges on which banks agree to route live tokenized-deposit payments through Oracle’s stack and onto Swift’s ledger, details neither Oracle nor Swift has disclosed publicly so far.

BlockWest is a news publication. Nothing here is investment advice. Read our disclaimer and editorial policy.