SWIFT launches stablecoin alternative: based on bank currency rather than cryptocurrency

,

, and

tags, and is suitable for direct use in content display.

The network that drives global capital flows took nine months to build a blockchain, and the most important decision it made was to clarify what should not be linked-no stablecoins, no public tokens, only bank deposits in a new coat.

Summary

On July 9, 2026, SWIFT and 17 major banks including Citigroup, HSBC, UBS, and BNP Paribas jointly launched a blockchain-based shared ledger for round-the-clock cross-border payments, using tokenized deposits.

The ledger is based on the Hyperledger Besu architecture compatible with the Ethereum virtual machine. It was completed within 9 months with the assistance of Consensus and is publicly positioned as the banking industry's response to the US$315 billion stablecoin market.

The key decision is the tool used. SWIFT is built for tokenized deposits, not stablecoins. This difference determines who controls the money, whether the money is insured, and whether it is used for lending.

Tokenized deposits retain funds on the bank's balance sheet, enjoy deposit insurance, and maintain credit creation. Stable coins draw funds out of reserves, float outside the banking system, and draw liquidity.

This is a structural shift for SWIFT: for the first time in 53 years, it has transformed from a pure messaging network with no access to funds to an active coordinator of value flows.

For 53 years, SWIFT has only done one thing: delivering messages. When a bank in Singapore makes a payment to a bank in Sao Paulo, SWIFT conveys instructions, not funds. It is the postal service of global finance and never opens envelopes.

On July 9, 2026, all this changed. SWIFT has launched a blockchain-based shared ledger with the world's 17 largest banks to coordinate the flow of value, not just news about value, for the first time in its history. The financial media reported this release as a technical story, and it did.

But the more important story lies behind it: SWIFT built the system to carry tokenized deposits, explicitly avoiding stablecoins. The decision indicates who the banking system intends to issue digital currency. This article aims to explore this choice, its importance, and who it excludes.

What did SWIFT actually launch?

Let's first look at the facts because they are specific and verified by SWIFT's official releases and independent reports.

On July 9, 2026, SWIFT announced that its blockchain-based shared ledger is ready for initial use, and 17 banks from six continents are preparing to pilot real-time transactions. The list is like a global bank directory: ANZ Bank, BNP Paribas, Bank of New York Mellon, Citibank, DBS Bank, First Bank of Abu Dhabi, First Rand Bank, HSBC, Itau United Bank, Lloyd's Bank, Masliger Bank, Mitsubishi UFJ Financial Group, Overseas Chinese Bank, Standard Chartered Bank, UBS, UOB Bank and Wells Fargo. The system took only nine months from announcement to preparation for production. It was developed with the participation of global financial institutions. According to multiple reports, Consensus sys also participated in the construction.

Technically, the ledger uses a Hyperledger Besu-based compatible Ethereum virtual machine architecture to serve as a shared coordination layer that verifies interbank payment commitments while retaining existing compliance, credit, risk and control standards. The purpose is specific and clear: to enable cross-border payments around the clock, including nights and weekends, which existing infrastructure cannot support due to its reliance on overlapping business hours for senders and recipients. Final settlement will still occur through the existing payment track. This ledger does not replace the agency bank relationship, but coordinates on top of it.

SWIFT's chief business officer sees the move as extending the trust and stability of the existing financial system to the forefront of digital currencies. This sentence is the company's official statement, but it is also very accurate. The whole design is about carrying the old thing-bank money-on top of the new thing-shared ledgers-without abandoning the control mechanisms that define bank money.

The choices that define it all

Here is a decision that is more important than the technology itself, and most published reports only mention it briefly: SWIFT was built for tokenized deposits, not stablecoins.

Tokenized deposits are a digital representation of the currency held by a regulated commercial bank, issued by the bank on the blockchain, maintaining a one-to-one relationship with deposits on its balance sheet. It is the currency of commercial banks in a new guise. A stablecoin is a token pegged to legal tender issued by non-bank entities and backed by reserve assets such as treasury bills that are outside the banking system and run on a public blockchain accessible to anyone with a wallet.

They look almost identical. Both dollar-denominated stablecoins and tokenized dollar deposits claim to be worth US$1, are transferred on the blockchain, and are settled within seconds. In a February 2026 staff report, the New York Federal Reserve drew a clear line of structural boundaries beneath superficial similarities: stablecoins convert safe assets into a medium of exchange, while tokenized deposits allow banks to continue to fund loans and support credit creation, only replaced by digital tracks. This is not a technical difference, but a matter of who has the right to create money and what consequences the banking system will face if the answer changes.

SWIFT chose a tool that puts banks at its core. Its official position is that bank-issued tokenized deposits provide a compliant alternative within existing regulatory frameworks, without the risks associated with non-bank stablecoins by certain institutions. To put it more bluntly: SWIFT has built a blockchain that can do what stablecoins can, but runs on tracks that banks already control, so banks don't have to adopt a tool that would exclude them.

Why banks value this difference so much?

This choice is important because stablecoins and tokenized deposits have diametrically opposed effects on banks 'balance sheets and thus on the banking system's ability to lend.

When customers purchase stablecoins, they transfer fiat currency from their bank accounts to the issuer's reserves. The money left the bank and now exists in the form of treasury bills or escrow accounts, supporting the tokens and contributing nothing to credit creation. Expanding the size of this market to a $315 billion market would produce measurable losses: Deposits leaving banks would reduce the money multiplier-the mechanism by which a dollar of deposit supports several dollars of loans. In the language of industry analysis, stablecoins draw liquidity from the banking system.

Tokenized deposits are the opposite. Funds remain on the bank's balance sheet, still count as deposits, and can still be used for loans and investments. Tokens are just a more liquid manifestation of them. As a result, banks that issue tokenized deposits retain funds that would otherwise have been lost to stablecoins, while providing customers with the same round-the-clock programmable settlement. From a bank's perspective, this is the whole goal: to provide the same user experience as stablecoins without sacrificing the deposit base on which lending depends.

Security is also a dimension, and it's not just marketing rhetoric. Tokenized deposits are supported by the bank's capital and the supervisory framework that regulates commercial banks, enjoy deposit insurance within legal limits, and the issuing bank can borrow from the Federal Reserve's loan window, thereby reducing the risk of runs. Stable coins do not have these. According to the GENIUS Act, stablecoins must hold full reserves and disclose them. This is true protection, but the holders of stablecoins are not protected depositors and do not have the central bank as backing them. The analogy for money market funds in 2008 is very pertinent: instruments that look like deposits and are treated as deposits only reveal that they have never been deposits until they fall below face value.

Optimistic outlook for SWIFT's solution

The optimistic interpretation is that SWIFT has done the cool and right thing, and its distribution network has made it the most credible player in the entire tokenized currency race.

coverage argument is indeed difficult to refute. SWIFT connects more than 11000 financial institutions in more than 200 countries. No stablecoin issuer, no crypto-native payment network, and no single banking alliance can match this coverage. If the pilot is successful with 17 banks and multiple currency corridors, the marginal cost of joining the next institution will be low because it is already within the SWIFT network. This is a distribution advantage measured by decades of accumulated membership networks, and distribution is the actual factor in determining payment standards.

The problems SWIFT is solving are also real, not fabricated. On its existing track, SWIFT can already process 75% of payments to collecting banks in 10 minutes, usually in a few seconds, so messaging speed has never been a real bottleneck. The bottleneck is the reliance on overlapping business hours: Asian payments to counterparties in the Americas on Friday night cannot be processed until Monday. Shared ledgers just eliminate this problem, allowing weekend and overnight settlements within regulatory boundaries. This is a precise fix for specific friction, rather than finding a solution to the problem.

Moreover, the model retains what regulators and financial executives really want to retain. Corporate treasurers who for decades processed weekend wire transfers through batch processing systems can now obtain round-the-clock flow of funds without having to step out of the compliance framework required by auditors. Banks retain deposits, and regulators retain supervisory powers. The financial system has gained programmable, round-the-clock settlement capabilities without forming a parallel monetary system outside it. It's a powerful selling point for institutions whose first reaction to any innovation is "What's going to go wrong?"

The pessimistic outlook for SWIFT's proposal

The skepticism interpretation is that SWIFT is defending the existing landscape, with a permission-based bank ledger recreating most of the constraints that stablecoins should be free of, and the market has moved to another model.

Look at the report card first. Stable coins are not a proposal. They already exist in the market, with a supply of more than US$300 billion, a settlement transaction volume of tens of trillions, and have experienced many crypto winters. Most of the tokenized deposits remain in the pilot stage, and SWIFT's own release is clearly an initial pilot rather than a full deployment. One tool has been tested on a large scale, the other is a promising experiment, and the gap between the two is measured in years rather than months. BlackRock's Larry Fink used an impressive analogy in his 2025 letter to investors: If SWIFT were a postal service, tokenization would be email, transferring assets directly and instantly, bypassing middlemen. SWIFT's ledger attempts to make postal services deliver like email while keeping the post office operational.

The deeper limitation lies in the licensing system. SWIFT's ledger is a closed, bank-only system. stablecoins are open: anyone with a wallet can hold and send them without a banking relationship, which is precisely why they have a foothold in cross-border corridors where banks are poorly served or expensive. A financial technology company in Lagos uses USDC to make payments to suppliers in Shenzhen because bank wire transfers cost 6%, which takes four days. SWIFT's ledger is of no help to such users because the user is not a bank on SWIFT. The tokenized deposit model was originally designed to serve those who were already well served by banks, and this was not a disruptive need.

In addition, there is a congestion issue that weakens the coverage argument. SWIFT is not the only banking consortium building such a system. A group including JPMorgan Chase, Bank of America, Barclays and Bank of New York Mellon is building a U.S. -focused tokenized deposit network through clearing houses, with the goal of going online in 2027. JPMorgan Chase already runs Kinexys, is active on Base and Canton, and is processing institutional payments today. If every large bank and consortium builds its own tokenized deposit track, the result will not be a clean stablecoin alternative, but a series of fragmented walled gardens-exactly what SWIFT's shared ledger claims to solve, only to reappear at a higher level.

What does this mean for the stablecoin giant

For TEDA and Circle, the two issuers that dominate the US$315 billion market, the difference is important.

It is not a direct threat because the two tools serve different users. Stablecoins control open, permission-free, retail and crypto corridors: exchange clearing, DeFi collateral, money transfers and a large number of users who lack good banking services. SWIFT's ledgers serve the flow of funds between regulated agencies. In the short term, these are different markets, and the SWIFT pilot will not directly reduce TEDA or Circle's accounts.

It is a signal because it signals that the banking system no longer treats stablecoins as something new, but is beginning to seriously build institutional-level alternatives, backed by the industry's most powerful distribution network.

The competitive question facing stablecoin issuers is whether tokenized deposits will expand to absorb the application scenarios that stablecoin hopes of expanding, especially institutional cross-border clearing and corporate finance-which is exactly what stablecoins are targeting as they move from crypto portals to real business. If banks lock in institutional corridors with protected, compliant tokenized deposits, stablecoins 'growth may be limited to permission-free margins and unable to expand into regulated core areas.

The GENIUS Act complicates the situation. It provides a federal framework and legitimacy for stablecoins, which works in their favor. At the same time, it also opened the door to a model for banks to issue stablecoins and blurred the line between the two instruments by granting OCC trust licenses to Circle, Paxos, Ripple, and others. The possibility for the future is not that one model wins, but convergence: bank-issued stablecoins, tokenized deposits, and non-bank stablecoins coexist, and interesting competition will occur at the border. SWIFT has just planted a flag on the bank side of the border.

Unmentioned three-way competition

The clearest way to see where SWIFT stands is is to stop viewing it as a stablecoin versus banks battle, and start counting the actual competitors, because there are three very different bets on how institutional money flows next, and they cannot all win.

The first is the open stablecoin model: TEDA, Circle and newer alliance efforts such as Open USD. Non-bank issuers, public blockchains, permission-free access, reserves held outside the banking system. The model has the present: it has transaction volume, corridors, and proven product-market fit in areas where banking services are poor. Its weaknesses lie at the regulatory and structural levels: it draws deposits from banks, has no insurance, and is in the vague legal category only recently defined by the GENIUS Act.

The second is the single-bank tokenized deposit model: JPMorgan Chase's Kinexys is a leading example, active on Base and Canton, and is processing real institutional payments today. Under this model, a large bank builds its own trajectory, issues its own tokenized deposits, and provides programmable settlements to customers within the bank. The advantage lies in control and timeliness: JPMorgan is not waiting for alliances. The weakness lies in coverage. A JPMorgan track handles JPMorgan's funds well but is completely unable to handle other banks 'funds, reintroducing the interoperability issues that correspondent bank relationships are designed to solve.

The third is the shared network model, which is exactly SWIFT's bet, as well as the 2027 launch plan promoted by JPMorgan Chase, Bank of America, Barclay and Bank of New York Mellon through clearing houses. It is not a walled garden of a single bank, nor an open public chain, but a coordinated ledger shared by multiple banks. Its advantage is precisely what the single banking model lacks: cross-institutional interoperability. The weakness lies in governance and speed, because getting 17 banks-let alone 11000-to reach a consensus is much slower than one bank acting alone or one issuer minting tokens.

Please note that there is also a tension of its own between the second and third models, not just competition with stablecoins. Every bank that builds its own Kinexys-style track will have less incentive to join the shared network because it already has a working system. SWIFT's bet is that no single bank's track can reach the coverage provided by default by its 11000 member network, so banks will converge on a shared layer rather than fragmented into competing Private Cloud. This is a reasonable bet, but not a certainty. Two outcomes have existed in the history of financial infrastructure: shared tools have become the universal standard, and walled gardens have remained closed because their owners valued control rather than coverage.

An honest observer would conclude that the endgame for digital currencies is not a victory for stablecoins or a victory for banks. It is a question of which of the three architectures can capture which application scenarios. The most likely answer is that the three coexist and serve different corridors, and the boundaries between them will be controversial for a long time. SWIFT's release did not solve this issue. It just ensures that the shared banking network model is supported by the strongest distributed network, which would not have been true a month ago.

Honest interpretation

Stripping away the various packaging, SWIFT's launch is best understood as the most serious attempt yet by the existing financial system to answer the question raised by stablecoins: If money is to flow on a programmable track, who will issue it and who will control the track?

The answer for stablecoins is: non-bank institutions, on the open network, outside the system. SWIFT's answer is the opposite: banks, on permission-based ledgers, within the system, all existing control mechanisms remain unchanged. Both answers are logical. The choice is not technical, but about whether to strengthen the dual-tier banking system in the digital currency era or bypass it-a question of power and financial stability, not block time.

SWIFT's move is important not because it has better technology-because public blockchain stablecoins are more open and composable in terms of raw capabilities. It's because SWIFT has something that crypto-native challengers cannot create: 11000 banks already connected to the network. This distribution gives a nine-month pilot for a 53-year-old messaging partnership more weight than a more glamorous launch from a better-funded startup. Banks have to move digital currency no matter what. SWIFT simply gave them a way to do this without holding stablecoins at all, which may be exactly what it wants for an industry whose entire instincts are self-preservation.

Whether it will succeed is an open question, and the pilot will be answered gradually, corridor by corridor, over several quarters. But the strategic picture is clear. The stablecoin industry has claimed for years that banks are too slow to compete in the digital currency space. SWIFT has just proved that they are only slow, not absent, and slow with 11000 members is a very different situation than fast with zero members.

FAQs

What has SWIFT launched?

On July 9, 2026, SWIFT and 17 major banks from six continents (including Citigroup, HSBC, UBS, and BNP Paribas) jointly launched a blockchain-based shared ledger for round-the-clock cross-border payments, using tokenized deposits. The ledger, based on Hyperledger Besu, was built in nine months and serves as a coordination layer to process tokenized deposits issued by banks, with final settlement still occurring through existing payment tracks. This is an initial pilot rather than a full deployment.

What is the difference between tokenized deposits and stablecoins?

Tokenized deposits are representations of commercial bank currency on the blockchain, issued by regulated banks, retained on bank balance sheets, and subject to deposit insurance up to statutory limits. Stablecoins are issued by non-banking entities, backed by reserve assets deposited outside the banking system, run on open blockchain, and have no deposit insurance. They look similar but differ in legal status, insurance coverage and impact on bank lending.

Why did SWIFT choose tokenized deposits over stablecoins?

Because tokenized deposits retain funds in the banking system. When customers buy stablecoins, funds are transferred from their banks to the issuer's reserves, draining the bank's deposits to lend. Tokenized deposits remain on the bank's balance sheet, maintaining credit creation, while providing the same round-the-clock programmable settlement. SWIFT's position is that they provide a compliant alternative that is free of the risks associated with non-bank stablecoins by certain institutions.

Does this pose a threat to TEDA and Circle?

It is not a direct threat, but it is a signal. stablecoins dominate open, permission-free corridors such as exchange clearing, DeFi and remittances, and SWIFT's bank-only books do not serve these areas. The competitive risk lies in the long run: If banks lock in cross-border institutional clearing with protected tokenized deposits, stablecoins 'growth could be limited to the permission-free margins rather than expanding into the core areas of regulated institutions that they have been approaching.

Will SWIFT's ledgers replace existing systems?

No. It is a coordination layer above the agency bank relationship, not a substitute. Banks issue tokenized deposits on their own ledgers; share ledgers coordinate movements, and final settlement is still carried out through existing payment tracks. SWIFT is already able to process most payments to receiving banks in minutes; the ledger's specific contribution is to support weekend and overnight settlements that cannot be supported by existing infrastructure.

Who else is building a tokenized deposit network?

Several major institutions. An alliance including JPMorgan Chase, Bank of America, Barclays and Bank of New York Mellon is building a U.S. -focused tokenized deposit network through clearing houses, with a goal of going online in 2027. JPMorgan's Kinexys is already running on Base and Canton, processing institutional payments. The proliferation of multiple independent banking networks poses the risk of fragmentation, which SWIFT's shared ledger claims to address.

Are tokenized deposits safer than stablecoins?

They come with different protective measures. Tokenized deposits are backed by bank capital, enjoy deposit insurance within legal limits, and are issued by banks that have access to the Federal Reserve's discount window, thereby reducing the risk of runs. Under the GENIUS Act, stablecoins must hold full reserves and disclose them, but the holders are not protected depositors and do not have central bank support. These tools have structurally different risk profiles.

Why is SWIFT coverage so important?

Because payment criteria are determined by distribution, not technology. SWIFT connects more than 11000 institutions in more than 200 countries, a coverage unmatched by any stablecoin issuer or crypto-native network. Once the pilot is successful, the marginal cost of joining another member bank is low because it is already on the SWIFT network. It is this accumulated network of members that makes the pilot of a 53-year-old cooperative organization more relevant than the launch of a technologically superior startup.