Sent money to the wrong account in India? What to do next.

It depends on what was wrong. A number that matches no account, or an IFSC that does not exist, is normally rejected and the money comes back. A number that belongs to somebody else is credited to that person, because Indian banks pay by account number, and recovering it then needs their bank and usually their consent.

That distinction decides almost everything that follows. A transfer that bounces is an inconvenience: the money takes a few days to return and you send it again to the right place. A transfer that lands in a stranger's account is a problem, because the money is no longer in the payment system. It is in somebody's balance, and they may already have spent it.

Most mistakes are small ones. A single digit typed twice, two digits swapped, an old account copied from a chat message, an IFSC from a different branch of the same bank. Each looks right at a glance, which is exactly why it gets past the person typing it.

The good news is that a wrongly credited stranger is the rarest of the outcomes, and the one that a few seconds of checking before the first payout prevents almost entirely. The rest of this guide covers what to do if it has already happened, and how to make sure it never does.

A failed transfer never reached any account: the recipient's bank rejected it, so the money is returned to the sender. A misdirected transfer did reach an account, just not the one you meant. Failed transfers resolve themselves; misdirected ones need action, because the money now sits in someone else's balance.

Common reasons for a failure are an account that has been closed or frozen, an account number that does not exist at that bank, an IFSC that does not match, or an account that cannot accept the type of credit being sent. In each case the receiving bank sends the payment back.

On ComplyRemit, if a transfer cannot be completed, the full amount debited from your US bank account is returned to you. You can watch every stage of a transfer in the activity screen, from funding through converting, sending and paying out to delivered, so a failure is visible rather than silent.

A misdirected transfer looks, from the outside, exactly like a successful one. The status says delivered. That is why the first sign is usually a phone call from the person you were paying, asking where the money is. If that call comes, check the account details on the transfer before anything else.

Often not at the moment of credit. The Reserve Bank of India's own guidance for NEFT says credit is released solely on the basis of the account number, and that it is the sender's responsibility to give the right one. A correct name beside a wrong number does not stop the money landing in the wrong account.

This surprises a lot of people sending from the US, where they assume the bank compares the name they typed with the name on the account. In India the account number is the address. The name travels with the payment, but the system is built around the number, and a payment that matches a real account is credited to it.

The same principle applies to IMPS, the instant interbank rail used for most transfers, and to RTGS for larger amounts. They are fast because they do not wait for a person to compare names.

That is why the useful check happens before you pay, not during. A verification that asks the recipient's bank who actually owns the account, and shows you the registered name, catches a wrong number while nothing has moved. Comparing that name with the person you meant to pay is the single most effective step against a misdirected transfer.

Usually the transfer is rejected or returned. The IFSC tells the payment system which bank and branch to route to, so a code that does not exist goes nowhere. If the code belongs to a real branch of a different bank, the account number will normally not match there, and the payment comes back.

The awkward case is an IFSC from a different branch of the same bank. Many Indian banks now run accounts centrally, so a payment routed to the wrong branch of the right bank can still find the account and be credited. That outcome is harmless, but it means a wrong IFSC is not always caught, and you should not rely on it to catch a wrong account number either.

The IFSC is an eleven-character code: four letters for the bank, a zero, and six characters for the branch. It is printed on the recipient's cheque book and passbook and shown in their banking app. Copy it from there, not from memory or an old message.

A returned payment takes time to come back, so a wrong IFSC still costs you days. Checking the account before the first payout avoids the round trip entirely.

A UPI ID that does not exist is rejected before any money moves. A UPI ID that belongs to somebody else resolves to their bank account, and the money is credited there. Because a UPI ID shows the registered name before you pay, checking that name is the moment to catch a mistake.

UPI IDs are short and human-readable, something like a phone number or a name followed by an @ and a bank handle. That makes them easy to share and also easy to mistype: one wrong digit in a phone-number UPI ID can belong to a real person you have never met.

Because a UPI ID points to whichever bank account its owner linked, the account behind it can change if they move banks. That is normally fine, but it is one reason to confirm the name each time you add or change a recipient rather than trusting a UPI ID from a contact list years old.

UPI payouts from the US also have a lower per-transfer ceiling than bank payouts. For a large amount, an account number and IFSC are the better choice anyway, and they give the recipient's bank a fuller record of where the money came from.

Contact your transfer provider straight away with the transfer reference, the details you entered and the details you meant to enter. Then tell the person you were paying, so they are not waiting. Speed matters: the sooner the receiving bank hears about it, the better the chance the money is still there.

On ComplyRemit, open the transfer in the activity screen and copy its reference. Start a chat in the app and choose Talk to a person, or email [email protected]. Our support team typically replies the same day, and a person can see exactly where the transfer is and what was sent where.

Write down what happened while you remember it: when you added the recipient, where you copied the details from, and when you noticed. Take screenshots of the transfer and of the message you copied the details from. If you need to escalate later, this is the record you will be asked for.

Whether a transfer can still be stopped depends on its stage. Once the money has been paid out and credited in India, it cannot be pulled back by the sender's provider: it can only be returned by the account holder, through their bank. That is why the first hour is about getting the right people involved, not about waiting to see what happens.

Do not send the money again to the right account until you have decided you can afford to. Recovery is not guaranteed, and two transfers are not cheaper than one.

Sometimes, but it is never guaranteed. The receiving bank can contact its account holder and ask them to return the money, and many people do. A bank cannot normally take money out of a customer's account without their consent or a legal order, so recovery depends on the person who received it.

The request usually travels from your provider to the bank that paid out, and from there to the recipient's bank, which contacts its customer. If the account holder agrees, they authorise a return and the money comes back along the same chain. If they do not respond, or refuse, the bank's options narrow quickly.

Where the account holder refuses to return money that was clearly not theirs, the remaining route is legal: a police complaint or a civil claim in India, which is slow and costly from abroad. For a small amount, many people decide it is not worth pursuing. For a large one, speak to a lawyer in India before you decide.

This is the honest picture, and it is the reason every step in this guide points back to checking the account before you pay. A wrongly credited transfer can be recovered. A transfer that was never misdirected does not need to be.

Complain to the bank first, in writing, and keep the reference. If it does not reply within 30 days, or you are unhappy with its answer, a complaint can go to the RBI Ombudsman through the Reserve Bank's online complaint portal. The Ombudsman examines deficiencies in a bank's service, not the stranger's refusal itself.

Under the Reserve Bank's Integrated Ombudsman Scheme, a complaint is only accepted once the regulated entity has been approached first, with proof of that complaint. It generally has to be filed within 90 days of the bank's last reply or of the deadline for one passing. The Reserve Bank's contact centre on 14448 explains the process.

Be realistic about what the Ombudsman can do. It can look at whether a bank handled your case properly: whether it contacted its customer, responded on time, or credited a payment it should have rejected. It cannot order a private person to return money they received in good faith.

The recipient you were paying is often better placed to follow this up than you are. They are in India, they may bank at the same institution, and a local branch visit with the transfer details tends to move faster than emails from abroad.

In the US, rules on international transfers give senders a window to report a suspected error to their provider, generally 180 days from the date the money was due to arrive. A mistake in the account number you typed is treated differently from an error by the provider, but report it anyway, and report it early.

There is no fixed timeline. When the account holder cooperates quickly, a return can come back within a couple of weeks. When the request passes through several banks, or the holder is slow to respond, it can take months. A returned failed transfer, by contrast, comes back on its own once rejected.

Each bank in the chain has its own process and its own queue. A request from abroad, about a customer the bank did not choose to pay, is rarely its most urgent work. Polite, regular follow-up with the transfer reference helps; long gaps do not.

Keep the person you were paying informed. If the money was for a deadline, such as school fees or a medical bill, the deadline will not wait for a recovery, and it is usually better to decide early whether you can send again rather than hope the first transfer returns in time.

A verification, often called a penny drop, asks the recipient's bank to confirm the account exists, is open and can receive money, and returns the name it is registered to. A wrong number, wrong IFSC or closed account is caught in seconds, before any of your money has been collected or sent.

On ComplyRemit, every recipient's payout account is verified with their bank before it is saved and before the first payout. It usually takes a few seconds. A recipient shows as not verified, verifying, verified or cannot be paid, so you always know whether a transfer to them will go through.

The check does two jobs. It catches details that point nowhere, which would otherwise bounce and cost you days. And it surfaces the registered name, which is the only way to notice details that point to somebody else. If the name the bank returns is not the person you meant to pay, stop and check the details with them directly.

Expect small differences in a name: initials instead of a first name, a surname first, a missing middle name, or a joint account. Those are normal. A completely different name is not, and it is far better to discover that now than after a transfer has been delivered.

Verification applies to the account, not to each transfer. Once a recipient is verified, sending to them again takes an amount and a confirmation code, with no details to retype and nothing new to get wrong.

Before any transfer leaves, we email a six-digit code tied to that exact recipient, amount and bank account. The email repeats those details, so it doubles as a final check: if the recipient or amount is not what you intended, you simply do not enter the code. It expires after ten minutes.

This is a security step first. A code bound to the transfer's details means somebody who gets into your account cannot quietly redirect a payment, because the code you receive describes the payment that would actually be sent.

It is also the last moment to catch your own mistake. Read the email rather than copying the code from a notification preview. Check the recipient's name and the last digits of their account, and check the amount, including the number of zeros. Nothing is sent until you enter the code.

If you notice something wrong at this point, leave the code unused. The transfer does not go ahead, nothing is collected from your bank, and you can correct the recipient or the amount and start again.

Be careful. A message saying a payment went to the wrong account, asking you to send it again to new details, is one of the most common payment scams. Confirm any change of account details by calling the person on a number you already have, never through the message that asked for the change.

The pattern is familiar: a relative's chat account is taken over, or a lookalike number messages you with their photo, saying their bank changed or the last transfer did not arrive, and asking you to pay a new account urgently. The urgency is the tell. Real account changes can wait for a phone call.

Another version targets the person who receives money by mistake. A stranger says they sent you money in error and asks you to send it back to a different account. Refunds of a genuine mistake go back through the bank, not to an account a stranger names.

Before you resend anything, check the activity screen. If the original transfer shows as delivered to a verified recipient whose name you recognise, the money arrived where you sent it, whatever a message says.

ComplyRemit staff will never ask you for your sign-in code, your confirmation code or your bank login, and never ask you to move money to a different account to fix a problem.

A payment to a closed account is normally rejected by the bank and returned, so the money is not lost, just delayed. Ask the recipient for their new account details, add them as a new payout account, and let it be verified before sending. Do not reuse old details from an earlier transfer.

Parents in India often keep several accounts, some opened decades ago, and older accounts are closed or merged when banks consolidate. A bank merger can also change an IFSC even when the account itself carries on. If a recipient has not been paid in a while, it is worth a quick message to confirm the account is still the one they use.

On ComplyRemit you can save more than one payout method for a recipient and choose which is primary. Adding the new account alongside the old one, and making it primary once it is verified, keeps a clean record of where earlier transfers went.

Get the details from the recipient's own bank document or app, not a forwarded message. Verify the account before the first payout and compare the registered name. Send a small first transfer when the amount that follows is large. Read the confirmation email before entering the code, and confirm any change of details by phone.

Copy, do not retype. Ask the recipient to share a screenshot of the account details screen in their banking app, or a photo of a cancelled cheque. Typing a fourteen-digit number from a voice call is how digits get swapped.

Treat the name check as the real check. The account number can look right and still be someone else's. The registered name is the part a typo cannot fake.

For large amounts, send a small test first and ask the recipient to confirm it arrived before the rest follows. It costs a day and removes the worst case entirely.

Keep recipients saved and verified rather than entering details fresh each time. Fewer keystrokes mean fewer chances to get one wrong.

Slow down when anyone is rushing you. Almost every expensive mistake, honest or fraudulent, happens when somebody says the money is needed in the next hour.

If a transfer cannot be completed, the full amount debited from your US bank account is returned. If you believe money reached the wrong account, our support team investigates with the transfer reference, follows up with the paying bank and tells you what is possible. We do not promise recovery, because that depends on the account holder.

Most of the work happens before a problem can start. Every recipient account is verified with their bank before its first payout, every transfer is confirmed with a code that names the recipient and amount, and every stage of the transfer is visible in the app with a reference you can copy for support.

When something does need a person, start a chat in the app and choose Talk to a person, or email [email protected]. Our team typically replies the same day.