Cross-border rails: what's actually faster than your bank's wire

"It'll clear in three to five business days" has been the default answer to cross-border payment timing for so long that most finance teams stopped questioning it. That's changed faster than most treasury policies have kept up with. Between real-time payment networks, stablecoin rails, and a new generation of fintech correspondent-banking alternatives, a payment that used to take a week can now realistically clear same-day for a growing share of corridors — and the gap between "what's technically possible" and "what your company actually uses" is now mostly a policy gap, not a technology gap.

The mistake most finance teams make isn't being too slow to adopt new rails. It's evaluating them all as one category — "faster payments" — when they're actually different tools with different risk profiles, suited to different situations.

Three categories, not one

Real-time payment (RTP) networks

Domestic and regional instant-payment schemes now cover a growing list of markets, settling in seconds for same-currency, same-network transfers. The catch: they're still largely bounded by network membership and currency, so they solve the "why does a domestic transfer take a day" problem well, but don't fully solve cross-currency, cross-border settlement on their own.

Fintech correspondent-banking alternatives

A newer layer of providers has effectively rebuilt correspondent banking with pre-funded local accounts in destination markets, converting and settling locally instead of routing through a chain of intermediary banks. This is often the most practical near-term upgrade for a mid-market company: materially faster and cheaper than a traditional wire, without requiring any change to how treasury thinks about currency risk or custody.

Stablecoin settlement

For corridors where banking infrastructure is thin or slow, moving value as a stablecoin and converting to local currency at the destination can outperform every other option on speed — often settling in minutes. It's also the option with the most new considerations attached: custody, issuer risk, and the documentation expectations covered in our stablecoins piece all apply here too, since a settlement stablecoin and a treasury-held stablecoin carry the same underlying questions.

What actually drives the decision

Speed gets the headline, but three other factors usually decide which rail makes sense for a specific payment:

• Corridor coverage. A rail that's excellent for US-to-EU payments may not exist for the specific corridor your vendor or contractor sits in. Coverage, not speed, is usually the first filter.
• Transaction size and frequency. High-frequency, lower-value payments (contractor payroll) tolerate a different risk and cost profile than a large one-time settlement.
• Who owns the operational risk. A faster rail that requires the finance team to manage new custody or compliance obligations isn't automatically the right trade — sometimes a slightly slower option with less operational overhead is the better call for a lean team.

The bank wire isn't slow because faster options don't exist. It's slow because it's the default nobody has had a reason to reconsider — until the volume or the corridor makes it worth the look.

A reasonable way to start

Rather than migrating a category of payments wholesale, pick one recurring, well-understood corridor — a contractor payroll run to a single country is a common starting point — and pilot a faster rail against it for a full cycle. That gives you a real comparison on cost, speed, and operational overhead before deciding whether to expand it, with a blast radius small enough that a rough edge doesn't become a board-level problem.

The direction of travel is clear enough that "we still use wires for everything" is no longer a neutral default — it's a decision, even if nobody framed it that way. Worth revisiting on purpose, corridor by corridor, rather than by inertia.