Field note

SWIFT vs Ripple: Evolution, Not Revolution in Cross-Border Payments

The headlines say XRP and RLUSD will replace SWIFT. The likelier path is evolution, not revolution - a hybrid book where each rail earns the job it is actually good at.

Jun 4, 2025 · Navin Agrawal · Payments · 3 min read

SWIFT vs Ripple: Evolution, Not Revolution in Cross-Border Payments

Visual brief

Visual brief

SWIFT vs Ripple: Evolution, Not Revolution in Cross-Border Payments

As of June 2025

This is not a SWIFT killer story. It is an evolution toward a hybrid book, where high-value flows stay on SWIFT and newer rails take the jobs they are genuinely better at.

Payment headlines are full of the claim that XRP and RLUSD will replace SWIFT’s “outdated” network. As someone who designs payment architectures for banks, my read is the opposite: not replacement, evolution.

The pain points are real, and I see them daily. Cross-border wires taking 3 to 5 days when an instant rail settles in seconds. Multiple correspondent banks stacking cost and complexity. Manual processes turning into operational headaches. That frustration is exactly what fuels the “SWIFT is finished” story.

But the frustration and the conclusion are two different things. SWIFT is not going anywhere soon. That does not mean blockchain is irrelevant to payments. It means the interesting work is not picking a winner - it is deciding which rail does which job.

The signals on the right are why this is worth watching now, not later: a regulated stablecoin is growing fast enough to register as institutional adoption, and the incumbent has put a hard date on its own modernization.

Signals as of June 2025: RLUSD market cap around $244M; roughly 87% month-over-month growth; SWIFT MT/MX ISO 20022 coexistence window closes November 2025.
The June-2025 signals behind the call.
The question is not whether blockchain will disrupt payments. It is whether we will lead that transformation or get dragged into it.

The hybrid book

Most banks will land on a hybrid approach rather than a single rail. The useful way to hold it in your head is not “old versus new” but four jobs, each going to the rail that does it best.

The hybrid book as of June 2025: high-value and regulated stays on SWIFT (ISO 20022 migration underway); mid-market commercial moves to blockchain/stablecoin rails; retail remittance goes digital-first; correspondent banking gradually absorbs crypto liquidity.
Four jobs, four rails - none of which requires SWIFT to lose.

High-value regulated transactions stay on SWIFT, where structured data, finality, and compliance posture matter most. Mid-market commercial payments move to blockchain rails where speed and transparency win. Retail remittances go digital-first, where reach and seconds beat correspondent chains. And correspondent banking gradually absorbs crypto liquidity to cut hops and cost. None of that requires SWIFT to lose. It requires each rail to earn a specific job.

Why the incumbent is not the loser people expect

The “SWIFT killer” framing assumes the incumbent is frozen. It is not. SWIFT’s ISO 20022 migration is moving the cross-border network toward structured, richer payment data, and the MT/MX coexistence window is scheduled to close in November 2025. The gap that blockchain advocates point to - thin, unstructured messaging - is the exact gap SWIFT is closing without changing the rail underneath.

On the other side, the signal worth watching is not a price chart. RLUSD near a $244M market cap with roughly 87% month-over-month growth says institutions are beginning to treat regulated stablecoins as plumbing, not a speculative sideshow. Early, yes. But it is the kind of adoption curve that turns into a settlement leg, not a slogan.

The real opportunity was never the “SWIFT killer.” It is building payment rails that deliver the speed and transparency customers want while working alongside the infrastructure that already moves the world’s money. Lead that transformation, or get dragged into it.

Was this useful?

Choose once.

Related Posts

View All Posts »
Stablecoin custody and issuance converge on one charter

Stablecoin custody and issuance converge on one charter

Two US regulatory threads just lined up. The GENIUS Act created a federal pathway to issue payment stablecoins, and the OCC's new rule lets national trust banks hold digital assets in non-fiduciary custody - then conditionally chartered Coinbase as one. Issuance and custody can now sit inside the same federally regulated counterparty.

A chartered bank just put a stablecoin on card settlement

A chartered bank just put a stablecoin on card settlement

SoFi Bank put SoFiUSD on Mastercard's settlement layer. Authorization still rides the card rails and the merchant sees nothing change, but the interbank fund movement happens on-chain, around the clock, with no batch window and no correspondent float. For the first time, issuers and acquirers get to choose their settlement medium.

Stablecoin payments have an architecture answer and no operations answer

Stablecoin payments have an architecture answer and no operations answer

At 3:17 AM the confirmation never arrived. Two million in institutional stablecoin, and the custody record said complete, the counterparty said pending, the smart contract said something else again. The regulatory stack is finally coherent. The exception playbook that ACH and wires spent decades building does not exist yet, and that gap is where institutions are walking in.

Under a second is the right answer to the wrong question

Under a second is the right answer to the wrong question

At an AWS Bedrock AgentCore Payments session the question was what happens at a thousand transactions a second, and the answer was settlement in under a second. Both are true and they answer different questions. The right frame for one payment crossing a trust boundary is the wrong frame for a million events a day inside one agent fleet, where the chain fee stacks up before anything else does.