eSewa & Khalti Payment Integration on Your Website: What Nepali Business Owners Must Know

Quick answer: to accept eSewa, Khalti or FonePay on your website you need (1) a merchant account with the gateway — requiring business registration, PAN and a bank account, (2) an integration into your site — a plugin on WooCommerce, an API integration on custom sites, and (3) server-side payment verification, the step careless developers skip and the reason some businesses ship products that were never paid for. This guide covers the whole picture from a business owner's perspective — no code required to follow along.

I'm Aryan Pariyar, a web developer in Nepal who has wired Nepali payment gateways into WooCommerce stores and custom Next.js checkouts. This is the guide I wish my clients had read before our first call.

Why online payments change the game for Nepali businesses

Nepal's digital payment adoption is massive — QR codes at every pasal, eSewa and Khalti on nearly every smartphone. But most business websites still end with "call us to order." Every extra step (call, screenshot, bank transfer confirmation) loses buyers. A checkout that finishes in the customer's own eSewa app converts dramatically better, runs 24/7, and creates a clean digital record of every sale.

Know the players: eSewa, Khalti, FonePay, ConnectIPS

Gateway	Strengths	Best for
eSewa	Largest wallet user base in Nepal, strong brand trust	Any consumer-facing store — the default first integration
Khalti	Excellent developer tools and documentation, smooth checkout	Startups and custom-built platforms
FonePay	Bank-network QR — customers pay from mobile banking apps	Reaching customers who use banking apps, not wallets
ConnectIPS	Direct bank-account payments, good for larger amounts	B2B, fees, tickets, higher-value transactions

You don't have to choose one. Serious stores integrate eSewa + Khalti at minimum — the second gateway is much cheaper to add once the first is architected properly.

Step 1: Get your merchant account

Consumer wallet apps can't receive website payments — you need a merchant account. Requirements are similar across gateways:

• Company or business registration certificate
• PAN or VAT certificate
• Bank account in the business name
• Citizenship of the authorized person + signed merchant agreement

Approval typically takes a few days to a couple of weeks. You'll receive merchant credentials — a merchant/product code and a secret key. Treat the secret key like a bank password: it belongs on your server only, never in your website's public code. (If a developer pastes it into the browser code, that's a red flag — more below.)

Don't have a registered business yet? Sort that first — and while you're at it, grab your free .com.np domain, which needs the same documents.

Step 2: Choose your integration path

Path A — WordPress / WooCommerce (most businesses)

If your store runs WooCommerce, both eSewa and Khalti provide official plugins: install, enter your merchant credentials, test in sandbox mode, then switch live after the gateway verifies your integration. It's the fastest, cheapest path — realistic development cost is roughly NPR 10,000–25,000 including sandbox testing, styling the checkout, and verifying the flow end-to-end. This is part of what a proper e-commerce build in Nepal includes.

Path B — Custom websites (Next.js, React, Laravel…)

Custom checkouts integrate the gateways' APIs directly — eSewa's ePay API, Khalti's KPG-2 (its modern payment API). The flow is always the same shape:

1. Your server initiates the payment with the gateway (amount, order ID, return URLs)
2. The customer is redirected to eSewa/Khalti to log in and approve
3. The gateway redirects the customer back to your site
4. Your server verifies the transaction with the gateway's verification API
5. Only after successful verification is the order marked paid

Custom integrations cost more — typically NPR 30,000–80,000+ depending on the checkout's complexity — but give you full control over the experience. This is the kind of build I do in my web development service.

The security rule that saves you money: never trust the redirect

Here's the mistake that actually costs Nepali businesses money. When the customer finishes on eSewa/Khalti, they're redirected back to your "payment success" page. That redirect is not proof of payment. A cancelled payment, a failed transaction — or a clever user typing your success URL directly — can all land on that page. If your website marks orders paid based on the redirect alone, you will eventually ship products that were never paid for.

The correct implementation verifies every transaction server-to-server with the gateway's verification API (checking the transaction ID, amount and status) before confirming the order. When you hire a developer, ask one question: "Do you verify payments server-side, or just on the redirect?" If they can't answer confidently, keep looking.

What it all costs: fees and development

Cost item	Typical amount	Notes
Merchant account	Free – nominal	Requires registered business documents
Transaction commission	~2–3% per transaction	Set by the gateway; negotiable at volume
WooCommerce integration	NPR 10,000 – 25,000	Plugin setup, sandbox testing, live verification
Custom checkout integration	NPR 30,000 – 80,000+	API integration with server-side verification
Full e-commerce website	NPR 1,00,000 – 5,00,000	Store + payments + training — full cost breakdown

Beyond the gateway: what makes the checkout convert

• Speed: a slow checkout kills sales before payment even starts — test your store with my free Website Speed Checker.
• Mobile-first: most Nepali buyers check out on a phone; the payment flow must be flawless on small screens.
• Trust signals: clear pricing, delivery info, a real address and phone number, and familiar gateway logos at checkout.
• Track your campaigns: tag your ad and social links with my UTM Link Builder so you know which marketing actually produces paid orders.

Frequently asked questions

Can I accept eSewa payments without a registered business?

For website checkout integration, no — merchant accounts require business registration and PAN. Unregistered sellers are limited to personal QR transfers, which don't integrate with a website checkout and offer no buyer confidence.

eSewa or Khalti — which should I integrate first?

If you only pick one, eSewa's user base makes it the safer default; Khalti is a close second with superior developer tooling. Plan for both — customers pay with what they have.

How long does payment integration take?

Once merchant credentials are in hand: a few days for a WooCommerce plugin integration (including sandbox testing), one to three weeks for a custom checkout with proper verification, depending on scope.

Do international cards work with these gateways?

eSewa/Khalti/FonePay serve Nepali customers. To charge international cards you'd add a global gateway (e.g. Stripe or PayPal, which have their own Nepal-related limitations) — a topic worth a consultation if foreign customers matter to your business.

Who can set this up for me?

Any experienced e-commerce developer — including me. I build WooCommerce and custom checkouts with eSewa/Khalti properly verified server-side, as part of my website development service in Nepal. Tell me about your store and I'll reply within 24 hours with exactly what it needs and what it costs.

Selling online in Nepal isn't a technology problem anymore — the gateways are mature and your customers already use them daily. The difference between a store that converts and one that doesn't is implementation quality. Get it done right the first time.