Merchant decision question
Which option between eSewa Merchant Services and Khalti Payment Gateway should we verify first for our Nepal checkout, operations, and reconciliation workflow?
When eSewa Merchant Services may fit
Prioritize when eSewa wallet acceptance, merchant payments, and the eSewa developer/contact route are central to the Nepal checkout plan.
When Khalti Payment Gateway may fit
Prioritize when Khalti's gateway documentation, merchant support route, and intended checkout workflow need first validation.
What to verify before integration
- What entity, local bank account, tax, and KYB documents are required for merchant onboarding?
- Which wallet, gateway, API, hosted checkout, payment-link, refund, and reconciliation flows are supported?
- Are the required webhooks, test environment, plugins, and production credentials available before launch?
- What fees, settlement timing, payout currency, reserves, and support commitments will be provided in writing?
- How are failed payments, customer disputes, and operational escalations handled?
Contact and verification next steps
- eSewa Merchant Services: official developer contact page/email if verified. Use the official eSewa developer contact page and published inbox; do not assume eligibility.
- Khalti Payment Gateway: official docs/contact page/email if verified. Use Khalti's official docs and contact route; do not assume merchant approval.
Commercial verification note
Use official provider pages or a written provider response to confirm commercial terms, payout handling, refunds, disputes, account setup, and support ownership for the exact merchant case.
Do not treat country coverage or brand support as proof that a specific merchant entity, industry, payout currency, or operational workflow is available.
Public sources to verify
Review notes
- Do not treat public marketing pages as final commercial terms; request written confirmation for the exact merchant model.
- Checkout fit can vary by product category, sales channel, currency, and customer location, so test the intended flow directly.
- Bank, wallet, and aggregator routes may create different refund, dispute, reporting, and reconciliation responsibilities.
- Onboarding review can depend on documentation quality, business category, ownership checks, and risk review questions.
Questions merchants ask
Should we choose eSewa Merchant Services or Khalti Payment Gateway in Nepal?
Use the comparison to prepare verification questions. The answer depends on customer behavior, merchant entity, industry, provider route, risk review, commercial terms, payout handling, refunds, disputes, and support.
Does this page confirm merchant eligibility?
No. Merchant eligibility must be confirmed with the PSP, acquirer, wallet operator, bank, scheme, or platform route before integration.
Are commercial terms confirmed here?
No. Confirm commercial terms, payout handling, refund handling, dispute ownership, and support commitments with the provider before launch.