eSewa Merchant Onboarding and Source Verification

What this page covers

If you are building a checkout for customers in Nepal, eSewa is one of the names you will come across. This page sets out what our directory has actually recorded about that profile, what a merchant review normally asks of you, and the questions to put to the provider before you build anything.

What our directory has recorded

Our directory holds a Nepal market coverage record for eSewa, created from the provider's own website on 11 August 2026, with the official website recorded as esewa.com.np. The same record set covers four other Nepal-linked names: connectIPS, Fonepay, IME Pay and Khalti.

A coverage record says one thing: our research team linked the provider to the Nepal market using an official source. It does not say the provider offers a merchant product, that the product is open to new merchants in your category, or that it is live today. Each profile shows the verification state and the source date of every field, and where our records hold nothing the profile says "Not publicly disclosed".

What a merchant review normally asks of you

The document set varies by provider, but the same categories recur: company registration records, a tax identification number, bank account details held in the business's own name, ownership or director information, a written description of what you sell and who buys it, and access to the website where you sell it. Providers also look at how refunds and cancellations are handled, because those patterns show up later in transaction monitoring.

The useful questions are the plain ones: who reviews the file, how long a complete submission normally takes, what triggers a second review, and what happens to funds while the file is open.

Questions to put to the provider

1. **Is the merchant product open to new businesses in my category today**, rather than planned? 2. **Which payment methods are enabled at go-live**, and which arrive later? 3. **What does the customer see** during payment, and what happens if they abandon the flow? 4. **How are failures reported** - timeouts, partial responses, and how you reconcile them? 5. **Refunds** - who initiates them, how long they take, and what the customer is told. 6. **Settlement** - when funds arrive, into which account, and in which currency. 7. **Cost** - what you pay per transaction and per failed attempt, in writing. 8. **Support** - the escalation route when a payment fails outside office hours.

Where the official material sits

Nepal Rastra Bank publishes material on payment systems at https://www.nrb.org.np. Read it for yourself rather than relying on a reseller's summary. Our directory does not interpret those rules for your business, and it does not state that any listed provider holds a licence.

What our records do not cover

For this provider the directory does not hold verified data on pricing, onboarding time, acceptance rules, settlement timing, or authorisation status. Those answers must come from the provider, in writing, so you can compare two or three of them on the same basis.

Where to look next

The Nepal country page lists the providers our directory has recorded for that market. Place two or three profiles in the comparison tool to see which fields are verified and which are still missing. If you hold an official document that adds or corrects a record, submit it through the correction form on the profile and we will check it against the source before the record changes.

One more thing worth asking

Ask who your account is escalated to when a payment is disputed or a payout fails, and what the expected response time is. A provider that cannot name an escalation route is telling you something about the support you will receive after go-live, and that answer is worth recording with the rest.