Oracle is integrating its financial-services technology with Swift’s blockchain ledger to help banks connect tokenized deposits with existing cross-border payment infrastructure. The integration brings Oracle Blockchain Platform, Digital Assets Data Nexus and Oracle Banking Payments together with Swift’s ledger, creating a unified operating model for traditional and blockchain-based payment flows.

Banks are moving from blockchain experimentation toward infrastructure that can connect tokenized assets with the payment systems already used by financial institutions.

At Sibos, Oracle announced an integration with Swift’s blockchain ledger designed to help financial institutions participate in cross-bank payment flows involving tokenized deposits while continuing to operate their own bank-centric digital-asset infrastructure.

The architecture addresses a central challenge in institutional blockchain adoption: tokenized deposits can exist on individual bank ledgers, but cross-bank payments require those systems to coordinate securely and consistently.

Swift’s blockchain ledger is designed to provide that coordination layer. Oracle’s integration connects the ledger to its existing financial-services technology, allowing institutions to incorporate tokenized deposits into interbank payment workflows while maintaining their existing payment-processing environment.

The initiative combines Oracle Blockchain Platform, Oracle Digital Assets Data Nexus and Oracle Banking Payments. Oracle says the pre-integrated environment can support Swift commitment contracts, event orchestration, enterprise blockchain operations, custodial wallets, transaction signing and smart-contract functionality.

For banks, the objective is not to replace conventional payment infrastructure with blockchain. Instead, the architecture connects traditional payment processing with digital-asset workflows.

That distinction is increasingly important as financial institutions experiment with tokenized deposits, which represent commercial-bank money on blockchain-based ledgers. Unlike privately issued stablecoins, tokenized deposits remain tied to participating banks and can potentially preserve existing banking relationships while adding programmability and continuous transaction capabilities.

Swift’s ledger provides the cross-bank coordination layer, while final settlement can continue through established mechanisms. Swift has described the ledger as infrastructure for orchestrating 24/7 cross-border payments using tokenized deposits rather than a replacement for its broader financial messaging network.

Oracle’s contribution sits at the integration layer. Its Digital Assets Data Nexus is designed to connect digital-asset data and blockchain activity with enterprise financial systems, while Oracle Blockchain Platform provides EVM-based blockchain capabilities and associated wallet, signing and smart-contract functionality.

The connection to Oracle Banking Payments is particularly relevant. The banking platform supports ISO 20022 payment processing, allowing traditional payment messages and tokenized deposit activity to operate within a connected payment lifecycle.

ISO 20022 has become an important foundation for global payments modernization because it provides a common data standard for richer payment information. Connecting blockchain events with ISO 20022-based processing could help banks avoid creating entirely separate operational workflows for digital assets.

Oracle says its architecture also coordinates payment and blockchain events through durable workflows and transaction coordination. That is designed to address an operational problem that can become more complicated when transactions span multiple systems: ensuring that payment states, blockchain states and institutional records remain synchronized.

For digital payments platforms and banking technology innovation, the development reflects a broader shift toward hybrid payment infrastructure. Banks increasingly need to support multiple forms of value and multiple settlement environments without forcing operations teams to manage each system independently.

The market opportunity is growing alongside institutional interest in tokenization. McKinsey estimates that tokenized financial assets could reach approximately $2 trillion by 2030 in a base-case scenario, excluding cryptocurrencies and stablecoins. Its analysis identifies deposits, bonds, funds and other financial instruments as potential candidates for tokenization. (mckinsey.com)

Tokenized deposits are becoming an important part of that market. McKinsey’s 2026 research argues that tokenized deposits could form part of an emerging on-chain monetary architecture, particularly for institutional payments, while interoperability between different bank systems remains a major challenge.

Oracle’s integration directly addresses that interoperability problem. Rather than asking banks to adopt a common blockchain for all of their internal operations, the approach allows institutions to retain their own tokenized-deposit infrastructure while connecting to a shared coordination layer.

That model also has implications for open banking infrastructure and embedded finance platforms. As digital assets become integrated into banking services, the infrastructure supporting them will need to communicate with core banking systems, payment engines, compliance tools and customer-facing applications.

The competitive landscape includes blockchain infrastructure companies, payment networks, core banking vendors and fintech providers building interoperability layers for tokenized assets. Oracle has an advantage in this segment through its existing relationships with banks and its portfolio of payment and financial-crime-management technologies.

The company also has a longstanding relationship with Swift. Oracle said the new integration builds on its previous work with Swift, including achieving Swift Compatible Application certification for payments earlier in 2026.

The larger trend is clear: financial institutions are looking for ways to introduce blockchain capabilities without creating parallel banking infrastructure.

For banks, the appeal of a unified operating model is operational as much as technological. A payment involving conventional commercial-bank money and one involving tokenized deposits can potentially move through related workflows, data structures and controls rather than requiring separate processes.

That could become increasingly important as institutions move from isolated tokenization pilots toward production systems. The competitive differentiator will not simply be whether a bank can issue a tokenized deposit, but whether that asset can participate in cross-bank payments while meeting requirements for security, compliance, resilience and operational transparency.

Oracle’s Swift integration is therefore another step toward treating tokenized deposits as part of mainstream payment infrastructure rather than a separate blockchain experiment.

Market Landscape

Institutional tokenization is shifting toward interoperability and integration with established financial infrastructure. Tokenized deposits are particularly relevant because they can provide programmable representations of commercial-bank money while remaining connected to regulated banking institutions.

Swift is developing the cross-bank coordination layer, while Oracle is connecting that infrastructure to enterprise blockchain, digital-asset and payment-processing systems.

The emerging competitive field includes banks developing proprietary tokenized-deposit networks, global payment infrastructure providers, blockchain interoperability companies and enterprise technology vendors. The major challenge is making these systems work together without weakening existing controls or operational resilience.

Top Insights

• Oracle is integrating Swift’s blockchain ledger with its enterprise blockchain and banking-payment infrastructure to support tokenized deposit workflows.
• The architecture allows banks to retain their own tokenized-deposit infrastructure while connecting to Swift’s cross-bank coordination layer.
• Oracle Banking Payments connects blockchain activity with ISO 20022 payment processing, creating a unified transaction lifecycle.
• Digital Assets Data Nexus and Oracle Blockchain Platform provide blockchain, wallet, signing and smart-contract capabilities for institutional deployments.
• The integration reflects a broader shift from blockchain pilots toward interoperable digital-asset infrastructure connected to established payment systems.

Get in touch with our fintech expert