You spent money on ads, a customer found your product, added it to cart, and tapped "Pay with eSewa" — and then nothing happened. The order never landed. In Nepal, this is one of the quietest ways online stores lose money. A failed or abandoned payment isn't just a lost sale; it's a customer who may not come back, especially during a high-traffic season like Dashain or Tihar when they have ten other shops to try.
The good news: most payment failures on Nepali stores come from a handful of fixable causes. Here's how to find them and close the gaps so more eSewa, Khalti, and bank payments actually complete.
Why payments fail or get abandoned in Nepal
Before fixing anything, it helps to separate the two problems, because they need different solutions.
- Failed payments are technical: the customer tried to pay but the transaction errored out, timed out, or got stuck. The money sometimes even leaves their wallet without the order confirming.
- Abandoned payments are behavioural: the customer reached checkout but chose not to finish — usually because of friction, surprise costs, or distrust.
In the Nepali context, the common culprits look like this:
- Wallet balance and limits. Many eSewa and Khalti users keep low balances and only top up when needed. A payment fails simply because the wallet is short, or because the customer hasn't completed KYC and hits a transaction limit.
- OTP and bank timeouts. Connecting a bank account or using card/bank transfer involves an OTP. Slow SMS delivery on busy networks means the OTP arrives after the session expires.
- Network drops mid-payment. The customer gets redirected to the eSewa/Khalti page, the connection stutters, and they never get redirected back to your store — so the order shows as pending or failed even when money moved.
- Surprise delivery charges. A customer in Pokhara or Biratnagar sees a Kathmandu-only shipping price, or no delivery cost at all until the final step, and quits.
- Distrust of paying in advance. Plenty of Nepali shoppers still prefer to see the product before paying. If your only option is prepaid, you lose the cash-on-delivery crowd entirely.
Fix the technical failures first
Offer both eSewa and Khalti, plus a fallback
Don't force every customer through one wallet. Someone whose eSewa balance is empty may have Khalti loaded, or prefer a bank transfer. Offering eSewa, Khalti, and a bank/card option side by side means a single wallet problem doesn't kill the sale. The more legitimate paths to "paid," the fewer dead ends.
Handle the redirect and verification properly
The most damaging failure is when a customer's money is deducted but your store marks the order as failed. This almost always comes from not verifying the transaction status with the payment provider after the redirect. Your checkout should confirm the final status directly with eSewa or Khalti — not just rely on the customer landing back on your "success" page, which a flaky connection can prevent.
This is where running your store on a platform built for Nepal helps: Saauzi integrates eSewa, Khalti, and bank payments with proper server-side verification and order reconciliation, so a dropped redirect doesn't turn a real payment into a lost order. You see the confirmed status instead of guessing.
Keep a pending state, don't auto-cancel
When a payment doesn't confirm instantly, mark the order pending rather than cancelling it. Give the customer a clear way to retry the same order, and check provider status before you release the cart. Auto-cancelling pending orders too fast is how stores accidentally reject payments that were actually going through.
Remove the friction that causes abandonment
Show the full price early — including delivery and VAT
Surprise costs at the last step are the number-one reason carts get abandoned. Show delivery charges as early as possible, ideally on the cart page, and set realistic rates for inside-valley versus outside-valley delivery. If you're VAT-registered, make it clear whether prices include VAT and show your PAN/VAT number on invoices — it builds trust with business buyers and keeps you compliant.
Always offer Cash on Delivery
COD is still the backbone of Nepali e-commerce. Many first-time customers will only buy if they can pay the courier on arrival. Offer COD alongside digital payment — and consider a small discount or free delivery for prepaid orders to nudge people toward eSewa/Khalti, which cuts your return-to-origin losses and gets you paid upfront.
Keep checkout short and mobile-first
Most of your customers are on a phone, often on mobile data. Cut the form down to the essentials: name, phone number, delivery address, and a landmark (Nepali addresses rely on landmarks more than street numbers). Don't force account creation before buying — let people check out as a guest. Every extra field is a chance to lose them.
Show that you're a real, reachable business
A visible phone number, a Viber or WhatsApp contact, your shop's location, and a clear return policy all reduce the hesitation that makes people abandon a prepaid payment. A customer who can message you before paying is far more likely to actually pay.
Get ready for festival traffic
Dashain and Tihar bring a surge of orders — and a surge of failed payments if you're not prepared. Before the season:
- Test the full checkout yourself with each payment method, including a small real eSewa and Khalti transaction, so you catch redirect or verification bugs before customers do.
- Confirm your courier covers the regions you're promising and update delivery charges and timelines, since festival logistics slow down.
- Pre-write a recovery message for pending or failed orders: a quick Viber or SMS saying "We saw your order didn't complete — here's a link to finish it" recovers sales you'd otherwise lose.
- Watch your order dashboard daily for stuck pending orders and reconcile them against your eSewa/Khalti transaction history.
Track what's actually happening
You can't fix what you don't measure. Keep a simple eye on three numbers: how many customers reach checkout, how many start a payment, and how many orders confirm. If lots of people start a payment but few confirm, you have a technical or verification problem. If few even start, your friction is earlier — price surprises, trust, or a clunky form. Checking this weekly tells you exactly where to focus.
Your takeaway
Failed and abandoned payments are mostly a friction problem, not a customer problem. This week, do three things: turn on at least two digital wallets plus COD, show full delivery and VAT costs before the final step, and make sure every real payment is verified server-side so deducted money never becomes a lost order. Those three fixes alone will recover sales you're losing right now — and they'll matter even more when the Dashain rush hits.
Comments
Be the first to comment.