Are Tokenized Bank Deposits Becoming the Future of Money?

Banks Are Putting Familiar Money on Unfamiliar Rails

The next major form of digital money may look less like cryptocurrency than a bank balance that learned how to move differently. On September 24, IBM announced that its Digital Asset Haven platform can connect financial institutions to Swift's blockchain-based shared ledger, allowing banks to initiate tokenized-deposit transactions through familiar ISO 20022 payment messages. Oracle announced another integration four days later, providing banks with an additional route between existing payment systems and tokenized deposits.

Swift, short for the Society for Worldwide Interbank Financial Telecommunication, operates the secure messaging network banks and other financial institutions use to communicate payment and securities instructions across borders. It does not normally move or hold the money itself; instead, its network provides standardized, trusted instructions that allow institutions to coordinate transactions. Swift connects more than 11,500 financial institutions and more than 200 countries and territories, making its involvement important: tokenized deposits are being tested within infrastructure already embedded in the global financial system rather than solely on a new blockchain network built outside it.

The announcements build on a larger experiment already underway. Swift says 17 banks across six continents are preparing initial transactions on its ledger, including Citi, BNY, Wells Fargo, HSBC, UBS and Standard Chartered. The significance is not that banks have invented another cryptocurrency. They are testing whether conventional commercial-bank money can gain some of blockchain's programmability and round-the-clock mobility without leaving the regulated banking system that already supports it.

A Tokenized Deposit Is Still a Bank Deposit

Tokenization makes the concept sound more exotic than it is. A tokenized deposit represents commercial-bank money on programmable infrastructure. The underlying claim remains a liability of the issuing bank, much as money in an ordinary checking or corporate account is a liability of that bank. Moving the deposit onto distributed-ledger infrastructure does not automatically transform it into cryptocurrency.

What changes is the infrastructure coordinating its movement. Swift's blockchain ledger acts as an orchestration layer connecting bank-issued tokenized deposits maintained on participating institutions' own systems. Banks can make funds available around the clock, including outside conventional payment windows, before final settlement through established systems. IBM's new connection is designed to let institutions interact with that network through existing ISO 20022 messaging rather than requiring an entirely separate blockchain workflow.

That approach addresses a persistent weakness in tokenized finance: individual banks can create digital representations of deposits, but those tokens become far more useful if they can move efficiently between institutions. Swift is effectively attempting to provide connective tissue between bank-controlled systems rather than asking the world's banks to migrate onto one proprietary blockchain.

Stablecoins and Tokenized Deposits Take Different Paths

The comparison with stablecoins reveals why banks are interested. Both can represent dollar-denominated value on programmable networks, yet the claim behind that value is different. A stablecoin is generally a liability of a private issuer supported by designated reserve assets. A tokenized deposit remains a deposit liability of a commercial bank.

The Bank for International Settlements argues that this distinction allows tokenized deposits to preserve the existing two-tier monetary structure: customers hold commercial-bank money while banks ultimately settle obligations using central-bank money. Stablecoins operate under a different structure, with their value dependent on the issuer, reserves and redemption framework.

The distinction also separates tokenized deposits from central bank digital currencies. A CBDC would be a direct liability of a central bank; a tokenized commercial-bank deposit is not. Bullion Exchanges recently examined the central-bank side of tokenization through Europe's Pontes settlement system, which connects tokenized financial markets with central-bank settlement. Swift's initiative addresses another layer of the same transformation: how ordinary commercial-bank money might operate in an increasingly tokenized financial system.

Why Banks Want Deposits to Move 24/7

Cross-border banking still contains frictions that digital-asset markets have made increasingly conspicuous. Payments cross time zones, pass through multiple institutions and encounter operating windows that do not always match a global economy running continuously. A business can operate on a weekend even when parts of the financial infrastructure required to settle its payments remain tied to traditional banking schedules.

Swift says its ledger is designed to support 24/7 payment availability while improving liquidity efficiency. The recent IBM and Oracle integrations address the practical challenge of connecting that new infrastructure with systems banks already use. Instead of requiring institutions to abandon established payment operations, the emerging architecture attempts to make tokenized deposits interoperable with them.

There is also a strategic reason for banks to care. Deposits are a fundamental source of bank funding. If more payments migrate toward privately issued stablecoins, some money that might otherwise remain in bank deposits could move into alternative instruments. A 2026 Federal Reserve Bank of New York study examining competition between stablecoins and tokenized deposits highlighted this connection between digital money and bank credit. Tokenized deposits therefore give banks a potential way to offer programmable digital payments while preserving the traditional deposit relationship.

Interoperability Will Decide Whether the Model Can Scale

Creating a token inside one bank is easier than building a system in which deposits issued by different institutions can move reliably across banks, currencies and jurisdictions. A tokenized dollar deposit remains the liability of its issuing bank, so institutions still need mechanisms governing settlement, compliance, liquidity, transaction finality and the obligations created when money moves between them.

That is why the latest integrations are more consequential than they initially appear. IBM and Oracle are not announcing consumer products that suddenly replace checking accounts. They are building connections into the infrastructure required for tokenized deposits to work across institutions. Swift's 17-bank initiative provides the next test: whether those connections can support actual transactions while retaining existing banking controls.

Central banks are exploring the settlement side of the same problem. BIS Project Agorá is examining how tokenized commercial-bank deposits could interact with central-bank money in wholesale cross-border transactions. Together, these projects suggest that tokenization is moving beyond experiments involving isolated digital assets toward a larger question about the architecture of money itself.

Digital Money Does Not Eliminate the Difference Between Money and Gold

For Bullion Exchanges readers, that distinction is more consequential than the underlying blockchain technology. A token can represent a claim on a commercial bank, a central bank, a stablecoin issuer or potentially a physical asset. Similar digital interfaces can therefore conceal fundamentally different financial relationships.

Gold occupies another category because physical ownership does not represent a claim on an issuing bank, central bank or stablecoin company. Tokenized deposits may make bank money faster, programmable and easier to use around the clock, but they do not remove the issuer from the equation. That is also why the expansion of digital money does not create a simple bullish or bearish conclusion for the gold market. Payment infrastructure and reserve assets perform different jobs.

Tokenized deposits remain an emerging technology rather than a replacement for conventional accounts. Interoperability, regulation, cybersecurity, governance and settlement still present significant hurdles. Even so, Swift moving forward with 17 major banks while IBM and Oracle build connections into the same infrastructure marks a meaningful transition from concept toward practical deployment.

If the model succeeds, the future of digital money could look surprisingly familiar. A dollar deposited at a bank would remain a dollar deposited at a bank. The important change would be its ability to operate on programmable infrastructure, interact with tokenized assets and move between institutions outside traditional payment windows. Rather than replacing commercial-bank money, tokenization may end up rebuilding the rails underneath it.