Shops, restaurants and small businesses
No website needed. Make a payment link for Rs 850 or let the customer type the amount, then share it on Viber, WhatsApp or SMS.
Payment linksTake eSewa, Khalti and Fonepay payments on your website.
Paymentsnp puts Nepal's wallets and QR payments behind one checkout. Customers pay the way they already do. The money goes straight to your own merchant accounts, and an order is only marked paid after the provider confirms it.
For any business that takes payments online in Nepal: online shops, SaaS and subscriptions, hosting companies on WHMCS, schools and colleges, hotels and travel agents, marketplaces and mobile apps. Testing is free.
Works with the apps your customers use
How it works
You keep your provider accounts. We sit in front of them and do the checking.
- 1
Add the merchant accounts you already have
Paste in your eSewa, Khalti and Fonepay credentials. We encrypt them and never show them again, not even to our own staff. Payments keep settling to those accounts, on the terms you agreed with each provider.
- 2
Send customers to one checkout
Create a checkout from your server, install a plugin, or just send a payment link on Viber. The customer sees your name and logo, picks eSewa, Khalti or Fonepay, and pays in the app they trust.
- 3
Mark the order paid when the provider says so
We check every payment with the provider for the exact amount before calling it paid. Then your server gets a signed webhook and the customer gets a receipt by SMS or email.
Who uses it
Anyone in Nepal who sells something and wants to get paid without chasing screenshots.
Online stores and marketplaces
Add checkout to WooCommerce or your own site. Each order is marked paid once, even if the customer closes the tab halfway through.
Plugins and API
Hotels, trekking and travel agents
Send a deposit link before the guest arrives, or a full invoice with 13% VAT that they can pay from anywhere.
Invoices
SaaS, hosting, schools and apps
Send an invoice for each plan renewal, WHMCS bill or term's fees, all through one API, with test keys to try everything before you go live.
Developer platformWhat your customer sees
Your business name at the top, the amount, and the methods you have switched on. One button takes them to eSewa, Khalti or Fonepay to finish. Click around: 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 Nepali, chosen by the customer
- Your logo and colour, with “Powered by Paymentsnp” below
Himalayan Coffee Co.Demo
Amount to payNPR 1,500.00Order
HCC-1001Choose a payment method
Payment is confirmed with the provider before your order is paid.
Powered by Paymentsnp
After the customer pays
Taking the money is half the job. The rest is paperwork, and most of it happens on its own.
- Receipts
- After each verified payment the customer can get an SMS and an emailed PDF receipt.
- Invoices with VAT
- Draft an invoice, add 13% VAT and a discount, and email it with a PDF and a pay button.
- Reminders
- Unpaid orders get up to two reminders with a fresh link. Paid ones are left alone.
- Webhooks
- Your system hears about each payment through a signed webhook, retried until it gets through.
- Reconciliation
- Upload your bank or wallet settlement CSV, Nepali dates included, and see what matches.
- Your brand
- Your logo and colour on checkout, even on your own domain. “Powered by Paymentsnp” stays at the bottom.
We never touch the money.
The customer pays eSewa, Khalti or Fonepay, and the provider settles to your merchant account like it always has. We only see the proof that the payment happened. There is no Paymentsnp wallet, balance or payout to wait for.
How we keep payments honestFor developers: one request makes a checkout
Send an order ID and an amount in paisa from your server. You get a checkout link back. Signing, redirects and verification for each gateway are our problem.
- Idempotency keys, so a retry never creates a second checkout
- Separate test and live keys
- SDKs on npm, Packagist and PyPI, plus WHMCS, WooCommerce and Shopify plugins
curl 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"
}'
# → { "checkout_url": "https://paymentnp.com/c/…", … }Run on your server. Never put your secret key in browser code.
Questions people ask first
Straight answers before you connect your first gateway.
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 or balance for your funds.
Do I need my own gateway merchant accounts?
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 are available?
eSewa, Khalti by IME and Fonepay are available now, each verified on the server. NEPALPAY QR is coming soon, once the acquirer API contract is confirmed.
Can I try it before going live?
Yes. Create a free account, verify your email and use the Sandbox gateway with test API keys. Live payments start after each provider completes UAT with your credentials.
Does it work with WHMCS, WooCommerce or Shopify?
Yes. Signed-in merchants can download the WHMCS module, the WooCommerce plugin and a self-hosted Shopify app from the dashboard. Each one marks an order paid only after Paymentsnp verifies the payment.
What does it cost?
Creating an account and testing in the Sandbox is free. Paymentsnp platform pricing has not been published yet; gateway fees follow your own agreement with each provider.