How to recover money sent to the wrong UPI ID

Three things that look alike on a phone screen have three completely different remedies, and people lose weeks by pursuing the wrong one. The first is a failed transaction: your account was debited and the beneficiary was never credited. The second is an unauthorised transaction: money left your account on an instruction you never gave. The third — this page — is a successful transaction that went to the wrong real person because you gave the wrong identifier.

For the first, the Reserve Bank's circular on harmonisation of turn around time and customer compensation does the work for you. It defines a failed transaction as one not completed "due to any reason not attributable to the customer such as failure in communication links, non-availability of cash in an ATM, time-out of sessions", prescribes auto-reversal timelines across UPI, IMPS, cards, ATMs and prepaid instruments, and requires compensation for delay to be paid suo motu — without a complaint from you. That framework is generous precisely because the customer did nothing wrong.

For the second, the Reserve Bank's July 2017 directions on limiting customer liability in unauthorised electronic banking transactions apply. They set out zero liability where the loss arises from a fault at the bank's end or from a third-party breach reported within three working days, limited liability on a sliding scale for slower reporting, and a requirement that the bank credit the disputed amount back within ten working days of your notification while it investigates. Again, the trigger is that the transaction was not authorised by you.

Your case is neither. You authorised it, you entered your UPI PIN, and the payment system executed the instruction it was given. That is not a deficiency in service by anybody, which is why the two most protective frameworks in Indian retail payments both step aside. The consequence is unwelcome but it is worth internalising early: there is no rule that entitles you to your money back, and the ₹100-per-day style compensation you may have read about does not attach to this at all.

It matters practically because the language you use decides where your complaint is routed. If you tell a call centre that a transaction "failed", it will be logged as a failed-transaction dispute, investigated against the switch logs, closed as "transaction successful" within a day or two, and you will have burned the most valuable seventy-two hours you had. Say instead that the transaction was successful but credited to an unintended beneficiary, and ask for a beneficiary credit reversal request to be raised.

There is one exception worth naming. If you were tricked into sending the money — a fake customer-care number, a QR code sent by someone impersonating a buyer, a "refund" that required you to pay first — that is fraud, not a mistake, and it belongs on a different track entirely: the National Cyber Crime Reporting Portal and the 1930 helpline, in parallel with the bank. The faster that route is triggered, the higher the chance the funds are frozen before they are layered away. Be honest with yourself about which of the three you are in, because the wrong framing does not just waste time — it makes you look evasive later, when the Ombudsman reads the file and finds three inconsistent descriptions of the same event.

The single most useful thing to understand is that Indian payment systems credit an account number, not a name. The Reserve Bank's NEFT FAQ says it in the plainest possible terms: "The credit is given to the account number written / given by remitter in his / her application / instruction", and "It is the responsibility of remitting customer to write correct account number." The RTGS FAQ repeats the position — credit is given "solely based on the account number provided" — and advises that "extreme care should be exercised in providing the account number of the beneficiary".

UPI adds a layer of protection that people over-trust. Because a virtual payment address is resolved to an account and the app shows you a name before you pay, it feels as though the system has verified the person. It has verified the account behind the identifier; it has not verified that the account belongs to the person you have in mind. Bank-registered names are frequently abbreviated, transliterated or a spouse's or a business's, so a name that looks close enough is a weak check, and the two-second pause before entering the PIN is the last point at which the transaction is yours to stop.

After the PIN, finality is the design. UPI settles between banks through infrastructure operated by NPCI, which the Reserve Bank describes as "an umbrella organisation for operating various Retail Payment Systems" under the framework of the Payment and Settlement Systems Act, 2007. Settlement finality is what makes a real-time rail usable at all — a merchant who releases goods against a UPI credit needs that credit to be irreversible. The same property that makes the system trustworthy is the property that makes your mistake sticky.

So there is no cancel button, and an app that offers to "raise a reversal" is not offering to take the money back. Google Pay's India help page states that cancelling after PIN entry is not possible, tells the user to contact the recipient or the merchant and ask for a refund, and only then to approach the bank with the UPI reference and NPCI's dispute mechanism. That sequence is not the app being unhelpful; it is an accurate description of who holds the power in this situation, and the answer is the person who received the money.

What the intermediaries can do is a defined and genuinely useful thing. Your bank, as the remitter's bank, raises a request with the beneficiary's bank. The beneficiary's bank contacts its account holder and seeks consent to debit the amount and return it. If consent is given, the funds come back through the same rails, usually within days. If consent is refused or the customer does not respond, the beneficiary's bank cannot force the debit — and its refusal to do so is not a service failure it can be penalised for.

This is why timing dominates outcome. An account that still holds the money when the request arrives can return it in one instruction. An account that has already spent it presents the bank with nothing to return even if its customer is willing, and a willing recipient who has spent the money becomes a debtor rather than a source of an instant refund.

Open the transaction in your UPI app and screenshot the full detail view, not the toast notification. You want the UPI transaction ID — the twelve-digit reference, sometimes shown as the UTR or RRN — the date and exact time, the amount, the payee's virtual payment address as it was entered, the masked account and IFSC if the app shows them, and the displayed beneficiary name. That reference number is the only key every downstream body will search on, and everything you do afterwards is quoted against it.

Screenshot the bank's SMS or email alert as well. It is generated by a different system from the app and it independently timestamps the debit, which matters if the app's record is later disputed, or if you were using a third-party app on an account held at another bank.

Now raise the grievance inside the app itself, through the help or "report a problem" flow on that specific transaction, choosing the option that describes an incorrect or unintended beneficiary rather than a failed payment. ClearTax's walkthrough of the process advises reporting a wrong transfer within 24 to 48 hours to improve the chances of recovery, and that is consistent with what actually determines the outcome — whether the money is still sitting in the account when the request lands. Note the ticket number the app issues; it is distinct from the UPI transaction ID, and you will need both.

If you know or can guess who received the money — a neighbour whose number is one digit from your intended payee, a contact whose name sat next to the right one — contact them directly and ask. Do it politely and in writing, on a channel that preserves the message. Most honest recoveries happen here, in the first few hours, without any institution being involved, and a screenshot of a WhatsApp message asking for the money back is evidence of demand that supports everything you do later.

Do not send a second payment to the same person "to test" anything, and do not accept an offer to return the money by a route that requires you to scan a QR code or approve a collect request. A collect request pulls money from you; approving one is how a straightforward mistake turns into a fraud loss. A genuine return is initiated by them, needs nothing from you but your UPI ID, and requires no PIN on your side.

The app grievance is not a substitute for a complaint to your bank. The bank is the regulated entity in this relationship; it is the one that can raise a beneficiary credit reversal request with the other bank, and — critically — it is the one whose conduct the Ombudsman can later examine. A complaint that never went to the bank in writing has nowhere to escalate to.

The Reserve Bank's own NEFT FAQ sets the sequence: "approach grievance redressal cell of your bank with details", and if the grievance is not resolved within 30 days, file under the Integrated Ombudsman Scheme. The RTGS FAQ says the same. That 30-day period is not a suggestion you can waive by being frustrated; it is the condition that makes the next rung available, and it starts running from the date of a complaint you can prove you made.

Use a channel that generates a docket. The bank's online complaint form, its designated grievance email address, or the Customer Facilitation Centre listed on its website all work; a phone call to a call centre does not, because nothing survives it. Every bank publishes a Customer Facilitation Centre for payment system queries and a nodal grievance officer above it, and both are worth using in that order.

Write it tightly. State that on the given date and time you made a UPI payment of the stated amount bearing the stated transaction reference; that the payment was successful; that it was credited to an unintended beneficiary because of an error in the identifier you supplied; and that you require the bank to raise a beneficiary credit reversal request with the recipient's bank and to inform you of the outcome in writing. Attach the screenshots. Ask for the complaint number in the acknowledgement.

Ask two specific questions in the same complaint, because the answers become the spine of any later escalation. First: on what date did you raise the request with the beneficiary bank, and under what reference? Second: on what date did the beneficiary bank respond, and what did it say? A bank that has done its job will answer both. A bank that has done nothing will produce a generic closure note saying the transaction was successful, and that mismatch is exactly the deficiency in service the Ombudsman exists to look at.

Escalate inside the bank once, promptly, if the first reply is a template. Every scheduled commercial bank has a principal nodal officer for grievances and an Internal Ombudsman to whom complaints the bank proposes to reject must be referred before the rejection is communicated. You do not approach the Internal Ombudsman yourself, but a flat rejection that shows no sign of that referral is a point worth making in writing.

NPCI operates the UPI switch and runs a dispute redressal mechanism that sits behind the apps and the banks. It is not a regulator and it cannot order anybody to pay you; what it does is give a complaint a home in the system that owns the transaction, and produce a reference that the participating banks have to work against.

There is a UPI helpline for exactly this. Google's help page for Google Pay in India directs users who cannot get resolution from the recipient or their bank to file a complaint with NPCI through its dispute redressal mechanism or to call 1800-120-1740, and ClearTax's walkthrough names the same number as the route to a formal complaint. It is a toll-free number and it is worth calling early, because it costs nothing and it creates a record independent of your bank.

The online route runs through the dispute redressal section of NPCI's UPI pages, where you choose the transaction category and then the nature of the issue. The category you want is the one describing an amount incorrectly transferred to another account, not a debit without credit. You supply the UPI transaction ID, your bank, the amount, the date and an email address, and you receive a complaint reference number you can use to check status later.

Understand what NPCI's involvement changes and what it does not. It changes whether the two banks have a shared, timestamped record of the dispute and a mechanism for exchanging the reversal request; it does not change the recipient's freedom to say no. Reporting on the current rules is consistent on this point — the sender's bank raises the reversal request through NPCI's process, the recipient's bank seeks consent from its account holder, and only if that person agrees can the amount be returned. If they refuse or ignore it, the banks cannot debit the account.

The practical value is therefore evidentiary as much as operational. When you later tell the Ombudsman that your bank sat on the matter, an NPCI complaint reference dated three days after the transaction is very hard to argue with, and when your bank says it "raised it with NPCI", you have a number against which to ask what became of it. Do not file the same dispute five times through five channels on the same day. Duplicate complaints across the app, the bank, the helpline and the portal get de-duplicated, and the visible effect is a string of closures that reads, to anyone looking at the file later, like a series of rejections. File once in each place, in the order given on this page, and follow up on the references rather than opening new ones.

One caution about the portal: it is a low-traffic corner of the internet, and there are convincing imitations of it alongside paid “UPI complaint” services and fake helpline numbers that rank well in search results. Reach the dispute page from npci.org.in itself rather than from a search result, and never give anyone your UPI PIN, an OTP or remote access to your phone as part of a “refund process”. No legitimate step in any of this requires you to authorise anything.

The scheme in force changed recently. The Reserve Bank – Integrated Ombudsman Scheme, 2026 took effect on 1 July 2026 and replaced the 2021 scheme, which continues to govern complaints filed before that date. The architecture is unchanged: one scheme covering commercial banks, regional rural banks, eligible co-operative banks, non-banking financial companies, non-bank prepaid payment instrument issuers and credit information companies, with a centralised receipt and processing centre so you do not have to work out which office has jurisdiction. Some Reserve Bank FAQ pages, including the NEFT and RTGS ones, still referred to the 2021 scheme at the time of writing.

Two conditions decide whether the Ombudsman entertains your complaint, and it is free and needs no lawyer once they are met. You must have complained to the bank first and given it the prescribed period — reported as 30 days, or the entity’s own published timeline where that is longer — and you must then file within the window the scheme allows. Reporting on the 2026 scheme, and the Reserve Bank’s own FAQ document, describe a filing window of 90 days running from the expiry of that period, considerably tighter than the one-year limitation the 2021 scheme carried. Treat it as a hard deadline and confirm the current wording on rbi.org.in before relying on any number.

Filing is straightforward. The primary route is the Complaint Management System at cms.rbi.org.in, which issues an acknowledgement and a complaint number immediately and lets you track status. Complaints can also be emailed to [email protected] or posted to the Centralised Receipt and Processing Centre at Chandigarh, and there is a toll-free helpline on 14448 — all three are given on the Reserve Bank's own NEFT and RTGS FAQ pages.

Now the honest part, and it is the reason this section sits fifth rather than first. The Ombudsman adjudicates deficiency in service by a regulated entity. It does not adjudicate a dispute between you and a stranger who has your money. It can find that your bank failed to raise the reversal request, failed to raise it promptly, failed to follow up with the beneficiary bank, failed to respond to you within its own published timelines, or closed your complaint on a false premise — and it can award compensation for the loss that flowed from that failure. It cannot order a person who is not a party to the scheme to return anything.

Where it bites hardest is delay. If your bank took three weeks to send a request that should have gone the same day, and the account was drained in week two, the causal link between the bank's inaction and your loss is the case, and it is a real one. Reporting on the 2026 scheme describes the Ombudsman as able to award up to ₹30 lakh for consequential loss and up to ₹3 lakh for time lost, expenses and mental anguish, with 30 days to appeal an award to the appellate authority. Those figures come from the scheme text and are revised from time to time, so check the current version.

Frame the complaint accordingly. "Someone else has my money" is not a maintainable complaint. "My bank was notified on the 3rd, told me on the 21st that it had raised a request, has never given me the date on which it did so or the beneficiary bank’s response, and closed my complaint as 'transaction successful' without addressing what I actually asked" is a complaint about service, with dates, and it is the version that gets decided. Recovering money from a stranger is not itself a service failure — which is why the Ombudsman route and the civil route in the next section answer two different questions, and often need to run together.

A large minority of these cases end with a person who has the money, knows they have it, and will not give it back. At that point the payments system has done everything it can, and the question stops being a banking question. The first thing to establish is what you can actually prove and what you can identify. You will have the transaction reference, the amount, the date, the virtual payment address you paid, and possibly a masked account number and the beneficiary bank's name. You will not have the person's name, address or full account number, because your bank cannot give you another customer's details. That asymmetry is the practical obstacle, and every route from here is in substance a way of putting the question in front of somebody who is allowed to see those details.

A police complaint is one such route. Where the recipient has been asked to return money that is plainly not theirs and has refused, keeping it is not merely uncharitable, and a written complaint to the local police station or the cyber cell — with the transaction record, the demand you made and the refusal — asks the police to identify the account holder and act. Whether an FIR is registered depends on how the facts are characterised and on the amount involved, and a station may prefer to treat a genuine mistake as a civil matter. Take the written complaint and its acknowledgement either way; it is evidence of demand and refusal.

If the payment was induced by deception rather than caused by your own slip, that is unambiguously the cybercrime route: the National Cyber Crime Reporting Portal and the 1930 financial fraud helpline, immediately, alongside the bank. Do not use that route for an honest mistake — a false fraud report against an identifiable person creates its own problems — but do not hesitate over it if you were misled into paying.

The civil route is the one that actually matches the legal shape of the problem. Money paid by mistake, received by someone with no entitlement to it, is recoverable; the claim is for recovery of the sum, and the fact that the recipient did nothing wrong in receiving it does not entitle them to keep it once they know. In practice this means a lawyer's notice first — cheap, often effective, and it converts an ignored WhatsApp message into a documented demand — and then a suit for recovery if that fails.

The civil route is the one that matches the legal shape of the problem. Money paid by mistake, received by someone with no entitlement to it, is recoverable; the claim is for recovery of the sum, and the fact that the recipient did nothing wrong in receiving it does not entitle them to keep it once they know. In practice that means a lawyer’s notice first — cheap, often effective, and it converts an ignored message into a documented demand — then a suit for recovery if it fails. Consumer forums are a poor fit for the core claim, because the person holding your money is not a service provider to you, although a complaint about how your own bank handled the matter can sit there.

The principle is identical across every retail rail in India, and the Reserve Bank states it most explicitly for the older ones. Its NEFT FAQ says credit is given to the account number the remitter supplied and that ensuring the number is correct is the remitting customer's responsibility. Its RTGS FAQ advises extreme care in providing the beneficiary account number and confirms that credit is given solely on that basis. A name that does not match the account number does not stop the credit.

Two things differ in practice. First, on NEFT, IMPS and RTGS you typically add a beneficiary before you can pay them, which introduces a deliberate pause and, on most banks, a cooling-off period on the first transfer — so the error is likelier to have been made once, at the point of adding the beneficiary, and then repeated silently every month. If you discover a wrong beneficiary, check whether you have paid them before; the older payments have their own references and their own recovery prospects, and the sum at stake may be much larger than the payment that made you notice.

Second, the failed-transaction position differs. RTGS has its own rule for payments that cannot be applied: the Reserve Bank's RTGS FAQ says funds received by a member bank that cannot be credited are returned to the originating bank within one hour of receipt or before the end of the RTGS business day, whichever is earlier, with compensation at the repo rate plus two per cent where the return is delayed. That is a rule about credits that fail, not credits that succeed to the wrong person, and it will not help you here — but it is worth knowing, because a payment rejected for a closed or frozen account does come back on its own.

The recovery sequence is otherwise the same and in the same order: complain to your branch or the bank's grievance cell in writing with the UTR, ask specifically for a reversal request to be raised with the beneficiary bank, get the dates of the request and the response, wait the prescribed period, then escalate to the Ombudsman under the integrated scheme. The Reserve Bank's own NEFT and RTGS FAQs set out that escalation route, including cms.rbi.org.in, [email protected] and 14448.

Whichever rail it happened on, keep the whole file in one place and in date order — the transaction screenshot, the bank alert, the app ticket, the written complaint and its acknowledgement, every reply, the NPCI reference, and anything you sent the recipient. If this ends in a lawyer’s notice or an Ombudsman complaint, that bundle is the case. And the habit that prevents the next one is reading the account number or the virtual payment address back against the source you were given, rather than against your memory of it.