How to Resolve Failed or Rejected International Transfers

You send a wire, and a few days later it comes back. Or it disappears into “pending” and the recipient never sees a rupee. Or your bank sends a terse email saying the transfer was rejected without telling you why.

Failed and rejected international transfers are more common than most US senders realize. In a corridor like the US to India, where the money passes through multiple systems and sits under two different regulatory regimes, it does not take much to knock a payment off track. The good news is that the recovery playbook is short and mostly the same regardless of which bank flagged the issue. If you know what to ask for and in what order, you can usually get the funds back or reissued within a week.

Here is how to work through it.

Failed vs Rejected vs Delayed

These get used interchangeably, but they are not the same thing and the fix depends on which one you are dealing with.

A delayed transfer is still moving. The money left your account and is somewhere in the chain, waiting on a compliance review, an intermediary bank, or a cut-off window. It has not been rejected. This is usually a wait-and-trace situation, not a recovery one.

A failed transfer is one where the payment never left your bank successfully, or was returned mid-flight because of a technical error. You should either see the debit reversed on your account or a bank notice that the wire did not go through.

A rejected transfer is one that reached the recipient’s bank (or an intermediary) and was refused. The money then reverses back through the chain toward you, minus any intermediary fees that got deducted along the way.

Knowing which of the three you have determines your next call.

Step 1: Identify Why It Failed

Before you can fix anything, you need to know the reason code. Some banks give you this in the initial notification. Others make you dig for it.

The usual suspects:

• Incorrect recipient details. The most common cause. A wrong SWIFT/BIC code, an IBAN or account number that does not exist, a recipient name that does not match the account holder, or a missing IFSC code for an India-side transfer.
• Sanctions or AML rejection. The recipient’s name partially matches a sanctions list, or the transaction pattern triggered anti-money-laundering flags on either side.
• Regulatory rejection. The transfer’s purpose does not fit the destination country’s rules. For India, an incoming USD transfer with an unclear or ineligible purpose can be bounced under FEMA or RBI reporting requirements.
• Account status issues. The recipient’s account has been closed, is dormant, is frozen, or cannot receive foreign currency.
• Amount limits. The transfer exceeds the recipient bank’s per-transaction cap or the sender’s own outbound wire limit.
• Wrong currency or wrong beneficiary bank. You sent USD to an account that only accepts INR, or specified a branch code that does not handle international payments.

Get the exact reason in writing. If the initial email is vague, call your bank and ask specifically for the SWIFT rejection code (they look like AC01, BE04, RC03, etc.) or the plain-English reason the receiving bank gave. Without the reason, you are guessing at the fix.

Step 2: Take Corrective Action Based on the Reason

Once you know the cause, the fix usually fits one of a few patterns.

For incorrect details: confirm the correct information with the recipient in writing, from their bank’s app or a recent statement. Do not correct details from memory. Once you have the right information, most banks will let you resend as a new transfer once the failed funds hit your account. Some allow a “repair and reissue” on the same wire, but this is bank-dependent and can add its own delay.

For sanctions or AML rejection: contact your bank’s compliance team, not the general support line. Be ready to provide identity documents for the recipient, proof of your relationship (family, employment, contract), and proof of the source of funds. If the recipient name is a false-positive match on a watchlist, resolving it can require a letter from your bank to their bank clearing the name.

For a regulatory rejection on the India side: confirm the purpose of the transfer matches an allowed FEMA category. Family maintenance, gifts within limits, contractor payments, tuition, and medical treatment are common allowed purposes. If your original transfer had a vague or wrong purpose code, resending with the correct one usually clears it. If the underlying purpose is not eligible (for example, sending USD directly to a personal Indian account for a business transaction that should go through a business-to-business channel), you may need to change the receiving structure entirely.

For account status issues: ask the recipient to confirm with their own bank that the account is open, active, and permitted to receive foreign inward remittances. NRE and NRO accounts have different rules from regular savings accounts; a mismatch here bounces the wire.

For amount limits: split the transfer into multiple smaller ones under the limit, or use a rail that supports the larger amount. The India side has real caps on instant rails: 200,000 INR via UPI, 500,000 INR via IMPS. Above those, settlement takes hours rather than seconds but still goes through.

Step 3: Track the Refund

If the transfer was rejected mid-chain, the money reverses back through the same correspondent path it took outbound. That is not instant.

Typical refund timelines:

• Same-day rejection at your own bank: funds reappear in your account the same or next business day.
• Rejection at an intermediary bank: 3 to 5 business days for the reversal to complete.
• Rejection at the receiving bank: 5 to 10 business days, sometimes longer if the funds sit in a suspense account on their end while their compliance team reviews.

Two things to know about refunds:

Intermediary banks may still deduct their fees from the returning wire. It is not uncommon to see a $20 to $50 gap between what you sent and what comes back, even on a full “rejection.” This is separate from your own bank’s wire fee.

The FX rate you get on the reversal is not always the same as the rate you sent at. If USD/INR moved against you between the send and the reversal, you can lose money on the round-trip even though the transfer never completed.

Reality Check: A “failed” international wire is not a free do-over. The FX movement plus intermediary fees can cost you 1 to 3 percent of the transfer amount by the time the money is back in your account, before you have even tried again.

Step 4: Escalate When You Are Stuck

If you have not gotten a clear answer or a refund within the expected window, escalate. In order:

Ask your bank to initiate a SWIFT trace using the transfer’s UETR (Unique End-to-End Transaction Reference). This forces every bank in the chain to report where the money currently sits. Traces usually complete in 2 to 5 business days.

If the trace does not resolve it, ask for the case to be escalated to the international payments operations team, not the front-line support desk. Get a case reference number and a named contact.

If your bank is unresponsive, file a complaint with your national banking regulator. In the US that is the CFPB for consumer accounts and the OCC for national banks. For India-side accounts, the recipient can file a complaint with the RBI Ombudsman. Regulator complaints are free and often get faster movement from the bank than direct calls do.

Keep a written log of every interaction: date, time, who you spoke to, what they said, and what they committed to. If the matter escalates to a regulator, this log is what determines how quickly it gets resolved.

Comparison: Failure Modes and Fixes

Failure Reason	Typical Fix	Recovery Time
Wrong SWIFT / IFSC / account number	Confirm correct details, resend	3 to 7 business days
Sanctions or AML flag	Provide documentation to compliance team	5 to 15 business days
Wrong or ineligible purpose (FEMA)	Resend with correct purpose code	3 to 5 business days
Recipient account closed or dormant	New payout method or new recipient	5 to 10 business days
Amount above receiving bank cap	Split into smaller transfers or change rail	1 to 3 business days

Avoiding a Second Failure on the Resend

If the original transfer failed for a details or purpose reason, do not resend on the same rails without changing what caused the problem the first time. That sounds obvious, but it is a common mistake, especially when the sender is frustrated and just wants the money to go.

A few habits that prevent repeat failures:

Confirm every digit of the recipient’s account number, SWIFT code, and IFSC code by having them screenshot it from their bank app. Reading it over the phone is where most errors creep in.

Match the recipient name character for character to what appears on their bank statement. Middle names, initials, and honorifics matter. “Priya Sharma” and “Priya K Sharma” can be treated as different account holders by strict banks.

Pick the correct purpose code. For US-to-India transfers, common accurate purposes are family maintenance, personal gift, contractor payment, tuition, and medical treatment. If none of those fit, ask before you send rather than picking the closest-sounding one.

For US-to-India specifically, using rails that plug directly into UPI or IMPS on the India side avoids the SWIFT correspondent chain entirely. That removes intermediary rejections, most cut-off delays, and the “refund is $30 short” problem. Sliq Pay is built on those rails and sends USD from a US bank account directly to a recipient’s UPI ID, phone number, email, or Indian bank account. Transfers within the instant caps land in seconds, and rejections at intermediary banks stop being a category of failure because there are no intermediary banks.

FAQs

How do I know if my transfer failed or is just delayed?

Ask your bank for the current status using the UETR or wire reference number. “In progress” or “pending correspondent bank” means it is still moving. “Returned,” “reversed,” or “rejected” means it failed and the money is coming back. If your bank cannot tell you which of those it is, that itself is a red flag worth escalating.

Can I cancel a rejected international transfer before the refund lands?

There is nothing to cancel if the transfer has already been rejected. It is already reversing. What you can do is confirm with your bank that they are treating it as a reversal (not a re-attempt) and get an expected refund date.

Will I get all my money back on a failed transfer?

Most of it, usually. Your own bank’s wire fee is often non-refundable. Intermediary banks may deduct fees from the returning wire. FX movement between send and reversal can add or subtract another percent or two. Instant-rail providers that route USD-to-India transfers directly into UPI or IMPS avoid the intermediary deduction problem entirely, so a failed transfer on those rails returns the full amount.

Why do international transfers get rejected for compliance more than domestic ones?

Cross-border payments are screened under both the US Bank Secrecy Act and the destination country’s regulations (in India, FEMA and RBI rules). Both sides run automated screening on every incoming and outgoing wire. Domestic ACH or Zelle transfers only screen against one country’s rules, so the surface area for a compliance flag is smaller.

My transfer was rejected because of the purpose. How do I know which purpose code to use?

For US-to-India transfers, RBI publishes a list of allowed purpose codes for foreign inward remittances. Family maintenance, personal gifts within LRS limits, freelance and contractor payments, tuition fees, and medical treatment are the most common valid categories for individual transfers. Picking the right code before sending is the customer’s responsibility, and having it decided before you start the transfer avoids a compliance round-trip later.

Is there a way to send US-to-India money that basically never gets rejected?

Rejection at intermediary banks is the single biggest cause of failed cross-border wires. Removing intermediaries by using direct-rail providers into UPI and IMPS removes that entire category of failure. You still need correct recipient details and a valid purpose, but the “your wire got bounced back by a correspondent bank” scenario stops being possible.

Before You Resend

A failed transfer is not the end of the story; it is a chance to fix what broke and get it right the second time. Confirm the reason, correct the underlying issue, and pick a rail that matches the corridor you are sending to. For US-to-India transfers, moving off legacy SWIFT wires and onto UPI or IMPS rails removes most of the recurring failure modes at once. Sliq Pay is one way to do that if you are sending regularly to India.

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.