eSewa vs Khalti for Merchants: Nepal's Two Wallets Compared

Why the comparison matters

Nepal is a compact but fast-digitising market. Two wallets, eSewa and Khalti, carry most consumer volume, while connectIPS and Fonepay link the banking system for larger transfers. A merchant deciding between eSewa and Khalti is really deciding how much of the addressable customer base to reach on day one.

Volumes are lower than the rest of the region, so operational discipline — clean reconciliation and predictable payouts — matters more than raw scale.

Side-by-side

Maturity

eSewa: The longest-established Nepali wallet with a wide user base

Khalti: Newer, with strong adoption among digital-first users

Flow

eSewa: Wallet authorisation with callback confirmation

Khalti: Wallet authorisation with callback confirmation

Limits

eSewa: Bounded by wallet KYC tiers

Khalti: Bounded by wallet KYC tiers

Best for

eSewa: Widest single-wallet coverage

Khalti: Incremental reach and redundancy

Operational differences that surface later

Feature tables rarely capture what actually costs you money in production:

• Confirmation behaviour. Callback timing under load differs between providers, so a single global timeout is usually wrong for at least one of them.
• Failure taxonomy. Reason codes are not identical; map them to your own canonical set rather than displaying raw upstream strings to customers.
• Reference formats. Store each rail's reference separately so reconciliation and refunds stay unambiguous.
• Downtime patterns. Independent providers rarely degrade at the same moment, which is why running both is a resilience decision as much as a coverage one.

Bank holidays follow the Bikram Sambat calendar, so settlement calendars must be configured locally or payouts silently slip a day.

Verdict

Support both, and add connectIPS or Fonepay bank transfer for amounts above wallet tiers. In a market this size the marginal integration effort is small relative to the conversion gained.

What to do at checkout

1. Show both options with recognisable branding rather than a generic "wallet" button.
2. Route by amount where limits differ, before the customer hits a failure.
3. Keep a bank transfer option visible for higher-value orders.
4. Log method selection so you can measure real preference in your own traffic.

Merchant benefits

• eSewa and Khalti through a single Nepal integration
• Automatic failover when one provider degrades
• Unified reconciliation across both rails
• Settlement on T+1 in most cases

Related guides and solutions

• Nepal Payment Gateway
• High Risk Payment Solution Nepal
• Solutions overview
• Cross-Border Payment Solutions
• Payment Infrastructure
• High-Risk Merchant Payment Processing
• Countries hub

Talk to our team

If you are evaluating acceptance in Nepal, the fastest way to get a useful answer is to share your vertical, expected monthly volume and required payout frequency. Our team can confirm which rails are available to your business, what documentation underwriting will ask for, and how quickly you can go live. Start with merchant onboarding or contact us directly.

Frequently asked questions

Should I integrate eSewa or Khalti first?

Support both, and add connectIPS or Fonepay bank transfer for amounts above wallet tiers. In a market this size the marginal integration effort is small relative to the conversion gained.

Does supporting both increase costs?

Marginally in integration effort, but the additional coverage and the resilience gained when one provider degrades normally outweigh it.

How do I handle amounts above wallet limits?

Route them to a bank rail. Detect the limit before submission so the customer sees the right option instead of a failure.

How is settlement handled across both methods?

Both settle into the same reconciled ledger with per-transaction references, on T+1 in most cases.