Oracle is integrating its digital-asset banking infrastructure with Swift‘s blockchain-based shared ledger, creating a bridge designed to allow banks to transfer tokenized commercial-bank deposits across institutional boundaries. The initiative connects Oracle Banking Digital Assets with Swift’s emerging ledger infrastructure, addressing one of the central challenges facing tokenized banking: deposits issued on one bank’s infrastructure are not automatically transferable or interoperable with deposits issued by another. Oracle’s platform enables financial institutions to issue and manage tokenized deposits and other digital assets while integrating those activities with existing core-banking systems.
Connecting that infrastructure to Swift’s shared ledger could allow participating banks to coordinate transactions involving tokenized money without requiring every institution to build direct blockchain connections with every counterparty. The project does not mean Swift or Oracle is issuing a new stablecoin. Tokenized deposits remain liabilities of the commercial banks that issue them, preserving the existing relationship between customers and their banks while changing the technological infrastructure used to transfer value.
Shared Ledger Targets Interbank Interoperability
Swift unveiled plans for its blockchain-based shared ledger as part of a broader effort to build infrastructure capable of supporting digital payments and tokenized assets across its global banking network. The ledger is intended to complement Swift’s existing messaging infrastructure by providing a shared record that financial institutions can use when executing transactions involving digital value. Oracle‘s integration focuses on making bank-issued tokenized deposits interoperable through that environment. A bank could issue a digital representation of a commercial deposit through Oracle Banking Digital Assets while maintaining the underlying account and compliance processes within its existing banking systems. Swift’s infrastructure could then provide a common mechanism for coordinating transfers involving another institution.
That is particularly important because tokenized deposits can otherwise develop into isolated pools of liquidity. If Bank A’s tokenized dollar cannot easily be exchanged with Bank B’s tokenized dollar, financial institutions could reproduce the fragmentation that blockchain-based settlement is intended to reduce. Interoperability infrastructure could allow multiple banks to retain control over their own deposits while participating in a common settlement environment.
Banks Race to Tokenize Commercial Money
Tokenized deposits are receiving increasing attention as banks explore blockchain-based alternatives to conventional payment rails and privately issued stablecoins. Unlike stablecoins such as USDT or USDC, a tokenized deposit represents a claim against a regulated commercial bank and remains part of the banking system’s deposit-money structure. Major financial institutions have already developed similar products. JPMorgan has expanded its blockchain-based deposit infrastructure, while banks including HSBC and Standard Chartered have experimented with tokenized deposits and blockchain settlement. In the UK, major lenders have also participated in industry trials involving tokenized commercial-bank money for payments and property transactions.
Swift’s approach could potentially connect these otherwise separate systems. The organization already links more than 11,500 financial institutions and corporations across more than 200 countries and territories, giving its digital-asset strategy significance beyond an individual blockchain network or banking consortium. However, the Oracle integration should currently be understood as infrastructure development rather than evidence that tokenized deposits have replaced conventional interbank settlement across Swift’s network. Banks still face questions involving regulation, liquidity management, interoperability standards, privacy and the treatment of tokenized deposits across jurisdictions.
The significance of the integration is instead architectural. Rather than requiring banks to abandon their existing core systems for an entirely new blockchain stack, Oracle and Swift are attempting to connect tokenized assets with infrastructure institutions already use. If deployed broadly, the model could allow a customer at one bank to transfer tokenized commercial-bank money to another institution while the underlying banks coordinate settlement through shared blockchain infrastructure. That would move tokenized deposits beyond isolated bank experiments toward something closer to an interoperable digital version of today’s commercial-bank money.