One way to get paid, shaped to how you sell
Every business gets the same core: a checkout for eSewa, Khalti and Fonepay, a server-side check of every payment, and money that settles straight to your own provider accounts. What changes is how your customers reach that checkout.
- Free account and test mode
- Settles to your own merchant accounts
- Paymentsnp never holds your money
| Order | Method | Amount | Status |
|---|---|---|---|
| PL-20261112-0007 | Khalti | NPR 2,450.00 | PendingSucceeded |
| PL-20261112-0006 | Fonepay | NPR 1,200.00 | Succeeded |
| PL-20261111-0005 | eSewa | NPR 899.00 | Succeeded |
Four kinds of business. Pick the one closest to yours.
Each page walks through a normal day of taking payments, the Paymentsnp products that fit, and the limits worth knowing before you start.

Online stores
You run a WooCommerce shop, a Shopify store or your own site, and an order should be marked paid only when the money has really moved. Paymentsnp checks each payment with the provider before your store hears about it.
- Main tools
- Hosted checkout, popup checkout, unpaid-order reminders, receipts
- Connects through
- WooCommerce plugin, Shopify app, REST API or an SDK

Selling on chat and social media
Orders arrive on Viber, WhatsApp or at the counter, and the proof of payment arrives as a screenshot. Send a payment link instead, and see the verified payment in your dashboard.
- Main tools
- Payment links, a QR for the counter, your workspace payment page
- Connects through
- Nothing to install. Everything runs from the dashboard

Schools, clinics and service businesses
You bill for fees, sessions and projects, and spend too long working out who has paid. Send a VAT invoice with a Pay button, let reminders go out on schedule, and record cash payments next to online ones.
- Main tools
- Invoices with 13% VAT, reminders, payment links, CSV exports
- Connects through
- The dashboard, or the invoices API from your own system

Hosting and software companies
Your billing system already generates the invoices. Paymentsnp adds a Pay now button to them, confirms each payment server-side, and gives your team an API, webhooks and reconciliation to keep the books straight.
- Main tools
- WHMCS module, invoices API, webhooks, reconciliation, MCP server
- Connects through
- WHMCS module, REST API, SDKs for TypeScript, PHP and Python
What every business gets. Whichever way you sell.
A server-side check of every payment
A return page is never treated as proof. Paymentsnp asks eSewa or Khalti for the payment status with the exact amount, or checks Fonepay's signed return, before anything is marked paid.
A receipt for every checkout payment
Each checkout payment gets its own numbered receipt automatically, sent by email or SMS when the customer leaves a contact. Invoices are numbered separately for each workspace.
Settlement to your own accounts
Customers pay into your eSewa, Khalti or Fonepay merchant account under your own agreement, fees and schedule. The dashboard shows verified payments, never a balance, because Paymentsnp never holds one.
- CustomerPays on the checkout you send
- ProvidereSewa, Khalti or Fonepay takes the payment into your merchant account
- PaymentsnpChecks the payment with the provider and records it
- YouSee the verified payment; the provider settles to you
Which tool does the work. Side by side.
Most businesses use more than one. A shop with a website can still send a payment link to a customer who ordered by phone.
| Business | Customers pay through | You learn it is paid from | Set up in |
|---|---|---|---|
| Online store | Your store's checkout, then hosted checkout | A webhook, the return check and a scheduled re-check | Plugin settings or your own code |
| Chat and social seller | A payment link | The dashboard, plus the receipt your customer gets | The dashboard |
| School, clinic or agency | A hosted invoice or a payment link | The invoice turning paid, so its reminders stop | The dashboard or the invoices API |
| Hosting or software company | A Pay now button on your own invoices | A webhook into your billing system, with cron as a fallback | The WHMCS module or the API |
Already on a platform? Connect it.
Plugins, a WHMCS module, SDKs and an MCP server. Verified owners, administrators and developers download them from the dashboard.
See all integrationsBefore you choose. Common questions.
Do I need a separate account for each way I sell?
No. One workspace can use hosted checkout, payment links, invoices and plugins at the same time, with the same connected eSewa, Khalti and Fonepay accounts. If you run separate businesses, one login can belong to several workspaces.
Do I need my own eSewa, Khalti or Fonepay merchant account?
Yes. Each method needs approved merchant access and credentials from that provider. Paymentsnp connects to those accounts. Signing up with Paymentsnp and onboarding with a provider are separate steps.
Can I try it before connecting a provider?
Yes. Creating an account and testing in the Sandbox is free. The Sandbox simulates success and failure in test mode and never moves money.
What does Paymentsnp cost?
Platform pricing has not been published yet. Gateway fees follow your own agreement with each provider, and any Paymentsnp pricing will be stated before you activate a paid service.