To sell online in Nepal, you need to accept payments your customers actually use. eSewa and Khalti dominate the digital wallet space. Here’s how to set them up on your website in 2026.
How an online payment works
The customer chooses a method, your site creates an order, and the provider handles authorisation. After payment, the provider sends a callback or redirect. Your server then checks the status directly with the provider before marking the order paid.
That last step is the one beginners skip. A browser redirect saying “success” is not proof. Anyone can fake a screenshot or manipulate a request. Only server-side verification should release goods.
Payment options for Nepali websites
| Method | Best for | Setup difficulty | Notes |
|---|---|---|---|
| eSewa | Nepali customers | Medium | Most popular wallet |
| Khalti | Nepali customers | Medium | Growing, good UX |
| Cash on Delivery (COD) | Local sales | Easy | Still widely used |
| Bank transfer | B2B/large orders | Easy | Manual but reliable |
| Stripe/International | Global customers | Medium | Good for exports |
Prerequisites
- Business registration (sole proprietorship/Pvt. Ltd.)
- PAN
- Bank account
- Active website
You will usually also need:
- A website with contact details, terms, privacy and refund policy
- A business bank account matching the registered business
- Someone responsible for disputes and customer support
- Basic bookkeeping for sales, fees and refunds
Requirements vary by provider and business type. If unsure about VAT registration or invoicing, ask an accountant; do not guess based on a blog post.
Step 1 — Get merchant accounts
eSewa Merchant
- Visit developer.esewa.com.np
- Apply for merchant account with required docs
- Get Merchant ID, Secret Key
- Test in sandbox, then go live
Keep application details consistent: business name, PAN, bank account and website should match. Mismatches delay approval. Ask about settlement time, fees, refunds and support contacts.
Khalti Payment Gateway
- Visit khalti.com/payment-gateway
- Register as merchant
- Get API keys (live/sandbox)
- Complete verification
Approval can take days or longer. Apply before launch day, keep sandbox and live credentials separate, and never reuse a sandbox key in production.
Step 2 — Integrate on your website
For WooCommerce:
- Use eSewa/Khalti WooCommerce plugins, or custom
- Enter API keys in settings
- Test checkout
Choose actively maintained plugins compatible with your WordPress version; stale plugins are a security risk.
For custom website (HTML/JS + backend):
- Follow official API docs
- Implement server-side verification (critical for security)
- Handle success/failure callbacks
Store the order and amount before redirecting, verify the response on your server, compare amount and order ID, then mark it paid. Handle duplicate callbacks so retries do not create two orders.
For no-code (Carrd + forms):
- Use payment links or third-party tools
Manual links suit low volume, but someone must reconcile each payment. Do not assume the customer’s note contains the order number.
Step 3 — Test before going live
- Test with small amount in sandbox
- Verify callbacks work
- Check order status updates
- Test failure scenarios
Also test cancellation, timeout, refresh, duplicate callbacks and a slow mobile connection. Check what the customer sees on success, failure and pending. A successful payment with an error page creates support work and distrust.
Step 4 — Go live & track
- Switch to live keys
- Enable logging
- Reconcile with bank/wallet statements
- Keep records for tax
Reconcile daily or weekly. Match settlement reports to orders, note fees and refunds, and investigate mismatches. Keep transaction IDs, not just screenshots.
Fees & considerations
| Gateway | Typical fee | Notes |
|---|---|---|
| eSewa | Varies by merchant | Check current rate |
| Khalti | Varies by merchant | Check current rate |
| Stripe | ~3%+fixed (int’l) | For global sales |
Check current merchant rates with providers.
Ask every provider whether the fee is percentage, fixed or both, whether VAT applies, when money settles, what refunds and chargebacks cost, and whether there are monthly fees. The cheapest headline rate is not always cheapest overall.
COD has hidden costs: failed deliveries, return trips and reconciliation. Offer it where customers expect it, but price it in.
Security tips
- Never expose secret keys in frontend code
- Always verify payments server-side
- Use HTTPS (required)
- Log transactions securely
- Keep keys rotated as needed
- Compare the paid amount and currency with the order
- Validate webhook signatures and use idempotency
- Enable two-factor authentication and restrict admin access
- Never store card numbers or wallet credentials
- Treat payment screenshots as unverified
- Be suspicious of overpayment refund requests
Compliance and record-keeping
Keep invoices, transaction IDs, settlement statements and refund records for accounting, tax and disputes. Display terms, delivery charges and refund policy before checkout.
Payment and foreign-exchange rules change. Confirm requirements with the provider, an accountant or a legal adviser. This is general guidance, not legal or tax advice.
Practical Nepal considerations
Wallet payments work best when the journey is familiar. Show eSewa and Khalti logos, explain steps in simple Nepali and English, and keep the amount visible. A QR code helps for delivery payments, but confirm payment before handing over goods.
Connectivity and failed transactions happen. Give customers a support number and a clear “payment pending” message. Outside major cities, COD may still decide the sale.
For international customers, check gateway eligibility for a Nepal-registered business before promising card payments. Some providers require a foreign entity; verify directly.
Implementation timeline
| Week | Focus |
|---|---|
| 1 | Prepare documents and apply for merchant accounts |
| 2 | Build and test integration in sandbox |
| 3 | Test failures, refunds and mobile checkout |
| 4 | Soft launch with small orders and reconcile |
Pre-launch checklist
- Merchant account approved and live keys stored securely
- Payment verified server-side before fulfilment
- Success, failure and pending pages are clear
- Test order reconciled
- Refund and cancellation process documented
- Terms, privacy and delivery policies published
- Support contact visible on checkout
- Mobile checkout tested on a real phone
Common mistakes
- Trusting the browser redirect instead of verifying server-side
- Hardcoding secret keys in JavaScript or a public repository
- Skipping failure and duplicate-callback tests
- Launching without a refund policy or support process
- Accepting a payment screenshot as proof
- Forgetting to reconcile settlements and fees
- Ignoring mobile checkout until after launch
The bottom line
For most Nepali online stores, eSewa + Khalti + COD cover 95% of customers. Get merchant accounts, test thoroughly, and focus on a smooth checkout experience.
Fact-checked September 2026. Fees/policies change; confirm with providers. General information.
