If you sell in Nepal, you already know the checkout dance. A customer messages you on Instagram, you send your eSewa ID, they pay, then they screenshot the confirmation, then you squint at the screenshot to check the amount, then you finally pack the order. Multiply that by 30 orders during Dashain and you have a full-time job just confirming payments.
The fix is not to pick one payment method. Nepali customers are split across eSewa, Khalti, direct bank transfer / mobile banking, and good old cash on delivery. If you only accept one, you lose the rest. The real goal is to offer all of them in a single checkout where the payment confirms itself — no screenshots, no manual matching.
Why "just send me your eSewa ID" stops working
Manual confirmation feels free, but it costs you in three ways that get worse as you grow:
- Mismatched amounts. A customer pays Rs. 1,200 for a Rs. 1,250 order, or forgets the delivery charge. Now you are negotiating over chat instead of shipping.
- Fake or recycled screenshots. An old payment screenshot looks identical to a new one. Without a transaction reference tied to the order, you cannot tell.
- It does not scale. Matching wallet payments to orders by hand is fine at 5 orders a day and impossible at 50. Festival season is exactly when you have no time for it.
An integrated checkout flips this. The customer picks their method, pays inside the flow, and the gateway tells your system "this exact order is paid" automatically. You ship. That is the entire difference.
The four payment methods Nepali shoppers actually expect
1. Digital wallets — eSewa and Khalti
These are the default for online shoppers, especially younger buyers in Kathmandu, Pokhara, and other cities. When eSewa or Khalti is wired in properly as a gateway, the customer is redirected, pays, and is sent back to your store with a verified status. You get an automatic confirmation with a transaction ID — not a screenshot. Reconciliation is done for you.
2. Bank transfer and mobile / connectIPS banking
Many customers, and almost all B2B and higher-value buyers, prefer paying straight from their bank — through mobile banking, connectIPS, or a fund transfer. The trick is making this part of checkout instead of a side conversation. A proper bank-transfer option captures the order, shows your account details with the exact NPR amount, and links the payment to that specific order so you are not hunting through your bank statement.
3. Cash on delivery (COD)
COD is still huge in Nepal, particularly outside the major cities and for first-time buyers who do not trust a new store yet. Do not treat COD as a problem — treat it as a trust on-ramp. Offer it, but pair it with your courier's COD remittance so you actually track which orders were collected and when the cash comes back to you. For higher-value items, a partial advance through eSewa or Khalti plus COD on the balance cuts down on rejected deliveries.
4. Cards (where relevant)
Card usage is smaller for everyday retail but matters for some customers and for buyers abroad sending to family in Nepal. If your gateway supports it, leave it on — it costs nothing to offer.
What "all in one checkout" should actually do
A checkout worth setting up does more than list logos. Look for these behaviors:
- One order, every method. The customer sees eSewa, Khalti, bank transfer, and COD on the same page and chooses — you are not sending different people to different places.
- Automatic verification. Wallet and bank payments come back with a transaction reference attached to the order. Paid orders are marked paid without you touching anything.
- Correct NPR amounts, including delivery and VAT. The total the customer pays already includes shipping and, if you are VAT-registered, the 13% VAT. No after-the-fact "actually it's Rs. 150 more."
- A clean record for your PAN/VAT filing. Every transaction is logged with date, amount, and reference, so your monthly filing is a report, not an archaeology project.
This is where using a platform built for Nepal pays off. With Saauzi, eSewa, Khalti, bank transfer, and COD are available in the same checkout with automatic payment confirmation, so a paid order shows up as paid in your dashboard and POS — you spend the saved time packing, not verifying screenshots.
A quick setup checklist
- Register your merchant accounts. Get your eSewa and Khalti merchant credentials ready — these connect the gateway to your store.
- Add your bank details once. Enter the account that should receive transfers so it appears automatically at checkout with the order's exact amount.
- Set your delivery zones and charges. Inside-valley, outside-valley, and remote-area rates should be baked into the total, not improvised per order.
- Decide your COD rules. Maybe COD is open everywhere, or only under a certain amount, or requires a small advance above Rs. 5,000. Write the rule down and apply it consistently.
- Test with a Rs. 10 order. Run one real transaction through each method yourself before you go live. Confirm the order auto-marks as paid.
Get festival-ready before Dashain and Tihar
Your biggest revenue days are also your most chaotic. The shops that win Dashain–Tihar are not the ones with the most stock — they are the ones whose checkout does not need a human babysitting it. Before the rush:
- Turn on every payment method so no sale is blocked by "sorry, I only take eSewa."
- Make sure auto-confirmation is working so you are not buried in screenshots on the busiest night of the year.
- Pre-set festival delivery charges and any cut-off dates so customers are not surprised.
- Keep your POS and online store on the same stock count so you do not oversell a product that just walked out the physical door.
Takeaway
Stop choosing between payment methods and stop confirming them by hand. Offer eSewa, Khalti, bank transfer, and COD in one checkout, with the exact NPR amount including delivery and VAT, and let the gateway verify each payment automatically. Do one thing today: list every method your customers asked for in the last month, then run a Rs. 10 test order through each so you know your checkout confirms payments on its own — before the festival rush arrives.
Comments
Be the first to comment.