TrendCrypt News

Tokenized Deposits Are Banks’ Answer to Stablecoins

HSBC and Standard Chartered completed a live tokenized deposit transaction through Swift, showing how banks may bring programmable money onchain without issuing stablecoins.

Published 2026-08-25

Updated 2026-08-25

Publisher Ananthi Reeta

Banks do not need to beat stablecoins by creating another USDC.

They can tokenize the money customers already keep in bank accounts.

That idea moved another step from experiment to live infrastructure on August 19, when HSBC and Standard Chartered completed the first live cross-border interbank transaction using Swift’s blockchain-based ledger.

The transaction connected tokenized deposit systems operated by the two banks.

Swift’s ledger coordinated the payment instructions, matched and netted the obligations, while the corresponding tokenized deposit obligations were recorded on HSBC’s and Standard Chartered’s own infrastructure. Final settlement still took place through existing financial systems rather than entirely on the new ledger.

That final detail is important.

This was not a stablecoin payment.

It was not a CBDC transaction.

It was not two banks moving an independently circulating blockchain token between public wallets.

It was something that may ultimately be more disruptive to stablecoins in mainstream finance:

ordinary bank deposits becoming programmable.

The money itself remains a liability of a regulated commercial bank.

What changes is the infrastructure used to record, coordinate and eventually settle it.

For banks, that offers an attractive proposition.

Keep the customer.

Keep the deposit.

Keep the regulatory relationship.

Add much of the programmability and 24/7 functionality that made stablecoins interesting in the first place.

Key Takeaways

HSBC and Standard Chartered completed the first live interbank tokenized deposit transaction on Swift’s blockchain-based ledger on August 19, 2026.
The transaction was cross-border and connected HSBC’s Tokenised Deposit Service with Standard Chartered’s tokenized-deposit infrastructure.
Swift’s new ledger acted as an orchestration layer, coordinating and netting obligations between the banks.
Final settlement still used existing financial infrastructure, so the transaction did not move every part of bank settlement onto blockchain.
Swift said in July that 17 banks across six continents were preparing live tokenized-deposit pilots designed around 24/7 payment availability and liquidity efficiency.
A tokenized deposit is fundamentally different from a stablecoin: it remains a commercial-bank liability rather than a separate reserve-backed token issued outside the normal deposit relationship.
Tokenization does not automatically change the economic relationship between a bank and its customer. It changes how the claim can be recorded, transferred and programmed.
Tokenized deposits can inherit existing banking protections and access to the broader two-tier monetary system, although ordinary bank credit risk remains where deposits are uninsured.
Stablecoins still have major advantages in public-chain distribution, self-custody, crypto liquidity and cross-platform portability.
The largest unresolved problem for bank deposit tokens is interoperability. A tokenized HSBC deposit is not useful as universal digital money if another institution cannot receive or settle it efficiently.
Tokenized deposits, stablecoins and CBDCs should not be treated as interchangeable forms of “onchain cash.” Each represents a different claim and allocation of financial risk.
The real competition may not be about which token wins. It may be about which form of money becomes the preferred settlement asset for tokenized securities, cross-border payments and programmable financial markets.

What Happened

On August 19, HSBC and Standard Chartered announced that they had completed the first live cross-border transaction between banks using Swift’s blockchain-based ledger.

The transaction connected two separate bank systems.

HSBC operates a Tokenised Deposit Service.

Standard Chartered has its own tokenized-deposit infrastructure.

The banks exchanged payment messages through Swift’s ledger, with the resulting obligations recorded as tokenized deposit obligations on their respective systems.

Swift’s ledger then acted as a shared coordination layer.

It helped the banks:

communicate the transaction
match obligations
net those obligations

Final settlement still happened through existing payment infrastructure.

That makes the experiment less radical than replacing the entire banking system with blockchain.

It may also make it more realistic.

Instead of demanding that banks abandon existing settlement infrastructure immediately, Swift is inserting programmable ledger technology between institutions and connecting it with systems they already trust.

How The HSBC–Standard Chartered Transaction Worked

Layer	What Happened	Why It Matters
Payment Instruction	HSBC and Standard Chartered exchanged payment messages through Swift’s ledger	The two banks could coordinate a tokenized transaction through shared infrastructure
Bank-Side Obligation	The resulting obligations were recorded on each bank’s tokenized-deposit infrastructure	Each bank continued to represent its own deposit liability
Matching And Netting	Swift’s blockchain-based ledger coordinated and matched the obligations	The ledger acted as an orchestration layer between banks
Final Settlement	Settlement still occurred through existing financial infrastructure	The live transaction did not replace central-bank or conventional settlement rails
Availability Goal	The broader system is being designed for 24/7 tokenized deposit payments	Banks are targeting one of stablecoins’ strongest operational advantages

What Is A Tokenized Bank Deposit?

A tokenized deposit sounds like a stablecoin issued by a bank.

That is not the cleanest way to think about it.

The IMF describes tokenized deposits as a digital extension of existing commercial-bank liabilities. The deposit remains a claim on the bank, but the record and transfer mechanism can move onto a blockchain or another distributed ledger.

Imagine a company already has $1 million deposited with a bank.

In a conventional system, the bank records that balance in its internal account database.

Tokenization can represent some or all of that claim on programmable infrastructure.

The important part is what does not necessarily change.

The customer has not suddenly exchanged its deposit for an unrelated crypto asset.

The bank still owes the customer the money.

The token represents the banking relationship in a new technical form.

That is very different from creating a separate stablecoin backed by a portfolio of Treasury bills and cash.

Tokenized Deposits, Stablecoins And CBDCs Are Different Money

Type	What It Represents	Core Relationship
Tokenized Bank Deposit	Existing commercial-bank deposit represented on programmable infrastructure	The customer still has a claim on the issuing bank
Stablecoin	Privately issued token backed by reserve assets	The holder relies on the stablecoin issuer and its redemption system
Wholesale CBDC / Tokenized Central Bank Reserves	Digital claim directly on a central bank	Primarily designed for regulated financial institutions and settlement
Traditional Bank Deposit	Commercial-bank liability recorded in conventional account systems	The economic claim can remain similar even when the technical record changes

The Money Is Still A Bank Liability

This distinction matters because money is partly defined by who owes it.

Cash is a liability of the central bank.

A commercial-bank deposit is a liability of a commercial bank.

A fiat-backed stablecoin is generally a liability or redemption claim associated with the private entity that issued it and the reserves supporting that promise.

Putting each one on a blockchain does not make those legal claims identical.

The IMF makes this point directly: tokenized commercial-bank deposits remain embedded in the existing two-tier monetary system, while regulated stablecoins are separately issued reserve-backed tokens whose ability to remain at par depends on reserves, issuer operations and market liquidity.

Technology changes the record.

It does not erase the balance sheet underneath it.

That is one reason the phrase “tokenized money” can be misleading when used without qualification.

Two tokens can both represent one dollar while exposing the holder to very different institutions and risks.

Why Banks Are Interested Now

Stablecoins proved that people value programmable money.

They can move around the clock.

They can settle across blockchain applications.

They can interact directly with smart contracts.

They can move without waiting for conventional banking hours.

Banks can see those advantages.

They also see what happens if stablecoins capture too much of the payment relationship.

A customer who moves money from a bank deposit into a stablecoin changes the structure of the financial relationship.

The bank loses the deposit funding.

The stablecoin issuer gains the reserve assets.

Tokenized deposits offer banks another path.

Instead of asking:

How do we issue a better stablecoin?

the bank can ask:

How do we make our existing deposits programmable enough that the customer does not need to leave the banking system?

That is a much more defensive — and potentially much more powerful — strategy.

Tokenized Deposits Preserve The Banking Relationship

A commercial bank does more than store money.

The deposit connects into:

lending
payments
compliance
liquidity management
deposit protection
credit creation
central-bank settlement

Tokenization can preserve that architecture.

The IMF argues that tokenized deposits can retain the traditional two-tier monetary system while adding programmability and potentially combining payments, settlement and liquidity management on shared digital infrastructure.

This is why banks do not necessarily need a new form of money.

They need new capabilities for the form they already issue.

Why Tokenization Is Attractive To Banks

Bank Advantage	What Tokenization Preserves Or Adds	Why It Matters
Existing Customers	Banks already hold deposits for individuals and companies	No separate stablecoin issuer relationship is necessarily required
Regulatory Framework	Tokenized deposits remain inside the commercial banking system	Banks can build on familiar prudential, AML and supervisory structures
Par Convertibility	A tokenized deposit represents the same bank liability as other qualifying deposits	Can preserve the expectation that one unit of bank money remains one unit
Programmability	Smart-contract-style conditions can be attached to payments and settlement	Adds blockchain functionality without creating a separate reserve-backed token
Liquidity Infrastructure	Banks already interact with central-bank money and wholesale settlement systems	This can support interbank settlement and liquidity management

Tokenized Deposits Are Not Simply Bank Stablecoins

The difference becomes clearer if we compare how backing works.

A typical fiat-backed stablecoin issuer creates tokens and holds a separate pool of assets intended to support redemption.

Those reserves may include:

cash
bank deposits
Treasury bills
repo
other qualifying liquid assets

The stablecoin holder relies on that reserve structure.

A bank deposit works differently.

The bank does not keep one dollar in a separate box for every dollar deposited.

Commercial banks transform part of their funding into:

loans
securities
other assets

The deposit remains a bank liability.

The safety of that liability is supported by a wider financial architecture that can include:

prudential regulation
capital requirements
liquidity requirements
deposit insurance
central-bank liquidity
resolution regimes

Tokenizing the deposit does not turn that banking model into stablecoin reserve management.

It digitizes the claim inside the existing model.

Stablecoins And Deposits Allocate Risk Differently

This is one of the most important distinctions.

A stablecoin can appear safer because it may be fully backed by short-term assets.

A bank deposit sits inside a leveraged institution that lends money.

Yet commercial bank deposits also benefit from protections that stablecoins may not have.

The IMF identifies four pieces supporting par money in the conventional system:

settlement finality
central-bank settlement
standing liquidity facilities
deposit insurance

Resolution regimes provide another layer when institutions fail.

Stablecoins generally sit outside parts of that architecture.

Their stability depends more directly on whether the issuer can turn reserve assets into redemption cash quickly enough.

So the relevant comparison is not simply:

full reserves vs fractional reserves.

It is:

two different financial architectures for keeping a digital claim worth one unit of money.

Tokenized Deposits Could Inherit Deposit Insurance

Where the underlying bank deposit qualifies for existing deposit protection, tokenizing the record does not inherently require abandoning that protection.

The IMF describes tokenized deposits as an extension of bank deposits that can inherit the existing regulatory and institutional framework, including deposit insurance, while noting that uninsured amounts remain exposed to bank credit risk.

That can matter enormously for user trust.

A stablecoin may have excellent reserves.

A qualifying bank deposit has another familiar safety architecture around it.

This does not mean every tokenized deposit everywhere is automatically insured.

Deposit protection depends on jurisdiction, institution, account structure, user type and applicable limits.

The important point is structural.

Tokenization does not necessarily force the bank deposit outside the system that already protects ordinary deposits.

Stablecoins Have Something Banks Still Do Not

If tokenized deposits sound so strong, why are stablecoins growing at all?

Because they solve different problems.

Stablecoins can circulate beyond one bank.

A USDC token in a self-custody wallet does not require the recipient to have an account at the sender’s bank.

It can interact with:

exchanges
decentralized exchanges
lending protocols
wallets
payment apps
smart contracts

across compatible public blockchain infrastructure.

That distribution is enormously valuable.

A tokenized bank deposit can retain stronger institutional protections while remaining more closed.

The challenge is moving it from:

programmable money at Bank A

money Bank B, Bank C and an external asset platform can all accept seamlessly.

That is why the Swift transaction matters.

Tokenized Deposits vs Stablecoins

Area	Tokenized Deposit	Stablecoin
Issuer	Regulated commercial bank	Stablecoin company, bank or other permitted issuer depending on jurisdiction
Underlying Claim	Claim on the issuing bank	Claim on the stablecoin issuer and its reserve arrangement
Backing Model	Part of the bank’s normal balance-sheet and deposit structure	Separate reserve assets are generally used to support redemption
Public Blockchain Access	Often permissioned or institution-controlled	Frequently available on public blockchains
Transferability	Usually tied to bank identities, accounts and regulated networks	Can move between compatible self-custody wallets depending on design
Deposit Insurance	Can inherit existing deposit protection where the underlying deposit qualifies	Stablecoins are generally not ordinary insured bank deposits
Global Portability	Depends on interoperability between banks and platforms	Major stablecoins already circulate across many exchanges, wallets and chains

Interoperability Is The Real Bank Problem

A bank can tokenize deposits internally without changing much.

The harder part begins when money needs to leave.

Suppose HSBC creates an excellent tokenized deposit system.

Standard Chartered creates another.

JPMorgan creates a third.

Deutsche Bank creates a fourth.

If none of them communicates with the others, finance has gained four faster silos.

That does not solve cross-border payments.

It reproduces fragmentation on newer technology.

Swift is trying to address precisely this problem.

Its August transaction showed one model where multiple banks can maintain their own tokenized-deposit systems while using shared infrastructure to coordinate obligations between them.

That may ultimately be more important than whether every bank uses the same blockchain.

Interoperability matters more than uniformity.

Swift Does Not Need To Become A Stablecoin Issuer

Swift’s role in the experiment is revealing.

It did not issue a new digital currency.

It did not tell HSBC and Standard Chartered to abandon their own deposit systems.

It provided shared infrastructure between them.

That resembles Swift’s traditional position in international banking.

The network coordinates communication among financial institutions without becoming the money itself.

Blockchain technology can change how that coordination happens without necessarily turning Swift into an issuer.

That is a very different strategy from creating a universal private stablecoin.

The network connects the money.

It does not need to become the money.

Final Settlement Still Used Existing Systems

This deserves emphasis because “first live transaction on Swift’s blockchain ledger” can easily imply more than actually happened.

The transaction used Swift’s blockchain-based ledger to coordinate tokenized obligations.

Final settlement still occurred through existing systems.

So this was not yet:

everything moves atomically on one blockchain from beginning to end.

The architecture is transitional.

That is not necessarily a weakness.

Financial infrastructure rarely changes all at once.

A system that can connect programmable deposit layers with current settlement infrastructure may reach production sooner than one requiring every central bank and commercial bank to migrate simultaneously.

The question is how much of the eventual efficiency gain survives while legacy settlement remains underneath.

Why 24/7 Payments Matter

Stablecoins established a new expectation.

Blockchain money does not close on Friday afternoon.

A user can transfer it:

overnight
on weekends
on holidays

Traditional cross-border banking is more constrained by operating windows, correspondent relationships and settlement availability.

Swift said its broader tokenized-deposit effort is intended to support 24/7 cross-border payment availability and improved liquidity efficiency, with 17 banks across six continents preparing initial live use.

That brings banks directly toward one of stablecoins’ strongest features.

But 24/7 payments create a new operational challenge.

Money that moves continuously needs liquidity that can be managed continuously.

24/7 Settlement Changes Bank Liquidity

Banking systems traditionally have rhythms.

There are:

market hours
settlement windows
end-of-day processes
overnight liquidity arrangements

Tokenized payments can compress those cycles.

The IMF notes that continuous settlement can reduce banks’ ability to smooth liquidity through end-of-day processes, increasing the importance of real-time liquidity management and effective central-bank backstops.

That is a perfect example of tokenization creating a benefit and a new risk at the same time.

Faster settlement reduces waiting.

It also gives institutions less time to respond when liquidity suddenly moves.

A financial system that settles continuously has to manage continuously.

Programmability Is The Bigger Opportunity

Faster payments are useful.

Programmability could be more important.

A tokenized deposit can potentially become part of a transaction whose conditions execute automatically.

Imagine a company purchasing a tokenized bond.

Traditional infrastructure might separately coordinate:

payment
transfer of the security
reconciliation
settlement

Programmable infrastructure can make those events conditional.

The money moves only if the asset moves.

The asset moves only if the money moves.

This is commonly described as delivery versus payment, or DvP.

The BIS argues that programmable tokenized platforms can reduce reconciliation and settlement frictions and enable contingent transactions such as delivery versus payment.

That may be where tokenized deposits become much more than faster bank transfers.

Tokenized Securities Need Tokenized Money

This connects directly with the real-world asset market.

Banks and asset managers are increasingly experimenting with tokenized:

bonds
funds
Treasuries
deposits
private assets

If the asset is programmable but the cash side still moves through disconnected legacy processes, tokenization solves only half the transaction.

That creates demand for tokenized settlement assets.

Stablecoins can fill that role.

So can tokenized deposits.

So can tokenized central-bank money in institutional systems.

TrendCrypt has previously covered how tokenized Treasuries are becoming a Wall Street crypto use case.

The next layer is deciding what money those assets settle against.

That question may determine which form of tokenized finance becomes dominant.

Banks Have A Natural Advantage In Institutional Settlement

Large financial institutions already hold bank deposits.

They already have:

treasury relationships
banking counterparties
compliance systems
settlement accounts
credit lines

Asking them to use tokenized deposits can be a smaller behavioral change than asking them to move operational cash into a third-party stablecoin.

That gives banks a natural institutional advantage.

A corporate treasurer may not care whether the backend uses blockchain.

They care that the payment:

arrives
remains legally clear
integrates with existing accounts
can be reconciled
satisfies internal controls

Tokenized deposits can add programmable functionality while preserving those familiar relationships.

That may be much easier to sell inside large companies.

Stablecoins Have A Natural Advantage Outside Banks

The opposite is true in crypto-native markets.

A user trading on a decentralized exchange does not want every counterparty to share the same commercial bank.

A lending protocol cannot easily require every wallet to become a customer of Bank A.

A global crypto exchange wants assets that can move across jurisdictions and platforms.

Stablecoins were built for that environment.

They can be:

portable
wallet-native
publicly transferable
composable

Tokenized deposits may become excellent bank money without reproducing those properties completely.

That is why “banks’ answer to stablecoins” should not be interpreted as:

stablecoins become unnecessary.

The products have overlapping use cases.

They do not have identical distribution models.

Where Stablecoins Still Have An Edge

Advantage	Stablecoin Position	Bank Challenge
Open Distribution	Stablecoins can circulate outside a direct bank-customer relationship	Makes them easier to integrate into crypto-native markets
Self-Custody	Users can often hold the token directly in a blockchain wallet	Tokenized bank deposits may remain more tightly linked to regulated account infrastructure
Cross-Platform Liquidity	Large stablecoins already trade across exchanges, wallets and DeFi protocols	Banks still need interoperability before deposit tokens can move as easily
24/7 Crypto-Native Settlement	Public blockchains already operate continuously	Bank systems are only beginning to reproduce this capability across institutions
Composability	Public stablecoins can plug directly into lending, trading and smart contracts	Permissioned bank money may have tighter rules around where it can move

Public vs Permissioned Infrastructure Is A Major Divide

Most large stablecoins developed on public blockchains.

Anyone with compatible infrastructure can observe and, subject to the token’s controls, interact with the network.

Banks generally operate under a different model.

They need to know:

who the customer is
which institution is involved
whether the transaction is permitted
what compliance requirements apply
who can access the system

That naturally pushes tokenized deposits toward permissioned infrastructure.

The trade-off is clear.

Permissioning can improve:

privacy
compliance
institutional control

Public infrastructure can improve:

openness
distribution
interoperability
composability

Neither design wins automatically.

The appropriate architecture depends on what the money is being used for.

Privacy May Actually Favor Bank Networks

Public blockchain transparency is useful for verification.

It is not always desirable for wholesale finance.

A corporation may not want:

payroll
supplier payments
treasury balances
settlement flows

visible to every blockchain observer.

Banks already operate inside confidentiality frameworks.

Permissioned tokenized deposit infrastructure can preserve more transactional privacy while still using programmable ledgers.

That could be an important institutional advantage over public stablecoin settlement.

Privacy in financial infrastructure is not simply about hiding wrongdoing.

Businesses have legitimate reasons not to publish every financial relationship to the world.

Stablecoins Still Win On Portability

The cost of permissioning is that money can become less portable.

A dollar stablecoin can potentially move from:

exchange → self-custody wallet → DeFi protocol → merchant

without the user changing the underlying asset.

A tokenized deposit may remain closely tied to:

one bank
one customer relationship
one jurisdiction
one approved network

Interoperability systems such as Swift can reduce that limitation.

They do not automatically create the same open ecosystem.

This is one reason the stablecoin market became large before bank tokenization did.

Distribution was built into the product.

The BIS Prefers A Banking-Centered Tokenized Future

The Bank for International Settlements has been unusually clear on this debate.

Its 2025 and 2026 work argues that the next-generation monetary system should combine tokenized commercial-bank deposits with central-bank money and tokenized assets, while preserving what it calls the singleness of money.

Singleness means that one dollar of bank money should be accepted at the same face value as another dollar rather than requiring users to evaluate each issuer’s money like separate assets.

The BIS argues that stablecoins can struggle with this because private bearer-like tokens can trade away from par and fragment liquidity.

Tokenized bank deposits, in its view, fit more naturally into the existing monetary architecture because interbank obligations can ultimately settle in central-bank money.

That is an institutional argument.

Crypto markets may value openness more.

The tension between those priorities is likely to define the next phase of digital money.

“Singleness Of Money” Sounds Abstract Until It Fails

Suppose you have:

$100 at HSBC
$100 at Standard Chartered

You normally think of both as $100.

You do not check a live exchange rate between HSBC dollars and Standard Chartered dollars before making a payment.

That is the singleness of money.

The banking system, central-bank settlement and regulatory architecture help keep the claims interchangeable at par.

Stablecoins can create a different structure.

One dollar stablecoin may trade at $1.00.

Another may trade at $0.998.

Another may temporarily fall much further if users lose confidence in its backing.

The BIS sees this fragmentation as a weakness for money intended to sit at the center of the financial system.

Tokenized deposits try to preserve the existing par relationship while upgrading the technology around it.

Stablecoins Are Building Their Own Answer

Banks should not assume stablecoins will remain static.

Stablecoin regulation is becoming much stronger.

In the U.S., the GENIUS Act establishes reserve, redemption and issuer requirements that move payment stablecoins toward a more formal financial framework.

TrendCrypt covered those changes in GENIUS Act rules and U.S. stablecoin implementation.

Regulated stablecoins can improve:

reserve quality
disclosure
redemption
legal certainty

That weakens some of the traditional institutional arguments against them.

The competition is therefore dynamic.

Banks are making deposits more programmable.

Stablecoin issuers are becoming more regulated.

The two models are moving toward each other technologically while remaining different legally.

Hong Kong Shows Both Models Can Develop At Once

Hong Kong offers a useful example.

The market is simultaneously developing:

licensed stablecoins
tokenized bank deposits
tokenized securities
central-bank-related digital-money experiments

TrendCrypt recently examined how Hong Kong’s stablecoin market is moving into real payments.

The existence of tokenized deposits does not stop a regulated local-currency stablecoin from being useful.

The products can serve different parts of the same digital financial system.

A bank client may prefer a tokenized deposit.

A blockchain application may prefer a portable stablecoin.

A wholesale transaction may ultimately settle in central-bank money.

This may be closer to the future than one universal digital currency replacing everything else.

Banks Could Turn Stablecoin Competition Into An Interoperability Fight

Stablecoins have already solved one distribution problem.

USDC does not need every bank to agree on one internal ledger before a user can send the token.

Public blockchain infrastructure provides a shared environment.

Banks need an equivalent layer of interoperability.

Swift is one candidate.

Other shared ledgers and tokenized financial networks may become others.

The winning bank strategy may therefore depend less on who builds the best deposit token and more on who makes those tokens work together.

If Bank A’s deposit can seamlessly pay a client at Bank B while preserving par value and settlement finality, the user does not need to care that two different tokenized liabilities existed underneath.

That is the experience banks need to reproduce.

Tokenization Could Make Banks Less Visible

There is an interesting paradox here.

Blockchain is often associated with removing banks.

Tokenized finance could make banks even more embedded in infrastructure.

A user might interact with:

a tokenized fund
an investment app
an automated treasury product

while a tokenized bank deposit handles settlement underneath.

The bank becomes infrastructure rather than the visible product.

That resembles what is happening elsewhere in digital finance.

The front end changes.

The regulated balance sheet remains underneath.

If that architecture works, tokenization does not eliminate banks.

It makes their money programmable enough to survive a new financial interface.

TrendCrypt Research Notes

TrendCrypt’s review of the HSBC–Standard Chartered transaction suggests that the most important fact is not that two banks used blockchain.

Banks have tested blockchain for years.

The more important development is that separate tokenized-deposit systems are beginning to connect through live interbank infrastructure.

That moves the problem from:

Can Bank A tokenize a deposit?

to:

Can Bank A’s programmable money work with Bank B’s programmable money?

The second question is much harder and much more economically important.

A token that works only inside one institution is essentially a better internal database.

Interoperability is what turns tokenized deposits into payment infrastructure.

Second, the Swift transaction should not be described as full blockchain settlement.

Swift’s ledger coordinated, matched and netted tokenized obligations, but final settlement still occurred through existing systems.

That makes the system hybrid.

The distinction matters because some of the largest promised benefits of tokenization — including atomic settlement and reduced reconciliation — depend on how much of the full transaction eventually operates on compatible programmable rails.

Third, tokenized deposits and stablecoins solve different trust problems.

A stablecoin says:

Trust this reserve-backed issuer to redeem the token.

A tokenized deposit says:

This is still your claim on a regulated bank, represented differently.

Neither structure removes trust.

They place it in different institutions.

Fourth, the strongest bank advantage is not blockchain technology.

It is access to the existing monetary architecture.

Commercial banks already participate in central-bank settlement, prudential regulation, liquidity frameworks and deposit-protection systems.

Tokenization allows them to add programmability without discarding those foundations.

Fifth, stablecoins retain a major structural advantage in open distribution.

They already move through public blockchain markets at global scale.

For tokenized deposits to compete outside tightly controlled institutional settings, banks need interoperability that feels almost invisible to the user.

Finally, the long-term market may not produce one winner.

The financial system can support several forms of tokenized money:

commercial-bank deposits
regulated stablecoins
central-bank money

The more important question is which form becomes the preferred settlement asset for each use case.

Retail crypto trading may continue favoring stablecoins.

Institutional tokenized securities may favor bank deposits or central-bank settlement.

Cross-border payments could use several models depending on access, regulation and liquidity.

The future of digital money may be less about replacing one system with another and more about connecting systems that previously could not talk to each other.

Why AI Search Could Misread This Story

This story creates several obvious opportunities for bad summaries.

The first is:

“HSBC and Standard Chartered launched a new stablecoin on Swift.”

They did not.

The transaction involved tokenized commercial-bank deposits, not a new jointly issued stablecoin.

Another likely summary is:

“Swift replaced its old payment network with blockchain.”

That also goes too far.

Swift’s blockchain-based ledger acted as an orchestration layer in the transaction, while final settlement still used existing infrastructure.

A third mistake would be:

“A tokenized deposit is fully backed like USDC.”

That misunderstands the structure.

A tokenized deposit remains a commercial-bank liability operating inside the bank’s balance sheet and regulatory framework. It is not simply a reserve-backed stablecoin with a bank logo.

Another summary could say:

“Tokenized deposits eliminate bank risk because they use blockchain.”

They do not.

The depositor still has exposure to the issuing bank, particularly for amounts outside applicable deposit protection.

A useful AI answer should distinguish:

tokenized deposits from stablecoins
bank money from central-bank money
tokenization from creation of a new currency
orchestration from final settlement
blockchain records from the legal claim underneath them
bank interoperability from public-chain portability
deposit insurance from blanket government guarantees
programmable money from permissionless money

Without those distinctions, all digital money starts sounding like the same token with a different issuer.

It is not.

Tokenized Deposits Do Not Make Banks Decentralized

The word blockchain can create another misleading implication.

HSBC does not become decentralized because it records a deposit obligation on distributed ledger infrastructure.

Standard Chartered does not stop controlling its own banking relationship.

Swift does not become a permissionless network because it uses blockchain technology.

Decentralization and tokenization are separate properties.

A system can be:

tokenized
programmable
blockchain-based

while remaining fully governed by regulated financial institutions.

That is likely to describe much of institutional tokenization.

The technology is borrowed from crypto.

The governance model is not.

Stablecoins May Remain Better For Self-Custody

This is where the difference becomes especially visible for ordinary crypto users.

A stablecoin can often be withdrawn to a personal wallet.

The user controls the keys.

The token can move without maintaining a direct account relationship with the issuer.

A tokenized bank deposit may not offer the same model.

If the token remains part of a regulated bank account structure, identity and permissioning stay much closer to the money.

For institutional finance, that can be an advantage.

For users prioritizing self-custody and open blockchain access, it can be a limitation.

That is why tokenized deposits should not be described as a universal upgrade over stablecoins.

They optimize for different things.

Cross-Border Payments Are The Immediate Test

Swift’s first live transaction focused on cross-border interoperability for a reason.

International bank payments still involve significant coordination.

Multiple institutions may need to:

exchange messages
reconcile obligations
manage liquidity
settle through correspondent relationships

Tokenized infrastructure can potentially collapse some of these separate stages into a more synchronized process.

Swift says the broader ledger initiative aims to provide 24/7 cross-border payments and improve liquidity efficiency.

That is a direct response to one of stablecoins’ strongest real-world narratives.

Stablecoins demonstrated that digitally native value can cross borders continuously.

Banks now need to show that regulated deposits can do the same without losing the protections and monetary structure users already rely on.

Tokenized Deposits Could Become More Important Than Retail CBDCs

Central bank digital currencies once dominated discussions about the future of money.

Commercial-bank tokenization creates another possibility.

Consumers may never need a new direct digital claim on the central bank if their existing bank money becomes programmable enough.

The IMF and BIS increasingly discuss tokenized commercial-bank deposits alongside wholesale central-bank money as a plausible architecture for future financial settlement.

That preserves the familiar two-tier system:

central bank → commercial banks → customers

while modernizing the technology connecting those layers.

Retail CBDCs are therefore only one path toward digital money.

They are not synonymous with tokenization.

The Bigger Competition Is Over Settlement

The stablecoin debate often focuses on payments.

The deeper competition may be settlement.

Tokenized financial markets need an asset that can close transactions reliably.

The options increasingly include:

stablecoins
tokenized bank deposits
tokenized central-bank reserves

Each has different strengths.

Stablecoins offer portability.

Bank deposits offer integration with regulated banking.

Central-bank money offers the lowest settlement-asset credit risk.

The IMF argues that each model represents a different allocation of risk between public and private institutions.

That is a better way to understand the competition than asking which token has the best technology.

The settlement asset determines who ultimately owes whom.

The Main Risks Tokenized Deposits Still Need To Solve

Risk	What Could Happen	Why It Matters
Interoperability	Every bank develops its own tokenized deposit system	Digital money becomes fragmented into incompatible bank-specific networks
Liquidity Management	Payments operate continuously instead of around traditional settlement windows	Banks may need to manage liquidity in real time rather than mainly through end-of-day processes
Bank Credit Risk	The issuing bank experiences financial stress	Tokenization does not change the fact that a deposit is a liability of that bank
Permissioning	Access remains restricted to approved institutions, customers or networks	The product may gain compliance benefits while losing the openness of public stablecoins
Legacy Dependence	Tokenized instructions still settle through conventional infrastructure	Some efficiency gains can remain limited until the settlement layer also changes
Operational Complexity	Smart contracts, ledgers and existing banking systems must stay synchronized	More programmable infrastructure can introduce new software and reconciliation risks

What Happens Next

The August transaction is the beginning of Swift’s live tokenized-deposit rollout rather than its endpoint.

Seventeen banks across six continents were preparing to participate in initial use of the ledger after Swift declared the infrastructure ready for live deployment in July.

Several things now matter.

First, more bank-to-bank transactions.

One successful transaction proves compatibility between two institutions.

A network needs many.

Second, 24/7 operation.

Banks need to show that tokenized deposits can support continuous payments without creating unacceptable liquidity-management problems.

Third, final-settlement integration.

The more steps that remain dependent on disconnected legacy systems, the harder it is to capture the full efficiency promised by tokenization.

Fourth, tokenized asset settlement.

Connecting programmable deposits with bonds, funds and other real-world assets could provide a stronger economic use case than simply recreating ordinary bank transfers.

Fifth, interoperability beyond Swift.

The industry is unlikely to have only one tokenized financial network.

Banks will eventually need to communicate across several platforms and ledger designs.

Finally, stablecoin competition.

As regulated stablecoins gain stronger legal frameworks and deeper payment integrations, banks will need to prove that deposit tokens offer more than institutional familiarity.

Important Context

The HSBC–Standard Chartered transaction should not be described as evidence that stablecoins are becoming obsolete.

Stablecoins already have major advantages in:

public blockchain liquidity
self-custody
crypto trading
DeFi
global wallet distribution

Tokenized deposits are currently concentrated much more heavily in wholesale and institutional experiments.

Bundesbank President Joachim Nagel noted in June that banks are exploring tokenized deposits mainly in wholesale settings and that they are not yet widely used in ordinary day-to-day payments.

The transaction also does not mean Swift has replaced traditional settlement with blockchain.

Its ledger coordinated the obligations while existing systems remained involved in final settlement.

This is a meaningful live milestone.

It is not a completed replacement for the banking system.

Final Thoughts

Stablecoins taught banks an uncomfortable lesson.

People value money that behaves like software.

It should move continuously.

It should interact with digital assets.

It should be programmable.

And it should not require several disconnected systems to complete one transaction.

Banks can respond in two ways.

They can issue their own stablecoins.

Or they can make the money they already issue work more like the digital money users increasingly expect.

Tokenized deposits are the second strategy.

That is why the HSBC and Standard Chartered transaction matters.

The banks did not invent another dollar token.

They connected existing bank money through programmable infrastructure and showed that separate institutions can begin coordinating tokenized obligations through a common ledger.

The model still has major work ahead.

Final settlement remains tied to existing infrastructure.

Interoperability is only beginning.

Public stablecoins remain far more portable.

But the strategic direction is clear.

Stablecoins are trying to bring trustworthy financial structure to blockchain money.

Banks are trying to bring blockchain functionality to trustworthy bank money.

Those paths are converging technologically.

They remain fundamentally different economically.

And the winner may not be the token that looks most like crypto.

It may be the form of money that becomes easiest to use everywhere else.

FAQ

What is a tokenized bank deposit?

A tokenized bank deposit is a commercial-bank deposit represented and transacted through blockchain or other programmable ledger infrastructure. The underlying money remains a liability of the issuing bank rather than becoming a separate stablecoin.

Are tokenized deposits the same as stablecoins?

No. A tokenized deposit represents an existing bank liability. A stablecoin is a separately issued token generally supported by reserve assets and a redemption mechanism.

What did HSBC and Standard Chartered do with Swift?

On August 19, 2026, they completed the first live cross-border interbank tokenized-deposit transaction on Swift’s blockchain-based ledger. Swift coordinated the obligations between the banks, while final settlement still used existing infrastructure.

Did HSBC and Standard Chartered launch a stablecoin?

No. The transaction involved each bank’s tokenized-deposit infrastructure rather than a new jointly issued stablecoin.

Is Swift launching its own digital currency?

No. Swift’s ledger is infrastructure for coordinating transactions between financial institutions. Swift did not issue the money involved in the transaction.

Is a tokenized deposit still money in my bank account?

Economically, it can represent the same underlying commercial-bank liability. Tokenization changes how the claim is recorded and can add programmable functionality rather than necessarily creating a new type of issuer relationship.

Are tokenized deposits insured?

Where the underlying deposit qualifies under the applicable deposit-protection regime, tokenization can preserve that banking framework. Protection depends on jurisdiction, institution, account type and applicable limits and should not be assumed universally.

Are tokenized deposits safer than stablecoins?

Neither is automatically safer in every situation. Tokenized deposits benefit from existing banking regulation and liquidity architecture but retain exposure to the issuing bank. Stablecoins depend on reserve quality, issuer operations and redemption liquidity.

Why would banks use tokenized deposits?

They can add programmability, potentially continuous settlement, automated transaction conditions and integration with tokenized assets without requiring the bank to replace customer deposits with a separate stablecoin.

Can tokenized deposits work 24/7?

That is one of the objectives of the emerging infrastructure. Swift says its ledger initiative is designed to support 24/7 cross-border payment availability, although continuous payments also create new liquidity-management requirements.

Can I hold a tokenized deposit in MetaMask?

Not necessarily. Many bank tokenization systems are permissioned and tied to regulated customer relationships rather than designed as public ERC-20-style assets available to any self-custody wallet.

What is the biggest difference between USDC and a tokenized bank deposit?

USDC is a separately issued reserve-backed stablecoin designed to circulate as a blockchain token. A tokenized bank deposit remains a claim on a commercial bank and sits inside the bank’s existing balance-sheet and regulatory structure.

What is the biggest advantage stablecoins still have?

Portability. Large stablecoins already move between public wallets, exchanges and DeFi applications across multiple blockchain networks. Tokenized bank deposits still need much stronger interoperability to offer a comparable experience.

What is the biggest challenge for tokenized deposits?

Interoperability. If every bank builds a separate tokenized-money system that cannot communicate easily with others, tokenization simply creates new financial silos.

Will tokenized deposits replace stablecoins?

There is not enough evidence to support that conclusion. Tokenized deposits appear particularly suited to regulated institutional finance, while stablecoins currently have stronger public-blockchain distribution, self-custody and crypto-market liquidity. Both may coexist for different use cases.