Most international transfers reach the recipient's bank within minutes. The waiting happens on either side. Before the money leaves, your bank applies its cut-off time and checks. After it arrives, the recipient's bank runs its own checks before crediting the account. Swift, the network banks use for international payments, says that's where over 80% of the time goes.
What "sent" actually tells you
"Sent", "completed" and "processed" usually mean your bank released the money, not that the recipient's bank credited it. Wells Fargo, for example, says its "Completed" status means the wire was sent, not that the recipient has it.
Where the time goes
Where an international payment spends its time
Share of the journey measured by Swift, from the moment your bank releases the payment to the moment the recipient is credited.
The part people blame, the international network, is usually the fastest. Swift says 75% of payments reach the recipient's bank within 10 minutes, and 86% travel direct or through a single intermediary bank. A study of 20 million tracked payments by the Bank for International Settlements found intermediaries processed 78% of payments in under five minutes. Receiving banks managed that for only 33%.
Swift ranks the causes of that last-mile delay in this order:
- Purpose-of-payment reporting. Some countries, including India and the UAE, require incoming payments to carry a reason. Without one, the recipient's bank may hold or reject the payment.
- Currency controls and national risk checks.
- Systems that don't run around the clock.
- Manual checks, including financial-crime screening.
Swift's figures leave out your own bank's time. Cut-off times differ by currency, even at the same bank. At HSBC Expat, US dollars close at 18:00 UK time, euros at 15:30, Indian rupees at 14:00, Turkish lira at 11:30, and UAE dirhams and Hong Kong dollars at 06:30. Miss the cut-off and processing starts the next business day.
Weekends and holidays count on both sides. At that bank, a US-dollar payment sent at 18:30 on Friday misses the 18:00 cut-off and counts as received on Monday. If that Monday is 12 October 2026, Columbus Day, the US Federal Reserve's wire system is closed, so the US leg can't settle until Tuesday. A "one-day" transfer takes four calendar days, and nothing went wrong. In several Middle Eastern countries the weekend is Friday and Saturday, so a Friday payment can wait there too.
How long is normal, and when to act
Not sure how it was sent? Ask your bank. A payment with a UETR went by SWIFT.
| If the payment went by | Normal | Start asking after |
|---|---|---|
| SEPA Instant (euro) | Under 10 seconds, any day | A few minutes: it either completes or returns to the sender |
| SEPA transfer (euro) | Next business day | Two business days |
| UK Faster Payments | Minutes, up to 2 hours | End of the next business day (the legal limit) |
| US domestic wire | Same business day | The next business day |
| SWIFT, major currency, no conversion | Same or next business day | Two business days past your bank's estimate |
| SWIFT with conversion, purpose codes or currency controls | 1–5 business days | Five business days, or sooner if the tracker shows a hold |
| A formal investigation | 5–10 working days | After that, ask the bank to escalate the case |
| A returned SWIFT payment | 5–15 business days | Ask for the return reason code |
Why less money arrived
When a payment arrives short, check the charge option first. People read SHA as "shared", but Swift's own standard defines it differently: you pay your own bank, and every other bank's charge comes out of the payment.
Why $2,000 arrives as $1,965
A US-dollar payment sent with "shared" charges (SHA) through one intermediary bank.
Conversion can also shrink the amount. If the recipient's account is in a different currency, their bank converts it at its own rate. Take an illustrative rate of 85 rupees to the dollar. A $1,000 payment that loses $15 to an intermediary, then is converted by an Indian bank at 0.5% below that rate, arrives as about ₹83,306 instead of ₹85,000.
One exception: for euro transfers between two EU banks, the deductions above don't apply. EU law requires the full amount to arrive, and each side pays its own bank.
Holds nobody will explain
Banks screen every international payment against sanctions and fraud lists. Swift puts the share of payments that trigger an alert at 5–10%, and 99% of those alerts are false. A hold is not an accusation, and the bank may not be allowed to tell you why. In the UK, telling a customer anything likely to prejudice a money-laundering investigation is a criminal offence.
Three country-specific checks:
India
Declare the purpose. An incoming payment may wait until the recipient states its purpose, such as family support. Ask the receiving bank which purpose code or documents it needs.
United Arab Emirates
Check the purpose code. Dirham payments need a valid Central Bank purpose code. Ask the bank to confirm it before sending; a missing or invalid code can mean rejection.
United States
Keep the promised arrival date. For covered consumer transfers sent abroad from the US, you have 180 days from that date to report an error to the provider. If the money is late, contact the provider now.
- Name mismatches: since 9 October 2025, euro-area banks check the name against the IBAN before you send a euro transfer and warn you if they don't match. A SWIFT payment from outside the EU gets no such check. In the US, a bank may credit by account number alone and ignore the name.
How to trace a payment
Every SWIFT payment carries a UETR, a 36-character reference that works like a parcel tracking number. Since November 2020, the recipient's bank must report to Swift's tracker whether it has credited the payment, put it on hold or rejected it. The status often says why. G003, for example, means the recipient's bank is waiting for documents: the recipient should contact their bank.
Banks often hand over a copy of the payment message, still called an "MT103" (since November 2025 it's a pacs.008 message). It shows how the payment was routed, not where the money is now.
Tracking statuses and return codes in plain English
Banks quote these when you ask for a trace. Type the code you were given.
| Code | What it means | Who acts next |
|---|---|---|
| ACSP / G000 | In progress: passed to the next bank on the tracked network | Nobody yet; check again later |
| ACSP / G001 | In progress: passed to a bank outside the tracked network, so visibility drops | Sender's bank, if it stalls |
| ACSP / G002 | The recipient's bank may not credit it the same day | Nobody; expect the next business day |
| ACSP / G003 | The recipient's bank is waiting for documents or information | The recipient: contact their bank |
| ACSP / G004 | The recipient's bank is waiting for the funds to arrive through its correspondent | The banks; ask the sender's bank to chase |
| ACCC | Credited to the recipient's account | The recipient: check other currency balances or pending items |
| RJCT | Rejected; the money is coming back | Sender: ask for the reason code |
| AC01 | Return: incorrect account number | Sender: get the right details before resending |
| AC04 | Return: the account is closed | Sender: ask the recipient for a current account |
| BE01 | Return: the name doesn't match the account holder | Sender: use the exact legal name on the account |
| AM05 | Return: duplicate payment | Sender: check it wasn't sent twice |
| RR04 | Return: regulatory reason | Sender's bank: ask what is needed |
| FOCR | Return following a cancellation or recall request | Nobody; the money is on its way back |
No match. Ask your bank for the "gpi tracker status" or the "return reason code".
Ask the sender's bank for a trace with this message:
Please trace an international payment.
UETR: [36-character reference]
Sent on [date] for [amount and currency] to [recipient's full legal name],
account [IBAN or account number] at [bank name, BIC].
Charges: [OUR / SHA / BEN]
Please confirm the current tracker status and which bank holds the payment,
send me a copy of the payment message, and open an investigation with a case number.
The recipient asks their bank the same from the other side: has a payment with this UETR arrived, even in a pending queue, and is it waiting for information, a name check or a purpose? Swift says an investigation can take 5 to 10 working days, so start one as soon as the table's "start asking" date passes.
Can you stop it, recall it or get it back?
- Cancelling. US consumers sending money abroad have a legal right to cancel within 30 minutes; Chase, for example, applies it to international personal wires. After that, the payment has usually left.
- Recalling. A recall is a request, not a refund. Swift's Stop and Recall service can stop a payment that's still in flight, and the bank holding it should act within 24 hours. Once the money is credited, the recipient usually has to agree. For euro transfers, a recall for an error must be sent within 10 banking days, and the recipient's bank has 15 banking days to answer.
- Returns. If the details were wrong, the payment comes back. A SWIFT return usually takes 5 to 15 business days (Xe's figure). A SEPA return must reach your bank within 3 banking days of settlement. A returned SWIFT payment often comes back smaller. Say you send €3,000 from a sterling account and it bounces. At an illustrative market rate of 1.17, your bank sells you the euros at a rate 2% worse: £2,616. An intermediary takes €15 and the recipient's bank a €25 return fee, so €2,960 comes back. Your bank converts it back, again 2% worse: £2,479. You lose £137, about 5%, even if exchange rates don't move.
- Your rights. A US consumer's 180-day error window for a late transfer doesn't cover delays from a required screening or from wrong details you gave. In the EU, if you gave a wrong IBAN, your bank must still make reasonable efforts to recover the money.
Don't send a second payment while the first is unresolved. Recovering a duplicate needs the recipient's bank to cooperate.
Next time: routes that don't wait
For euro payments inside Europe, SEPA Instant arrives in under 10 seconds, any day of the year. Since January 2025, euro-area banks can't charge more for it than for a regular transfer. The UK has Faster Payments, and the US has FedNow and RTP, which also run around the clock.
For SWIFT payments, three things remove the most common causes of delays and returns: the recipient's exact legal name on the account, the payment's purpose in the reference, and sending well before your bank's cut-off for that currency.
How this works in Tara
This matters if you keep savings in digital dollars, say because you live between countries or your local currency keeps losing value. Your crypto sits in a wallet only you control (the Vault). Your spending balance (the Smart Account) pays for card purchases and bank transfers, including SWIFT.
Paying a bank account abroad when your money is in crypto
Every bank transfer in the chain has its own cut-off, fees and checks. Fewer bank transfers means fewer places to get stuck.
The usual way: two bank transfers
- Send crypto to an exchangeNetwork fee; wait for confirmations
- Sell, withdraw to your own bankExchange spread and withdrawal fee; a bank transfer with its own cut-off
- Send an international transferBank fee, possible intermediary deductions, the recipient bank's checks
In Tara: one bank transfer
- Choose the amount and the recipient's bank detailsThe payment goes from your spending balance, which you top up from any crypto in your wallet
- See an estimate before you confirmThen follow the payment's status in the app
In practice:
- Top up your spending balance from any crypto in your wallet.
- Pick a saved recipient, or add a new one with their bank details.
- See the fee and the amount, then confirm.
- Follow the payment in the app.
Hold everything. Spend anywhere.
Your crypto and everyday payments, together in one app.
Join the waitlistSources
- Swift: how long does a Swift payment take? and Swift data shows focus needed on the beneficiary leg, October 2024
- Swift: Spotlight on speed 2025 (causes of last-mile delay)
- BIS CPMI: gpi data on the drivers of fast cross-border payments, 2022
- Swift: what is a UETR? and Swift gpi
- Swift MT103 message reference (charge options, field 71A)
- HSBC Expat cut-off times; Fedwire operating hours
- Chase wire transfer FAQs; Wells Fargo wires FAQ; Barclays overseas delivery charges
- Xe: returned international payments
- EU Instant Payments Regulation 2024/886 and PSD2
- Reserve Bank of India circular on inward cross-border payments, April 2026
- US Remittance Rule, error resolution; CFPB: consumer rights when sending money abroad
- Tara Smart Account terms, checked 30 September 2026
- Sources: Swift, "How long does a Swift payment take?" and "Swift data shows focus needed on beneficiary leg" (October 2024); BIS CPMI study of 20 million gpi payments (2022), which notes the sending bank's own time is not observed.
- The $20 intermediary charge is illustrative: each bank sets its own; there is no standard tariff. Charge definitions from the Swift MT103 standard, field 71A.
- Tracker statuses from the Swift gpi standard (as documented by Oracle Banking); return reasons from the ISO 20022 code list.
