Why Your Payment Gateway Choice Actually Matters
If you're setting up an online store in Nepal, the first question customers ask is usually: "Do you accept eSewa or Khalti?" But as a merchant, your decision is more nuanced than just switching both on and calling it done. Merchant fees compound across every sale, settlement timing affects your cash flow during tight months, and a poorly integrated checkout kills conversions at the final step.
This guide compares the three payment options most relevant to Nepali SMBs — eSewa, Khalti, and FonePay — across the dimensions that actually affect your business: fees, settlement speed, customer reach, and integration effort.
eSewa: The Household Name
Launched in 2009, eSewa is Nepal's oldest digital wallet and still carries the largest registered user base in the country. Demographic reach is its main advantage — customers in their 30s and 40s, government employees, people outside the Kathmandu Valley, and anyone who uses digital payments to pay electricity or water bills almost certainly has eSewa installed already.
Merchant Fees
The standard merchant fee is around 1.5% per transaction. High-volume merchants can negotiate, but for most small stores you'll be at or near that rate. There is no recurring monthly platform fee for basic merchant access, though you'll need to complete business KYC — PAN number at minimum, VAT registration if your turnover requires it — before your merchant account goes live.
Settlement Speed
Settlements land on a T+1 or T+2 basis (next business day or the day after) for verified merchants. Plan for an extra day during Dashain and Tihar: the entire Nepal digital payments infrastructure handles a massive transaction spike across those weeks, and settlement queues can stretch longer than usual. If you're running a Dashain sale, factor that into your cash-flow expectations rather than getting surprised mid-festival.
Customer Adoption
eSewa's biggest strength is breadth. It's accepted at petrol pumps, government payment portals, telecom top-ups, and thousands of physical shops via QR. Customers have been loading and spending from eSewa wallets for over a decade, so checkout friction is low — they know exactly what to do.
Integration
eSewa provides a REST API and a hosted checkout option. Documentation has improved steadily. The most common integration mistake is skipping or incorrectly implementing the server-side payment verification step — after eSewa redirects the customer back to your store, you must verify the transaction on your server before marking the order as paid. Skipping this creates a security gap that bad actors can exploit.
Khalti: The Developer-Friendly Challenger
Founded in 2017, Khalti has built a strong position among urban, digitally native users — particularly in Kathmandu, Pokhara, and among college students and young professionals. It's also developed a reputation among developers for having cleaner, more navigable API documentation, which matters a lot when you're a small business integrating without a dedicated tech team.
Merchant Fees
Khalti's fees sit broadly in the same range as eSewa — around 1.5% to 2%, depending on your agreement and monthly volume. Khalti also supports a bank transfer option (Khalti Online) that lets customers pay directly from their bank account rather than a loaded wallet balance. For higher-ticket orders — furniture, electronics, bulk purchases — this removes the friction of customers needing to top up their wallet before buying.
Settlement Speed
Settlement is generally T+1 for verified merchants. The merchant dashboard gives reasonably clear visibility into pending and completed settlements, which helps with daily reconciliation — a task most small shop owners in Nepal still handle manually alongside their physical cash records.
Customer Adoption
Khalti's installed base is smaller than eSewa's in absolute numbers but growing. If your store skews toward younger buyers — fashion, accessories, digital products, gaming, online courses — Khalti may actually convert better for that segment. Offering both gateways at checkout is increasingly the baseline expectation for any credible Nepal e-commerce store; a customer who lands on a checkout with only one option and it's not their wallet will often abandon.
Integration
Khalti's developer portal is well-regarded for its clarity, with working sandbox credentials and straightforward documentation. The same rule applies here: always verify payments server-side and never trust only the client-side redirect. Both Khalti and eSewa's webhooks can be tested thoroughly in sandbox before you go live.
FonePay: The QR Network for Hybrid Sellers
FonePay is a different animal entirely. It's not a wallet — it's an interoperable QR payment network operated under the Nepal Clearing House Limited (NCHL) framework and connected to most major Nepali banks and wallets. When a customer scans your FonePay merchant QR, they can pay from their NIC Asia mobile banking app, NMB, Laxmi Bank, Khalti, or any other connected institution — all through one QR code you got from your bank.
Where FonePay Fits
FonePay is strongest for physical retail and hybrid businesses — shops that have a counter or POS as well as an online presence. If you run a clothing store in Baneshwor and also sell through Instagram or your own website, a FonePay QR at your till means walk-in customers can pay however they prefer without you maintaining separate terminal agreements with every bank. Funds settle directly to your linked bank account rather than into a third-party wallet you then need to cash out, which some merchants prefer for accounting simplicity.
Online Store Integration
FonePay does have an online payment API, but it's less commonly integrated into e-commerce storefronts compared to eSewa or Khalti. For a pure online store, eSewa and Khalti will cover more of your customer base with less integration effort. For brick-and-mortar shops moving online, FonePay can serve as a natural bridge — your existing bank relationship likely already supports it.
Comparing Them Side by Side
- Largest customer base: eSewa
- Best API documentation: Khalti
- Best for physical/POS and hybrid stores: FonePay
- Settlement speed: All three are broadly T+1 to T+2 for verified merchants; expect festival delays
- Merchant fees: Broadly 1.5–2% across all three; negotiate if you have consistent volume
- KYC requirement: All three require business KYC — PAN number minimum, VAT if applicable
- Bank transfer option: Khalti (via Khalti Online); FonePay natively; eSewa wallet-primary
What Most Nepal Online Stores Should Actually Do
For most SMBs, the practical answer is: integrate both eSewa and Khalti. The incremental effort of adding the second gateway once the first is working is small — most of the infrastructure (server-side verification logic, order status handling, webhook security) is already in place. The cost of not offering both is losing customers at the final step.
If you also have a physical counter, add a FonePay QR sticker from your bank — it requires one branch visit and zero additional code. Customers who prefer bank transfers appreciate having the option, and you're not locked into a single wallet network for walk-in sales.
Platforms like Saauzi that are built specifically for Nepal handle these integrations at the platform level, so you can activate eSewa, Khalti, and COD from a single dashboard without debugging webhook callbacks yourself — useful when your time is better spent on sourcing, pricing, and customer service.
Finally: keep COD enabled. Cash on delivery still drives the majority of orders in Nepal outside the major urban centers. Many first-time buyers default to COD and switch to digital wallet on repeat purchases once they trust your store. Disabling COD to push digital payments early will cost you more orders than the reconciliation effort is worth.
Actionable Takeaway
Treat this as a stack, not a choice: enable eSewa for reach, Khalti for urban and younger buyers, FonePay if you have a physical presence. Complete business KYC with each provider — your PAN and, if applicable, VAT registration number will be required. Test every payment flow end-to-end in sandbox before your next Dashain or Tihar campaign. A broken callback discovered during your highest-traffic week of the year is an expensive lesson.
Comments
Be the first to comment.