9/18/202616 min read
E-Commerce & Logistics

Nepal Payment Gateway Integration Guide (2026): eSewa, Fonepay, Khalti Fees, APIs, QR Screenshots & COD Defense

A comprehensive technical and commercial guide for online sellers and developers in Nepal: Merchant Discount Rates (MDR), API integration architectures, the 1-in-20 QR screenshot consumer habit, automated Gmail API bank alert parsing, and how micro-deposits slash 35% COD returns.

ℹ️
Editorial & Research Disclaimer:The insights, benchmarks, policy analyses, case studies, and technical breakdowns shared in this article represent independent industry research and observational commentary. They are compiled strictly for informational, educational, and discussion purposes. They do not constitute formal business, tax, legal, or investment advice. Platform algorithms, financial regulations, and advertising costs evolve rapidly; always conduct independent due diligence and seek certified legal or tax professionals before making commercial or operational decisions. Sajedar assumes no liability or responsibility for direct, indirect, or consequential actions taken based on this content.


Nepal Payment Gateway Integration Guide (2026): eSewa, Fonepay, Khalti Fees, APIs, QR Screenshots & COD Defense

For any merchant operating an online store, D2C brand, or tech startup in Nepal, selecting and integrating the right payment infrastructure is the single most critical factor determining checkout conversion and cash flow velocity.

While the Nepal Rastra Bank (NRB) reports exponential growth in digital retail payments—surpassing NPR 4 Trillion monthly across RTGS, IPS, and mobile wallets—the consumer dynamics of direct-to-consumer (D2C) retail in Nepal are vastly different from Western or Indian e-commerce.

Most developers build complex web checkout flows expecting customers to enter credentials into redirect payment gateways. In production, they are met with staggering 65%+ checkout abandonment rates.

This guide provides a rigorous technical, financial, and operational blueprint of Nepal's payment ecosystem—covering official gateways (eSewa, Fonepay, and Khalti), the 1-in-20 QR screenshot paradox, automated Gmail API bank alert parsing, and the Micro-Deposit Advance Commitment Flow that slashes returns down to under 8%.

---

1. The 1-in-20 Paradox: Why 95% of Nepali Shoppers Prefer QR Screenshots over Payment Gateways

In international e-commerce, customers expect a checkout gateway with credit cards or PayPal. In Nepal, empirical data from retail stores reveals a fascinating consumer dynamic:

Only 1 out of 20 online shoppers (~5%) completes payment through an official web redirect payment gateway.

The remaining 19 out of 20 shoppers (95%) insist on scanning a static Fonepay/eSewa QR code and sending a screenshot of the payment receipt.

Why Does This Happen?


1. Ingrained Daily Habits: Millions of Nepalis scan QR codes daily at physical grocery shops (kirana), supermarket checkouts (Bhatbhateni), vegetable stalls, ride-sharing (Pathao/InDrive), and restaurants. Scanning a QR code via their mobile banking app is second nature; navigating an unfamiliar web gateway feels alien.
2. Security Skepticism & Friction: When an online store redirects a shopper to an external gateway page requiring them to type in their eSewa password or wait for an SMS OTP, anxiety spikes. Shoppers fear phishing, wallet deductions without order confirmation, or technical errors, causing them to abandon the cart.
3. App-to-Browser Disconnect: Over 92% of Nepali social commerce traffic originates from mobile devices (Instagram/TikTok/Facebook in-app browsers). In-app browsers frequently break OAuth popups and multi-factor redirect loops, causing failed transactions.

---

2. Gateway Comparison: eSewa vs. Fonepay vs. Khalti

| Feature / Metric | eSewa (ePay v2) | Fonepay (Dynamic QR / Merchant) | Khalti (ePayment v2) |
| :--- | :--- | :--- | :--- |
| Market Penetration | 7.5M+ Registered Wallets | 60+ Commercial Banks & Wallets | 4.0M+ Active Users |
| Merchant Discount Rate (MDR) | 2.5%3.0% per transaction | 1.2%1.8% (Interbank QR) | 2.5%3.0% per transaction |
| Primary Checkout Method | Web Redirect / Mobile SDK | Dynamic QR Scan / Direct Bank Push | Web Pop-up / SDK / Mobile Number OTP |
| Settlement Timeline | T+1 Business Day | T+0 (Instant to Bank Account) | T+1 Business Day |
| Refund API Support | Partial / Full (Dashboard & API) | Manual Bank Settlement | Full Automated Refund API |
| Best Used For | Mass-market consumer purchases | High-ticket retail & in-person pickup | Modern tech-savvy shoppers & micro-transactions |

---

3. The High Expense Barrier of Official Gateways

For early-stage entrepreneurs, student founders, or boutique sellers testing a product line with NPR 30,000 to 80,000 in seed capital, official payment gateways present steep economic hurdles:

1. Upfront Setup Fees & AMC: Commercial payment gateway aggregators often charge NPR 15,000 to NPR 35,000 in one-time onboarding fees, alongside annual maintenance charges (AMC).
2. High Transaction Friction (MDR): 2.5% to 3.0% Merchant Discount Rate directly erodes already thin retail margins.
3. Rigid Corporate KYC Requirements:
* Ward commercial registration (वडा कार्यालय दर्ता).
* Inland Revenue Department (IRD) PAN/VAT certificate.
* Corporate current bank account requiring NPR 5,000–25,000 minimum maintaining balance.
* Formal site audit requiring full Terms of Service, Return Policies, and live inventories.

For a new brand selling 5 to 10 items a day, committing NPR 30,000+ upfront before validating market demand is financially irresponsible.

---

4. The Bootstrapped Developer Workaround: Automated Gmail API Bank Alert Parsing

To bridge the gap between expensive gateways and tedious manual screenshot checking, developers can implement an automated bank credit alert parsing architecture.

The Architecture:


```
[ Customer Scans Standee Fonepay/eSewa QR ]


[ Types Order ID (e.g. ORD-1042) in "Remarks" ]


[ Bank (NIC Asia / Nabil / Global IME) Sends Instant Email Credit Alert ]


[ Background Cron Worker Queries Gmail API for Unread Bank Alerts ]


[ Regex Engine Extracts Amount & Remarks -> Matches Order ID ]


[ Admin Dashboard Automatically Flags Order as "PAID / VERIFIED" ] (< 10 Seconds)
```

Open Source Implementation:


To eliminate manual regex writing, our engineering team open-sourced the parser in [nepali-messenger-nlp@1.2.0](https://www.npmjs.com/package/nepali-messenger-nlp):

```typescript
import { parseBankCreditAlert, matchPaymentWithOrder } from "nepali-messenger-nlp";

// Sample transactional alert email from NIC Asia Bank or Fonepay
const bankEmailBody = "Dear Customer, Your A/C has been credited by NPR 1,500.00 on 18-Sep-2026. Ref: TXN99824. Remarks: ORD-8842. From RAM SHRESTHA via Fonepay. Current Bal: NPR 42,000.00 - NIC ASIA Bank";

const parsedAlert = parseBankCreditAlert(bankEmailBody);
console.log(parsedAlert);
// Output:
// {
// bank: "NIC_ASIA",
// amount: 1500,
// referenceId: "TXN99824",
// remarks: "ORD-8842",
// senderName: "RAM SHRESTHA",
// isCredit: true
// }

// Automatically match incoming order
const match = matchPaymentWithOrder("ORD-8842", 1500, [parsedAlert]);
if (match.isMatched && match.confidence > 0.9) {
// Update order status in your database to CONFIRMED
console.log("Payment automatically verified! Dispatching order...");
}
```

---

5. Technical Integration: eSewa ePay v2 Cryptographic Signatures

When your order volume reaches scale and justifies formal gateway contracts, eSewa's modern ePay v2 requires generating an HMAC-SHA256 signature to prevent request tampering:

```typescript
import crypto from "crypto";

interface EsewaPaymentRequest {
amount: number;
tax_amount: number;
total_amount: number;
transaction_uuid: string;
product_code: string;
secret_key: string;
}

export function generateEsewaSignature(params: EsewaPaymentRequest): string {
const message = "total_amount=" + params.total_amount + ",transaction_uuid=" + params.transaction_uuid + ",product_code=" + params.product_code;
return crypto
.createHmac("sha256", params.secret_key)
.update(message)
.digest("base64");
}
```

---

6. The 35% COD Defense: The NPR 100 Advance Token Model

The biggest leak in Nepali e-commerce is the uncommitted Cash-on-Delivery order. When an order requires zero financial commitment, customers order impulsively on TikTok or Facebook and reject the parcel when the courier arrives 4 days later in Butwal or Pokhara.

The Solution:


Instead of demanding full 100% upfront payment (which slashes checkout conversion by 60%), leading Nepali brands implement the NPR 100 Commitment Token:

```
[ Customer Adds Item: NPR 2,400 ]


[ Selects Cash on Delivery (COD) ]


[ AI Chatbot Generates NPR 100 Dynamic QR Token ]


[ Customer Pays NPR 100 via Mobile Banking / eSewa ]


[ Courier Dispatches with Remaining COD Due: NPR 2,300 ]
```

Impact on Unit Economics:


* COD Cancellation Rate: Drops from 35% down to under 8%.
* Customer Psychology: Paying even NPR 100 creates psychological ownership and guarantees the customer will answer the courier's phone call.
* Courier Fee Protection: If the customer still refuses delivery, the NPR 100 token absorbs 70%100% of the courier's return penalty fee (NPR 100–150).

---

7. Crucial Disclaimers: Temporary Bootstrap Bridge vs. Enterprise Architecture

[!WARNING]

Regulatory & Scalability Disclaimer:

Automated Gmail API bank alert parsing and screenshot verification is a pragmatic, cost-effective bootstrap bridge designed for early-stage stores, micro-merchants, and solopreneurs operating with constrained capital.

>
Limitations of the Workaround:

1. Bank Email Latency: While most commercial banks dispatch credit alert emails within 5 to 30 seconds, network congestion or bank switch delays can occasionally stall notifications for several minutes.

2. Lack of Automated Refunds: Reversing a payment requires manual bank transfers since static QR payments lack an automated programmatic refund API.

3. Forged Receipts: Sophisticated fraudsters can generate forged screenshot receipts using photo editors. Always ensure your verification logic relies on server-side bank alert confirmations rather than client-uploaded images alone.

>
The Long-Term Solution:

As your brand scales past 30 to 50 transactions daily, transitioning to formal, licensed payment gateways (eSewa ePay, Fonepay Merchant API, Khalti) is mandatory for automated financial reconciliation, tax audit compliance, and seamless multi-channel scaling.

---

8. Sourcing & Profit Margin Planning

Before finalizing your payment infrastructure and pricing corridor, simulate your landed margins, customs duties, and courier return buffers using the free [Sajedar E-Commerce Profit & Landed Cost Calculator](https://www.sajedar.com/tools/ecommerce-calculator).

For custom payment integration or automated conversational checkout, explore [Sajedar's AI Services](https://www.sajedar.com/services).

Ready to scale your business with AI & market validation?

We help Nepali businesses automate customer operations and validate profitable products with empirical data.

Chat on WhatsApp