A ++BIS analysis of actual SWIFT gpi data++ found the median cross-border payment settles in under two hours. The fastest corridors settle in under five minutes, and the slowest take more than two days, and the differences are driven almost entirely by delays at the receiving bank.
BIS found that the slowest corridors cluster in lower and lower-middle income countries, tied to capital controls, limited bank operating hours, and batch processing at the receiving end. And if your business moves money through commodities-exporting markets or emerging-market trade corridors, this is the exact route you're using.
How a SWIFT payment actually settles
SWIFT is a messaging network. Banks use it to send payment instructions to each other, and the actual movement of funds happens through correspondent banking relationships behind that messaging layer. The friction is a feature of correspondent banking specifically, not of bank-operated payment rails generally. Fedwire, the US domestic real-time gross settlement system, moves funds in seconds because it skips the correspondent chain entirely. SWIFT's cross-border speed problem is a correspondent-banking problem, not a banking problem.
++SWIFT's own published data++ shows 75% of cross-border payments now reach the beneficiary bank within 10 minutes. That's the messaging and interbank leg, and it's genuinely fast. What happens after that, crediting the actual recipient's account, is a separate step, handled entirely by the receiving bank.
Why the "takes days" reputation persists
The instruction can arrive at the beneficiary bank in minutes and still take a day or more to actually land in the recipient's usable balance. BIS's own research points to why: compliance checks and operating-hours mismatches at the receiving bank, compounded by batch processing instead of real-time handling.
A payment between two well-connected financial centers can complete end to end in minutes. A payment into a market with capital controls or a bank running overnight batch processing can sit for a day or two after it's already arrived, waiting for the receiving side to actually act on it.
How stablecoin settlement actually works
A stablecoin transaction confirms on whatever blockchain it runs on, and confirmation times vary by network and by definition. Bitcoin transactions typically need 10 to 60 minutes for a reliable confirmation. Faster networks, including Solana, Polygon, and Tron, confirm in seconds. Ethereum sits in between, and the exact number depends on what you mean by "confirmed": a single-block confirmation can happen in seconds, while a stricter finality checkpoint takes longer.
++Ethereum's own documentation on finality++ describes finality as a process that deepens over multiple blocks, not a single instant. A transaction can be practically usable for commercial purposes before it reaches the network's strictest definition of final.
The full story
On-chain settlement finality is only half the story. The other half is what happens after the recipient has the stablecoin: can they actually use it, or do they still need to convert it to local fiat currency to pay staff, suppliers, or taxes?
If the recipient can hold the stablecoin directly, or off-ramp it instantly through a well-liquidity local provider, the speed advantage is real and immediate. If they're in a market with limited off-ramp liquidity, part of that advantage gets absorbed at the same kind of last-mile friction that slows down SWIFT payments on the receiving end.
The rail changed and the last-mile bottleneck didn't necessarily disappear, it just moved. This is the same reason off-ramp reliability matters as much as on-chain speed.
Best case vs. worst case
| Best case | Worst case | |
| SWIFT | Under 5 minutes, well-connected corridors | 2+ days, EM corridors with capital controls or batch processing |
| Stablecoin (on-chain) | Seconds (Solana, Polygon, Tron) | Up to 60 minutes (Bitcoin, full confirmation) |
| Stablecoin (usable funds) | Same as on-chain, if the destination has strong off-ramp liquidity | Delayed further if the destination's off-ramp liquidity is limited |
On the fastest SWIFT routes, the gap barely exists, but on the slowest, it's the difference between minutes and days, provided the stablecoin's destination also has reliable off-ramp access.
Why this matters most for cross-border B2B and commodities traders
The routes where SWIFT is fast tend to be exactly the routes a commodities trader or cross-border B2B operator doesn't rely on. The corridors BIS flags as slow overlap heavily with where commodities actually get bought and sold, and those same markets are often where stablecoin off-ramp liquidity is still developing.
That's the case for stablecoin settlement in this context. SWIFT's speed varies enormously by corridor, and the corridors this business runs through are the ones where it's at its worst. The full benefit depends on choosing a settlement partner with genuine off-ramp reach into those same markets, not just fast on-chain confirmation.
Related reading: ++The Real Cost of Crypto Payments++ · ++On-Ramps and Off-Ramps Explained++