You sent money abroad, the funds left your account, and then — nothing. Or worse, you got an email saying the transfer failed. If you're in this situation, the first thing to know is: your money almost certainly did not disappear.
Failed international transfers are more common than most people realise. SWIFT-based bank wires fail at a rate that can reach 5-10% on certain corridors, according to industry data, often due to compliance screening or incorrect account details. Fintech platforms like Wise and Remitly have lower failure rates — but they still happen.
What follows depends entirely on where in the payment chain the failure occurred, which provider you used, and why the transfer was rejected. This guide walks through every scenario, tells you exactly where your money is at each stage, and gives you a step-by-step recovery plan.
5–10% — Estimated failure rate for SWIFT cross-border payments on complex corridors (McKinsey Global Payments Report, 2024)
The answer depends on how far the payment travelled before it failed. There are three distinct stages where a failure can occur, and each has a different outcome for your funds.
Stage 1 — Pre-dispatch failure: The transfer was rejected before it left the sending platform (Wise, your bank, Remitly). This is the cleanest outcome. Your money was never actually sent and is typically returned to your source account within minutes to 1 business day. This happens when you enter an invalid account number, when your debit card is declined, or when the platform's internal compliance check flags the transaction.
Stage 2 — In-flight failure: The transfer left the sending institution but was rejected by an intermediary bank or the recipient's bank. This is the most common scenario for SWIFT wires. Your money is sitting in a correspondent bank's suspense account while the failure is being processed. Refunds at this stage take 3–7 business days, and the sending bank may deduct a recall fee of $15–35.
Stage 3 — Delivery failure: The funds arrived at the recipient bank but could not be credited to the account. This happens when the account number is valid but the name doesn't match, the account is closed, or the recipient bank has restrictions on that currency. In this case, the recipient bank returns the funds to the sender's bank, adding another 2–5 days to the total refund timeline.
| Provider / Method | Failure Stage | Where the Money Is | Refund Timeline | Recall Fee |
|---|---|---|---|---|
| Bank wire (SWIFT) | Pre-dispatch | Held by sending bank | 1–2 business days | None |
| Bank wire (SWIFT) | In-flight | Correspondent bank suspense account | 3–7 business days | $15–35 |
| Bank wire (SWIFT) | Delivery failure | Recipient bank → return in progress | 5–10 business days | $15–35 |
| Wise | Any stage | Wise balance or refunded to source | 1–3 business days | None |
| Remitly | Any stage | Refunded to source payment method | 3–5 business days | None |
| Western Union | Pre-dispatch | Not sent; refunded to card/bank | 1–3 business days | None |
| Western Union | In-flight or delivery | Agent network hold | 3–7 business days | None |
| USDC on Stellar/Tron | Pre-broadcast | Never left your wallet | Instant | None |
| USDC on Stellar/Tron | On-chain (rare) | Funds remain on sender address | Instant (reversal not needed) | None |
If you sent a SWIFT wire and it failed mid-flight, do not resend immediately. Your original funds may still be in transit. Resending before the first transfer is recalled can result in double-sending. Always confirm the original transfer is cancelled and refunded before initiating a new one. Call your bank directly — most SWIFT recall requests require a phone or branch visit, not just an app.
1. Incorrect account details: The single most common cause. A wrong IBAN, account number, sort code, or routing number causes immediate rejection. Even a single transposed digit will result in a failed or misdirected payment. Always double-check by asking the recipient to share their bank's required fields in writing.
2. Name mismatch: Many banks now enforce Confirmation of Payee (CoP) checks — particularly in the UK and EU — which reject transfers when the recipient name doesn't match the account holder name exactly. Even common abbreviations (e.g. 'Mike' vs 'Michael') can trigger a rejection.
3. OFAC / AML compliance screening: Both sending and receiving banks run payments through sanctions and anti-money-laundering filters. Transfers involving certain countries, high amounts, or first-time recipient accounts can be held or rejected pending additional documentation. This is more likely on corridors like Iran, North Korea, Cuba, Syria, and Venezuela.
4. Recipient bank restrictions: Some banks in receiving countries have restrictions on the currencies or transfer methods they accept. For example, certain Nigerian banks temporarily restricted USD inflows during periods of FX shortages. Some Indian banks have daily limits on inward SWIFT remittances.
5. Insufficient funds or card decline: For fintech providers that fund transfers from a debit card or bank account, a real-time funds check can fail if balances change between scheduling and execution, or if your bank declines the debit as a suspicious large transaction.
6. Expired or locked recipient account: Dormant accounts, accounts with insufficient KYC on file, or accounts locked due to fraud investigations will reject inbound funds. The recipient's bank returns the money to the originating bank without notifying either party in advance.
7. Transfer amount exceeds regulatory limits: Some corridors have per-transaction or per-day caps set by central banks. For example, the Philippine central bank (BSP) requires additional documentation for inward remittances above PHP 500,000. Nigeria's CBN has had periods of daily inward caps per beneficiary.
8. Platform-side technical failures: Rare but real — if a provider's banking partner experiences an outage during settlement, transfers can be left in a pending state. Wise, Remitly, and Western Union all maintain status pages you can check for live service incidents.
Before taking any action, verify the status in your provider's app or website. 'Processing' and 'Pending' statuses are normal and do not mean failure. Most providers take 1–2 business days for standard transfers and up to 5 for SWIFT-routed payments.
Check for a notification email or in-app alert explicitly stating the transfer was 'cancelled,' 'rejected,' or 'failed.' If your transfer is still within the expected window, wait before escalating.
For Wise transfers, check the transfer status page in the app. For SWIFT wires, log in to your online banking and look at the payment history — a returned payment will appear as a credit with a reference matching your original wire.
Tip: For SWIFT wires, the 'expected delivery' date shown by most banks assumes no intermediary delays. If the date has passed by more than 2 business days, contact your bank for a trace request.
Contact your provider immediately and ask for the specific failure code or reason. For bank wires, ask your bank to provide the SWIFT return code. Common codes include: AC04 (closed account), AC01 (incorrect account number), BE04 (missing creditor address), and RC01 (incorrect bank identifier code / BIC).
For fintech providers, failure reasons are usually displayed in the app or emailed to you. Wise typically specifies whether the issue was with the recipient bank details, your funding source, or a compliance hold.
Document everything: screenshot the failure message, note the transfer reference number (UTR for UK, IMAD for US wires), and record the date and time you spoke to support. You'll need this if you need to escalate or file a complaint.
Tip: Ask your bank to provide the full MT103 SWIFT message for the failed transfer. This contains the exact return reason code from the recipient bank and will speed up any investigation.
Once the failure is confirmed, verify that a refund has been initiated. For fintech platforms, this is usually automatic — Wise refunds failed transfers to your Wise balance or the original payment method within 1–3 business days. Remitly refunds to the original debit or credit card within 3–5 business days.
For bank wires, you must explicitly instruct your bank to recall the payment if it has not already been returned. Most banks charge a recall fee of $15–35, which is non-negotiable on SWIFT-routed payments. Some banks require this request in writing or in branch.
Ask the bank to provide a recall confirmation number or reference. Follow up every 2 business days if the refund has not appeared — escalation is your right under most consumer protection frameworks.
Never resend before you've identified and fixed the root cause. If the failure was due to incorrect account details, obtain the correct information directly from the recipient — ask them to send a screenshot of their bank account details or a bank statement header. Do not rely on verbal communication for account numbers.
If the failure was a name mismatch, ask the recipient exactly how their name appears on the bank account. In the Philippines, for example, some accounts are registered in a formal legal name that differs from the everyday nickname.
If the failure was a compliance hold, your provider may ask you to submit identity verification documents or a transfer purpose declaration. Have these ready — a copy of your passport and a short written explanation of the transfer purpose (e.g. 'supporting family') is typically sufficient for consumer remittances under $10,000.
Tip: For recurring transfers to the same recipient, ask them to send you a formal bank details confirmation letter or screenshot. Save it securely — this protects you from future errors and speeds up any future investigations.
A failed transfer is also a prompt to evaluate whether you used the right provider. Bank wires are the most failure-prone option due to SWIFT's multi-hop routing and the number of correspondent banks that can reject a payment. Fintech providers like Wise route payments more directly and give clearer failure notifications.
For urgent resends where speed and reliability matter, consider crypto rails as an alternative. USDC on Stellar or Tron settles in under 5 seconds, is not subject to intermediary bank compliance checks, and is verifiable on-chain in real time. The main requirement is that the recipient has access to a regulated exchange that supports their local currency off-ramp.
Use RemitRoutes to compare all available providers for your corridor — including their typical success rates and settlement times — before resending.
On-chain USDC transfers on Stellar, Tron, or Solana are either broadcast and confirmed in seconds, or they are never submitted to the network at all. There is no intermediary bank that can reject the payment mid-flight. The main failure point is the off-ramp — the local exchange converting USDC to local currency — but regulated exchanges like CoinDCX (INR), Bitso (MXN), Luno (NGN/ZAR), and Quidax (NGN/GHS) process withdrawals reliably. If the recipient's exchange account is verified, the funds will arrive.
Misdirected payments — where the transfer succeeds but lands in the wrong account due to incorrect details — are more complex than simple failures. Unlike a rejected transfer, the money has legally been credited to another person's account.
For bank wires, you must contact your bank immediately and file a misdirected payment claim. In the US, the Electronic Fund Transfer Act gives you recourse; in the UK, the Payment Systems Regulator's Contingent Reimbursement Model (CRM) Code covers certain APP (Authorised Push Payment) fraud cases. Your bank will contact the recipient bank and request voluntary return of the funds, but this can take 2–4 weeks and is not always successful if the recipient refuses.
For fintech platforms, the process is similar — contact support immediately, provide the incorrect recipient details and transaction reference, and they will file a recall request with the recipient bank. Wise's support team typically responds within 1–2 hours for urgent cases.
Prevention is far more effective than recovery. Always confirm large transfers with a small test amount of $1–5 first. For amounts above $1,000, ask the recipient to confirm receipt of the test amount before sending the full sum.
If you sent money to an incorrect account and the recipient has already withdrawn the funds, recovery may be impossible. Banks can request return but cannot force it if the account holder refuses. The Consumer Financial Protection Bureau (CFPB) in the US notes that liability for sending to a wrong account number typically rests with the sender, not the bank — even if you made a typo. This is why verifying account details before every large transfer is critical.
If your refund has not arrived within the timeframe your provider quoted, escalate. For fintech platforms, use their in-app support to escalate to a 'payment investigation' — most have a dedicated team for this. Wise, for example, has a formal payment investigation process and will provide a case reference number.
For bank wires, ask your bank to open a SWIFT gpi (Global Payments Innovation) trace. Under SWIFT gpi, participating banks are required to complete a payment investigation within 24 hours. Ask your bank specifically: 'Is this wire routed via SWIFT gpi?' — if so, they can track the payment in real time and confirm exactly where it is in the chain.
If you are in the US and your provider is not resolving the issue, you can file a complaint with the CFPB at consumerfinance.gov/complaint. In the UK, the Financial Ombudsman Service (FOS) handles unresolved complaints against regulated payment firms. In the EU, you can escalate to the national financial regulator in the country where your provider is licensed.
Document every interaction: note the date, time, name of the agent, and what was agreed. Written complaints (email) always create a paper trail that's more enforceable than phone calls.
| Country | Regulatory Body | Complaint Portal | Timeline for Response |
|---|---|---|---|
| United States | CFPB | consumerfinance.gov/complaint | 15 business days |
| United Kingdom | Financial Ombudsman Service | financial-ombudsman.org.uk | 8 weeks max |
| European Union | National NCAs / EBA | Via licensed country's regulator | Varies by country |
| Australia | AFCA | afca.org.au | 45 days |
| UAE | Central Bank of UAE | centralbank.ae/en/complaints | 30 days |
| Canada | FCAC | canada.ca/fcac | 30 days |
Different providers have very different failure rates, refund speeds, and support quality. Use RemitRoutes to see real fees and reliability data for your specific corridor — and avoid the providers most likely to fail.
Your money is almost certainly safe. If the transfer failed before it was sent, it remains with your provider and will be returned to your account within 1–3 business days. If it failed mid-transit through the SWIFT network, it is held in a correspondent bank's suspense account and will be returned within 3–7 business days, sometimes with a $15–35 recall fee. Contact your provider immediately with your transfer reference number to confirm the refund is in progress.
For fintech platforms like Wise or Remitly, refunds typically arrive within 1–3 business days. For SWIFT bank wires, refunds take 3–7 business days if the failure was mid-transit, or up to 10 business days if the recipient bank already received the funds and is returning them. Banks may charge a recall fee of $15–35 for mid-transit failures.
The most common reasons are: incorrect account number or IBAN, recipient name mismatch, compliance/sanctions screening, recipient account closed or dormant, transfer amount exceeding regulatory limits, or a bank-side technical issue. Your provider should give you a specific failure code or reason — for SWIFT wires, ask for the MT103 return code from the recipient bank.
Not immediately. First confirm the original transfer has been cancelled and the refund is in progress, then identify and fix the root cause. Resending before the first transfer is recalled can result in double-sending if the original transfer is still processing. For SWIFT wires especially, wait for the refund to appear in your account before initiating a new transfer.
Contact your provider immediately. They will file a recall request with the recipient bank. Recovery is not guaranteed — if the recipient has withdrawn the funds and refuses to return them, recovery may require legal action. Prevention is the best approach: always verify account details with a small test transfer of $1–5 before sending large amounts.
No. On-chain USDC transfers on Stellar, Tron, or Solana either succeed in seconds or are never broadcast to the network at all — there is no mid-flight failure stage. The most likely friction point is the off-ramp exchange (e.g. CoinDCX for INR, Bitso for MXN), but regulated exchanges process withdrawals reliably once the recipient's account is verified. This makes crypto rails significantly more predictable than SWIFT-routed payments.
First, ask your bank to open a SWIFT gpi trace request — under SWIFT gpi, banks must respond to investigations within 24 hours. If unresolved, file a complaint with your national financial regulator: CFPB in the US, Financial Ombudsman Service in the UK, or your country's equivalent. Document all interactions in writing and reference your transfer's UTR or IMAD number in every communication.
Once your refund is confirmed, use a fintech platform or crypto rails for the resend rather than another SWIFT wire. Wise, Remitly, and crypto rails (USDC on Stellar or Tron via exchanges like Coinbase and CoinDCX) have significantly lower failure rates and faster settlement than bank wires. Use RemitRoutes to compare all available options for your corridor.
Compare live rates across 370+ corridors on RemitRoutes · methodology.