Digital Payment Integration in Nepal 2026: eSewa, Khalti, Fonepay & NepalQR Explained

Walk into almost any shop in Kathmandu, Pokhara, or Birgunj today and you'll spot a laminated QR code sitting by the till — tea stalls, momo carts, hardware stores, even street-side fruit vendors now accept digital payments. Behind that simple QR sticker sits a genuinely mature ecosystem of wallets, banks, and a central regulator working together. For any business or developer looking to accept money online in Nepal, understanding digital payment integration Nepal options isn't optional anymore — it's core infrastructure. This guide breaks down how eSewa, Khalti, Fonepay, ConnectIPS, and the unified NepalQR standard actually fit together, and what to consider before you integrate any of them.

1. Why Nepal's Digital Payment Ecosystem Is More Mature Than Expected

For a country often assumed to be behind on financial technology, Nepal's digital payment infrastructure has quietly become genuinely sophisticated. What started as a handful of isolated wallet apps competing for users has consolidated into an interoperable system where one QR code can accept money from practically any wallet or banking app in the country. This shift matters enormously for digital payment integration Nepal businesses now rely on, because it means accepting payments no longer requires forcing customers into a specific app ecosystem.

2. NepalQR: The Unified Standard Behind Everything

At the center of Nepal's payment ecosystem sits NepalQR, the country's unified QR payment standard defined by Nepal Rastra Bank, built on the same underlying specification used by similar unified QR systems in other countries in the region. Before this standardization, a single shop often had to display three or four separate QR codes, one per wallet, and would simply turn away customers whose app didn't match any of them.

NepalQR changed that completely. A single, properly registered QR code at a shop counter can now be scanned by a customer using virtually any compliant wallet or mobile banking app — the payment routes through the underlying rails to the merchant's registered account regardless of which specific app the customer opened. As a merchant, you don't need to understand the technical routing between networks; you simply need your QR code properly registered with an acquiring bank or payment provider.

3. The Major Players: eSewa, Khalti, Fonepay, IME Pay, ConnectIPS

Nepal's digital payment space is generally understood as five major pieces, each playing a distinct role:

eSewa

Nepal's original digital wallet and still the most widely recognized brand name in the space, with the largest active user base and merchant network in the country. Its biggest strength is brand trust — most Nepalis already have an eSewa account, which matters enormously for consumer-facing checkout flows.

Khalti

Known among developers specifically for having the cleanest, best-documented API of the major gateways, with a sandbox environment that behaves reliably close to production. Following its merger with IME Pay, Khalti has also expanded into a broader financial services ecosystem beyond simple payments.

Fonepay

Less of a consumer-facing wallet brand and more of a foundational network — Fonepay sits underneath a huge portion of Nepal's bank-to-bank and QR transaction volume. It's particularly important for interbank transfers, utility payments, and B2B contexts where a customer prefers paying directly from their bank account rather than a separate wallet balance.

IME Pay

Strong particularly in the remittance space, given IME's long-established international money transfer network, and now increasingly integrated with Khalti's ecosystem following their merger.

ConnectIPS

A Nepal Rastra Bank-regulated system built specifically for higher-value, bank account-based transfers. It's generally the most involved of the major systems to integrate, and matters most for financial services businesses or anyone needing to comply closely with NRB's banking-linked payment guidelines.

In practice, eSewa and Khalti are the wallets consumers recognize and open on their phones. Fonepay is largely the network quietly routing transactions underneath, especially for QR and bank-linked payments. ConnectIPS sits apart as the higher-compliance, bank-transfer-focused option. Understanding this layering helps explain why a single QR code can accept payments from multiple apps at once — several of these systems interoperate at the rails level, even when the customer-facing brand differs.

4. Which Gateway Should Your Business Integrate First?

For most businesses building a website or app that needs to accept payments in Nepal, the practical starting point looks like this:

Adding Fonepay on top of eSewa and Khalti extends your reach specifically to customers who bank more than they use dedicated wallet apps — a meaningful segment, especially for higher-value transactions.

5. What Integration Actually Involves

At a technical level, nearly every Nepali payment gateway follows a broadly similar flow, regardless of which specific one you choose:

1. Your server initiates the payment request with the gateway, specifying amount and order details.
2. The customer is redirected to the gateway's own interface to authenticate and authorize the payment — your application never directly handles the customer's wallet or banking credentials.
3. The gateway processes the payment and redirects the customer back to your site or app with a status indicator.
4. Your server independently verifies the payment with the gateway's API before marking an order complete — this verification step should never be skipped, since a client-side redirect alone is not proof that payment actually succeeded.

One practical difference worth planning for early: refund handling varies significantly between gateways. Some offer a genuine programmatic refund endpoint that your system can call directly, while others require refunds to be processed manually through a merchant portal rather than through the API. If your product involves returns, cancellations, or subscription changes, it's worth confirming each gateway's actual refund capability before building your unhappy-path flows, since a manual-only refund process needs to be designed into your operations, not just assumed away.

6. Understanding the Real Costs

Budgeting for payment integration in Nepal generally involves a few distinct cost categories:

• Merchant account setup fees: Most gateways charge a one-time setup fee to onboard a business merchant account, which varies by provider and account tier.
• Development costs: Whether building integration in-house or hiring a developer/agency, this covers the actual technical implementation, testing, and go-live process.
• Ongoing transaction fees: Most gateways charge a percentage of each transaction processed, which is the primary recurring cost of accepting digital payments.
• Ready-made plugins: For common platforms like WooCommerce, existing plugins for eSewa and Khalti can meaningfully cut development time and cost compared to building custom integration from scratch.

Aggregator services that connect to multiple gateways through a single integration point can also reduce overall development time considerably compared to integrating each gateway separately, which is worth weighing if you want broad payment coverage without a heavier custom-build effort.

7. NRB Regulation and Compliance Basics

Nepal Rastra Bank, the country's central bank, plays a direct regulatory role in this entire ecosystem — not just as an overseer, but as the body that actually defines the NepalQR standard itself, alongside the licensing of payment service providers and payment system operators.

• Licensing matters: Choosing gateways that are properly NRB-licensed isn't just a legal formality — it directly affects customer trust and your business's long-term compliance standing.
• Merchant documentation requirements typically include a PAN (Permanent Account Number) from the Inland Revenue Department, and for businesses above the VAT threshold, a VAT registration certificate as well.
• Identity documentation: Citizenship certificates of the proprietor for sole proprietorships, or of authorized signatories for partnerships and companies, are generally required as part of merchant onboarding.
• Individual vs. business accounts: Personal or individual merchant accounts are available with more limited features, while full business accounts with higher transaction limits generally require proper business registration.

Because payment system regulation is an actively evolving area, always confirm current NRB requirements and any recent regulatory updates directly through official channels before finalizing your merchant onboarding, rather than relying on older guidance.

8. Common Integration Challenges to Plan For

• Documentation gaps: Some gateways' public technical documentation is genuinely limited, meaning you may need to work directly with a provider's technical support team at some point during integration rather than relying purely on published docs.
• Inconsistent refund handling: As noted above, not every gateway offers a programmatic refund API — plan your operational process for manual refund handling where needed.
• Failure and timeout handling: A properly built integration needs to gracefully handle payment failures — ensuring the customer is clearly informed, their money isn't incorrectly deducted (or is automatically reversed), and they have a clear path to retry.
• Signature and security mismatches: Payment gateway integrations commonly involve cryptographic signature verification between your server and the gateway — mismatches here are a frequent source of debugging time during initial setup, so careful testing in the sandbox environment before going live is essential.
• Social engineering risks: Phishing attempts targeting wallet OTPs remain one of the most common fraud vectors for both merchants and customers — no legitimate support agent will ever ask for a wallet OTP, and this is worth communicating clearly to both your team and your customers.

9. Where Nepal's Payment Ecosystem Is Heading

A few directions worth watching as this space continues to mature:

• Deeper interoperability with international standards: Nepal's QR standard already shares its underlying specification with similar unified QR systems used regionally, and further cross-border interoperability continues to be an area of active development.
• Continued consolidation: The Khalti–IME Pay merger reflects a broader trend of Nepal's payment providers combining forces to build more complete financial ecosystems rather than competing as narrow, single-purpose wallets.
• Growing small-vendor adoption: The rapid spread of simple, low-cost QR acceptance among small vendors — tea stalls, momo carts, and street vendors — suggests digital payment acceptance will continue pushing further into informal and semi-formal retail segments.
• Increasing aggregator adoption: As more businesses want broad payment coverage without managing multiple separate integrations, aggregator-style services connecting to several gateways through one integration point are likely to keep growing in relevance.

10. Frequently Asked Questions

Do I need to integrate every payment gateway to reach most customers in Nepal?

Not necessarily — integrating eSewa and Khalti together typically covers the majority of digital wallet users, and adding Fonepay extends reach to customers who prefer paying directly from their bank account rather than a wallet balance.

What's the difference between a wallet like eSewa and a network like Fonepay?

Wallets like eSewa and Khalti are consumer-facing apps where users hold a balance and make payments directly. Fonepay operates more as an underlying network connecting banks and wallets together, particularly for QR and interbank transactions, often working quietly beneath transactions that appear to happen through a different consumer-facing app.

Can a single QR code at my shop accept payments from any wallet app?

Yes, provided it's properly registered as a NepalQR-compliant code through your bank or a payment provider — this is precisely the interoperability the unified standard was built to enable, replacing the older system of multiple separate QR codes per wallet.

Is ConnectIPS necessary for a typical small e-commerce business?

Generally not required for typical consumer checkout flows — ConnectIPS is more relevant for financial services businesses or higher-value bank-account-based transfers subject to closer NRB compliance requirements, rather than everyday retail payment acceptance.

Nepal's digital payment ecosystem has moved well past the early fragmented-wallet stage into something genuinely interoperable and increasingly sophisticated, anchored by the NepalQR standard and a handful of well-established, NRB-regulated players. Whether you're a developer integrating your first payment flow or a business owner deciding which gateways deserve your attention first, the practical path forward for most projects remains straightforward: cover the widest consumer base with eSewa and Khalti, extend reach with Fonepay's bank interoperability, and reserve ConnectIPS for cases genuinely requiring bank-account-level compliance. Getting digital payment integration Nepal right today means designing for interoperability and graceful failure handling from the start, not treating any single gateway as a complete solution on its own.