Nepal · Payment Gateway

Nepal Payment Gateway

Accept eSewa, Khalti and bank transfers through one enterprise API

By PayEurasia Payments TeamLast updated

Nepal is a small market by population and a large one by opportunity. Wallet adoption has moved faster than merchant acceptance, which means demand routinely exceeds the number of businesses able to take a local payment. Merchants who establish native NPR acceptance early face far less competition for the checkout than they would in India or Bangladesh.

PayEurasia is a Nepal payment gateway built to the same standard as our larger markets: eSewa and Khalti coverage, bank transfer for higher tickets, idempotent APIs, HMAC-signed webhooks, monitored routing and settlement reporting a finance team can reconcile without manual matching.

Payment methods

The Nepali rails that convert

Two wallets carry most consumer digital payment volume in Nepal, with interbank transfer covering larger and business-to-business flows. Offering both wallets rather than one materially widens the customer base you can serve.

eSewa

Nepal's longest-established digital wallet, with nationwide agent coverage and deep consumer trust.

Khalti

A rapidly growing wallet and payment platform with strong adoption among urban and younger customers.

Bank transfer

Interbank collection with unique reference matching for larger ticket sizes and B2B settlement.

Local bank accounts

Dedicated NPR collection accounts for merchants requiring bank-native acceptance.

Payouts

Disbursement to wallets and bank accounts with the same idempotency and webhook guarantees as collections.

Routing control

Adjust method and provider routing from the merchant portal as live performance data accumulates.

How it works

From checkout to settlement in four steps

1. Create a transaction

Call the transactions API with amount, currency, method and an idempotency key. You receive a transaction reference and the payment instruction immediately.

2. The customer pays locally

The customer completes the payment in eSewa or Khalti, or sends a bank transfer quoting the unique reference returned by the API.

3. Signed webhook

An HMAC-signed webhook fires the moment the payment state changes. Verify the signature and keep the handler idempotent — delivery is at-least-once.

4. Settlement and reporting

Confirmed volume enters your NPR merchant balance. Settlement, fee and commission lines are exportable per period for reconciliation.

Developer API

Engineering details that keep ledgers correct

Idempotency keys

Safe retries: a repeated request returns the original transaction instead of creating a duplicate.

Stable references

A single reference used across dashboards, webhooks, exports and support tickets.

Retrying webhooks

Automatic retry with backoff so transient downtime on your side does not drop events.

Sandbox coverage

Test success, failure, timeout and duplicate scenarios before production traffic.

Explicit states

Documented transaction states with complete per-transaction history.

Structured errors

Actionable error codes that speed up integration debugging.

Industries

Merchants we support in Nepal

Complex verticals are the ones most often turned away by domestic processors focused on simple e-commerce. We underwrite each merchant individually — see the high risk payment solution Nepal page for how that review works in practice.

  • Forex
  • iGaming
  • Sports betting
  • Casino
  • Gaming
  • SaaS
  • Digital services
  • Subscriptions
Benefits

Why merchants choose PayEurasia in Nepal

Route monitoring

Continuous success rate, latency and decline tracking, with failover where redundant capacity exists.

Real-time dashboards

Transactions, balances, settlements and disputes updated as events land.

Clean reconciliation

Fee and commission lines attached to each transaction for straightforward period close.

Compliance built in

KYB onboarding, AML monitoring and auditable administrative logs.

Predictable settlement

Agreed cadence with pending payouts and reserves visible in the portal.

Dedicated support

A named team reachable on Telegram and email through integration and live operations.

Ready to accept payments in Nepal?

Submit a merchant application and our team will scope your method mix, settlement cadence and integration timeline within one business day.

FAQ

Frequently asked questions

What is a Nepal payment gateway?

It is the infrastructure that lets a business collect payments from Nepali customers over domestic rails — digital wallets such as eSewa and Khalti plus interbank transfer — confirm them programmatically and settle the funds to the merchant. PayEurasia provides that layer with reconciliation, reporting and payout tooling behind one REST API.

Which methods does PayEurasia support in Nepal?

eSewa, Khalti, local bank accounts and direct bank transfer. Merchants can enable any combination and adjust routing between them from the merchant portal.

Is card acceptance enough for Nepali customers?

No. Cross-border card usage is limited and concentrated, while wallet adoption is broad. A wallet-first checkout with a bank transfer fallback covers far more of the addressable market than a card-only page.

How is settlement handled?

Confirmed volume enters your merchant balance in NPR. Cadence, settlement currency and any reserve terms are agreed at onboarding and remain visible, with fee and commission lines, in the merchant portal.

Do you accept high-risk merchants in Nepal?

Yes. Forex, iGaming, betting, gaming, SaaS, digital services and subscription businesses are core verticals, underwritten individually rather than declined on category.

How long does integration take?

Typically a few days. Sandbox credentials, idempotent endpoints, HMAC-signed webhooks and reference payloads are available before go-live.

What documents are required to onboard?

Company registration documents, director KYC, a description of the business model and traffic sources, and settlement bank details. Compliance review usually completes within a few business days.

Related reading

Related guides

External references