SWIFT just built its answer to stablecoins. It runs on bank money, not crypto.

The network that moves the world's money spent 9 months building a blockchain, and the most important decision it made was what not to put on it. No stablecoins. No public tokens. Just bank deposits, wearing a new coat.
Summary

• On July 9, SWIFT launched a blockchain-based shared ledger with 17 major banks, including Citi, HSBC, UBS, and BNP Paribas, for round-the-clock cross-border payments using tokenized deposits.
• The ledger is built on Hyperledger Besu, an EVM-compatible architecture, developed with Consensys in 9 months, and it is positioned openly as the banking industry's answer to a $315 billion stablecoin sector.
• The decisive choice is the instrument. SWIFT built this for tokenized deposits, not stablecoins. That distinction determines who controls the money, whether it is insured, and whether it funds lending.
• Tokenized deposits keep money on bank balance sheets, carry deposit insurance, and preserve credit creation. Stablecoins pull money into reserves, sit outside the banking system, and remove liquidity from it.
• For SWIFT, this is a structural shift: for the first time in 53 years, it is moving from a pure messaging network that never touches funds to an active coordination layer for the movement of value.

For 53 years, SWIFT has done exactly one thing: move messages. When a bank in Singapore pays a bank in Sao Paulo, SWIFT carries the instruction, not the money. It is the postal service of global finance, and it never once opened the envelope.

On July 9, 2026, that changed. SWIFT switched on a blockchain-based shared ledger with 17 of the world's largest banks, and for the first time in its history it is coordinating the movement of value rather than just the messages about it. The financial press covered the launch as a technology story, which it is.

The more important story is a choice buried inside it: SWIFT built this thing to carry tokenized deposits and pointedly not stablecoins, and that single decision is a statement about who the banking system intends to let issue digital money. This piece is about that choice, why it matters, and who it leaves out.

What SWIFT actually launched

The facts first, because they are concrete and verified across SWIFT's own release and independent reporting.

On July 9, SWIFT announced its blockchain-based shared ledger was ready for initial use, with 17 banks across 6 continents preparing to pilot live transactions. The roster reads like a directory of global banking: ANZ, BNP Paribas, BNY, Citi, DBS, First Abu Dhabi Bank, FirstRand, HSBC, Itau Unibanco, Lloyds, Mashreq, MUFG, OCBC, Standard Chartered, UBS, UOB, and Wells Fargo. The system was built in 9 months from announcement to production readiness, developed with input from financial institutions globally and, per multiple reports, with Consensys involved in the build.

Technically, the ledger uses an EVM-compatible architecture based on Hyperledger Besu, functioning as a shared orchestration layer that validates inter-bank payment commitments while preserving existing compliance, credit, risk, and control standards. Its purpose is specific and narrow: enable 24/7 cross-border payments, including overnight and on weekends, that current infrastructure cannot support because it depends on overlapping business hours between sender and receiver. Final settlement still occurs through existing payment rails. The ledger does not replace correspondent banking; it coordinates on top of it.

SWIFT's chief business officer framed the move as extending the trust and stability of incumbent finance into the frontiers of digital money. That sentence is corporate, but it is also precise. The whole design is about carrying something old, bank money, on something new, a shared ledger, without letting go of the controls that make bank money what it is.

The choice that defines it

Here is the decision that matters more than the technology, and that most launch coverage mentioned only in passing: SWIFT built this for tokenized deposits, not stablecoins.

A tokenized deposit is a digital representation of money held in a regulated commercial bank, issued by that bank on a blockchain, maintaining a one-to-one relationship with the deposit on the bank's balance sheet. It is commercial bank money with a new wrapper. A stablecoin is a token pegged to a currency and issued by a non-bank entity, backed by reserves such as Treasury bills that sit outside the banking system, and it operates on public blockchains accessible to anyone with a wallet.

They look almost identical. A dollar-denominated stablecoin and a tokenized dollar deposit both claim to be worth $1, both move on a blockchain, both settle in seconds. The New York Fed, in a February 2026 staff report, drew the structural line that the surface similarity hides: stablecoins intermediate safe assets into a medium of exchange, while tokenized deposits allow banks to keep funding loans and supporting credit creation, just on digital rails. That is not a technical distinction. It is a distinction about who gets to create money and what happens to the banking system if the answer changes.

SWIFT chose the instrument that keeps banks in the center. Its stated position is that bank-issued tokenized deposits offer a compliance-ready alternative within existing regulatory frameworks, without the risks some institutions associate with non-bank stablecoins. In plainer terms: SWIFT built a blockchain that does what stablecoins do, on rails the banks already control, so that the banks do not have to adopt an instrument that cuts them out.

Why banks care so much about the difference

The reason this choice carries such weight is that stablecoins and tokenized deposits do opposite things to a bank's balance sheet, and therefore to the banking system's capacity to lend.

When a customer buys a stablecoin, they move fiat out of their bank account and into the issuer's reserves. That money leaves the bank. It now sits in Treasury bills or a custodial account backing the token, where it does nothing for credit creation. Multiply that across a $315 billion sector, and you get a measurable drain: deposits leaving banks reduce the money multiplier, the mechanism by which $1 of deposits supports several dollars of lending. Stablecoins, in the language of one industry analysis, remove liquidity from the banking system.

Tokenized deposits do the reverse. The money stays on the bank's balance sheet, still counted as a deposit, still available to fund loans and investment. The token is just a more mobile representation of it. So a bank that issues tokenized deposits keeps the funding it would lose to a stablecoin, while offering customers the same 24/7 programmable settlement. From the bank's perspective, that is the entire game: match the stablecoin's user experience without surrendering the deposit base that the lending business depends on.

There is a safety dimension too, and it is not merely marketing. Tokenized deposits are backed by a bank's capital and the supervisory framework that governs commercial banks; they carry deposit insurance up to the statutory limit, and the issuing bank can borrow from the Federal Reserve's lender-of-last-resort window, which reduces run risk. Stablecoins have none of that. Under the GENIUS Act, they must hold full reserves and disclose them, which is real protection, but a stablecoin holder is not an insured depositor, and there is no central bank standing behind the token. The 2008 money-market-fund parallel is apt: instruments that look like deposits and are treated like deposits right up until one breaks the buck and reveals it was never a deposit at all.

The bull case for SWIFT's approach

The optimistic reading is that SWIFT has done the sober, correct thing, and that its distribution makes it the most credible entrant in the entire tokenized-money contest.

The reach argument is genuinely hard to counter. SWIFT connects more than 11,000 financial institutions across over 200 countries. No stablecoin issuer, no crypto-native payment network, and no single bank consortium can match that footprint. If the pilot works across 17 banks and multiple currency corridors, the marginal cost for the next institution to join is low, because it is already on SWIFT. That is a distribution advantage measured in decades of accumulated network membership, and distribution is what actually decides payment standards.

BREAKING: Ripple Treasury adds SWIFT to its list of strategic partners pic.twitter.com/XnVSB3oaKN --- crypto.news (@cryptodotnews) April 13, 2026

The problem SWIFT is solving is also real rather than invented. SWIFT already processes 75% of payments to beneficiary banks within 10 minutes on existing rails, often in seconds, so speed of messaging was never the true constraint. The constraint is the dependency on overlapping business hours: a Friday-evening payment from Asia to a counterparty in the Americas waits for Monday. The shared ledger removes exactly that, enabling weekend and overnight settlement inside the regulated perimeter. This is a targeted fix to a specific friction, not a solution in search of a problem to solve.

And the model preserves what regulators and treasurers actually want preserved. Corporate treasurers who have routed weekend wires through batch systems for decades get round-the-clock movement without stepping outside the compliance framework their auditors require. Banks keep their deposits. Regulators keep their oversight. The financial system gets programmable, always-on settlement without a parallel monetary system forming outside it. For institutions whose first question about any innovation is what could go wrong, that is a strong pitch.

The bear case for SWIFT's approach

The skeptical reading is that SWIFT is defending an incumbency, that a permissioned bank ledger recreates most of the limitations stablecoins were built to escape, and that the market has already voted for the other model.

Start with the scoreboard. Stablecoins are not a proposal; they are in the wild, with supply above $300 billion and tens of trillions in settled transaction volume, having survived multiple crypto winters. Tokenized deposits remain largely in pilots, and SWIFT's own launch is explicitly an initial pilot, not full deployment. One instrument is battle-tested at scale, and the other is a promising experiment, and the gap is years, not months. BlackRock's Larry Fink put the competitive framing memorably in his 2025 investor letter: if SWIFT is the postal service, tokenization is email, moving assets directly and instantly, sidestepping intermediaries. SWIFT's ledger is an attempt to make the postal service deliver like email while keeping the post offices in business.

The permissioning is the deeper limitation. SWIFT's ledger is a closed, bank-only system. Stablecoins are open: anyone with a wallet can hold and send them, no banking relationship required, which is precisely why they took hold in cross-border corridors that the banking system serves poorly or expensively. A fintech in Lagos pays a supplier in Shenzhen in USDC because the bank wire costs 6% and takes 4 days. SWIFT's ledger does nothing for that user, because that user is not a bank on SWIFT. The tokenized-deposit model, by design, only serves people already well served by banks, which is not where the disruptive demand is.

There is also a crowding problem that undercuts the reach argument. SWIFT is not the only bank consortium building this. A group including JPMorgan, Bank of America, Barclays, and BNY is building a US-focused tokenized-deposit network through The Clearing House, targeting 2027. JPMorgan already runs Kinexys, live on Base and expanded to Canton, settling institutional payments today. If every major bank and consortium builds its own tokenized-deposit rail, the result is not one clean alternative to stablecoins but a fragmented set of walled gardens, which is the exact problem SWIFT's shared ledger claims to solve, reappearing one level up.
You might also like: Ripple vs SWIFT: Is XRP complementing the banking network or replacing it?

What this means for the stablecoin giants

For Tether and Circle, the two issuers who dominate the $315 billion sector, SWIFT's move is a signal rather than an immediate threat, and the distinction matters.

It is not an immediate threat because the two instruments serve partly different users. Stablecoins own the open, permissionless, retail-and-crypto corridors: exchange settlement, DeFi collateral, remittances, and the long tail of users without good banking access. SWIFT's ledger serves regulated institutions moving money between themselves. In the near term, these are different markets, and SWIFT's pilot takes nothing directly off Tether's or Circle's books.

It is a signal because it marks the point where the banking system stopped treating stablecoins as a curiosity and started building the institutional-grade alternative in earnest, with the sector's most powerful distribution network behind it.

The competitive question for the stablecoin issuers is whether tokenized deposits expand to absorb the use cases stablecoins hoped to grow into, particularly institutional cross-border settlement and corporate treasury, which is exactly the ground stablecoins have been migrating toward as they moved from crypto on-ramps into real commerce. If banks lock down the institutional corridor with insured, compliant tokenized deposits, stablecoins may find their growth capped at the permissionless edge instead of expanding into the regulated core.

The GENIUS Act complicates the picture in both directions. It gave stablecoins a federal framework and legitimacy, which helps them. It also opened the door to bank-issued stablecoin models and, through OCC trust charters granted to Circle, Paxos, Ripple, and others, blurred the line between the two instruments. The likely future is not one model winning but convergence: bank-issued stablecoins, tokenized deposits, and non-bank stablecoins coexisting, with the interesting fights happening at the boundaries. SWIFT just planted a very large flag on the bank side of that boundary.

JUST IN: Ripple CEO Brad Garlinghouse declares "What we're doing... is taking over SWIFT" https://t.co/DTxV5QPDod pic.twitter.com/icZUO24Af4 --- crypto.news (@cryptodotnews) April 5, 2026

The three-way race nobody named

The cleanest way to see where SWIFT fits is to stop treating this as stablecoins-versus-banks and start counting the actual competitors, because there are three distinct bets being placed on how institutional money moves next, and they do not all win.

The first is the open stablecoin model: Tether, Circle, and the newer consortium efforts like Open USD. Non-bank issuers, public blockchains, permissionless access, reserves held outside the banking system. This model owns the present. It has the volume, the corridors, and the proven product-market fit in exactly the places banks serve badly. Its weakness is regulatory and structural: it pulls deposits out of banks, it carries no insurance, and it sits in a legal category the GENIUS Act only recently defined.

The second is the single-bank tokenized-deposit model: JPMorgan's Kinexys is the leading example, live on Base and Canton, settling real institutional payments today. Here, a single large bank builds its own rail, issues its own tokenized deposits, and offers clients programmable settlement inside that bank's walls. The strength is control and immediacy: JPMorgan did not wait for a consortium. The weakness is reach. A JPMorgan rail moves JPMorgan money well and everyone else's money not at all, which reintroduces the interoperability problem that correspondent banking exists to solve.
You might also like: Ripple spent a decade fighting SWIFT. Now it wants to plug into it

The third is the shared-network model, and this is SWIFT's bet, alongside the JPMorgan-BofA-Barclays-BNY effort running through The Clearing House for a 2027 launch. Instead of one bank's walled garden or an open public chain, a coordinated ledger that many banks share. The strength is exactly what the single-bank model lacks: interoperability across institutions. The weakness is governance and speed, because getting 17 banks, let alone 11,000, to agree on anything is slower than one bank acting alone or an issuer minting a token.

Notice that the second and third models are in tension with each other, not just with stablecoins. Every bank that builds its own Kinexys-style rail is a bank that has less reason to join a shared network, because it already has a working system. SWIFT is betting that no single bank's rail can achieve the reach that its 11,000-member network offers by default, and that banks will therefore converge on a shared layer instead of fragmenting into competing private ones. That is a plausible bet and not a certain one. The history of financial infrastructure is full of both outcomes: shared utilities that became universal, and walled gardens that stayed walled because their owners preferred control to reach.

Where this leaves the honest observer is that the digital-money endgame is not stablecoins-win or banks-win. It is a question of which of three architectures captures which use cases, and the likeliest answer is that all three persist, serving different corridors, with the boundaries between them contested for years. SWIFT's launch does not settle that. It just guarantees that the shared-bank-network model has the strongest possible distribution behind it, which was not true a month ago.

The honest read

Strip away the framing and SWIFT's launch is best understood as the incumbent financial system's most serious attempt yet to answer a question stablecoins forced onto the table: if money is going to move on programmable rails, who issues it and who controls the rails?

Stablecoins answered: non-banks, on open networks, outside the system. SWIFT's answer is the opposite: banks, on a permissioned ledger, inside the system, with all the existing controls intact. Both answers are coherent, and the choice between them is not really technical. It is a choice about whether the digital-money era strengthens the two-tier banking system or routes around it, and that is a question about power and financial stability, not about block times.

What makes SWIFT's move consequential is not that it is better technology, because in raw capability a public-blockchain stablecoin is more open and more composable. It is that SWIFT has the one thing the crypto-native challengers cannot manufacture: 11,000 banks already on the network. That distribution is why a 9-month pilot from a 53-year-old messaging cooperative is a bigger deal than a flashier launch from a better-funded startup. The banks are going to move digital money somehow. SWIFT just gave them a way to do it without ever holding a stablecoin, and for an industry whose entire instinct is to preserve itself, that may be exactly the product it wanted.

JUST IN: Over 11,000 banks already tested XRP on SWIFT network, "XRP is a tool, it's a done deal" pic.twitter.com/7ESoDacdxq --- crypto.news (@cryptodotnews) March 31, 2026

Whether it works is an open question, and the pilot will answer it slowly, corridor by corridor, over quarters. But the strategic picture is already clear. The stablecoin sector spent years arguing that banks were too slow to compete in digital money. SWIFT just proved they were slow, not absent, and being slow with 11,000 members is a very different position than being fast with none.

Frequently Asked Questions

What did SWIFT launch? {#faq-question-1784402484434}

On July 9, 2026, SWIFT launched a blockchain-based shared ledger with 17 major banks across 6 continents, including Citi, HSBC, UBS, and BNP Paribas, for round-the-clock cross-border payments using tokenized deposits. Built on Hyperledger Besu in 9 months, it acts as an orchestration layer coordinating bank-issued tokenized deposits, with final settlement still occurring through existing payment rails. It is an initial pilot, not full deployment.

What is the difference between a tokenized deposit and a stablecoin? {#faq-question-1784402491970}

A tokenized deposit is commercial bank money represented on a blockchain, issued by a regulated bank, kept on the bank's balance sheet, and covered by deposit insurance up to the statutory limit. A stablecoin is a token issued by a non-bank entity, backed by reserves held outside the banking system, operating on open blockchains with no deposit insurance. They look similar but differ in legal status, insurance, and effect on bank lending.

Why did SWIFT choose tokenized deposits over stablecoins? {#faq-question-1784402499074}

Because tokenized deposits keep money inside the banking system. When a customer buys a stablecoin, funds leave their bank for the issuer's reserves, draining deposits banks use to fund lending. Tokenized deposits stay on the bank's balance sheet, preserving credit creation, while offering the same 24/7 programmable settlement. SWIFT's position is that they provide a compliance-ready alternative without the risks some institutions associate with non-bank stablecoins.

Is this a threat to Tether and Circle? {#faq-question-1784402512081}

Not immediately, but it is a signal. Stablecoins dominate open, permissionless corridors such as exchange settlement, DeFi, and remittances, which SWIFT's bank-only ledger does not serve. The competitive risk is longer term: if banks lock down institutional cross-border settlement with insured tokenized deposits, stablecoins may find growth capped at the permissionless edge instead of expanding into the regulated institutional core they have been moving toward.

Does SWIFT's ledger replace the existing system? {#faq-question-1784402522120}

No. It is an orchestration layer on top of correspondent banking, not a replacement. Banks issue tokenized deposits on their own ledgers; the shared ledger coordinates the movement, and final settlement still runs through existing payment rails. SWIFT already processes most payments to beneficiary banks within minutes; the ledger's specific contribution is enabling weekend and overnight settlement that current infrastructure cannot support.

Who else is building tokenized deposit networks? {#faq-question-1784402533687}

Several major institutions. A consortium including JPMorgan, Bank of America, Barclays, and BNY is building a US-focused tokenized deposit network through The Clearing House, targeting 2027. JPMorgan's Kinexys is already live on Base and Canton, settling institutional payments. The proliferation of separate bank networks raises the risk of fragmentation, the same problem SWIFT's shared ledger claims to solve.

Are tokenized deposits safer than stablecoins? {#faq-question-1784402543368}

They carry different protections. Tokenized deposits are backed by bank capital, covered by deposit insurance up to the statutory limit, and issued by banks that can access the Federal Reserve's lender-of-last-resort window, reducing run risk. Stablecoins under the GENIUS Act must hold full reserves and disclose them, but holders are not insured depositors, and no central bank stands behind the token. The instruments carry structurally different risk profiles.

Why does SWIFT's reach matter so much? {#faq-question-1784402552272}

Because payment standards are decided by distribution, not technology. SWIFT connects more than 11,000 institutions across over 200 countries, a footprint no stablecoin issuer or crypto-native network can match. Once the pilot works, the marginal cost for another member bank to join is low because it is already on SWIFT. That accumulated network membership is why a pilot from a 53-year-old cooperative can matter more than a technically superior launch from a startup.

Disclaimer: This article is for information and educational purposes only and does not constitute financial or investment advice. It describes payment infrastructure and a pilot program whose outcomes are uncertain, and it is not a recommendation to buy or sell any asset or token. Always do your own research. Information is accurate as of July 17, 2026.
Read more: Swift built the thing XRP was supposed to replace. It chose deposits.