Why we built Paymentsnp
Selling online in Nepal should not mean three integrations, three dashboards and a phone full of payment screenshots. We wanted one checkout that works with the apps people already use, and keeps the money with the business.
The problem we kept running into
A customer in Pokhara wants to pay with eSewa. The next one only has Khalti. Someone else opens their bank app and looks for a QR. For the business, each of those is a separate merchant account, a separate set of keys, a separate way of signing requests and a separate idea of what “paid” means.
Most shops end up asking customers to send a screenshot, then checking the wallet app by hand before packing the order. That works until it doesn't: a fake screenshot, a payment that arrives twice, a customer who paid but closed the page.
Paymentsnp does the boring, careful part once. You connect the merchant accounts you already have. Your customers get one clear checkout. Your system gets one answer it can trust, after we have checked with the provider. The money never leaves the path between your customer, the provider and you.
Decisions we made early
These shape everything else, and we do not plan to change them.
We do not hold your money.
No wallet, no balance, no payouts. Settlement stays between you and your provider, under the agreement you already signed.
“Paid” means the provider said so.
Not a return link, not a screenshot. When the answer is unclear, the payment stays pending, and we say so.
Your brand comes first.
Customers see your name and logo. A small “Powered by Paymentsnp” line stays at the bottom of checkout so they know who is handling the page.
We only say what is true today.
No made-up merchant counts, partnerships or certificates on this site. If something is coming soon, it is labelled that way.
Who we build for
The momo shop that takes orders on Viber. The café with a QR on the counter. The hosting company billing through WHMCS. The school collecting fees and the trekking agency taking deposits from abroad.
Where things stand
Live payments also need each provider to finish UAT with your own credentials; that part is between you and them.
| Area | What it includes | Status |
|---|---|---|
| Checkout with eSewa, Khalti and Fonepay | Hosted checkout, popup checkout, payment links, server-side verification, signed webhooks | Available |
| Paperwork after payment | Receipts by SMS and email, invoices with VAT and PDF, reminders, reconciliation, CSV exports | Available |
| Plugins and SDKs | WHMCS, WooCommerce and a self-hosted Shopify app; SDKs for TypeScript, PHP and Python; a CLI and an MCP server | Available |
| NEPALPAY QR | Credentials can be saved today; checkout follows once the acquirer API contract is confirmed | Coming soon |
| Refunds | Only once providers support them reliably through their APIs | Not yet |
| Mobile app | A merchant app for checking payments on the go | Not yet |
The source and architecture notes are public, including why an unclear payment is “unknown” rather than “failed”. Paymentsnp on GitHub (opens in a new tab)
Common questions
What does Paymentsnp do?
It connects a business's own eSewa, Khalti and Fonepay merchant accounts to one checkout, confirms each payment with the provider, tells the business's systems, and keeps the records: receipts, invoices, reports and reconciliation.
Can I register and accept payments now?
Yes. Create a workspace, verify your email, and test with the Sandbox. Live eSewa, Khalti and Fonepay payments use your own merchant credentials once the provider has completed UAT for your account.
Is Paymentsnp the same as NEPALPAY QR?
No. Paymentsnp is this checkout and payments product. NEPALPAY QR is a payment network run by NCHL, which may be connected through an approved acquiring bank.
How much will the platform cost?
Pricing has not been published. Provider fees and settlement terms remain governed by your merchant agreements. Any Paymentsnp platform pricing will be stated before merchants activate a paid service.
Will IME Pay have its own checkout method?
Khalti and IME Pay have merged into Khalti by IME, so IME Pay customers pay through Khalti. A separate IME Pay option would only be added if an independently supported merchant API is confirmed.