Best Payment Gateway Nepal: 2026 Merchant Guide

Nepal is a compact but fast-maturing digital payment market. Wallet adoption is high in urban and semi-urban areas, bank-linked rails have improved significantly, and merchants selling into Nepal now have genuine options — provided they understand the settlement and entity constraints before they integrate.

This guide explains how to choose the best payment gateway in Nepal, which methods actually convert, and what changes for internationally incorporated or higher-risk merchants.

What is a payment gateway?

A payment gateway is the software layer that converts a customer's intent to pay into an instruction the financial system will act on, then returns a result your application can rely on. In Nepal that means integrating wallets, bank-linked rails and cards through a single interface, recording every attempt durably, and reconciling those records against what actually settled.

Three roles matter. The gateway is the technical surface — API, checkout, webhooks. The acquirer is the licensed institution that clears funds, typically a bank or a payment institution authorised by the central bank. A payment service provider wraps both together with onboarding, risk monitoring, settlement and support. Nepali merchants generally work with a PSP, because direct wallet and bank relationships require local incorporation, deposits and a compliance function.

Everything commercially meaningful is set at the acquiring layer: permitted categories, per-transaction and daily limits, refund handling, reserves and settlement timing. Those terms — not the checkout design — are what you are really choosing between.

Why businesses need a payment gateway in Nepal

Nepal's digital payment adoption has moved quickly, particularly in urban and semi-urban areas, and consumers now expect wallet payment as the default online experience. A merchant offering only bank deposit instructions or card entry converts poorly against that expectation.

The practical case for integrating properly:

• Conversion. Native eSewa and Khalti flows remove manual deposit-and-screenshot workflows, which are the largest single source of abandonment in this market.
• Automation. Manual verification of transfers cannot scale, and it invites forged-receipt fraud.
• Reconciliation. A gateway produces a traceable chain from attempt to settlement batch — essential once you are handling hundreds of orders a month.
• Payouts. Refunds, agent commissions and customer withdrawals are far safer through a disbursement API than through spreadsheets and manual bank transfers.
• Compliance. Regulated collection provides the KYC, narration and audit trail that banks and auditors expect.

Coverage for the market is summarised on the Nepal payment gateway page, with the ledger, routing and reporting layer described on payment infrastructure.

The Nepali payment landscape

eSewa

eSewa is the most established digital wallet in Nepal with the broadest consumer recognition. For most merchants it is the anchor method: if only one wallet is enabled, this is usually the one, though single-wallet strategies leave meaningful volume on the table.

Khalti

Khalti is the other major wallet with strong urban penetration and a well-developed merchant ecosystem. Running eSewa and Khalti together is the practical baseline for national coverage.

Bank transfer rails and connectIPS

Bank-linked transfer infrastructure handles larger ticket sizes and business payments. Wallet limits make bank rails necessary for anything above consumer-scale amounts, and a competent gateway will reconcile wallet and bank credits into a single ledger view.

Cards

International card acceptance exists but is a minority channel for domestic Nepali consumers and is subject to issuer and cross-border controls. Treat cards as complementary.

Country detail lives on the Nepal payment gateway page and in the eSewa merchant payment guide.

How to evaluate a Nepali gateway

Method coverage and conversion

Ask for per-method completion rates over a recent ninety-day window. Confirm native branding for each wallet in checkout. Generic wallet buttons underperform branded ones consistently, and in a market this size the lost percentage matters.

Settlement and entity requirements

Domestic providers settle NPR into a Nepali bank account held by a locally registered entity. If your company is foreign, that path is generally closed and you need a cross-border capable partner. Confirm in writing: receiving entity, currency, cycle, reserve, release schedule and FX treatment.

Compliance and documentation

Expect corporate documents, ownership disclosure, director identification, business model description, website review and licence evidence where the vertical requires it. Providers in a supervised market must do this; those that skip it create risk for you, not convenience.

API, webhooks and reconciliation

Look for idempotent creation, signed webhooks with retries, honest sandbox behaviour, explicit terminal states, and downloadable reconciliation. Wallet payments involve a customer confirmation step, so pending-state and timeout handling deserve close attention. See how payment APIs work.

Payouts

If you need to send money out — refunds, withdrawals, partner payments — verify wallet-level payout support, limits, beneficiary validation and return handling. Payout capability lags collection capability in most markets, Nepal included.

Pricing in context

Compare method-level MDR, fixed fees, payout costs, platform fees, FX spread, dispute costs and reserve drag, then convert everything into landed cost per successful order. In a smaller market, provider stability and support quality often matter more than a marginal rate difference.

Cross-border merchants selling into Nepal

The structural constraint is familiar: local settlement assumes a local entity. A cross-border provider collects on Nepali rails and settles to your foreign account, usually in a major currency. Merchants covering multiple South Asian markets should read the cross-border payment guide for South Asia before signing four separate local contracts.

High-risk verticals

Forex, gaming, betting and casino businesses are excluded by mainstream providers. Specialist providers can support certain flows where the activity is legitimate and the structure sound. Be explicit about your category — see how high-risk payment processing works and the high-risk payment solution Nepal page.

Go-live checklist

1. Enable both major wallets with correct branding.
2. Add bank transfer for higher-value payments.
3. Use idempotency keys on payment creation.
4. Define pending-state timeouts and a reconciliation sweep.
5. Verify webhook signatures; handle replays safely.
6. Reconcile daily across wallets, bank credits and payouts.
7. Monitor per-method success rates with alerting.
8. Publish clear refund and support policies.
9. Confirm settlement entity, cycle and reserves contractually.
10. Identify a fallback route before peak trading periods.

Common mistakes

• Assuming one wallet equals national coverage.
• Ignoring bank rails and capping your average order value by accident.
• Leaving pending wallet payments unresolved.
• Not testing payouts before promising customer withdrawals.
• Discovering the entity requirement after integration is complete.

How PayEurasia supports Nepal

PayEurasia integrates the leading Nepali wallets alongside bank rails, unifies reconciliation across collections and payouts, and settles cross-border on transparent terms. We support high-risk verticals that mainstream providers decline and are direct at onboarding about what we can place.

Contact our team with your entity structure, volumes and vertical.

Features to consider when comparing Nepali gateways

Nepal is a smaller market with fewer providers, which makes disciplined comparison easier — and more important, because switching later is disruptive.

Wallet integration depth

Every provider lists the same wallet logos. What differs is whether the connection is direct or intermediated, the limits applied to your category, whether failures return usable error codes, and how quickly wallet-side incidents are communicated to you. Ask how many parties sit between your API call and the wallet.

Disclosed success rates

Ask for authorisation rates by method for merchants of comparable size and category over the last 90 days, then verify with a small capped pilot. In a market with fewer redundant rails, a provider's real success rate matters more than its price.

Checkout on real devices

Test on mid-range Android over mobile data, including app-switch behaviour and the return journey to your site. A checkout that only works well on a fast connection will underperform outside Kathmandu.

Payout capability

Wallet and bank disbursement, limits, beneficiary validation, failure handling and return timelines. Merchants who need withdrawals should test payouts before signing, not after.

Refunds and dispute handling

Partial refunds, per-method timelines, and who supports the customer when a wallet is debited but the order fails. This directly drives your support workload.

Reporting and finance integration

Transaction-level exports, settlement reports carrying batch identifiers, per-line fee breakdowns and an API to retrieve both. Tax treatment of fees should be documented.

Reliability and communication

Status page, uptime history, and how incidents are reported. In a concentrated market, honest incident communication is a genuine differentiator.

Local payment methods: operational detail

eSewa

The most established wallet in Nepal and, for most merchants, the anchor method. Recognition is broad across age groups and geographies, and consumers are comfortable completing purchases inside the app. If you enable only one wallet, this is normally the one — but enabling only one leaves measurable conversion on the table.

Khalti

The other major wallet, with strong adoption among younger, urban and digitally native users, and a solid presence in bill payment and top-up behaviour. Overlap with eSewa is partial rather than complete, so running both typically increases total conversion instead of merely splitting existing volume.

Bank transfer rails and connectIPS

Bank-linked rails carry higher-value payments and B2B collections, and interbank infrastructure has improved substantially. The operational question to ask any provider is how inbound transfers are matched to your order references — unmatched credits are the most common source of manual reconciliation work in Nepal.

Cards

Domestic card use online is limited, but card acceptance matters for diaspora customers and international buyers. Confirm 3-D Secure handling, decline reporting and tokenisation support if you run recurring billing.

Security: controls to verify

Credentials and transport

TLS-only endpoints, scoped API keys, separate sandbox and production credentials, IP restriction and self-service rotation. Ask what rotation looks like during a live incident rather than in theory.

Webhook authenticity

Callbacks should be HMAC-signed over the raw body with a timestamp for replay protection. Verify before parsing, reject stale events, and make handlers idempotent — delivery is at-least-once.

Idempotency on money movement

Idempotency keys on charges, refunds and payouts stop a network timeout from becoming a duplicate transfer. The API documentation sets out the key format and retry semantics PayEurasia uses.

Fraud patterns in a wallet-led market

Chargebacks are uncommon; the real exposures are forged payment receipts, refund abuse, account takeover and structuring across small deposits. Practical controls: velocity limits per customer and device, first-transaction caps, wallet-to-account name matching, deposit/withdrawal asymmetry monitoring, and a manual review queue with thresholds you control.

Access control and audit

Role-based administrative access, masked sensitive fields, and an immutable audit log of admin actions. If card data touches your systems, confirm PCI DSS scope and prefer hosted checkout to stay out of it.

Merchant onboarding in Nepal

Documents to prepare

• Company registration certificate and constitutional documents
• PAN or VAT registration where applicable
• Director and beneficial-owner identification with ownership structure
• Bank account details or bank letter for settlement
• Website with visible pricing, terms, refund policy, contact details and address
• Business model note: product, average ticket, expected volume, refund rate
• Category licences where the vertical requires them

The sequence

1. Commercial scoping — methods, volumes, settlement destination, category.
2. KYB and risk review — documents, screening, website assessment.
3. Approval with terms — limits, pricing, reserve, settlement cycle.
4. Technical onboarding — sandbox keys, integration, webhooks, testing.
5. Staged go-live — capped volume, verification, then higher limits.

Domestic merchants with complete documents move quickly; foreign entities and regulated categories take longer, because the entity question has to be solved before the technical one. Start at merchant onboarding.

Ask in writing

• What triggers a limit reduction, reserve increase or settlement hold?
• Who is the escalation contact and what response time applies?
• What notice and fund-release terms apply on termination?
• Which method-level restrictions apply to my category?

Cross-border support and getting paid outside Nepal

Domestic Nepali providers collect NPR and settle NPR into a local bank account held by a locally registered entity. If your operating company sits outside Nepal, that chain does not reach you — and no amount of technical integration changes that.

The workable route is either local incorporation, with the tax and compliance overhead it carries, or a provider that holds Nepali collection infrastructure and settles cross-border under a documented arrangement. Verify:

• Settlement currency, reference rate and FX spread, which is often the largest and least advertised cost.
• Beneficiary matching between the contracting and receiving entities.
• Corridor documentation — invoices, agreements or licence evidence the remitting bank requires.
• Cut-offs and the Nepali banking calendar, which differs from regional norms and shifts value dates.

Merchants collecting in several South Asian markets should consolidate rather than run four domestic integrations — see cross-border payment solutions and the countries hub.

API and integration in practice

A sane integration flow

1. Create the payment intent server-side with amount, currency, method and your own order reference.
2. Launch the wallet flow, bank instruction or card form.
3. Treat the signed webhook as the source of truth for terminal status.
4. Verify signature, resolve by your own reference, and apply state changes idempotently.
5. Reconcile daily against the settlement report rather than trusting webhooks alone.

Test before go-live

• Success, decline, timeout and abandonment on each method
• Duplicate and out-of-order webhooks
• Full and partial refunds and their events
• Rate limits and error payload structure
• Settlement report format: order reference, method, fee and batch ID per line

Instrumentation

Measure authorisation rate by method, hour and amount band, and keep a rolling 30-day baseline. In a market with limited redundancy, early detection of a degrading rail is the difference between a bad hour and a bad week.

Settlement mechanics explained

• Cycle. Confirm T+1, T+2 or weekly, whether T means transaction or batch-close date, and the daily cut-off.
• Per-method batching. Wallets and bank rails may settle separately with different timelines.
• Reserves. Percentage, holding period and release schedule must be written into the agreement.
• Fee treatment. Netted from settlement or invoiced monthly; netting is simpler, invoicing reports more cleanly.
• Refund funding. From incoming volume or a prefunded float — significant on low-volume days.
• Reporting. Payout lines must tie back to individual transactions, or month-end close becomes estimation.

Pricing considerations

General guidance rather than a quote — build a total cost model:

• MDR varies by method; blended quotes hide which rail is expensive for your mix.
• Fixed per-transaction fees dominate low-ticket, high-count economics.
• FX spread on cross-border settlement is frequently larger than the MDR.
• Payout fees are separate from collection fees.
• Setup, minimum monthly and maintenance fees appear more often in higher-risk categories.
• A rolling reserve is working capital you cannot deploy.
• Lower headline pricing with lower success rates costs more per delivered order.

Compare cost per successful order, and require every provider to quote against the same volume assumptions.

After go-live: the operating playbook

Track four numbers weekly: authorisation rate by method, actual time to settlement against the contracted cycle, refund and dispute rate, and support tickets per thousand transactions. Keep your own attempt ledger and match it to settlement lines by your order reference rather than relying only on the provider dashboard. Maintain a current compliance pack — incorporation documents, ownership, licences, refund policy, processing statistics — so a risk review can be answered in a day rather than a fortnight. And revisit commercial terms annually, because twelve months of clean processing history is the strongest negotiating position a merchant ever has.

A decision framework for Nepali merchants

Most merchants overcomplicate the choice. Four questions resolve it in the right order.

1. Where is your operating entity registered? A Nepali company can work with domestic providers directly and settle NPR locally. A foreign entity cannot, no matter how good the technical fit, and should shortlist only providers that hold Nepali collection infrastructure and settle cross-border. Answer this first; it eliminates most of the market either way.

2. What is your category, honestly stated? Providers underwrite the business model, not the website. Describing a higher-risk model as generic e-commerce buys a few weeks of processing followed by a freeze and a held balance. Merchants in gaming, trading, travel, nutraceuticals, ticketing and similar categories should look at high-risk merchant payment processing and disclose fully during underwriting.

3. What is your ticket profile? Low-ticket, high-count businesses live or die on wallet success rates and fixed per-transaction fees. High-ticket businesses care far more about bank rail reliability, limits and settlement timing. The two profiles rarely pick the same provider.

4. Do you need payouts? Collections-only merchants have more options. If you disburse — refunds at volume, agent commissions, customer withdrawals — payout coverage, limits and failure handling should carry equal weight in the evaluation, and should be tested in sandbox before signing.

A short scorecard

Score each shortlisted provider from one to five on: wallet coverage depth, disclosed success rates, settlement structure fit, onboarding realism, API and webhook quality, reporting depth, payout capability, support responsiveness, and incident transparency. Weight settlement structure and category acceptance double, because those are the two failure modes that end a relationship rather than merely irritate you.

Common mistakes worth avoiding

• Choosing on headline MDR and discovering the FX spread afterwards
• Enabling one wallet because it is "the big one" and losing the other half of the market
• Building against the happy path and meeting timeout handling in production
• Treating webhooks as guaranteed exactly-once delivery
• Launching without a reconciliation process, then discovering a three-month gap at audit
• Running a single provider with no tested fallback

Frequently asked questions

What is the best payment gateway in Nepal?

The best gateway natively supports eSewa and Khalti with strong completion rates, adds bank transfer for larger tickets, settles into an account your entity can legally use, and provides dependable webhooks, payouts and reconciliation.

Can a foreign company collect payments in Nepal?

Generally not directly through a domestic PSP, because settlement requires a local entity and bank account. Foreign merchants typically use a cross-border provider that collects locally and settles internationally.

eSewa or Khalti — which should I enable?

Both. eSewa has the broadest recognition and Khalti has strong urban traction. Enabling both maximises coverage; enabling one leaves a significant share of customers without their preferred method.

How fast is settlement in Nepal?

Domestic settlement is commonly same-day to T+2 depending on provider and method, while cross-border settlement follows the agreed corridor and cycle. Always confirm reserve percentage and release timing.

Do Nepali gateways support merchant payouts?

Support varies by provider and wallet. If your business model requires outbound payments, test payout coverage, limits and failure handling explicitly before you commit to a provider.

Are high-risk businesses supported in Nepal?

Mainstream gateways exclude Forex, gaming, betting and casino traffic. Specialist providers support some of these flows when the structure and disclosure are correct. Always declare your category up front.

Nepal in regional context

Merchants who sell across South Asia often ask how Nepal compares operationally with its neighbours. Volume is smaller and the provider landscape is more concentrated, which means less redundancy when a rail degrades and fewer alternatives if an account is declined. Wallet behaviour resembles Bangladesh more than India: consumers pay from an app balance rather than through a real-time interbank scheme, and card usage online stays limited. Settlement structures are closer to Bangladesh as well, with local-entity requirements shaping who can receive funds domestically.

The practical implication is that Nepal is rarely worth a standalone integration project. Merchants already collecting in Bangladesh, India or Pakistan usually get better economics and simpler operations by adding Nepal through the same provider and the same reconciliation pipeline, rather than by contracting a separate domestic gateway and maintaining a second settlement chain. Compare coverage per market on the countries hub before committing to an architecture.

Glossary for merchants

Acquirer. The licensed institution that holds the relationship with the wallet or bank network and clears funds to the payment service provider.

Authorisation rate. The share of payment attempts that succeed. Measured by method, hour and amount band, it is the single most useful health metric for a Nepali checkout.

Chargeback. A forced reversal initiated through the card networks. Rare on wallet rails in Nepal, but relevant if you accept international cards.

Cut-off time. The daily deadline after which a transaction rolls into the next settlement batch. It determines whether "T+1" means tomorrow or the day after.

FX spread. The margin applied between the reference exchange rate and the rate used to convert your settlement. For cross-border merchants this is often the largest single cost, and it is rarely quoted alongside MDR.

Idempotency key. A client-supplied identifier that guarantees a retried request is not processed twice. Essential on charge, refund and payout endpoints.

KYB. Know Your Business — the due diligence a provider performs on your company, ownership and business model before approving processing.

MDR. Merchant discount rate, the percentage fee deducted per successful transaction. Varies by method; blended quotes obscure which rail is expensive for your mix.

Payment intent. A server-created record representing an intended payment, carrying the amount, currency, method and your own order reference.

Payout / disbursement. Money leaving your balance to a customer, agent or supplier through a wallet or bank transfer.

Reconciliation. Matching your own attempt records against the provider's settlement report, line by line, so that every payout can be traced to individual transactions.

Rolling reserve. A percentage of settlement withheld for a defined period as protection against refunds and disputes, then released on schedule. Common in higher-risk categories.

Settlement batch. A group of transactions paid out together, identified by a batch ID that should appear in your settlement report.

Underwriting. The risk assessment that determines whether you are approved, at what limits, with what reserve and at what price.

Value date. The date on which funds actually become available in your account, which can differ from the payout initiation date because of banking holidays and cut-offs.

Velocity limit. A cap on how many attempts, or how much value, a single customer, device or account may push through in a defined window. One of the cheapest and most effective fraud controls in a wallet-led market.

3-D Secure. The authentication step applied to card payments, which reduces fraud liability but adds friction and can lower completion rates on slow connections.

Webhook. An asynchronous, signed HTTP callback from the provider that carries the terminal status of a payment. Treat it as the source of truth, and treat delivery as at-least-once.

Where to go next

If you are comparing providers for Nepal specifically, the Nepal payment gateway page sets out method coverage and settlement, while the countries hub compares Nepal against Bangladesh, India and Pakistan for merchants selling across the region. Businesses in restricted or complex categories should start with high-risk payment solutions for Nepal, and developers evaluating the integration effort can read the API overview before requesting sandbox credentials.

Conclusion

The best payment gateway in Nepal is the one whose method depth, settlement structure and category policy fit your business. Because the market has fewer providers than India or Bangladesh, the cost of a poor choice is higher and switching is more disruptive — which makes the up-front diligence worth doing properly. Verify wallet coverage and real success rates, confirm exactly how and where funds reach you, read the onboarding requirements before you build, and test the failure paths, not just the happy path.

If your operating entity sits outside Nepal, or your category is one domestic providers decline, resolve settlement and acceptance first; those two answers define your shortlist.

Next step

PayEurasia operates Nepali collection rails across eSewa, Khalti and bank transfer with cross-border settlement, signed webhooks and transaction-level reconciliation. For a direct answer on whether your business can be supported, request an integration or start merchant onboarding — including for high-risk verticals in Nepal.

Related reading

• Nepal Payment Gateway — coverage, methods and settlement
• High Risk Merchant Payment Processing — underwriting for complex categories
• Cross-Border Payment Solutions — collect locally, settle into one treasury
• Solutions and API — collections, payouts and developer surface
• Countries — coverage across Bangladesh, India, Pakistan and Nepal