How to Handle Customer Refunds for Digital Payments in Nepal (eSewa, Khalti, Bank Transfer)

Refunds are part of running any retail or online business — a customer ordered the wrong size, a courier returned a parcel, a product arrived damaged, or someone paid twice during a busy Dashain sale. In Nepal, the tricky part is that money moves through several channels: eSewa, Khalti, bank transfer, and cash on delivery. Each one returns money differently, and getting the process wrong costs you time, trust, and sometimes the money itself.

This guide walks through practical refund workflows for each payment method used in Nepali e-commerce, plus the seller-protection policies you should put in writing before disputes happen.

Start with a written refund policy

Most refund headaches in Nepal come from not having a clear policy customers agreed to before buying. Before touching any payment method, publish a simple policy on your store and your Instagram/Facebook page. At minimum, state:

• Eligibility window: e.g. 3 or 7 days from delivery for unused items with tags and original packaging.
• Non-refundable items: innerwear, cosmetics, perishables, custom orders, and clearance stock.
• Who pays return shipping: you cover it for damaged or wrong items; the customer covers it for change-of-mind returns.
• Refund timeline: a realistic 3–7 working days after you receive and inspect the returned product.
• Refund channel: money goes back to the same method and same account used to pay.

That last rule is your strongest seller protection. Refunding to the original account prevents fraud where a buyer asks you to send money to a different wallet or bank.

Refunding eSewa payments

eSewa does not auto-reverse a completed transaction the way a card chargeback works, so most small sellers handle refunds manually.

1. Verify the original payment. Match the eSewa transaction reference (the code in the confirmation SMS or receipt) against your order. Never refund on a screenshot alone — screenshots are easily faked.
2. Confirm the customer's eSewa ID. Refund to the same registered mobile number that paid, and ask the customer to confirm that number in writing.
3. Send the refund from your eSewa account to that number, and write the original transaction reference in the remarks field.
4. Save proof. Keep the refund transaction code and a screenshot in the order notes.

If the payment came through an eSewa merchant/business account integrated with your store, check your merchant dashboard first — some integrated payments support a reversal within the settlement window, which is cleaner than a manual send.

Refunding Khalti payments

The workflow for Khalti mirrors eSewa, with one advantage: if you accept Khalti through a proper merchant integration, refunds can often be initiated from the merchant dashboard or via the merchant support channel rather than a manual wallet-to-wallet transfer.

• For integrated merchant payments, raise the refund against the original Khalti transaction ID so it reconciles automatically.
• For manual wallet payments (a customer who simply sent money to your Khalti number), send the refund back to the same Khalti mobile number and note the original purchase reference.
• Confirm whether the customer wants the refund to their Khalti balance — some prefer it because it is instant and reusable.

Refunding bank transfers and connectIPS

Bank refunds are the slowest but the most paper-trailed, which actually helps you.

1. Collect full bank details in writing: account holder name, bank name, branch, and account number. The account name should match the buyer's name on the order.
2. Cross-check the deposit. Look for the original credit in your bank statement before refunding. Bank transfers and connectIPS take time to settle, so confirm the money actually arrived.
3. Transfer back via the same channel and keep the bank voucher or transaction confirmation.

For larger amounts, bank transfer is the safest refund route because both sides hold a permanent record — useful if a dispute ever escalates.

Don't forget cash on delivery (COD)

COD is still the backbone of Nepali e-commerce, and refunds here are different because the money may be sitting with your courier, not with you yet.

• If the customer refuses the parcel at the door, no money changes hands — confirm the return with your courier (Pathao, Upaya, NCM, Aramex, or your local rider) and reconcile so you are not charged a wrong COD remittance.
• If the customer paid COD and later returns the item, you usually refund digitally — ask whether they want it in eSewa, Khalti, or bank, then follow the matching workflow above.
• Reconcile courier COD statements weekly so a refund isn't paid twice — once by you and once stuck in the courier's settlement.

Tax and accounting: handle VAT and PAN correctly

If you are VAT-registered, a refund isn't just sending money back — it affects your books.

• Issue a credit note against the original tax invoice instead of deleting the sale. This keeps your VAT records consistent with IRD requirements.
• Adjust the VAT amount proportionally; you reclaim the VAT you already accounted for on the refunded portion.
• Keep the original invoice number linked to the credit note so your PAN/VAT filing matches.

Even if you only hold a PAN and aren't VAT-registered, record every refund against its original sale so your income figures stay accurate at year-end.

Protect yourself from refund fraud

A few habits prevent most refund abuse seen by Nepali sellers:

• Never refund before the product is back in your hands and inspected — except for a clear double-payment or a failed transaction.
• Refund only to the original payer's account: same eSewa number, same Khalti ID, same bank account.
• Require an unboxing or return video for high-value or fragile items so a "damaged" claim can be verified.
• Watch for double-payment claims: verify against your own transaction history, not the buyer's screenshot.
• Log everything in the order record — original payment reference, refund reference, reason, and date.

Plan for festival-season volume

During Dashain and Tihar, order volume spikes and so do refund and return requests. Prepare before the rush: pre-write template replies for refund requests, set a slightly longer but clearly stated refund window, and keep a small float in your eSewa and Khalti accounts so you can process refunds quickly instead of making frustrated customers wait. Fast, clean refunds during the festival season turn a complaint into a repeat customer.

This is where keeping payments, orders, and refunds in one place pays off. A platform like Saauzi lets Nepali sellers manage online-store orders, POS sales, and eSewa/Khalti/bank payments together, so when a refund comes in you can match it to the original transaction and record it against the right order — without juggling separate apps and screenshots.

Takeaway

Refunds in Nepal are manageable if you follow three rules: publish a clear policy customers agree to upfront, always refund to the same method and account the customer paid from, and keep a transaction reference for every refund. Set these up once — before the next Dashain rush — and refunds become a quick, trust-building step instead of a source of losses and arguments.