How to Resolve Failed or Reversed Wire Transfers
A failed wire is not the same as a delayed wire. A delayed wire is in transit and will eventually land. A failed or reversed wire has been kicked back by the receiving bank, an intermediary, or a compliance check, and the money is now sitting somewhere along the chain waiting to be recovered.
The recovery process is not complicated, but it is time-sensitive and paperwork-heavy. This guide walks through how to identify why the wire failed, what to do first, how long refunds actually take, and when to escalate.
Failed, reversed, and returned: what actually happened
Banks use these three terms loosely, but they describe different states. Understanding which one you are in changes the recovery steps.
A failed wire was rejected before it left the sending bank. This is the easiest case. The funds were never debited from your account, or if they were debited, the reversal typically hits the same day or the next business day. You initiate again with corrected details.
A returned wire left the sending bank but was bounced back by the receiving bank or an intermediary. Common triggers include a closed beneficiary account, a mismatched beneficiary name, a wrong SWIFT/BIC, a missing IFSC on an Indian wire, or a purpose code the receiving bank cannot process for that beneficiary. The funds come back through the same chain they went out on, usually less the intermediary fees each hop deducted.
A reversed wire landed at the receiving bank but was clawed back after credit, either because the beneficiary bank identified an issue post-credit, or because a recall request from the sender was honored. Reversals after credit are the slowest to resolve because the money has to be pulled back through a settled transaction, and if the beneficiary has already moved the funds, recovery is harder.
Ask your bank explicitly which category applies. The recovery timeline and escalation path are different for each.
Step one: identify the failure cause
Every failed or returned wire generates a rejection message with a reason code. Get this from your sending bank in writing. The common reasons are surprisingly consistent across corridors.
The most frequent causes are an incorrect beneficiary account number, a beneficiary name that does not match the account, an incorrect or missing IFSC code for an Indian receiving bank, a closed or dormant beneficiary account, a purpose of remittance the receiving bank is not authorized to process, sanctions or AML flags on the sender, beneficiary, or an intermediary, and insufficient funds in a correspondent account somewhere along the chain.
If the bank gives you a vague answer, ask for the specific rejection reason from the SWIFT message. That reason code is what determines the next step. “Wire failed” is not actionable. “Beneficiary account closed” is.
Step two: fix the underlying issue before you re-initiate
The temptation after a failed wire is to immediately send again. Resist it until the reason is fully understood.
If the reason is a data error (account number, IFSC, SWIFT), confirm the corrected details with the beneficiary in writing before re-sending. Ask them to share a bank statement header or a recent transaction record showing the correct account number and IFSC. Do not rely on a screenshot of a chat message.
If the reason is a closed or dormant account, the beneficiary must reactivate the account or provide a new one, and you need written confirmation before the next attempt.
If the reason is a compliance or sanctions flag, do not just re-send. A second attempt will hit the same flag and may escalate the review. Talk to your bank’s compliance team, understand what documentation is required, and provide it before initiating the corrected wire.
Step three: track the refund
Once a wire has been returned or reversed, the funds have to travel back through the correspondent chain. This is not instant. Refund timelines depend on which hop bounced the wire and how many intermediaries need to reverse their leg of the transfer.
Typical timelines look like this.
| Scenario | Typical refund window | Notes |
|---|---|---|
| Failed at sending bank (never left) | Same day to next business day | Cleanest case |
| Returned by intermediary | 3 to 7 business days | Fees may be deducted at each hop |
| Returned by receiving bank | 5 to 10 business days | Slower on cross-corridor wires |
| Reversed after credit | 7 to 21 business days | Requires beneficiary cooperation |
| Reversed with dispute | 30 to 90 business days | Formal recall process |
Intermediary and receiving bank fees are usually retained even on a returned wire. This is one of the annoying realities of SWIFT-based transfers: a failed transfer often costs money you cannot recover, even though no funds reached the intended beneficiary.
Ask your bank for the SWIFT reference (UETR or MT103) of both the original wire and the return message. With both references, they can trace exactly where the money is at any point in the return journey.
Reality Check: SWIFT recalls are requests, not guarantees
If you asked your bank to recall a wire that had already landed at the beneficiary bank, the bank sends a SWIFT MT192 recall request. The receiving bank is not obligated to return the funds. If the beneficiary refuses, or has already moved the money, the recall fails and the sender’s only remaining path is a civil dispute against the beneficiary directly. Recalls work best when raised within hours of the original wire, and get exponentially harder after credit.
Step four: escalate if the process stalls
If the refund is stuck and the responses from your sending bank are vague, there are a few escalation levers to pull in order.
The first is to ask for a written status update with the SWIFT references. Written requests move faster than phone calls because they create a paper trail the bank has to acknowledge.
The second is to ask for a formal SWIFT investigation. Your bank can send an MT199 or MT299 investigation message to the correspondent or receiving bank asking for a status. This is a specific interbank workflow and it prompts a response.
The third is a regulatory complaint. In the US, complaints against a bank for a mishandled wire go to the Office of the Comptroller of the Currency (OCC) for national banks, or to the Consumer Financial Protection Bureau (CFPB). In India, the beneficiary can complain to the Reserve Bank of India’s Ombudsman for banking services if the receiving bank is unresponsive. Regulatory complaints often produce answers when nothing else has, but they are a last resort and take weeks to process.
Keep every wire receipt, every email, every SWIFT reference, and every phone call log with dates and names. If the escalation reaches a regulator, the paper trail is what makes the complaint credible.
What US senders should know about recovery
The recovery process rewards preparation. Senders who initiate wires with confirmed beneficiary details, a clear purpose statement, and reasonable notice to the beneficiary rarely see failures. When failures do happen, senders who know the SWIFT reference, the failure reason, and the correspondent chain fix the issue in days instead of weeks.
Rebuilding your process after a failed wire
A failed wire is a data point about how your remittance channel handles edge cases. If failures happen occasionally through the traditional wire route, that is normal. If they happen repeatedly, the channel is not the right one for your use case.
Modern payments apps built on domestic rails have very different failure modes. Instead of a multi-day recovery on a SWIFT wire, a rejected UPI transfer typically fails within seconds, refunds automatically, and gives a specific reason code you can act on immediately. Sliq Pay is one such app for US-to-India transfers: mid-market FX with no markup, instant settlement over UPI or IMPS, and a clean transaction log for reconciliation. Join the waitlist if you want a cross-border payment path that fails fast and clearly instead of failing slowly and quietly.
Frequently Asked Questions
How do I know if my wire failed or is just delayed? Ask your sending bank for the current SWIFT status. If the wire has been rejected or returned, they will have a message with a reason code. If it is still in transit, they will see it at whichever hop it is currently sitting on.
Will I get my full amount back if the wire is returned? Not always. Intermediary and receiving bank fees are often retained on returned wires. Expect to lose the wire fees even if the underlying funds come back.
How long do I have to raise a recall? There is no fixed deadline, but recalls raised within a few hours of the original wire have the highest chance of success. After 24 hours, recovery depends heavily on the beneficiary’s cooperation.
What if the beneficiary bank in India credited the wrong account? The beneficiary should raise a formal complaint with their bank immediately. If the funds have been credited to a wrong but valid account, the receiving bank can attempt a debit reversal with the account holder’s cooperation. If cooperation is not forthcoming, the process becomes a legal one. For a cleaner audit trail on future transfers, apps like Sliq Pay give you a real-time transaction status you can reference.
Do I get compensated for a bank’s mistake? Sometimes. If the sending or receiving bank was clearly at fault, you can request a fee refund and, in some jurisdictions, interest compensation for the period the funds were unavailable. This usually requires a written complaint.
Can I dispute a wire the way I dispute a credit card charge? No. Wires are treated as authorized funds transfers, not consumer purchases, and consumer chargeback rules do not apply. Recovery goes through the SWIFT recall process or a civil action.
What documents should I keep in case a wire fails? The wire confirmation, the SWIFT reference (UETR/MT103), any rejection messages, the beneficiary details you provided, and all correspondence with the bank about the failure.
Is a same-name transfer to my own account easier to recover? Yes, usually. If the beneficiary is you (an NRE, NRO, or savings account in your name), recall and recovery are far simpler because you can cooperate with the receiving bank directly.
Before You Go
A failed wire feels like a crisis when it is happening. Most of the time it is a solvable data problem or a compliance query the bank can walk through with the right reference number. Move quickly, get the failure reason in writing, track the refund, and escalate on a clear timeline. For senders who want to stop dealing with wire failures altogether, a payments app on modern instant rails removes most of the failure modes SWIFT is prone to.
Disclaimer: The information provided on this blog is for general informational purposes only and does not constitute legal, financial, tax, or professional advice. Product features, pricing, eligibility, and availability may vary by country, user type, regulatory requirements, and are subject to change. Please refer to Sliq Pay’s Terms of Use and official product pages for the most accurate and up-to-date information. Sliq Pay makes no representations or warranties regarding the completeness, accuracy, or reliability of the content.
