Payment Gateway Nepal: A Practical Guide for Online Businesses

What a payment gateway does in Nepal

A gateway sits between your checkout and the local payment rails. It presents the customer with the instruments they hold, initiates the transaction on the relevant rail, tracks its lifecycle, and reports the outcome back to your systems. 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.

The difference between a good and a poor gateway in Nepal is rarely the headline price. It is whether the gateway maintains enough redundant connections to keep approval rates stable, and whether it returns data clean enough to reconcile automatically.

Payment methods that matter in Nepal

Coverage is the first filter. A gateway that supports only one wallet forces a share of your customers to abandon, and in a market this concentrated that share is not small.

• eSewa — supported through PayEurasia's Nepal acceptance stack with reference data returned on every transaction.
• Khalti — supported through PayEurasia's Nepal acceptance stack with reference data returned on every transaction.
• connectIPS — supported through PayEurasia's Nepal acceptance stack with reference data returned on every transaction.
• Fonepay — supported through PayEurasia's Nepal acceptance stack with reference data returned on every transaction.

Bank rails are covered through dedicated collection accounts with Nabil Bank, NIC Asia, Global IME and other local institutions, which is what makes larger ticket sizes practical. Coverage per market is listed on the countries hub.

Approval rate is the metric that matters

Two gateways quoting the same fee can differ by several percentage points in completion rate. The causes are usually structural:

• Number of upstream connections per method, and whether traffic can fail over automatically
• Timeout and retry behaviour when a wallet or bank is slow to confirm
• Whether the checkout is optimised for the mobile devices and connection speeds your customers actually use
• How quickly a degraded provider is detected and removed from the routing pool

Bank holidays follow the Bikram Sambat calendar, so settlement calendars must be configured locally or payouts silently slip a day. Ask any prospective provider for approval rate by method over the last 90 days, not a blended average. Our payment infrastructure page explains how routing and failover are implemented on our side.

Fees, and what they are actually made of

Pricing in Nepal generally combines a percentage of transaction value with per-transaction and payout costs. When comparing quotes, normalise for:

• Method mix — wallet and bank rail economics differ
• Refund and reversal handling
• Payout frequency and any minimum settlement amount
• Reserve requirements, if your vertical carries one
• Chargeback or dispute administration costs

A lower rate attached to a lower approval rate is more expensive in practice. Model the total cost per successful order, not per attempt.

Settlement and reconciliation

Settlement runs on T+1 in most cases. What matters operationally is the file behind the money: each payout should be accompanied by a line-level breakdown containing your order reference, the gateway reference, the rail reference, the amount, the fee and the timestamp.

Finance teams should be able to close a day without opening a support ticket. If a provider cannot deliver reconciliation data in a machine-readable format, expect that to become a recurring monthly cost in staff time. The merchant payment infrastructure guide covers the ledger design that makes this straightforward.

Risk, compliance and merchant categories

Nepal Rastra Bank supervises payment service providers closely, and merchant categories are reviewed carefully, so onboarding evidence needs to be accurate from the start. Travel, education, digital subscriptions and remittance-adjacent services drive much of the online payment demand.

Merchants in regulated or high-risk categories should be candid during onboarding. Underwriting that knows what it is looking at can usually structure an approval; underwriting that discovers the truth later suspends the account. See high-risk merchant payment processing and High Risk Payment Solution Nepal for how that works in practice.

Integration checklist

1. Confirm method coverage against your actual customer base, not a generic list.
2. Test failure paths in sandbox: cancellation, timeout, insufficient balance, duplicate submission.
3. Implement idempotency keys on every create call.
4. Verify webhook signatures and make handlers replay-safe.
5. Reconcile a full day in staging before launch.
6. Agree monitoring and escalation contacts before go-live, not after the first incident.

Merchant benefits

• One integration covering eSewa, Khalti, connectIPS and local bank transfers
• Redundant upstream connections with automatic failover
• Reconciliation data designed for finance teams, not just developers
• Settlement on T+1 in most cases
• Support for complex verticals through dedicated underwriting

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

Which payment gateway is best in Nepal?

There is no single answer; the right gateway depends on your vertical, ticket size and payout needs. Compare method coverage, approval rate per method, settlement timing and reconciliation quality rather than headline pricing.

How much does a payment gateway cost in Nepal?

Pricing is normally a percentage of transaction value plus per-transaction and payout costs, and varies by method and merchant category. Compare cost per successful order rather than per attempt.

How fast is settlement?

Settlement generally runs on T+1 in most cases. Payout frequency is agreed at onboarding and depends on volume, method mix and risk profile.

Do I need to support both wallets and bank transfers?

In most cases yes. Wallets carry the majority of transactions by count while bank rails handle larger amounts, so supporting both widens the range of customers you can convert.

Can high-risk merchants get a gateway in Nepal?

Yes, but through providers that underwrite the category deliberately. Expect more documentation, possible reserves and closer monitoring than a standard ecommerce account.