Tokenized bank deposits and Swift blockchain ledger for cross-border payments

By CoinAINews Editorial Desk

For years, blockchain has been discussed as a technology that could make international payments faster. The difficult part was never simply putting money on a blockchain. Banks also needed a way to connect blockchain-based assets with the payment systems, compliance processes and messaging standards they already use.

That is where tokenized bank deposits and Swift's new blockchain-based ledger come into the picture.

In July 2026, Swift said its blockchain-based ledger was ready for initial use, with 17 banks from six continents preparing to pilot live transactions using tokenized deposits. The goal is to support cross-border payments around the clock rather than relying entirely on traditional banking schedules and settlement processes.

Then, on September 24, IBM announced a beta integration connecting its Digital Asset Haven platform to Swift's blockchain-based shared ledger. IBM's new ISO 20022 Messaging Adapter is designed to let financial institutions instruct tokenized deposit transactions using payment messages they already understand.

But what exactly is a tokenized bank deposit? Is it the same thing as a stablecoin? And does Swift's blockchain ledger actually move bank money?

The answers are important because this system is not simply replacing traditional banking with crypto. It is attempting to connect regulated bank money with blockchain infrastructure.

What Is a Tokenized Bank Deposit?

A tokenized bank deposit is essentially a digital representation of a bank deposit recorded using distributed-ledger technology.

The underlying money remains a bank liability. What changes is the way the deposit can be represented, transferred and potentially programmed.

That makes tokenized deposits different from many cryptocurrencies. They are not designed to function as independent digital commodities whose value floats according to market demand.

They are intended to represent deposits held with regulated financial institutions.

A simple example helps.

Suppose Bank A holds $10 million for a corporate customer. Instead of representing that balance only through the bank's traditional internal ledger, a corresponding tokenized deposit can be represented within a permitted digital-asset infrastructure.

The token can then potentially be transferred through a network designed for participating financial institutions, subject to the rules governing the deposit and the participating banks.

The important word is “tokenized.” The bank deposit does not magically become cryptocurrency simply because distributed-ledger technology is used.

How Are Tokenized Deposits Different From Stablecoins?

This is one of the most common points of confusion.

Feature	Tokenized Bank Deposit	Stablecoin
Issuer	Typically a regulated bank	Usually a private stablecoin issuer
Underlying claim	Bank deposit	Issuer's backing/reserve structure
Blockchain/ DLT	Can be used to represent and transfer the deposit	Commonly used for issuance and transfers
Primary users	Banks and institutional customers	Broad range of users, depending on the stablecoin
Purpose	Digitizing bank money and improving settlement/ payment workflows	Digital money for payments, trading and other applications

The distinction matters because a tokenized deposit remains closely connected to the banking system that issued it.

A stablecoin, meanwhile, is generally a separate digital asset issued under the rules and legal structure of its issuer.

Why Is Swift Building a Blockchain Ledger?

Swift already connects more than 12,500 financial institutions across more than 200 markets. Its role has historically centered on financial messaging rather than acting as a blockchain settlement network.

The new ledger is designed to add blockchain-based infrastructure to that existing financial ecosystem rather than asking banks to abandon everything they already use.

Swift says its blockchain-based ledger is intended to support 24/7 cross-border payments using tokenized deposits.

That is significant because traditional cross-border payments often involve multiple institutions, operating schedules, intermediary banks and settlement systems.

A blockchain-based shared ledger can provide a common digital environment in which participating institutions can coordinate payment activity continuously.

But there is an important caveat:

24/7 movement on the ledger does not automatically mean that every part of final bank settlement becomes instant.

Swift's current design allows tokenized assets to move on the ledger ahead of final settlement through existing systems.

So Does Swift's Blockchain Actually Replace Banks?

No.

This is perhaps the biggest misunderstanding surrounding the project.

Swift's blockchain ledger is not designed to eliminate banks from the payment process.

Instead, it provides another infrastructure layer for participating financial institutions.

The banks still maintain their relationships with customers, manage compliance, control their assets and participate in settlement arrangements.

Swift's objective is essentially to make blockchain infrastructure work alongside the financial system rather than forcing banks to build a completely separate financial universe.

What Does IBM Have to Do With It?

IBM's role is particularly interesting because it addresses the connection between existing bank technology and blockchain infrastructure.

On September 24, IBM announced that clients using IBM Digital Asset Haven can connect to permissioned blockchain networks including Swift's blockchain-based shared ledger through a beta offering.

The key addition is an ISO 20022 Messaging Adapter.

ISO 20022 is already widely used in modern financial messaging. Banks therefore do not necessarily need to create an entirely separate operational language just because the underlying transaction involves tokenized assets.

IBM says institutions can use standard ISO 20022 messages to instruct tokenized deposit transactions through the shared ledger.

In simple terms, the idea looks like this:

Existing bank payment system → ISO 20022 message → IBM Digital Asset Haven → Swift blockchain ledger → tokenized deposit transaction

The architecture is designed to reduce the amount of operational change banks need to make when experimenting with blockchain-based money.

Why Is ISO 20022 Important?

Blockchain developers often think in terms of wallets, smart contracts and on-chain transactions.

Traditional banks think in terms of payment messages, account relationships, compliance procedures and settlement instructions.

ISO 20022 sits between these worlds.

It provides a standardized way of representing financial information in payment messages.

By connecting tokenized deposit transactions to ISO 20022, banks can potentially use familiar payment processes while the underlying transaction is handled through newer digital infrastructure.

This may sound like a small technical detail, but it could be one of the more important pieces of institutional blockchain adoption.

Financial institutions do not necessarily need another completely separate payment system. They need blockchain technology that can fit into the systems they already operate.

How Would a Tokenized Cross-Border Payment Work?

Consider a simplified example involving two banks in different countries.

Bank A wants to send a payment to Bank B.

Under a traditional system, the payment instruction may pass through established messaging and settlement arrangements, potentially involving correspondent relationships and different operating schedules.

With a tokenized-deposit infrastructure, the participating institutions can represent bank money digitally and coordinate the transfer through the shared ledger.

A simplified process could look like this:

The customer instructs its bank to make a payment.
The bank creates the appropriate payment instruction.
The instruction is represented using an established financial messaging standard such as ISO 20022.
The tokenized deposit transaction is sent to the participating ledger infrastructure.
The shared ledger coordinates the digital transaction between participating institutions.
The banks continue to handle final settlement through their existing arrangements.

The exact operational process will depend on the participating institutions and settlement arrangements. The important point is that the blockchain ledger does not have to replace every existing financial system to provide value.

Why 24/7 Payments Matter

Financial markets operate globally, but traditional payment infrastructure has historically been constrained by business hours, holidays, settlement windows and intermediary processes.

A ledger capable of operating continuously can reduce some of those timing restrictions.

Swift says its new ledger is designed to enable 24/7 cross-border payments using tokenized deposits.

For multinational companies, this could eventually mean better visibility over when money is moving between financial institutions.

It could also improve liquidity management because businesses would have greater flexibility over when payments are initiated and processed.

However, 24/7 digital movement should not be interpreted as a guarantee that every underlying banking settlement process is already available continuously.

That distinction will remain important as the system moves from pilot activity toward wider production use.

Who Is Testing Swift's Tokenized Deposit Ledger?

Swift announced in July that 17 banks from six continents were preparing to pilot live transactions using tokenized deposits.

The project was developed with more than 40 financial institutions, according to Swift.

The participating institutions include major banks such as HSBC, Citi, UBS, BNY and Wells Fargo, among others.

The initial focus is cross-border payment activity using bank-issued tokenized deposits.

That gives the project a different character from many crypto experiments.

Rather than starting with retail users buying tokens on a public exchange, the project begins with regulated financial institutions testing digital representations of bank money.

Does This Mean Banks Are Moving to Public Crypto?

Not necessarily.

The Swift ledger is designed as permissioned infrastructure, meaning participation is controlled rather than open in the same way as a public cryptocurrency network.

That distinction is important for banks because compliance, identity, transaction monitoring and operational controls remain central requirements.

Institutional blockchain adoption therefore may not look like the permissionless crypto networks that consumers are familiar with.

Instead, banks may use distributed-ledger technology behind controlled infrastructure while preserving regulatory and operational requirements.

What About Blockchain Settlement?

Settlement is one of the areas where headlines can become misleading.

A payment can be digitally represented or coordinated on a blockchain ledger without every component of the underlying financial settlement happening on that blockchain.

Swift's current approach explicitly allows digital assets to move on its ledger ahead of final settlement through existing systems.

This is why it is more accurate to describe the system as connecting blockchain-based payment infrastructure with traditional settlement rails rather than saying that Swift has moved all bank settlement onto a blockchain.

Could Tokenized Deposits Compete With Stablecoins?

Potentially, they could compete for some of the same payment use cases, but they are not identical products.

Stablecoins have already established themselves as a major form of blockchain-based digital money, particularly for crypto trading and on-chain transfers.

Tokenized deposits take a more bank-centered approach.

The deposit remains tied to a regulated financial institution, while distributed-ledger technology provides additional capabilities for transfer, programmability and interoperability.

Which model becomes more important in institutional payments will depend on regulation, liquidity, interoperability, costs and the willingness of banks and businesses to adopt the infrastructure.

Could AI Agents Eventually Use Tokenized Bank Deposits?

Possibly, and this is one of the more interesting long-term implications.

Swift itself has identified agentic commerce as one potential future area for its ledger infrastructure.

An AI agent that needs to purchase computing resources, access an API or pay another automated service requires a way to move value programmatically.

Today, much of the discussion around autonomous payments focuses on stablecoins and public blockchains.

Tokenized deposits could offer another route if banks develop infrastructure that allows programmable payment instructions within regulated environments.

That future is not yet the same as saying that AI agents are already widely using tokenized bank deposits. The technology and institutional infrastructure are still developing.

What Are the Biggest Challenges?

Tokenized deposits solve some problems, but they do not eliminate the difficult parts of global payments.

Interoperability remains important. Different banks and networks need to communicate reliably.

Liquidity is another challenge. A 24/7 ledger is useful only if participating institutions have the liquidity and settlement arrangements necessary to complete transactions.

Regulation will also determine how tokenized deposits can be issued, transferred and used across borders.

Cybersecurity and key management become critical because digital assets require secure control of cryptographic credentials.

Finally, banks need to decide whether the efficiency gains justify the cost of integrating new infrastructure into existing systems.

Why IBM's On-Premises Option Matters

IBM also announced an on-premises beta for Digital Asset Haven running on IBM Z and LinuxONE.

The option allows institutions to manage digital assets such as stablecoins and tokenized deposits inside their own data centers rather than depending entirely on public-cloud infrastructure.

For highly regulated institutions, control over infrastructure and cryptographic keys can be an important consideration.

IBM says the on-premises version is designed to provide the same core architecture, APIs and workflows as its existing SaaS and hybrid offerings while keeping the deployment within the client's environment.

This could matter for banks that want to experiment with tokenized assets without moving sensitive digital-asset operations completely into an external cloud environment.

What Does Swift's Blockchain Ledger Actually Change?

The biggest change may not be that banks are suddenly “using crypto.”

Instead, the more significant development is that blockchain-based value transfer is being connected to the infrastructure banks already understand.

That is a different adoption model.

Rather than asking a bank to replace its payment messaging system, its compliance workflows and its operational processes, the new architecture attempts to add a digital-asset layer around those existing systems.

If that approach works at scale, blockchain could become less visible to the end user.

A corporate customer may simply see a faster payment while the underlying infrastructure quietly combines traditional banking systems, standardized messages and distributed-ledger technology.

What Happens Next?

The next important milestone is not another announcement. It is production-scale usage.

The current Swift ledger is moving through early adoption and pilot activity. Seventeen financial institutions are preparing to test live tokenized deposit transactions, while IBM's connection is currently described as a beta capability.

The key questions will be whether banks can move from pilot transactions to sustained commercial use, whether cross-border liquidity can be managed efficiently and whether tokenized deposits deliver measurable advantages over existing payment systems.

If those pieces come together, tokenized deposits could become an important bridge between traditional bank money and blockchain-based financial infrastructure.

Bottom Line

Tokenized bank deposits are not simply another type of cryptocurrency.

They are digital representations of bank deposits that can use distributed-ledger technology to enable new ways of moving and programming bank money.

Swift's blockchain-based ledger is attempting to bring that technology into the existing financial system rather than replacing it outright.

IBM's September 24 integration adds another important layer: banks can use familiar ISO 20022 messaging to instruct tokenized deposit transactions through Swift's shared ledger.

The result is a model where traditional banking infrastructure and blockchain technology can operate together.

Whether this becomes a major part of global payments will depend on what happens after the pilots. But the direction is clear: the next stage of blockchain adoption may not be about replacing banks. It may be about making the existing financial system capable of moving digital value around the clock.

Frequently Asked Questions

What is a tokenized bank deposit?

A tokenized bank deposit is a digital representation of a bank deposit that can be recorded and transferred using distributed-ledger technology. The underlying claim remains connected to the issuing bank.

Are tokenized deposits the same as stablecoins?

No. Tokenized deposits represent bank deposits, while stablecoins are separately issued digital assets backed according to the structure of their respective issuers.

What is Swift's blockchain ledger?

It is Swift's blockchain-based shared ledger infrastructure designed to support regulated digital-asset transactions, including 24/7 cross-border payments using tokenized deposits.

What does IBM have to do with Swift's blockchain ledger?

IBM announced a beta connection between Digital Asset Haven and Swift's blockchain-based shared ledger. Its ISO 20022 Messaging Adapter allows participating institutions to instruct tokenized deposit transactions using standard financial messages.

Does Swift's blockchain ledger replace traditional banks?

No. The system is designed for participating financial institutions and is intended to work alongside existing banking, compliance and settlement infrastructure.

Can tokenized bank deposits move 24/7?

Swift says its ledger is designed to support 24/7 cross-border payment availability using tokenized deposits. However, digital movement on the ledger should not be confused with every underlying final-settlement process becoming instant.

How many banks are participating in Swift's tokenized deposit pilot?

Swift announced in July 2026 that 17 banks from six continents were preparing to pilot live transactions using tokenized deposits.

Why is ISO 20022 important for tokenized deposits?

ISO 20022 provides standardized financial messaging. Connecting tokenized deposit transactions to that standard can allow banks to use existing payment processes rather than building completely separate blockchain-specific messaging workflows.

Sources

Disclaimer: This article is for informational and educational purposes only. It is not financial, investment, legal or banking advice. The Swift ledger and IBM integration include pilot and beta components, so capabilities and implementation details may change as the technology develops.

What Are Tokenized Bank Deposits? How Swift's Blockchain Ledger Could Change Cross-Border Payments