eSewa Merchant Account: A Complete Guide

If you sell anything in Nepal, an eSewa merchant account is usually the first digital rail you turn on. It is the oldest wallet in the country, the one your customers already have installed, and the one your accountant will spend the most evenings reconciling. This guide walks the whole path - from application to merchant code to the settlement flow - and flags the gotchas that trip up new merchants.

Getting a merchant account

An eSewa merchant account is different from the personal wallet on your phone. A personal wallet receives money person-to-person. A merchant account receives money as a business, gives you a merchant code, and settles the pooled balance to a bank account in your business name.

To apply you generally need:

• A registered business (PAN or VAT registration, company or firm registration).
• A bank account in the business name for settlements.
• Owner identification and, for companies, the registration documents.
• The physical or digital storefront you want to accept payments for.

You submit these through eSewa's merchant onboarding, and after verification you are issued a merchant code (often written as a SCD or product code) along with the credentials your integration needs.

Merchant code, secret key, and environments

Once approved you get three things that matter for reconciliation later:

• The merchant code - identifies your account on every transaction. It is the anchor you will match reports against.
• A secret key - used to sign payment requests so eSewa can verify the amount was not tampered with in the browser. Treat it like a password; it belongs on your server, never in client-side code.
• A test environment. eSewa publishes a sandbox at developer.esewa.com.np with test credentials so you can run the full payment and verification loop before going live.

The current integration is the ePay v2 flow: your server builds a signed request, the customer is redirected to eSewa to authorise, and eSewa redirects back with a signed response you verify server-side. Always re-verify the status through eSewa's status-check endpoint rather than trusting only the browser redirect - a customer can close the tab at exactly the wrong moment.

How money actually moves

This is the part new merchants misread most often, so it is worth being precise.

A successful payment does not land in your bank. It lands in your eSewa merchant wallet. The money only reaches your bank when a settlement sweeps the wallet balance - net of fees - into your settlement account.

So your money lives in two places at once:

• Settled - already moved to the bank.
• Pooled - captured in the wallet, waiting for the next settlement.

A single bank credit is a batch containing many payments collapsed into one number, with the service fee already deducted. If you have ever wondered why the credit is smaller than your dashboard total, this is why. We cover the decomposition in detail in reading your eSewa settlement report.

The report and settlement flow

For reconciliation you will work with two exports:

• The transaction / wallet report - every payment captured, with reference codes, amounts, and timestamps. This is your gross.
• The bank statement - where settlements land, tagged with narrations like ESEWA STL.

The reconciliation job is to prove that a group of transactions in the report, minus the service fee, equals a specific credit on the bank statement. When they sum, the settlement is decomposed. Whatever is left over is a residual - and a residual is a question you should answer, not a rounding difference to ignore.

Gotchas that cost real money

• Fees are silent. The service fee is deducted inside the settlement, not billed separately. On a busy day a 2-3 percent fee is meaningful, and it is easy to forget when you glance at gross sales.
• Timing splits batches. A payment late in the day may settle in tomorrow's batch. Today's settlement looks short until you realise the payment simply moved.
• Refunds may net rather than reverse. A refund can be deducted from a later settlement instead of appearing as its own line - the same behaviour Khalti has, which we explain in why a Khalti refund reduces your next settlement.
• Trusting the redirect. Never mark an order paid on the browser redirect alone. Always confirm with the server-side status check.
• Wallet vs. bank confusion in your books. If your accounting treats a wallet capture as cash-in-bank, your bank reconciliation will never tie out. Keep the wallet as its own ledger until settlement.

VAT and record-keeping

Digital payments do not change your tax obligations - a sale is a sale. But the fee and settlement structure does affect how you record revenue and the cost of collection. Keep the transaction reports; they are the primary evidence behind every rupee, and the eSewa figures should tie back to the deposits you report. Nepal Rastra Bank sets the payments rules the wallets operate under, and you can read the framework at nrb.org.np.

Where RakamHQ fits

Once you are live, the daily grind is not taking payments - it is proving they all arrived. RakamHQ ingests your eSewa report and your bank statement, decomposes every settlement into the payments and fee inside it, and names any residual instead of absorbing it. The goal is a proven daily close every morning, without opening a spreadsheet.

Frequently asked

What do I need to open an eSewa merchant account?

A registered business with PAN or VAT, a settlement bank account in the business name, owner identification, and details of the storefront or site accepting payments.

Does a successful eSewa payment go straight to my bank?

No. It lands in your eSewa merchant wallet first and only reaches your bank when a settlement sweeps the wallet balance, net of fees, in a batch.

Why is my eSewa bank credit smaller than my sales total?

The service fee is deducted inside the settlement, timing can push a late payment into the next batch, and refunds may net against the payout rather than appear as a separate line.

Should I trust the browser redirect to confirm payment?

No. Always re-verify with eSewa's server-side status-check endpoint, because a customer can close the tab before the redirect completes.

Keep reading

How to Read Your eSewa Settlement Report (Without the Headache)

Read

The eSewa Wallet Balance Rule Nobody Reads

Read

eSewa vs Khalti vs Fonepay for Merchants

Read