Oracle Integrates With Swift Blockchain Ledger to Connect Banks’ Tokenized Deposits

Oracle is expanding its digital-assets infrastructure into one of the most important areas of modern banking: connecting tokenized deposits with existing cross-border payment systems.

The technology company announced that its Oracle Digital Assets Data Nexus will integrate with Swift’s blockchain-based ledger, allowing banks to participate in payment flows coordinated through Swift while continuing to operate their own tokenized-deposit infrastructures. The announcement was made around Sibos 2026 in Miami.

The development matters because tokenized deposits have faced a practical limitation: a bank can put deposits on a blockchain, but customers still need a way to send those digital representations of bank money to customers at other financial institutions.

Oracle and Swift are now working on infrastructure designed to address that interoperability problem without requiring banks to abandon their existing payment systems.

What Oracle and Swift Are Building

Oracle's Digital Assets Data Nexus is designed to connect traditional banking systems with blockchain-based digital-asset infrastructure.

The platform can support digital-asset issuance, custody, transactions, wallets, smart contracts and governance controls. Oracle said its new capabilities can connect these activities with existing ISO 20022-based payment operations, allowing banks to extend their existing payment architecture into digital forms of money rather than creating a completely separate system.

The Swift integration adds another layer.

Swift's blockchain-based ledger is being developed as a shared orchestration layer for financial institutions. Oracle's integration is designed to let banks record corresponding interbank payment commitments and transaction states through Swift while retaining control of their own tokenized deposits, wallets and settlement arrangements.

In simpler terms, the goal is to connect bank-issued digital money, blockchain infrastructure and conventional payment systems within one operating framework.

Why Tokenized Deposits Need Interoperability

A tokenized deposit is essentially a digital representation of a commercial-bank deposit. The underlying bank liability remains with the issuing bank, but blockchain technology can make the deposit programmable and potentially usable around the clock.

The problem appears when money needs to move between two different banks.

Imagine a corporate customer at Bank A wants to pay a supplier whose account is with Bank B. If both banks use tokenized deposits but operate separate blockchain systems, simply moving a token from one ledger to another is not enough.

The banks must coordinate customer balances, compliance checks, the transfer of their respective liabilities and the settlement of the resulting interbank obligation.

This is where interoperability becomes economically important.

Oracle says its integration with Swift Ledger is intended to synchronize transaction state with existing banking and payment systems, helping coordinate workflows across wallets and payment infrastructure.

Swift’s Ledger Is Moving Beyond the Pilot Stage

The Oracle announcement comes as Swift's blockchain-ledger initiative begins demonstrating real-world transactions.

In September, DBS, OCBC and UOB completed live domestic Singapore-dollar transactions using tokenized deposits on Swift's blockchain-based ledger. The three banks described the transactions as the first live interbank domestic SGD transactions between them using tokenized deposits.

Earlier in September, DBS and Citi also completed a cross-border dollar payment using tokenized deposits through Swift's ledger. The transaction was completed over a weekend, demonstrating the potential for payment infrastructure that operates outside traditional banking hours.

These developments are significant because they show that tokenized deposits are moving from isolated experiments toward interoperability between established financial institutions.

Oracle's integration therefore arrives at a time when banks are increasingly testing how blockchain-based money can work with the financial infrastructure they already use.

Oracle Wants to Avoid a Separate Digital-Asset Silo

One of the biggest challenges for banks adopting blockchain technology is operational fragmentation.

Traditional payments may run through established payment hubs, core banking systems and correspondent networks, while tokenized assets can exist on separate blockchain networks and wallets.

Running these systems independently can create duplicated processes for reconciliation, compliance, liquidity management and transaction monitoring.

Oracle's strategy is to bring these functions closer together.

Its Digital Assets Data Nexus is designed to connect with Oracle Banking Payments, enabling payment instructions to be mapped to wallets and digital-money rails while coordinating on-chain and off-chain execution. Oracle also says payment status and transaction information can be returned to existing payment hubs.

That could be important for banks that want to experiment with tokenized deposits without rebuilding their entire payments infrastructure.

AI Could Become Part of the New Payment Stack

The Oracle-Swift integration is not only about blockchain.

Oracle is also adding AI-enabled monitoring and analysis to its Digital Assets Data Nexus platform.

The company says AI capabilities can help banks identify transaction anomalies, operational exceptions, liquidity pressures and other emerging risks, with policy-controlled responses available through the platform.

This is particularly relevant because blockchain-based payments can execute rapidly and potentially operate 24 hours a day.

Traditional banking processes often provide time for manual intervention when an unusual transaction is detected. A faster digital-money environment reduces that window.

Banks therefore need automated controls capable of screening transactions, enforcing wallet and authorization policies, applying transfer limits and identifying suspicious activity before or during execution.

Oracle says its platform is designed to incorporate those controls into digital-asset workflows.

What This Could Mean for Banks

For banks, the potential benefit is not simply faster payments.

A connected tokenized-deposit infrastructure could eventually allow financial institutions to offer corporate customers more programmable treasury services.

For example, businesses could potentially use tokenized deposits for payments that depend on specific conditions, automate parts of treasury operations or move funds outside traditional banking hours, subject to the relevant regulatory and network frameworks.

Banks could also potentially improve liquidity management by getting greater visibility into balances and payment obligations across different systems.

But the economic case will depend on more than technology.

Banks must still consider regulatory requirements, liquidity, settlement arrangements, cybersecurity, customer adoption and the costs of maintaining multiple payment networks.

Oracle Faces a Growing Digital-Asset Infrastructure Market

Oracle is not entering an empty market.

Other major technology companies are also connecting institutional digital-asset systems with Swift's ledger.

IBM, for example, announced on September 24 that its Digital Asset Haven platform could connect to permissioned blockchain networks including Swift's blockchain-based shared ledger through a beta ISO 20022 messaging adapter.

That suggests a broader competitive trend: large technology providers are attempting to become the infrastructure layer between traditional financial institutions and emerging blockchain-based payment networks.

For Oracle, the opportunity extends beyond tokenized deposits. Its Digital Assets Data Nexus is designed to support other digital forms of money and assets, including stablecoins, central-bank digital currencies, digital bonds and funds, and tokenized real-world assets.

Tokenized Deposits vs Stablecoins

The rise of tokenized deposits also needs to be viewed alongside stablecoins.

A tokenized deposit remains a claim on the commercial bank that issued the deposit. A stablecoin, by contrast, is generally structured as a digital payment instrument backed by reserves according to its issuer's terms and applicable regulations.

Both can provide programmable digital transfers, but their banking and settlement models are different.

For banks, that creates a strategic question: whether to develop tokenized deposits, support regulated stablecoins, or potentially use both.

Oracle itself has discussed the differences and potential complementary roles of tokenized deposits and regulated stablecoins in institutional payments.

The development of interoperability infrastructure could make that decision more practical because banks would have more options for connecting different digital-money networks to their existing operations.

Risks and Challenges

Despite the potential, tokenized deposits remain an emerging market.

Regulation is one of the biggest uncertainties. Rules governing digital money, stablecoins, tokenized deposits, custody and cross-border transfers continue to develop across jurisdictions.

Interoperability is another challenge. Connecting different ledgers does not automatically create a single global payment network. Each system still needs rules governing settlement, identity, liquidity and transaction finality.

Cybersecurity and operational risk also become more important when financial transactions are increasingly automated and blockchain-based.

Finally, banks will need to determine whether customers are willing to adopt these systems at scale. Faster settlement is valuable only if businesses and counterparties can actually use the underlying digital money.

What Investors Should Watch

For Oracle investors, the important question is whether digital-assets infrastructure develops into a meaningful commercial business rather than remaining primarily a technology-pilot market.

Key indicators include:

• Adoption of Oracle Digital Assets Data Nexus by banks

• Expansion of Swift Ledger participation

• Growth in tokenized-deposit transactions

• Regulatory progress around digital money

• Integration with Oracle Banking Payments

• Demand for blockchain-based custody and transaction infrastructure

• Enterprise adoption of AI-powered risk and payment orchestration

The wider opportunity also extends beyond payments. If banks increasingly tokenize deposits, bonds, funds and other financial assets, demand could grow for the databases, wallets, compliance systems, smart-contract infrastructure and transaction-management platforms required to operate them.

Conclusion

Oracle's integration with Swift's blockchain-based ledger is an important step toward connecting bank-issued tokenized deposits with the existing global payments infrastructure. The technology is designed to let financial institutions participate in shared payment orchestration while retaining control over their own digital-asset infrastructure and settlement arrangements.

The broader significance is interoperability. Tokenized deposits are unlikely to become a major payment technology if they remain trapped inside individual banks or isolated blockchain networks. Connecting them to established financial infrastructure could help move digital money from experimentation toward practical institutional use.

For investors, the next signals will be bank adoption, transaction volumes, regulatory developments and whether Oracle can turn its digital-assets technology into a scalable commercial business.

Follow the blog for more updates on Oracle, fintech, blockchain, AI, digital assets and global financial markets.

This article is for informational and educational purposes only and should not be considered investment advice.