SWIFT just made its biggest move on retail payments in years, and without mentioning Ripple once, it accidentally handed the XRP community a lot to talk about.
The company announced Wednesday in Brussels, that SWIFT‘s new consumer payments framework has drawn in more than 50 banks globally, with over 25 committing to go live by June 2026.
The corridors span Australia, Bangladesh, Canada, China, Germany, India, Pakistan, Spain, Thailand, the UK and the US, five of which rank among the world’s ten largest remittance markets.
The promises attached to all of this are things such as upfront fee certainty, full-value delivery, end-to-end tracking on every transaction, and near-instant settlement where local banking infrastructure supports it.
What the crypto community noticed almost immediately was the participant list. When people went through it bank by bank, at least 30 of the 50-plus institutions named already have existing ties to Ripple’s network, including Santander, HSBC, Deutsche Bank, Standard Chartered, Axis Bank and JPMorgan. SWIFT’s announcement however doesn’t reference Ripple at all. But the overlap is really hard to ignore.
The Ripple connection is real with an important catch
The banks showing up in both ecosystems use Ripple in different ways. Akbank was among the earliest banks to adopt Ripple-based payments in Turkey, while ANZ tested Ripple’s protocol as far back as 2015.
Axis Bank has run live RippleNet corridors in India since 2017, and Bank Alfalah has used Ripple’s rails for UAE-to-Pakistan remittances since 2021. Santander’s One Pay FX international transfer service runs on RippleNet, and Deutsche Bank combined Ripple’s blockchain infrastructure with SWIFT earlier this year to build a cross-border payment ledger.
But the nuance that matters here is that most of those connections are to RippleNet, Ripple’s messaging and settlement network, rather than to XRP the token itself. RippleNet can run entirely in fiat.
Only around 40 percent of RippleNet partners use Ripple’s On-Demand Liquidity product, which is the service that actually requires XRP as a bridge asset between currencies. Santander’s use of RippleNet, for instance, doesn’t involve XRP directly. Neither does Deutsche Bank’s integration. So 30 Ripple-connected banks appearing in SWIFT’s framework doesn’t automatically translate into 30 banks using XRP.
Where the two ecosystems actually intersect
There’s a more indirect connection worth paying attention to. Thunes, a Singapore-based payments company that Ripple has partnered with since 2020 and expanded its relationship with in September 2025, brought stablecoin payout capability to all 11,500 SWIFT-connected banks through SWIFT’s messaging infrastructure.
This creates a routing chain where a payment can flow through SWIFT, get routed via Thunes, and ultimately settle on Ripple’s On-Demand Liquidity rails using XRP as the bridge asset, without any bank being forced to use XRP directly.
SWIFT is also building its own blockchain-based shared ledger in parallel, developed alongside more than 30 financial institutions including JPMorgan, HSBC, BNY Mellon and Citi. If that ledger scales, it gives SWIFT the infrastructure to handle real-time, around-the-clock settlement without needing Ripple’s rails at all.
SWIFT processes over $150 trillion in cross-border payments annually. No blockchain network, including that of the Ripple network, comes close to that reach. But the pressure from blockchain alternatives has clearly been real enough to push SWIFT toward features, near-instant settlement, full transparency, predictable fees, that crypto networks have been offering for years.
Where Ripple still has a practical edge is in the corridors where SWIFT has historically been slowest. SWIFT itself acknowledges that roughly 80 percent of a payment’s total processing time happens in the “last mile,” the gap between a payment reaching the destination bank and actually landing in the customer’s account.
That problem is quite notable, especially in emerging markets, and Ripple has deeper local bank relationships and pre-existing liquidity pools in several of those routes.
Whether the SWIFT framework solves that last-mile problem on its own remains to be seen. If it doesn’t, and if Ripple’s On-Demand Liquidity remains faster and cheaper on those corridors, that’s where the real XRP demand story could eventually show up. The first wave of SWIFT corridors goes live in mid-2026, and that’s the moment worth looking out for.