Oracle integrates with Swift's ledger to link bank tokenized deposits
RWA & Tokenization ·
The integration lets financial institutions plug their own tokenized deposit systems into cross-bank payment flows coordinated through Swift's blockchain ledger.
Oracle announced the integration at Sibos in Miami on September 28, 2026, positioning it as a way for banks to extend existing payment infrastructure rather than replace it, according to Oracle's announcement. Under the setup, institutions keep their tokenized deposits on their own bank-centric ledgers while Swift's ledger acts as the coordination layer that lets those tokenized assets move through interbank payment flows alongside traditional payments.
The technical stack combines several existing Oracle products. Oracle Blockchain Platform and Oracle Digital Assets Data Nexus provide a pre-integrated base that can host Swift commitment contracts and handle the event orchestration needed to connect to Swift's ledger, including EVM-based enterprise blockchain functions, custodial wallet capabilities, signing, integration, and smart contract support. Oracle Banking Payments then ties that digital asset activity into existing ISO 20022 payment processing, so tokenized deposit transactions and conventional payments run through a single operating model rather than parallel systems.
Jamie Bullard, vice president of application software engineering for payments and financial crime management at Oracle Financial Services, said the goal is to give institutions a trusted way to bring tokenized deposits into established payment infrastructure without sacrificing control, security, or operational resilience. The pitch centers on two problems Oracle says banks face as they build out digital asset strategies: getting tokenized deposits to work across institutions, and connecting that activity to the payment rails already in place.
Oracle frames the combined system as reducing integration and operational complexity for banks while increasing payment transparency and supporting governance, security, and regulatory oversight requirements that apply across global financial services. The company also points to durable workflows and transaction coordination across the Swift ledger lifecycle as a way to keep processing consistent even as tokenized and traditional payment events run in tandem.
Not yet detailed is which banks or markets will be first to deploy the integration, on what timeline, or how adoption will be measured. The announcement outlines the technical architecture and stated goals but does not specify pilot participants, transaction volumes, or a rollout schedule, leaving those details as points to watch as the integration moves from announcement to implementation.