Frequently asked questions
Short answers, each linked to the page with the full story. If yours is not here, ask us.
Getting started
What you need, and how an account goes from sign-up to taking payments.
What is Paymentsnp?
One checkout for Nepal's payment providers. You connect your own eSewa, Khalti and Fonepay merchant accounts, and Paymentsnp hosts the checkout, verifies each payment with the provider and keeps the records. Payments go directly to your provider accounts.
What do I need before I start?
To take real payments, an approved merchant account with each provider you want to offer, and its credentials. To try Paymentsnp, nothing: the Sandbox works without any provider account.
How do I sign up?
Create a free account and verify your email. New accounts are approved by the Paymentsnp team by default; once yours is approved, connect your providers under Gateways.
Can I try it without moving real money?
Yes. Test mode with the Sandbox simulates successful and failed payments and never moves money. It is free, and test keys can never see live data.
Do I need a developer?
Not always. Payment links and invoices work from the dashboard without code, and there are plugins for WHMCS and WooCommerce and a self-hosted Shopify app. The API is there when you want a custom integration.
Can my team share one workspace?
Yes. Invite teammates as Owner, Administrator, Developer or Finance; each role sees and changes different things. Invitations are emailed and last seven days.
Payment methods
Which methods checkout offers, and the limits of each.
Which payment methods does checkout offer?
eSewa, Khalti by IME and Fonepay. You choose which ones to switch on, separately for Test and Live.
Does Paymentsnp support NEPALPAY QR?
Checkout does not offer NEPALPAY QR yet. You can save NEPALPAY credentials, and checkout will follow once an approved acquirer API contract is confirmed.
Can customers pay by card?
Paymentsnp does not process cards. Khalti's own payment page may offer customers other options, such as mobile banking or cards; those are Khalti's, not ours.
What about IME Pay?
Khalti and IME Pay merged into Khalti by IME, so IME Pay customers pay through Khalti. A separate IME Pay option would only be added if an independent merchant API is confirmed.
Is there a minimum amount?
Khalti's minimum is Rs 10, so Khalti is hidden at checkout below that. We set no minimum for eSewa or Fonepay.
How do customers pay with Fonepay?
Checkout opens Fonepay's page with a QR for the order, and the customer scans it with their mobile banking app. Bank logos on this site show banks on Fonepay's network, as listed by Fonepay; they are not Paymentsnp partners.
Money and settlement
Where the money goes, and what Paymentsnp does and does not do with it.
Does Paymentsnp hold my money?
No. Customers pay into your own merchant account with the provider. Paymentsnp holds no funds, keeps no balance and makes no payouts.
When do I get paid?
On the settlement schedule and fees in your agreement with each provider. Paymentsnp does not set or change them.
Why does the dashboard not show a balance?
Because no money passes through Paymentsnp. The dashboard shows verified payments; upload a provider settlement file to see what reached your bank.
How do refunds work?
Refund the customer in the provider's merchant panel, then record the refund in Paymentsnp so totals and webhooks stay right. Paymentsnp does not send refunds through provider APIs.
Can I reconcile against settlement files?
Yes. Import a provider or bank settlement CSV, including Bikram Sambat dates, lakh commas and Nepali digits, and each row is classified as matched, unmatched or a mismatch.
Which currencies are supported?
Nepali rupees only. Amounts are stored as whole paisa.
Checkout and customers
What your customers see, and how long a checkout lasts.
What do customers see at checkout?
Your name, logo and colour, the amount, the methods you enabled and an English or Nepali toggle, with a small Powered by Paymentsnp line at the bottom.
Can I remove Powered by Paymentsnp?
No. It stays on hosted checkout, payment link and invoice pages so customers know who runs the page. Everything above it can carry your brand.
Can checkout run on my own domain?
Yes. Verify a domain with a DNS TXT record and point a CNAME to Paymentsnp; the certificate is issued automatically. Only checkout, payment link and invoice pages are served there.
How long does a checkout stay open?
A checkout session lasts one hour. A payment attempt that nobody finishes expires after 30 minutes, and a late eSewa or Khalti success is still recorded.
Do customers get receipts?
Yes. Every checkout payment gets an automatic receipt, sent by email or SMS to the contact details the customer gives.
Can I share a payment link on Viber or WhatsApp?
Yes. A payment link can have a fixed amount or let the customer enter one, expires in 1 to 365 days, and is an ordinary web address you can share in any chat or SMS.
Developers
Keys, confirmation, SDKs and where the full documentation lives.
How does the API authenticate?
With a secret key in the Authorization header: np_test_ keys for Test, np_live_ keys for Live. Each key carries scopes and can have an expiry, an IP allowlist and its own rate limit.
How do I know a payment succeeded?
Wait for the signed payment.succeeded webhook, or fetch the payment from the API. A customer landing on your return URL is never proof of payment.
Which SDKs are there?
TypeScript (@paymentsnp/sdk, with a paymentsnp CLI), PHP (paymentsnp/paymentsnp-php) and Python (paymentsnp). All three have no runtime dependencies.
Can customers pay without leaving my site?
The popup checkout opens in a small window over your page and reports the result back. If the browser blocks the popup, checkout opens in the same tab instead.
Is there an MCP server for AI assistants?
Yes, @paymentsnp/mcp. It runs on your machine, is read-only unless you allow writes, and masks customer details.
Where is the full documentation?
The developer pages on this site give an overview. The full guide is in the dashboard after you sign in, and the generated API reference is public.
Security and data
Secrets, customer data and what has been reviewed.
Who can see my provider credentials?
Nobody through the product, Paymentsnp staff included. They are encrypted with AES-256-GCM and never returned to a browser, an administrator or a log.
Does Paymentsnp see customer wallet passwords or OTPs?
No. Customers sign in and approve payments on the provider's own page. Paymentsnp never asks for them.
Is my data kept apart from other businesses?
Yes, in the database itself: row-level security is forced on every business table, and Test and Live records are separated.
Can I turn on two-factor sign-in?
Yes, with an authenticator app, and keep the ten one-time recovery codes somewhere safe. You can also see your signed-in devices and sign others out.
Has Paymentsnp been audited?
The team carried out an internal security review dated 17 October 2026 and fixed its findings. It was not an independent audit, and Paymentsnp claims no certification.
How do I report a vulnerability?
Use the contact form with the topic Security report. Include the steps to reproduce it.
Pricing
What is free today, and what is not published yet.
How much does Paymentsnp cost?
Platform pricing has not been published yet. Creating an account and testing in the Sandbox is free.
Do I still pay provider fees?
Yes. eSewa, Khalti and Fonepay fees follow your own agreement with each provider, and they are settled between you and them.
Will pricing be clear before I pay anything?
Yes. Any Paymentsnp platform pricing will be stated before you activate a paid service.