eSewa Merchant Payment Guide: Accepting Payments in Nepal

eSewa is Nepal's most established digital wallet and the anchor method for most merchants selling into the country. Nepali consumers reach for wallets before cards, and a checkout that does not present eSewa clearly loses volume it never sees. This guide explains eSewa acceptance from a merchant operations perspective.

Why eSewa matters

eSewa has the broadest brand recognition in Nepal's digital payment market, a mature merchant ecosystem and strong urban and semi-urban penetration. For merchants:

• It is the wallet most customers assume will be available.
• Trust is high for first-time payments to unfamiliar merchants.
• It reaches customers who do not hold internationally usable cards.
• Combined with Khalti, it covers the practical majority of digital payers.

Enabling both major wallets is the baseline; treating either as optional caps your conversion.

How the payment flow works

Initiation

Your gateway creates a payment with amount, merchant reference and callback destination. The customer is directed into the wallet's confirmation experience to authenticate and approve.

Confirmation

Credit the order from a signed webhook confirming execution. Browser redirects are unreliable as a crediting mechanism because customers close tabs, switch apps and lose connectivity.

Terminal states

Plan for completed, failed, cancelled and expired. The problematic state is created-but-unconfirmed. Set an explicit timeout, sweep unresolved payments against the provider's status endpoint, and resolve every order definitively.

Integration best practice

1. Idempotency keys on every payment creation call.
2. Store the provider reference against your internal order ID at creation.
3. Verify webhook signatures; make handlers idempotent and replay-safe.
4. Use status polling as a safety net, never as the primary path.
5. Handle expiry with clear messaging and easy retry.
6. Present eSewa with correct branding and NPR formatting.
7. Log every state transition with timestamps.
8. Test timeouts, duplicates and late confirmations before launch.

Provider API behaviours worth validating are described in how payment APIs work.

Limits and bank rail pairing

Wallet payments are sized for consumer transactions and constrained by per-transaction and periodic limits. Merchants with larger average order values should pair the wallet with bank transfer rails, recommend the appropriate method by amount automatically, and surface limits before the customer attempts payment.

Full method context is on the Nepal payment gateway page.

Improving success rates

• Give the wallet native branding and prominent placement.
• Show the exact amount clearly before the confirmation step.
• Preserve the merchant session so customers return to a working order.
• Monitor completion rates by hour and ticket band.
• Offer an immediate alternative method after failure rather than a dead end.
• Use health-based routing across available paths where supported.

In a smaller market, small conversion differences matter proportionally more, and provider stability often matters more than a marginal pricing advantage.

Payouts

If your model requires outbound payments — refunds, customer withdrawals, partner or affiliate settlements — evaluate payout capability separately from collections. Confirm per-transaction and daily limits, beneficiary validation, the status lifecycle including returns, batch capability, reconciliation of failures and realistic completion times.

Reconciliation

Reconcile daily across wallet collections, bank credits, payouts and returns. Match by provider reference and internal order ID, categorise breaks, and investigate within twenty-four hours. Wallet markets generate unmatched credits when customers pay with incorrect references; a disciplined reconciliation process catches these while they are still resolvable.

System-level guidance is in the merchant payment infrastructure guide.

Cross-border settlement

eSewa settles in NPR to Nepali bank accounts, which generally requires a locally registered entity. Merchants incorporated abroad collect through a provider with dedicated Nepali banking that settles internationally in a major currency. Confirm cycle, reserve terms and FX methodology in writing — see the cross-border payment guide for South Asia.

Where eSewa fits in a full strategy

The practical Nepali stack is eSewa plus Khalti for wallet coverage, bank rails for higher-value payments, and cards as a secondary channel. Selection guidance is in best payment gateway Nepal. High-risk merchants should also read how high-risk payment processing works and the high-risk payment solution Nepal page.

Common mistakes

• Crediting orders from redirects rather than webhooks.
• Enabling one wallet and assuming full coverage.
• No timeout policy for unconfirmed payments.
• Ignoring bank rails and capping order value unintentionally.
• Reconciling monthly instead of daily.
• Promising customer withdrawals before testing payouts.

How PayEurasia supports Nepal

PayEurasia integrates the leading Nepali wallets alongside bank rails, with signed webhooks, idempotent APIs, method-level reporting, payout capability, unified reconciliation and transparent cross-border settlement for merchants incorporated outside Nepal.

Contact our team with your entity structure, volumes and vertical.

Frequently asked questions

How do merchants accept eSewa payments in Nepal?

Merchants integrate through a payment gateway that creates a payment with an amount and merchant reference, directs the customer into the eSewa confirmation flow, and credits the order on a signed webhook confirming execution, backed by a status query sweep.

Should I enable both eSewa and Khalti?

Yes. eSewa has the broadest recognition and Khalti has strong urban traction, so enabling both maximises coverage. Enabling only one leaves a meaningful share of Nepali customers without their preferred wallet.

What are eSewa transaction limits?

Wallet payments are subject to per-transaction and periodic limits designed for consumer-scale transactions. Merchants with higher order values should pair the wallet with bank transfer rails and display limits before the customer attempts payment.

Does eSewa support merchant payouts?

Payout support depends on the provider and configuration. If your business requires refunds at scale or customer withdrawals, verify payout coverage, limits, beneficiary validation and return handling before you rely on it.

Can a foreign company collect eSewa payments?

Not directly, since settlement is in NPR to Nepali bank accounts that generally require a local entity. Foreign merchants use a cross-border provider operating dedicated Nepali banking and settling internationally.

How fast is settlement for Nepali wallet payments?

Domestic settlement is commonly same-day to T+2 depending on provider and agreement, with cross-border settlement following the agreed remittance cycle. Confirm reserve percentage and release timing alongside the cycle.