Integrating eSewa, Khalti and Cards Into Your Website

The moment your website can take payment, it stops being marketing and starts being infrastructure. eSewa and Khalti payment integration is what turns "DM us to order" into orders that confirm themselves at midnight. The technology is mature now. What trips businesses up is everything around the code: merchant approval, fees, and when the money actually lands in your bank. Here's the full picture.

How the payment flow actually works

Customer clicks "Pay with eSewa" on your checkout. They're sent to eSewa's page or app, log in with their own credentials (your site never sees their password), approve the amount, and bounce back to your site. Behind the scenes, your website then verifies the transaction directly with eSewa's servers before marking the order paid. That server-side verification step is where cheap integrations cut corners, and it's exactly the hole fraudsters look for: a faked "success" redirect without a real transaction behind it. Khalti's flow is nearly identical. Done properly, the customer experience is about fifteen seconds.

Two details separate a trustworthy checkout from a worrying one. First, receipts: the customer should get an automatic confirmation with an order number the moment payment verifies, by email and ideally SMS, because a Nepali customer who pays and sees nothing will be calling you within ten minutes, understandably nervous. Second, the failure path: payments fail constantly for boring reasons, wallet balance short, OTP timeout, network drop between the wallet and your server. Your site must show a clear "payment did not complete, you have not been charged twice" message and let them retry, not a blank error page. We log every attempt, success or failure, so when a customer says "I paid but got no confirmation", your staff can answer in one search instead of one panic.

Becoming a merchant: the paperwork nobody warns you about

You can't just plug in. eSewa and Khalti both require a merchant agreement: company registration documents, PAN, a bank account, and a review that takes anywhere from a few days to a few weeks. Registered businesses sail through; unregistered side hustles don't. Start this paperwork the same week you commission the website, not after launch, or your beautiful checkout will sit disabled while the approval crawls. WebsNP guides clients through the merchant forms because we've filled them in dozens of times.

Fees and settlement: the part that surprises people

Both wallets charge roughly 2 to 3.5 percent per transaction depending on your category and volume; specifics come with your merchant agreement. Settlement, when the wallet actually transfers collected money to your bank, typically runs on a cycle of one to a few business days. Plan cash flow around it: a big Dashain sale weekend means money arriving the following week, not that night. Keep the dashboard reconciliation habit from day one. Mismatched orders are far easier to chase when they're a day old, not a month.

What about international cards?

Stripe doesn't operate for Nepali merchants, which kills the standard worldwide answer. Practical options: PayPal (workable for receiving from abroad, with its own withdrawal hoops), or card gateways from Nepali banks such as Himalayan or Nabil, which come with their own merchant processes and fees around 3 to 4 percent. Serving foreign customers, a trekking agency taking booking deposits from Germany, say, usually means running a wallet for locals and PayPal or a bank gateway for internationals, side by side on the same checkout. We build exactly that combination regularly.

What integration costs and how WebsNP does it

Adding eSewa or Khalti to an existing WordPress or WooCommerce site runs about NPR 15,000 to 35,000 per gateway including testing with real transactions. A full ecommerce build with payments wired in from the start is more economical: NPR 60,000 to 150,000 all-in, delivered in about a week, with free domain, a year of NVMe hosting, SSL, daily backups and on-page SEO included. Custom Laravel checkouts for booking systems or portals are quoted per project, fixed price within 24 hours as always, 50/50 payment terms and a money-back guarantee. One caution from experience: never let anyone launch your payment integration without testing refunds and failed-payment paths, not just successes. The success path is easy. The edge cases are where your accountant's headaches come from, and we test them all before handover.