International Payment Gateway Nepal: How Foreign Merchants Accept Local Payments

Why global gateways do not solve Nepal

Most international payment gateways are card-first. They were designed for markets where a Visa or Mastercard number is the default instrument, and their coverage in Nepal is either absent or limited to a small minority of cardholders. 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 practical result is that a foreign merchant who launches with a global processor sees a conversion rate that looks catastrophic. The traffic is real, the intent is real, but the payment instrument on the page is one the customer does not hold. An international payment gateway for Nepal therefore has to mean something specific: a gateway that presents licensed wallets plus connectIPS and Fonepay bank transfers to the customer while giving the merchant a single foreign-facing integration and settlement relationship.

Volumes are lower than the rest of the region, so operational discipline — clean reconciliation and predictable payouts — matters more than raw scale.

What an international gateway must actually provide

There are four separate problems hiding inside the phrase "accept payments in Nepal".

1. Local acceptance. The checkout must offer instruments customers hold, in NPR, with local-language conventions and mobile-first layouts.
2. Local collection. Funds have to land somewhere regulated inside the country before they can move anywhere else.
3. Cross-border settlement. NPR is managed against the Indian rupee, and outward remittance is tightly controlled, which makes a licensed local settlement partner essential for foreign merchants.
4. Reporting that survives an audit. Every payout to the merchant has to be traceable back to individual customer transactions.

A provider that solves only the first is a checkout widget, not a gateway. PayEurasia's cross-border payment solutions exist because the last three problems are where most projects stall.

Payment methods that matter in Nepal

International merchants usually start by asking which method has the largest market share. The better question is which combination covers the widest range of ticket sizes, because eSewa and bank transfers serve very different customers.

• 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.

Settlement out of NPR

Collections settle on T+1 in most cases. Money collected locally is aggregated, reconciled against transaction references, and then paid out to the merchant according to an agreed schedule and currency.

NPR is managed against the Indian rupee, and outward remittance is tightly controlled, which makes a licensed local settlement partner essential for foreign merchants. In practice this means the merchant signs with a partner that holds the local relationships, and receives consolidated settlements with a statement that maps every payout line back to underlying transactions. That statement is what makes the arrangement auditable — and it is the single most common gap when merchants try to assemble a solution from local agents.

Compliance expectations for foreign merchants

Nepal Rastra Bank sets the framework that local acquirers and payment service providers operate under, and those obligations flow through to you as a merchant. Expect to provide:

• Certificate of incorporation and ownership structure for the operating entity
• Licences relevant to your vertical, where one is required
• A description of the service being sold and the customer journey
• AML and KYC policy documents, including how you handle sanctions screening
• Historical processing statements if you have them

Nepal Rastra Bank supervises payment service providers closely, and merchant categories are reviewed carefully, so onboarding evidence needs to be accurate from the start. Our compliance page sets out the standards we apply, and the KYC and AML policies describe the underlying process.

Integration model

A well-built international integration in Nepal looks the same regardless of vertical:

• One create-transaction call that returns a redirect or intent for the chosen method
• Signed webhooks for every state change, with retries and idempotency keys
• A reconciliation endpoint that can be replayed for any date range
• Separate credentials for sandbox and production

Full details are in the API documentation, and the general design principles are covered in our payment infrastructure overview.

Common mistakes

• Treating a wallet like a card. Bank holidays follow the Bikram Sambat calendar, so settlement calendars must be configured locally or payouts silently slip a day.
• Ignoring failure taxonomy. "Failed" is not a reason. Insufficient balance, limit exceeded, user cancelled and timeout each need a different retry or message.
• Under-provisioning payouts. Merchants often plan collections carefully and then discover they also need local disbursements, which requires separate capability and approvals.
• Skipping reconciliation until month one closes. Build it on day one; retrofitting it across thousands of transactions is painful.

Merchant benefits

• Local acceptance in NPR without incorporating in Nepal
• One API for eSewa, Khalti, connectIPS and bank rails
• Consolidated settlement with per-transaction reporting
• Routing across multiple local providers so a single outage does not stop revenue
• Underwriting that understands complex verticals rather than rejecting them by category

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

Can a foreign company accept NPR payments in Nepal?

Yes, through a licensed local partner. The merchant does not need a local entity, but the collection must happen inside a regulated structure in Nepal, and settlement out of NPR must follow the applicable foreign-exchange rules.

Which payment methods should an international merchant launch with?

eSewa and Khalti cover the majority of consumer transactions, and bank transfers handle larger amounts. Launching with both wallet and bank coverage is normally worth the extra integration effort.

How long does settlement take?

Settlement typically runs on T+1 in most cases, with payout frequency agreed during onboarding based on volume and risk profile.

What documents are needed to onboard?

Incorporation documents, ownership details, any vertical-specific licence, AML and KYC policies, and a clear description of the product being sold. Processing history helps but is not mandatory.

Is a local bank account required?

No. Collections land in the partner's regulated local accounts and are settled onward to the merchant, which is what removes the need for the merchant to hold NPR accounts directly.