Sent money to the wrong number on eSewa or mobile banking? How reversal actually works in Nepal

One digit. A friend paying his share of a Pokhara trip typed 98510 instead of 98501 into Fonepay Direct, hit send on Rs 12,000, and watched the confirmation screen congratulate him on paying a complete stranger. The bank's reply the next morning was the line every wrong-sender in Nepal eventually hears: "the system cannot reverse it, sir."

That line is true, and it is also not the end of the story. Nepal's payment rails settle around 78.9 million mobile-banking transactions a month, and the rules behind them, NCHL's operating rules, the wallets' dispute policies, NRB's complaint portal, and two laws most people have never read, define exactly what happens after a mistaken send. The honest version: recovery is possible, it runs through the recipient rather than around them, and every route has a deadline you can miss.

Why "reversal" mostly does not exist

The design is deliberate. NCHL's own ConnectIPS FAQ states that payments made through ConnectIPS cannot be stopped or reversed through the system, and tells users to verify bank, branch, and account number with the beneficiary beforehand. Khalti's dispute policy is blunter still: funds sent mistakenly to another Khalti user "can't be reverted back, as it's your own liability to confirm", the app having shown you the recipient's name and photo before you pressed send.

Settlement finality is what makes instant payments instant. The money is in the recipient's account seconds after you confirm, and from that moment it is legally their balance to operate, which is why every recovery route below works through the receiving side rather than over it. Under NCHL's Retail Payment Switch operating rules, a refund of an accepted and settled transaction is "initiated by the crediting member": the bank or wallet that received the money, with its customer's cooperation, sends it back. Nobody else can.

One exception fixes itself, and it is worth separating before panic sets in. If your app shows debit success, credit failed, the transfer did not complete; that is a reconciliation exception, and ConnectIPS refunds it normally by the next working day. Chase your bank if two working days pass. Everything below concerns the worse case: the payment succeeded, to the wrong person.

The first hour

Speed matters more than channel. Three things, in order:

1. Screenshot everything. Transaction ID, timestamp, recipient number or account, amount. Every dispute desk and every later complaint will ask for these.
2. Contact the recipient if any handle is visible. A direct request returns more wrong transfers than any formal process, and it costs nothing. Most recipients of a stray Rs 12,000 know it is not theirs; many also know (or can be politely informed) that keeping it is legally untenable.
3. Call the operator's support line the same day. eSewa: toll-free 1660-01-02121 from NTC numbers (1810-21-02121 from Ncell), or csd@esewa.com.np. Khalti: in-app support or dispute@khalti.com. Banks: your branch or the app's call centre. You are not asking for a reversal; you are opening the dispute that triggers the holds described below.

The wallet route: eSewa and Khalti

The two big wallets, between them claiming over 20 million registered users, run written dispute processes with hard windows.

Details worth knowing before filing. eSewa's process is negotiation-shaped: the fund hold exists to stop the money leaving while the two of you talk, and a dispute once closed cannot be reopened, so submit your evidence completely the first time. eSewa also refuses disputes arising from activity against its terms or anything illegal, which closes the door on, say, recovering a payment made for a grey-market purchase.

IME Pay users now follow the same ladder as Khalti: the two wallets merged in July 2025 under the Khalti by IME brand, which reshaped the eSewa vs Khalti vs IME Pay picture for everyday transfers.

Wrong mobile recharges are their own sad category. The wallet only forwards your complaint to the telecom, and the refund decision sits with NTC or Ncell; reporting suggests NTC cooperates on refunds more often than Ncell, and both get reluctant once a recharge has succeeded and taxes are deducted. Treat a wrong recharge above a few hundred rupees as worth one complaint and no more chasing.

The bank route: mobile banking, ConnectIPS, Fonepay Direct

For interbank transfers, the rulebook is NCHL's Retail Payment Switch operating rules, and it sets out a sequence most branch staff will not volunteer:

• Your own bank is the first point of contact. File the dispute there in writing, with the transaction reference. The branch cannot reverse anything, but its report is what activates the rest.
• The receiving bank must block the disputed amount. For a disputed transaction reported through the debtor bank or NCHL, the creditor bank "shall support in resolving the dispute and/or investigation, until which it shall block the available transaction amount." This is the clause that stops your Rs 12,000 being withdrawn while the process runs, and it is the reason same-day reporting matters: a block can only hold money still in the account.
• Clean exceptions move on a clock. Reversals or adjustments for customer-raised cases are due within 2 business days when both accounts sit at the same bank and 7 business days across banks, "except for transactions under dispute." A genuinely contested wrong transfer, where the recipient does not consent, falls outside the clock and into investigation, with NRB the final interpreter of the rules.

Prevention is uneven across rails, which is half the reason wrong transfers keep happening. Fonepay Direct shows the recipient's name before you send, as does Khalti. Plain account-number transfers on ConnectIPS put the onus on the sender to verify the account details beforehand; there is no universal name-lookup on Nepal's account-number rails. The five seconds spent reading the confirmation screen name is the entire difference between this post being theoretical or practical for you. Which rail you use matters for other reasons too; the ConnectIPS versus mobile banking comparison covers the fee and limit side.

Escalation: NRB's complaint portal

When the wallet's 30 days or the bank's investigation produces silence, the regulator's door is open and free. NRB runs a grievance portal at gunaso.nrb.org.np: file online with documents, receive a registration number by email, track status. The portal's contact channels are 01-5719605 (extension 172) and gunaso@nrb.org.np, and any NRB office accepts complaints. The expected sequence is bank or wallet first, NRB second, so attach the dispute correspondence that proves you already tried.

The escalation has more weight than it looks. Licensed wallets are required to run internal complaint-handling linked to NRB's grievance system, which is why Khalti's own dispute policy routes unresolved cases to the portal, so an NRB-registered grievance lands where the operator's regulator can see it. (NRB's payment-systems directive is published as a scanned Nepali PDF, so no specific resolution-deadline clause can be quoted here; the portal's tracking number is your practical instrument.)

When the recipient refuses

Some do. The stranger who received your Rs 12,000 stops answering, or answers and declines. Two laws then apply, and they are unambiguous.

The civil one: the National Civil Code 2074's unjust-enrichment chapter. Section 665 requires a person who receives anything by mistake to return it to the person they received it from. Section 667 adds that anything kept with malafide intention must be returned with interest, plus compensation for any loss. Section 671 gives you two years from the cause of action to file the lawsuit. For a five-figure sum, a lawyer's demand letter quoting Section 665 is cheap and frequently sufficient.

The criminal one: Section 5 of the Banking Offence and Punishment Act 2064 prohibits withdrawing money from another person's account or transferring funds from a customer's account in an unauthorised manner. A recipient who knowingly drains a mistaken credit is operating money that is not theirs, and the Act's punishments scale with the amount involved. Practitioner reporting also indicates banks can now freeze suspect accounts immediately regardless of amount, which makes a prompt police complaint practical leverage rather than a gesture.

One routing note: a pure wrong transfer is not cybercrime, so the regular police and the banking-offence route handle a refusing recipient. The Cyber Bureau (Bhotahiti, 01-5319044) is the right door only when deception was involved, someone tricked you into sending, which is the territory of the QR and wallet scam post and the OTP and phishing fraud playbook. No published Nepali court ruling on a kept mistaken credit turned up in research for this post, so treat litigation as the slow last rung; the demand letter and the account block do most of the real work.

The boring prevention habits

Nepal's rails moved Rs 612 billion through mobile banking and Rs 53 billion through wallets in a single month of early 2026, across 30 million mobile-banking customers. At that volume, fat-fingered digits are a daily certainty, and the safeguards are unevenly distributed: name-and-photo on Khalti, name confirmation on Fonepay Direct, nothing but your own eyes on an account-number transfer. So:

• Read the name on the confirmation screen out loud before confirming. If no name appears, you are on a rail with no safety net; check the number twice.
• For first-time recipients, send Rs 10 first, confirm receipt, then send the balance. Two transactions cost a few rupees extra and cap the worst case at Rs 10, and they stay well inside the per-tier wallet send limits either way.
• Save verified payees instead of retyping numbers. Most wrong transfers are retyping errors, not wrong saved contacts.

What you actually need to know

1. Nothing reverses; everything routes through the receiving side. The recipient's cooperation, voluntary or legally persuaded, is how money comes back. Spend your first hour on screenshots, the recipient, and the operator's support line, in that order.
2. The windows are short and the holds reward speed. 45 days at eSewa, 30 at Khalti, and a receiving-bank block under NCHL rules that only helps while the money is still sitting there. Same-day reporting is the single highest-leverage move.
3. A refusing recipient is breaking the law, and saying so works. Civil Code Section 665 obliges return, the Banking Offence Act covers knowingly spending a mistaken credit, and accounts can be frozen without a threshold. A demand letter citing the sections resolves most refusals long before any courtroom.

This post is part of the Nepal Money Basics guide — the digital money section. If a wallet or bank stonewalled your dispute past its own published windows, or the gunaso portal worked for you: email parjanya57@gmail.com.