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
PaymentsLast 7 days
OrderMethodAmountStatus
PL-20261112-0007KhaltiNPR 2,450.00PendingSucceeded
PL-20261112-0006FonepayNPR 1,200.00Succeeded
PL-20261111-0005eSewaNPR 899.00Succeeded

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.

  • A shopkeeper at the counter of a busy clothing and souvenir shop in Kathmandu

    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
    Read about online stores
  • A man sitting on the steps of a small momo restaurant decorated with prayer flags

    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
    Read about selling on chat and social media
  • A smiling receptionist at a desk in front of the Nest Nepal sign

    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
    Read about schools, clinics and service businesses
  • A man writing on a glass whiteboard while two colleagues watch

    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
    Read about hosting and software companies

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.

  1. CustomerPays on the checkout you send
  2. ProvidereSewa, Khalti or Fonepay takes the payment into your merchant account
  3. PaymentsnpChecks the payment with the provider and records it
  4. YouSee the verified payment; the provider settles to you
Money moves from the provider to your account under your own agreement. Paymentsnp only verifies and records it.

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.

Paymentsnp tools by business type
BusinessCustomers pay throughYou learn it is paid fromSet up in
Online storeYour store's checkout, then hosted checkoutA webhook, the return check and a scheduled re-checkPlugin settings or your own code
Chat and social sellerA payment linkThe dashboard, plus the receipt your customer getsThe dashboard
School, clinic or agencyA hosted invoice or a payment linkThe invoice turning paid, so its reminders stopThe dashboard or the invoices API
Hosting or software companyA Pay now button on your own invoicesA webhook into your billing system, with cron as a fallbackThe 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 integrations

Before 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.