Most SWIFT payments reach the destination bank within an hour. The days go to cut-offs, correspondent hops, compliance checks, and local crediting.
Cross-border payments are slow because the money has to wait at every bank it passes through. The payment message moves in minutes, but each bank in the chain works on its own cut-off times, business days, and time zone, screens the payment for sanctions, and may convert currency or hold it for missing data. The last bank then has to credit the recipient, which is often the slowest step of all.
It's an architecture problem, not a speed problem. Nothing in the chain is slow on purpose. The chain is just long, and most of it closes at night.
It depends on which part you measure. Swift reported in October 2024 that 90% of cross-border payments on its network reach the destination bank within an hour. Only 43% reach the end customer's account within an hour.
That gap is the story. The interbank leg got fast. The last mile, from the receiving bank to the account, didn't.
End to end, the range is wide. The U.S. Faster Payments Council's July 2026 report on stablecoins for cross-border payments puts traditional cross-border settlement at 1 to 10 days, with international wire fees of up to $50 depending on the business's relationship with its bank.
Six things add waiting time. Most payments hit at least three of them.
| Delay | What happens | Typical cost in time |
|---|---|---|
| Cut-offs and business hours | A payment sent after a bank's daily cut-off waits for the next business day | Hours to a full weekend |
| Time zones | The sending bank's afternoon is the receiving bank's night | Up to a business day |
| Correspondent hops | Each intermediary bank processes the payment on its own schedule | Hours to days per hop |
| Compliance screening | Sanctions and AML checks at each bank, plus holds for missing or unclear data | Minutes to weeks |
| Currency conversion | FX is executed somewhere in the chain, often during that desk's trading hours | Hours |
| Local crediting | The receiving bank books the funds to the customer's account, sometimes after manual checks | Minutes to days |
Every bank sets a daily cut-off for outgoing international payments, and the settlement systems behind them only run on business days. A US bank might stop accepting same-day SWIFT instructions mid-morning Eastern time. Miss it and the payment leaves tomorrow.
Now add a second country. A payment from New York to Singapore that leaves at the end of the US business day arrives in the middle of the Singapore night. A Friday payment can sit through two weekends if the countries don't share one, and a holiday on either side adds a day. Nobody made a mistake. The calendars just don't line up.
Most banks don't hold accounts with every other bank in the world. To pay into a country where it has no presence, a bank routes through a correspondent that does, and sometimes through two. Each correspondent holds pre-funded accounts, called nostro and vostro accounts, in the currencies it serves.
Every hop is another queue, another screening, and another chance for a fee to come off the top. The mechanics of those pre-funded accounts, and why they trap capital, are in correspondent banking vs stablecoin liquidity.
Each bank in the chain screens the payment against sanctions lists and its own AML rules. Most payments pass in seconds. A name that partially matches a sanctioned party, a missing beneficiary address, or a vague payment purpose can stop the payment until someone reviews it or asks for more information.
This is where the long tail lives. A payment that clears automatically takes minutes. One that needs a human can take days. Structured data helps: Swift's move to ISO 20022 messages, with the coexistence period for cross-border payment instructions ending in November 2025, gives banks cleaner name and address fields and fewer payments to repair by hand.
Somebody has to convert the currency. It might be the sending bank, a correspondent, or the receiving bank. For major pairs this is quick. For less-traded currencies, conversion can depend on a specific desk's hours or on liquidity in that market, which adds time and usually a wider spread. What is a liquidity market explains where that liquidity comes from.
The receiving bank has to credit the account. Swift's data shows this is the step with the widest variation between countries. Delays come from local market infrastructure hours, local regulation, and practices like checking with the customer that a payment was expected and confirming the final amount before crediting it.
Because tracking shows you where the payment is, not how to move it. Swift gpi gives each payment a unique end-to-end reference, the UETR, so every bank in the chain can report status against it. That ended the era of "we sent it, we don't know where it is." It didn't remove the cut-offs, the hops, or the manual checks.
Visibility still matters. A finance team that can see a payment sitting at a correspondent can chase it. A team that can't just waits.
The G20's roadmap for cross-border payments sets targets for the end of 2027. For speed, the goal is 75% of cross-border payments credited within one hour and the rest within one business day. For cost, the goal is a global average of no more than 1% for retail cross-border payments.
Progress is slow. The Financial Stability Board's October 2025 progress report found that the speed of wholesale payments and remittances improved, but average costs stayed sticky, and that there is "still much distance to cover" to reach the targets.
A stablecoin changes the architecture of the middle of the payment. Instead of hopping between correspondent banks, value moves on a blockchain between two parties in seconds to minutes, any day of the week. There's one settlement asset, one shared record of the transfer, and no correspondent in between.
| Delay | Does a stablecoin leg remove it? |
|---|---|
| Correspondent hops | Yes. Value moves directly on-chain |
| Time zones and weekends in the middle | Yes. Blockchains don't close |
| Pre-funded accounts in each country | Mostly. One stablecoin balance replaces a set of local nostro accounts |
| Currency conversion | No. FX still happens, at the on-ramp or the off-ramp |
| Compliance screening | No. KYC, KYB, sanctions, and monitoring still run |
| Cut-offs on the fiat legs | No. Bank transfers in and out keep their own hours |
The FPC report is blunt on the compliance point: requirements "are the same for stablecoins as for cash-based payments and could be far greater." A stablecoin removes waiting time. It doesn't remove checks. For how the on-chain leg works, see blockchain payments explained.
At the fiat edges. A stablecoin payment usually starts and ends in a bank account, and those legs run on bank rails.
So the fastest cross-border flows pair a stablecoin in the middle with instant rails at both ends. How long does a stablecoin payout take lists the times by country, and stablecoin API SLAs and settlement finality explains what "settled" actually means at each step.
BlindPay moves the cross-border leg in stablecoins and connects it to local rails at the edges. Payouts over Pix, SPEI, and Argentina's Transfers settle in minutes, including weekends, and RTP payouts in the US are instant. Where a slower rail is the only option, the cut-offs are published: 9:00 PM ET for ACH, 3:00 PM ET for domestic wires, and 10:30 AM ET for SWIFT, as listed in cut-off times.
International wires run as SWIFT payments and collections on behalf of your customers (POBO/COBO), with UETR tracking and MT103 confirmations, so a finance team can see where each payment is. The setup is in POBO and COBO. Payouts don't need pre-funding: a quote locks the rate for a few minutes and the payout executes against it, covered in no pre-funding stablecoin payouts.
Compliance runs in the flow too. Customers are verified before their first transaction, and a payout that needs review shows up as a status with a webhook, not a wire that disappears for a week. If you're debugging a slow payout today, common stablecoin payout mistakes covers the cut-off and paperwork issues that cause most of them.
Pull your last 50 international payments and write down when each one was sent, when it reached the recipient, and which of the six delays above it hit. The pattern usually points at one or two causes. If it's correspondent hops and weekends, a stablecoin leg with instant local payouts fixes most of it. If it's compliance holds, better data at onboarding does. For the bigger picture, start with stablecoin payments explained.
AP2, ACP, and x402 each verify that an AI agent had permission to spend. Here is what every protocol covers, who backs it, and the reconciliation gap none of them close.
Seven stablecoin payment platforms compared for US fintechs in 2026: what makes an API production-ready, how each provider handles compliance, settlement speed against ACH, and how to run the evaluation.
How to choose a stablecoin payment provider in 2026: the four provider types, a comparison of 10 options, and the questions that decide the fit.