You sent money to the wrong account in Nepal

Nepal's retail payment rails are built around finality. Once a payment instruction has been authenticated and settled, the system treats it as done, because a system in which settled payments can be pulled back on request would be unusable for the merchants, employers and government offices that depend on money staying where it lands. Nepal Clearing House Limited operates most of the account-to-account infrastructure — the cheque clearing system NCHL-ECC, the interbank fund transfer system NCHL-IPS, connectIPS, connectRTGS, corporatePAY and NEPALPAY QR — with, by its own count, 54 bank and financial institution members and more than a hundred non-bank members, under the leadership and guidance of Nepal Rastra Bank.

The consequence is that there is no cancel button anywhere in the chain. The connectIPS FAQs are explicit that payments made through the platform cannot be stopped or reversed through the system, and that for a transaction-specific issue you should contact your own bank's customer service, which may in turn take it to NCHL. Notice the direction of travel: you talk to your bank, your bank talks to the infrastructure. You do not have a direct line to the clearing house and you do not need one.

The wallets say the same thing in their own language. Khalti's dispute policy states that because the app makes you confirm the receiver's name and photo before sending, funds sent by mistake to another Khalti user cannot be reverted, and lists mistaken transfers due to user negligence among the categories it will not hear. That is a harsh sentence to read on the day it applies to you, but it is honest about where the responsibility for the keystroke sits.

What does exist, and what people miss, is the hold. eSewa's dispute page describes placing a hold on all funds related to a disputed transaction, restricting them so they cannot be withdrawn while the dispute is open or until it is closed. That is not a reversal; it is a freeze. Its entire value is that it stops the money leaving the recipient's account while the two of you talk, and it only works if you report the transaction before the recipient spends or withdraws the balance. Every hour you spend re-reading your own transaction history instead of reporting it is an hour in which the freeze becomes worthless.

It is also worth separating the case where you paid a real, registered merchant from the case where you paid a private individual. If the wrong recipient is a business — the wrong shop's QR, the wrong biller, the wrong merchant code — you are in a refund conversation with an entity that has a licence, a settlement account, a grievance officer and a strong reason to behave well. Fonepay, for example, describes refunds as something the merchant initiates from the Fonepay Business App, choosing a full or partial refund against the transaction. If the wrong recipient is a private person with a wallet and no reason to care, you are in a persuasion exercise backed by a hold and, eventually, by a police complaint.

One last distinction that saves people a great deal of wasted effort. If the digits you typed belong to nobody — a closed account, an account number that fails validation, a wallet ID that does not exist — the transfer usually will not complete at all, and you are back in the reconciliation case that resolves itself. Money genuinely stuck in the middle is a technical problem with a technical fix. Money sitting in a stranger's account is a human problem, and no amount of shouting at a helpdesk converts one into the other.

Stop and screenshot before you do anything else. Capture the transaction detail screen exactly as it appears in your banking app, wallet or connectIPS history: the amount, the date and time, the transaction or reference number, the sending account or wallet ID and, crucially, the receiving account number or wallet ID and whatever name the app displayed for it. Screenshots taken later, after a status changes or a list scrolls, are never as good, and the reference number is the single identifier every desk you deal with will index your case by.

Save the confirmation SMS and any email receipt. Do not delete them to tidy your inbox, and do not rely on being able to find them again in a thread of two hundred bank messages. Forward them to your own email address so that you have a copy that survives losing the phone, and note the exact timestamp — Nepali payment records are usually timestamped to the second, and a dispute is far easier to trace when you can name the second rather than the afternoon.

Report it to the sending institution immediately, by whichever channel is fastest, and then again in writing. The order matters: a phone call gets a human looking at the transaction inside minutes, and a written report creates the record that a regulator can later look at. eSewa asks for dispute details to be emailed to its customer service desk and answers a toll-free line — 1660-01-02121 from NTC numbers and 1810-21-02121 from Ncell numbers. Khalti asks for disputes in writing to its dispute address and lists a support line and toll-free number, and says its grievance desk addresses issues within 72 hours. Fonepay runs a complaint portal, a support email and a phone line with a named grievance officer.

Ask, in those words, for a hold to be placed on the funds. Do not ask for the transaction to be reversed, because the answer to that is no and the conversation stops there. Ask for a hold, a block, or a restriction on the credited amount pending dispute. eSewa's published process is built around exactly that mechanism, and asking for it by name tells the person on the other end that you know what is actually available.

Get a reference for the report itself, separate from the reference for the transaction. A complaint number, a ticket number, a case ID, or at minimum the name of the officer you spoke to and the time you spoke to them. If you later have to escalate to Nepal Rastra Bank, the portal expects you to have complained to the provider first — so the evidence that you did, and when, is part of your file.

If you know who received the money, contact them directly and civilly, in writing, on a channel that preserves the conversation. A wrong digit in a phone number frequently lands money with somebody whose number is one off yours, or on an old number belonging to somebody you used to pay. A polite message with the transaction reference and a request to return it works far more often than people expect, and the message thread itself becomes evidence — eSewa's dispute process asks for all messages and conversations between the parties.

Finally, write a one-page timeline while it is fresh. What you intended to send, to whom, what you actually did, what the app showed you at each step, when you reported it and to whom, and what you were told. Every subsequent desk will ask you to recount it, and a written account you can hand over is worth more than a memory that drifts. This costs ten minutes and it is the difference between a case that reads as careless and a case that reads as documented.

If you moved money between bank accounts — mobile banking, internet banking, connectIPS, an over-the-counter transfer or a standing instruction — the route runs through your own bank first. connectIPS is unambiguous that for a transaction-specific query you contact your bank's customer service, and that the bank may take it to Nepal Clearing House Limited as required. There is no customer-facing dispute desk at the clearing house and no purpose in trying to find one.

Go to the branch, not the call centre, if the amount matters. Take a printed or written application addressed to the branch manager setting out the transaction reference, the date and time, the amount, the account you meant to credit and the account you actually credited, and asking the bank to contact the beneficiary bank to request a hold and a return of the amount credited in error. Attach your screenshots and your statement page. Ask the branch to acknowledge receipt on your copy, with a stamp and a date. That acknowledged copy is the document that makes every later escalation work.

Understand what your bank is actually going to do with it. It cannot debit the beneficiary's account: that account belongs to a customer of another institution, protected by that institution's obligations to its own customer. What it can do is write to the beneficiary bank, identify the credit, and ask that bank to place a lien or hold on the amount and to seek the account holder's consent to return it. The refund, when it comes, is initiated from the receiving side — the crediting institution acting on its own customer's instruction.

That is why the beneficiary bank's cooperation is the hinge of the whole thing, and why it is not automatic. A bank that freezes a customer's balance on the say-so of a stranger's bank exposes itself, so most will hold pending the customer's response rather than hold indefinitely. If the customer agrees, the money comes back quickly. If the customer refuses or does not respond, the bank's position is that it cannot take money out of a customer's account without either consent or a legal order, and you are into a slower route.

Keep chasing in writing at fixed intervals rather than continuously. A polite written follow-up every few working days, referencing your acknowledged application and its date, builds a record. Daily phone calls to a branch officer do not. If the officer handling it changes, ask for the new name in writing. If the branch tells you the beneficiary bank has not responded, ask them to say that to you in writing too, because that sentence is exactly what Nepal Rastra Bank's grievance system exists to act on.

The special case worth naming is a transfer to an account at your own bank. Here the whole problem sits inside one institution: the same bank holds both accounts, can see both balances, and can approach its own customer directly. These are the cases that resolve fastest and they are the ones where a same-day visit to the branch genuinely changes the outcome. Do not treat an internal transfer as less urgent because it went nowhere far.

If the amount is large, take advice early rather than late. Nepal's Acts and Codes are published by the Nepal Law Commission, and a lawyer can tell you whether a civil claim against the recipient is proportionate to the sum involved. For most everyday amounts it is not, which is precisely why the hold-and-persuade route matters so much — it is the only route that is cheap enough to be worth using.

The wallets publish their dispute processes, which is more than most Nepali financial services do, and the two published processes are not the same. Read the one that applies to you rather than assuming the other applies as well, because the deadlines differ and a missed deadline ends the matter.

eSewa asks you to email the details of the transaction and the contact details of the parties involved to its customer service desk within 45 calendar days of the transaction. Its published process then runs in stages: a negotiation period of 20 days in which the parties are expected to resolve it between themselves, with the dispute closing automatically after that window unless it is escalated into a formal claim, and then an investigation that it aims to complete within 30 days, longer for complex cases. Throughout, it places a hold on the funds related to the transaction so they cannot be withdrawn until the dispute is resolved or closed.

Two things follow from that structure. First, the 20-day negotiation window is not a waiting room — it is your window to reach the recipient and get agreement, and if you let it lapse without escalating, the dispute closes. Second, because eSewa asks for all messages and conversations between the disputing parties, the record of you asking politely and them refusing or ignoring you is not a side note; it is the substance of your case. Submit it complete the first time.

Khalti runs a shorter and narrower process. Its dispute policy requires complaints in writing — by email to its dispute address or by physical delivery — within 30 days of the transaction, with the Khalti ID, the amount, the date, the parties involved, a contact number and supporting evidence such as screenshots. It says investigations typically take at least 20 to 25 days. Its general terms separately reference a 15-day window for reporting transaction disputes for chargeback purposes, so if a card or a merchant charge is involved, treat 15 days as your working deadline rather than 30.

Be clear-eyed about what Khalti says it will not hear. Its policy excludes transfers to unauthorised merchants who then refuse service, anything involving illegal activity such as gambling, betting or cryptocurrency, and — the one that stings — mistaken transfers arising from user negligence, on the basis that the app showed you the receiver's name and photo before you confirmed. If your case is a plain mistyped ID, expect the formal answer to be that the dispute desk cannot compel a refund, and expect the useful help to come from Khalti contacting the recipient rather than from Khalti reversing anything.

Both wallets sit inside the same regulatory perimeter, which is where your leverage comes from. Khalti's own dispute policy tells dissatisfied complainants to escalate to Nepal Rastra Bank's complaint portal. That is not a threat you need to make loudly; it is a route the provider itself publishes, and mentioning it calmly in your written follow-up tends to move a file along.

A practical note on identifying the recipient. Wallet dispute teams will not hand you a stranger's name, phone number or address, and you should not expect them to. What they will do is act as the channel. Ask them to contact the recipient on your behalf, to convey your request and the transaction reference, and to tell you what the recipient said. That is the version of the request they are able to say yes to.

QR is where most everyday wrong payments now happen, because scanning is fast, the shop is busy and two stalls share a wall. Fonepay, which runs the largest QR network in the country, tells customers with a payment problem to contact their bank or the merchant's customer support, and describes refunds as something the merchant initiates from the Fonepay Business App as a full or partial refund. That tells you where the money is and who can send it back: it is in the merchant's settlement, and the merchant is the one who returns it.

So go back to the shop. Take the payment confirmation on your phone, show the merchant the timestamp and the amount, and ask them to look at their own notification or Business App history for the same second. A merchant who accepts Fonepay QR receives a notification within a second of a successful payment, which means the transaction you are describing is visible on their side too. Most genuine businesses will refund a mispayment they can see in their own record, because a refused refund on a verifiable transaction is a reputational problem they do not want.

If the merchant will not, escalate through the network rather than arguing at the counter. Fonepay publishes a complaint portal, a support email and a phone line, and names a grievance officer — the point of a named grievance officer is that a complaint reaches a person with a duty to answer it. Give the transaction reference, the amount, the timestamp, the merchant name as it appeared on your screen, and what the merchant said when you asked. Your own bank is also a route, since Fonepay's guidance sends payment problems to the customer's bank as well as the merchant.

Wrong-number top-ups are a different animal and generally the hardest single case to fix. The money has not gone to a person's account at all; it has been converted into airtime or data on a telecom account belonging to somebody you cannot identify, and there is nothing left in a wallet to hold. You should still report it to the wallet within its dispute window, and you should still contact the number you actually recharged, because a wrong digit usually means the balance landed close to home. But temper your expectations: once value has been consumed as airtime, there is often nothing for anybody to freeze.

Paying the wrong biller is the most recoverable of the merchant cases and the one people panic about unnecessarily. If you paid your electricity bill against a neighbour's customer number, or a school fee against the wrong student ID, the money is sitting as a credit balance on somebody's account with an institution that keeps proper records. Go to that institution — the utility, the school, the municipality — with the payment reference and ask for the credit to be transferred to the correct account or refunded. This is routine administration for them, not a dispute.

In every merchant case, resist the urge to make a second payment to the correct recipient before you have documented the first. People do this constantly under time pressure, and it doubles the sum at risk while muddying the record. Screenshot, report, then pay again — in that order, and in the same session if you can manage it.

The recipient's position is the part of this problem that nobody explains, and it is worth understanding for two reasons: because it tells you what pressure is realistic, and because sooner or later somebody will send money to you by mistake.

Start with what is not true. Receiving money you did not expect does not make it yours, and no wallet or bank treats an unexplained credit as a windfall. Equally, it does not make you a criminal for having received it — you did nothing. The obligation attaches at the point where you know the money was not meant for you and you decide what to do next. That is where a mistake becomes a choice.

The right response, if a credit you cannot explain appears, is to leave it alone and tell your bank or wallet in writing. Do not spend it, do not withdraw it, and do not transfer it onward to a friend for safekeeping, which is the single worst thing you can do because it converts an easily-unwound credit into a chain of transfers that looks exactly like money laundering. Telling your institution costs you nothing and puts the record on your side.

If someone contacts you claiming a mistaken transfer, verify before you return anything. Ask them for the transaction reference and check that a credit of that amount, at that time, actually exists in your history. A well-established scam runs the other way round: a stranger claims to have sent you money by mistake, pressures you to send it straight back, and either no payment ever arrives or the original payment is itself reversed or disputed later, leaving you out of pocket twice. Return money through your own bank or wallet, against a credit you can see, and never in cash to a person you cannot identify.

Where a recipient refuses outright, the sender's remaining routes are civil and criminal rather than technical. A person who keeps money they know is not theirs is not in the same position as a person who spent it before anyone told them. Nepal's Acts and Codes are published by the Nepal Law Commission, and whether a particular refusal is a civil matter about returning what was received without entitlement or something a police complaint can address is a question for a lawyer on the facts. What is consistent across every institution's published process is that the institution itself will not decide it for you — it will hold funds, pass messages, and wait for consent or an order.

Our reading of the practical position, which none of the cited providers state in these terms, is that the decisive variable is time rather than law. A hold placed on the same day usually recovers the money because a balance still exists and the recipient has nothing to gain by refusing. A hold placed a week later usually recovers nothing, because the balance is gone and the only remaining route costs more than the sum in dispute. The providers publish deadlines of 30 and 45 days; those are the outer limits of what they will accept, not a description of when action still works.

Nepal Rastra Bank runs a Financial Consumer Protection portal and an online grievance management system at gunaso.nrb.org.np, and it is a genuine escalation route rather than a suggestion box. It exists to handle complaints from the customers of institutions NRB licenses, with the stated aim of fairness, reliability and transparency in financial customer redress.

The rule that trips people up is that it is a second-stage forum. The registration form asks directly whether you have already registered your complaint with the financial service provider, and the published process is to complain to the provider first, then bring it to NRB with complete details and documents if it is not resolved. Going straight to the portal on day one wastes the complaint. Complain to the bank or wallet, wait for its own process to run or fail, and then escalate with the acknowledgement as your evidence.

The complaint subjects the form offers cover the ground you need — among them account operation, ATM issues, cards, mobile and internet banking, payment services and remittance — and the service providers you can name include banks and financial institutions, money changers, payment service providers and remittance companies. That perimeter matters: it means eSewa, Khalti and the other licensed wallets are inside it, alongside every bank. NRB's Payment Systems Department maintains the licensed lists of payment system operators and payment service providers and issues the unified payment systems directive they operate under.

Know what the portal will refuse, because a rejected complaint costs you weeks. NRB's guidelines say it will not address complaints that are incomplete, that carry false contact information, that are already pending before a court, that target entities it does not license, that contain abusive language, or that concern internal employee disputes within a licensed institution. Write plainly, give the full transaction detail, attach your documents, and use your real contact details — you will receive a registration number by email, and you track the case with that complaint number afterwards.

The police route is separate and it is for a different problem. If your money went to the wrong place because you were tricked — a fake payment request, a spoofed account number, a QR sticker pasted over the real one, an impostor claiming to be somebody you owed — that is fraud rather than error, and it belongs with the Nepal Police Cyber Bureau. Its reporting page offers a dedicated form for online financial fraud, and asks for a copy of your citizenship certificate, national identity card or passport along with the relevant links and clear screenshots.

You do not have to travel to Kathmandu to use it. The Bureau accepts complaints at district police offices, in person at its office in Bhotahiti, and by email, and lists its office numbers alongside the police control room. In practice a district-level complaint plus an emailed copy with your evidence attached is the fastest way to get a case number, and a case number is what turns a bank's polite stalling into cooperation.

Be realistic about the limits of all of it. Nepal Rastra Bank supervises how institutions handle their customers; it does not adjudicate the ownership of a rupee balance sitting in a third party's account, and it will not order a stranger to pay you back. The Cyber Bureau investigates offences; it is not a debt collection service for a mistyped account number. Neither of them can do what a same-day hold can do, which is why the first hour matters more than every escalation route on this page combined.

Read the confirmation screen, every time, out loud if you are tired. Khalti's entire position on mistaken transfers rests on the fact that it shows you the receiver's name and photo before you confirm, and it is right that this is the moment the error is cheap to catch. The two seconds you save by tapping through are the two seconds that cost you the money.

Save beneficiaries rather than retyping account numbers. Every banking app and wallet in Nepal lets you store a payee, and a saved payee cannot suffer a transposed digit. The one discipline that goes with it is to verify the saved entry the first time with a small test transfer, and to name it in a way you will still understand in a year — not a bare account number, but a name and a purpose.

Send a token amount first for anything large or anything new. One hundred rupees to a new supplier, a new landlord or a relative's new account, confirmed received by a phone call, and then the real sum. This is standard practice among people who move money professionally and almost unknown among people who do it occasionally, and it converts a catastrophic error into a trivial one.

Treat account numbers sent over chat as untrusted by default. Account details forwarded through Viber, WhatsApp or Messenger are the most common vector for a payment that goes to exactly the wrong place on purpose, because a compromised account can send a perfectly plausible correction saying the details have changed. Confirm the number by voice, with a person whose voice you recognise, before you pay against it.

For QR, check the merchant name that appears on your screen against the business you are standing in, not against the sticker. The sticker is paper and paper can be replaced; the name your app resolves comes from the network. If the name does not match the shop, do not pay, and tell the shopkeeper — a QR sticker overlaid on another is a problem for them as much as for you.

Finally, know your own limits before you need them. Wallets operate transaction and balance ceilings set within the regulatory framework — Khalti publishes per-transaction and monthly caps that differ by service type, and eSewa's terms warn that a wallet holding more than the permitted balance ceiling will be blocked. Knowing roughly where your ceilings sit stops you from splitting a payment into three hurried attempts, which is the situation in which mistyped transfers actually happen.