Here's the paradox: SWIFT says around 90% of cross-border payments now reach the beneficiary's bank in under an hour. Yet "my international transfer is taking three days" remains one of the most common complaints in business banking. Both are true. The SWIFT network itself is fast. The delays happen inside the banks along the way — and above all in the receiving country, where SWIFT's own research finds roughly 80% of a payment's total journey time takes place.
The short version
A SWIFT payment slows down when any of the following happen:
- Compliance checks stop it for manual review at one of the banks
- Cut-off times, time zones, weekends and public holidays leave it waiting for the next business day
- Multiple intermediary banks each process it in turn
- Currency conversion or FX controls add a step, or require documents
- Missing or mismatched information forces a bank to query or "repair" it
- The receiving bank's own processes — manual crediting, local reporting rules, no 24/7 infrastructure — hold it after arrival
1. Compliance screening at every bank
Every bank that touches a payment must screen it against sanctions lists and watch for money laundering and fraud. Most payments clear automatically. But a partial name match ("Mohammed Ali Trading" vs a listed individual), an unusual country combination, or a vague payment description can trigger a manual review — and that reviewer may be in a different time zone.
- Where it happens: Sending bank, each intermediary, receiving bank
- Typical delay: Hours to several days if documents are requested
- What you can do: Use full legal names, a clear payment purpose ("Invoice 2026-114, website design services") and complete addresses
2. Cut-offs, time zones and holidays
Each bank sets daily cut-off times per currency, tied to when the currency's settlement system is open. A USD payment sent from Bangkok on Friday evening may miss the New York window, wait through the US weekend, then arrive in Europe on Monday afternoon. Add a public holiday in any country along the chain and it slips again.
- Where it happens: Every bank and settlement system in the chain
- Typical delay: One to three business days in bad cases
- What you can do: Send early in the week, early in the day, and check holiday calendars at both ends
3. Too many hops
If your bank has no direct relationship with the beneficiary's bank, the payment is relayed through one or more intermediaries. Each has its own processing queue, screening, and cut-offs. (See How banks send money through SWIFT.)
4. Currency conversion and FX controls
Converting currencies adds a step, and in markets with capital or FX controls, banks must collect supporting information before crediting — purpose codes in India are a well-known example, and several Asian markets require documentation for larger inbound amounts. SWIFT's 2025 speed research lists regulatory reporting and currency controls among the main causes of delay.
5. Missing or mismatched details
A beneficiary name that doesn't match the account, a missing address, an outdated BIC, or an IBAN typo will cause a payment to be queried, repaired or returned. Returns are the worst outcome: they can take a week or more and often cost you fees and an FX loss on the way back.
6. The "last mile" in the receiving country
Once the payment arrives, the beneficiary bank must credit the customer. Some do this automatically in minutes; others rely on manual processes, batch runs, or domestic systems that don't operate 24/7. This is the single biggest source of delay SWIFT has identified — and the one senders can least control.
7. Weekends — the system is still mostly business-hours
Most correspondent banking still runs on business days. SWIFT's blockchain-based ledger (piloting with 17 banks from July 2026) and its 2026 retail payments scheme are both aimed at making cross-border transfers faster and eventually always-on, but for most payments today, weekends still mean waiting.
Comparison at a glance
| Cause | Where it happens | Typical impact | Can you prevent it? |
|---|
| Compliance review | Any bank in chain | Hours–days | Partly — clear names, purpose, addresses |
| Cut-offs / time zones | Every bank | Up to 1–2 days | Yes — send early, early in the week |
| Holidays / weekends | Every country in chain | 1–3 days | Yes — check calendars |
| Multiple intermediaries | Correspondent chain | Hours–1 day | Partly — choose providers with direct/local routes |
| FX controls / documents | Receiving country | Hours–days | Partly — provide purpose and documents upfront |
| Data errors | Any bank | Days; returns 1–2 weeks | Yes — verify details before sending |
| Last-mile crediting | Beneficiary bank | Hours–days | Rarely |
What this means for your payments
Most delay is predictable. Send early, send complete information, send in the recipient's account currency, and always get the UETR so you can see exactly which bank is holding a delayed payment. For corridors where the "last mile" is the problem, the best fix is often avoiding it entirely — paying out through the recipient country's local instant rails rather than waiting for a foreign transfer to be credited.
Sources
- SWIFT — A year of shared progress: 5 highlights from 2025 (30 Dec 2025) — www.swift.com
- SWIFT — FIN traffic figures — www.swift.com
- SWIFT — Blockchain ledger ready for use as 17 banks set to pilot (9 Jul 2026) — www.swift.com
