eSewa, Khalti, FonePay, connectIPS and cards — how Nepali businesses actually accept online payments, and what integration takes.
A decade ago, taking an online payment in Nepal was the hardest part of e-commerce. In 2026 the rails exist and compete for merchants — the complexity has moved from “is it possible” to “which mix of rails does your customer base need”. This guide maps the options and the operational work that comes with each.
The rails, one by one
Wallets — eSewa, Khalti and peers. The consumer default. Two-tap checkout from an app most Nepali customers already have, simple merchant onboarding, per-transaction fees. Wallets are where small-ticket commerce lives: food, tickets, top-ups, digital goods.
Bank rails — FonePay, connectIPS. Direct account-to-account payments through the banking network. Strong for larger amounts and for customers who distrust wallets; weaker on checkout friction (more steps, redirection to the bank’s interface).
Cards. Necessary for international customers and expected for credibility. Nepali merchants can acquire cards through supporting providers; the constraints are stricter onboarding and the permanent work of fraud and chargeback handling. Historically this was the wall that blocked Nepali e-commerce — it has opened considerably, but treat it as a compliance project, not a plugin install.
QR at the edge. Interoperable QR quietly did as much for commerce as any gateway product: the same scan-to-pay works for the corner shop and the online order confirmation. If you sell offline-to-online, QR is part of your stack whether you planned it or not.
What integration actually takes
All the majors expose REST APIs and plugins for WooCommerce and the common carts. The engineering is a few days. The permanent work is operational:
- Reconciliation — matching settlement reports against orders, daily. Discrepancies are normal; unnoticed ones are not.
- Refunds — each rail has its own refund flow and timing. Write yours down before launch.
- Failure handling — users double-pay when a confirmation times out. Idempotent checkout and a clear “what did you pay?” lookup save support hours.
- Checkout UX — show fees honestly, keep the wallet choice to two options, and test on cheap Android phones over 4G.
Onboarding checklist
Merchant onboarding typically wants: a registered business (PAN/VAT), a bank account in the business name, a working website with visible product, pricing, contact and refund pages, and a reachable phone. Prepare those before applying and approval is measured in days. Fees vary by provider and volume — get current rates in writing from each provider rather than trusting any article (including this one) for exact percentages.
Deep dives, rail by rail
Each rail has its own onboarding and its own operational quirks, so we maintain a dedicated guide per rail:
- eSewa merchant account — documents, onboarding and integration for the default wallet
- Khalti merchant guide — the second wallet, and the cleanest API
- FonePay QR — the interoperable counter QR and its settlement model
- connectIPS — the bank-account rail for high-ticket and corporate buyers
- Accepting international payments — card acquiring, foreign entities, Payoneer, Wise and dollar cards
- PayPal in Nepal — the reality check, and what to use instead
A note from this domain’s history
The old podamibenepal.com sold “The Smart Gateway” payment-integration product in 2021 and published exactly this kind of explainer in 2020 — the thesis then was that payments were Nepal’s e-commerce bottleneck. That turned out to be right, and the bottleneck has since been broken open. What hasn’t changed is the operating discipline the good merchants had then and still have now: reconcile daily, refund fast, and never make the customer guess whether their money arrived.
FAQ
Which payment gateway should a Nepali online store use?
Wallet coverage (eSewa, Khalti) plus a bank rail (FonePay or connectIPS) covers most Nepali customers. Cards matter for international buyers. Most stores integrate two rails rather than one.
Can Nepali merchants accept international cards?
Yes, through providers that support card acquiring for Nepali merchants; onboarding requirements and fees are stricter than for domestic wallets. Historically this was the hard part — it has improved but still deserves a compliance check first.
How long does merchant onboarding take?
With complete documents — business registration, PAN/VAT, bank account, a working website with clear product and refund pages — days rather than weeks. Incomplete paperwork is what turns onboarding into months.