SWIFT: The blockchain ledger has been enabled—banks unite to put an end to stablecoins

The organization that manages global bank transfers and is often used as a sanctions weapon, SWIFT, has officially announced that its own blockchain ledger is ready for use, with 17 major global banks preparing to run real transactions on-chain.

This time, SWIFT has shed its usual slow pace, taking only nine months from concept to launch. For an organization connecting over 200 countries and more than 11,500 financial institutions, this speed of deployment shows strong internal momentum and that blockchain technology is indeed relatively mature.

SWIFT officially announced 17 partner banks spanning six continents: Citibank, HSBC, UBS, BNP Paribas, Standard Chartered, Wells Fargo, Bank of New York Mellon, DBS, Mitsubishi UFJ, among others.

While not as large as Open USD's 140 partners, SWIFT's cooperation with these 17 major players is a serious collaboration.

The specific approach: banks tokenize deposits on their own books into "tokenized deposits" and circulate them on the SWIFT shared ledger. Customer funds can be moved 24/7—at night, on weekends—while final settlement still runs through existing systems.

Simply put: The front desk records and releases funds first, while the back office settles later.

Currently, 75% of payments on the SWIFT network arrive within 10 minutes. What has always been slow is not the messaging itself, but the operating hours and settlement arrangements of the banks on both sides.

This move targets the pain point: "money freezes once the bank closes."

On its own, this is a technology upgrade. In a broader context, it is a defensive counterattack by the traditional payment system against stablecoins.

In the past two years, stablecoins have offered cross-border instant transfers, weekend availability, and negligible fees. More and more people in foreign trade and remittance are directly using USDT and USDC, bypassing banks entirely.

For banks, this is not just about losing fee income—it's about losing deposits.

When money is converted to stablecoins, it leaves the bank's balance sheet. Without deposits, banks lose the ammunition for lending. This strikes at the very foundation.

The banks' response is clear: You're fast? I'll be fast too, but I won't let money leave the banking system—tokenize bank deposits themselves. The money still sits on the bank's books, still protected by deposit insurance and regulation, just wrapped in a digital shell for 24/7 circulation.

In fact, many banks tried this independently before: JPMorgan has Kinexys, HSBC has its own tokenized deposit service. But the fatal flaw of going it alone is that Morgan's token can't leave Morgan's system—the systems of different banks don't connect.

What SWIFT is doing this time is connecting the isolated islands: it doesn't issue its own coin, doesn't touch the money, and only acts as the orchestration layer. This is its old forte—it never manages the money; it only manages how banks talk to each other.

So SWIFT's blockchain ledger can be seen as a bank consortium chain. It copies the most compelling features of public chains—speed and 24/7 operation—while discarding the parts that trouble regulators—anonymity and permissionlessness.

Peel back the technical shell, and underneath is a battle over the right to issue currency.

The stablecoin model: Tether and Circle use U.S. Treasuries as reserves to issue digital dollars—this can be seen as shadow banking.

The tokenized deposit model: The digital dollar is the bank deposit itself. The issuance power lies with commercial banks, and credit creation remains unaffected.

These two models cannot coexist peacefully for long. Every time stablecoins grow, the bank deposit base erodes.

SWIFT's move is essentially the global commercial banking collective showing its hand: Digital dollars can exist, but they must live on the bank's balance sheet.