Take eSewa, Khalti and Fonepay with one integration.

One checkout for Nepal's wallets and QR payments. The money goes straight to your own merchant accounts, and an order is only marked paid after the provider confirms it.

  • Free Sandbox and test keys
  • Your own provider accounts
  • Verified before it counts

Customers pay in the apps they already use.

  • eSewa
  • Khalti
  • Fonepay
One test payment, start to finish
  1. Checkout created

    POST /v1/checkout/sessions → 201 · order-1042

  2. Customer pays

    Picks Khalti · NPR 1,500.00

  3. Checked with Khalti

    Exact amount confirmed by the provider

  4. Your server is told

    payment.succeeded → 200 OK · receipt by SMS

Banks whose mobile banking apps can scan a Fonepay QR at our checkout
  • Agricultural Development Bank
  • Everest Bank
  • Global IME Bank
  • Himalayan Bank
  • Kumari Bank
  • Laxmi Sunrise Bank
  • Machhapuchchhre Bank
  • Nabil Bank
  • Nepal Bank
  • Nepal SBI Bank
  • NIC Asia Bank
  • Nepal Investment Mega Bank
  • NMB Bank
  • Prabhu Bank
  • Prime Commercial Bank
  • Rastriya Banijya Bank
  • Siddhartha Bank
  • Standard Chartered

Banks on Fonepay's network, as listed by Fonepay. They are not Paymentsnp partners. How providers and banks relate to Paymentsnp

Every way to take a payment. One record of all of them.

The same eSewa, Khalti and Fonepay accounts sit behind every surface, and every verified payment lands in one dashboard you can reconcile against settlement. Pick the surfaces that fit how you sell.

NPR 1,500.00

  • eSewa
  • Khalti
  • Fonepay

Hosted checkout

One API call gives you a checkout page with your name, the amount and the methods you have switched on.

Hosted checkout

NPR 4,850.00

  • eSewa
  • Khalti
  • Fonepay

Popup on your own site

The same checkout opens over your page with one script tag. Only domains you approve can open it.

Popup checkout

Payment links

No website needed. Make a link in the dashboard, with a fixed amount or one the customer types, and paste it into Viber, WhatsApp or an SMS.

Payment links
Subtotal
10,000.00
Discount
−1,000.00
VAT 13%
1,170.00
Total NPR
10,170.00

Invoices with VAT

Draft an invoice, add 13% VAT and a discount, and email it with a PDF and a pay button.

Invoices and receipts
eSewa · 2,500.00
Matched
Khalti · 1,200.00
Matched
Fonepay · 4,850.00
Mismatch
Bank row · 900.00
Unmatched

Reconciliation

Upload the settlement CSV from your provider or bank, with Nepali dates and lakh commas, and see which payments match.

Reconciliation and reports
pay.yourshop.com.np
Your Shop

Your brand, your domain

Your logo and colour on checkout, even on your own domain. “Powered by Paymentsnp” stays at the bottom.

Branding and custom domain
Payment methods
3
eSewa, Khalti by IME and Fonepay
To create an account and test
Rs 0
Sandbox gateway and test API keys on every account
Checkout languages
2
English and नेपाली, picked by the customer
Rupees held by Paymentsnp
0
Each provider settles to your own merchant account

We never touch the money. We check it.

The customer pays eSewa, Khalti or Fonepay, and the provider settles to your merchant account as it always has. Paymentsnp opens the checkout and checks the proof. There is no Paymentsnp wallet, balance or payout to wait for.

  1. CustomerPays in the app they already use
  2. eSewa · Khalti · FonepayThe provider's own payment page
  3. Your merchant accountWith that provider, under your own agreement
Paymentsnp

Confirms the exact amount with the provider, records the payment and sends your server a signed webhook. Holds nothing.

Money moves along the top line only. Settlement timing and fees are set by each provider under your agreement with them.
Checked with the provider
An order is paid only after the provider confirms the exact amount.
Signed webhooks
Your server hears about each payment, retried with backoff for up to eight attempts.
Receipts and reminders
A receipt for every checkout payment. Switch on reminders and an unpaid order gets up to two, each with a fresh checkout link.
Reconciliation
Upload a settlement CSV, Nepali dates included, and see what matches.
How Paymentsnp keeps payments and credentials safe

How it works. Three steps, and you keep your provider accounts.

Paymentsnp sits in front of the providers you already use and does the checking. The quickstart walks through it with a test key in about five minutes.

Read the quickstart
  1. Connect the merchant accounts you already have

    Paste in your eSewa, Khalti and Fonepay credentials. Paymentsnp checks them with the provider, encrypts them and never shows them again. Payments keep settling to those accounts on the terms you agreed with each provider.

  2. Integrate once

    Create a checkout from your server with one API call, install the WHMCS or WooCommerce plugin, or skip code entirely and share a payment link. Test keys and the Sandbox gateway are there as soon as your account is approved.

  3. Customers pay, you get a signed webhook

    The customer picks a method and pays on the provider's own page. Paymentsnp confirms the exact amount with the provider, then your server receives a signed payment.succeeded webhook and the customer gets a receipt.

What your customer sees. Try it here.

Your business name at the top, the amount, and the methods you have switched on. One button takes the customer to eSewa, Khalti or Fonepay to finish. This demo moves no money.

  • Only the methods you have connected and enabled appear
  • Opens as a full page, or in a popup over your own site
  • English or नेपाली, chosen by the customer
  • Your logo and colour, with “Powered by Paymentsnp” below
Hosted checkout in detail
  1. Customer picks a method
  2. Pays on the eSewa, Khalti or Fonepay page
  3. Paymentsnp confirms the amount with the provider
  4. Your order is marked paid and your server gets a webhook
Himalayan Coffee Co.Demo
Amount to payNPR 1,500.00Order HCC-1001

Choose a payment method

Payment is confirmed with the provider before your order is paid.

Powered by Paymentsnp
Merchant accent colour

One API for every stack. Built for retries.

Send an order ID and an amount in paisa from your server, and you get a checkout link back. Signing, redirects and verification for each provider happen on our side.

  • SDKs on npm, Packagist and PyPI
  • An Idempotency-Key on every create, so a retry never opens a second checkout
  • Signed webhooks you can verify with one SDK call
  • Separate np_test_ and np_live_ keys; test keys never see live data
Create a checkout
curl -X POST https://api.paymentnp.com/v1/checkout/sessions \
  -H "Authorization: Bearer $PAYMENTNP_SECRET_KEY" \
  -H "Idempotency-Key: order-1001" \
  -H "Content-Type: application/json" \
  -d '{
    "order_id": "order-1001",
    "amount_minor": 150000,
    "currency": "NPR",
    "success_url": "https://shop.example.com/orders/1001",
    "cancel_url": "https://shop.example.com/cart"
  }'
// Server only. Node 18+ has fetch built in.
const res = await fetch("https://api.paymentnp.com/v1/checkout/sessions", {
  method: "POST",
  headers: {
    Authorization: "Bearer " + process.env.PAYMENTNP_SECRET_KEY,
    "Idempotency-Key": "order-1001",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    order_id: "order-1001",
    amount_minor: 150000, // NPR 1,500.00
    currency: "NPR",
    success_url: "https://shop.example.com/orders/1001",
    cancel_url: "https://shop.example.com/cart",
  }),
});
const session = await res.json();
if (!res.ok) throw new Error(session.error.message);
// Save session.id with your order, then send the customer to:
console.log(session.checkout_url);
<?php
$ch = curl_init('https://api.paymentnp.com/v1/checkout/sessions');
curl_setopt_array($ch, [
  CURLOPT_POST => true,
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_HTTPHEADER => [
    'Authorization: Bearer ' . getenv('PAYMENTNP_SECRET_KEY'),
    'Idempotency-Key: order-1001',
    'Content-Type: application/json',
  ],
  CURLOPT_POSTFIELDS => json_encode([
    'order_id' => 'order-1001',
    'amount_minor' => 150000, // NPR 1,500.00
    'currency' => 'NPR',
    'success_url' => 'https://shop.example.com/orders/1001',
    'cancel_url' => 'https://shop.example.com/cart',
  ]),
]);
$session = json_decode(curl_exec($ch), true);
if (curl_getinfo($ch, CURLINFO_HTTP_CODE) !== 201) {
  throw new Exception($session['error']['message'] ?? 'Checkout failed');
}
// Save $session['id'] with your order, then redirect the customer:
header('Location: ' . $session['checkout_url']);
# pip install paymentsnp
import os
from paymentsnp import Paymentsnp

client = Paymentsnp(api_key=os.environ["PAYMENTNP_SECRET_KEY"])
session = client.checkout.sessions.create(
    {
        "order_id": "order-1001",
        "amount_minor": 150000,  # NPR 1,500.00
        "currency": "NPR",
        "success_url": "https://shop.example.com/orders/1001",
        "cancel_url": "https://shop.example.com/cart",
    },
    idempotency_key="order-1001",
)
# Save session["id"] with your order, then redirect the customer:
print(session["checkout_url"])
Run on your server. Never put your secret key in browser code.
  1. 201Checkout created. Send the customer to checkout_url
  2. payThe customer pays on the provider's page
  3. checkPaymentsnp confirms the exact amount with the provider
  4. hookpayment.succeeded arrives, signed with Paymentnp-Signature

Ask your payments in plain words. From Claude, Cursor or any MCP client.

The Paymentsnp MCP server runs on your machine with your API key. It is read-only unless you allow writes, and a test key only ever sees test data.

Set up the MCP server

How much have we taken in verified payments, and is anything pending?

payments_summary read-only

NPR 84,250.00 verified across 37 payments, with one attempt still pending. That is not a balance: the money is already in your provider accounts.

Sample conversation and figures.

Questions people ask first.

Straight answers before you connect your first provider.

All questions
Does Paymentsnp hold my customers' money?

No. Payments go through your own eSewa, Khalti or Fonepay merchant account and settle to you under your agreement with that provider. Paymentsnp has no wallet, balance or payout for your funds.

Do I need my own merchant accounts with the providers?

Yes. You need approved merchant access with each provider you want to offer. Paymentsnp brings them into one checkout; it does not replace provider onboarding.

Which payment methods does checkout offer?

eSewa, Khalti by IME and Fonepay, each verified on the server. Checkout does not offer NEPALPAY QR yet, because it needs an approved API contract from the merchant's acquiring bank or PSP.

When can I take live payments?

New accounts are approved by our team before first sign-in. After that you can test with the Sandbox gateway and test keys. Live payments start once each provider has completed UAT with your own merchant credentials.

How do refunds work?

Refunds are record-only. You refund the customer in the provider's own panel, then record it in Paymentsnp from the dashboard or the API. Paymentsnp keeps totals within the payment amount and sends a payment.refunded webhook; it does not call a provider refund API.

What does it cost?

Creating an account and testing in the Sandbox is free. Paymentsnp platform pricing has not been published yet, and gateway fees follow your own agreement with each provider.

Try it with test money first.

Sign up and verify your email. Once your account is approved, take a payment through the Sandbox gateway with a test key, then connect your real provider accounts when you are ready.