NPR 1,500.00
Hosted checkout
One API call gives you a checkout page with your name, the amount and the methods you have switched on.
Hosted checkoutOne 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.
Checkout created
POST /v1/checkout/sessions → 201 · order-1042
Customer pays
Picks Khalti · NPR 1,500.00
Checked with Khalti
Exact amount confirmed by the provider
Your server is told
payment.succeeded → 200 OK · receipt by SMS













Banks on Fonepay's network, as listed by Fonepay. They are not Paymentsnp partners. How providers and banks relate to Paymentsnp
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


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


The same checkout opens over your page with one script tag. Only domains you approve can open it.
Popup checkoutNo 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 linksDraft an invoice, add 13% VAT and a discount, and email it with a PDF and a pay button.
Invoices and receiptsUpload the settlement CSV from your provider or bank, with Nepali dates and lakh commas, and see which payments match.
Reconciliation and reportsYour logo and colour on checkout, even on your own domain. “Powered by Paymentsnp” stays at the bottom.
Branding and custom domainThe 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.
Confirms the exact amount with the provider, records the payment and sends your server a signed webhook. Holds nothing.
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 quickstartPaste 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.
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.
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.
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.
HCC-1001Payment is confirmed with the provider before your order is paid.
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.
Idempotency-Key on every create, so a retry never opens a second checkoutnp_test_ and np_live_ keys; test keys never see live datacurl -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"])201Checkout created. Send the customer to checkout_urlpayThe customer pays on the provider's pagecheckPaymentsnp confirms the exact amount with the providerhookpayment.succeeded arrives, signed with Paymentnp-SignatureSigned-in merchants download the plugins from Dashboard > Downloads. The SDKs and the MCP server install from npm, Packagist and PyPI.
All integrationspaymentnpv23.0.0WHMCS moduleWHMCS 8.x on PHP 7.4 to 8.3. Adds Pay now to unpaid invoices and re-checks pending payments on cron.paymentsnp-for-woocommerce1.0.0WooCommerce pluginWordPress 6.0+, WooCommerce 7.0+, PHP 7.4+ and a store currency of NPR. Classic checkout and the Checkout block.paymentsnp-shopify-app1.0.0Shopify appSelf-hosted on Node 20. A manual payment method with a signed pay link, not a gateway inside Shopify checkout.@paymentsnp/sdk1.0.0SDKs for TypeScript, PHP and PythonNode 18+, PHP 7.4+ and Python 3.9+. Typed errors, retries and webhook signature checks in each.@paymentsnp/mcp0.1.0MCP serverNode 20+. Read-only unless you allow writes, with your API key kept on your own machine./checkout.jsPopup checkoutOne script tag with no dependencies. Opens only on domains you approve, up to 20 per environment.Many begin with a chat message, a fee reminder or a renewal. Pick the one closest to your business.
All solutions



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 serverHow 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.
Straight answers before you connect your first provider.
All questionsNo. 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.
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.
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.
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.
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.
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.
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.