Online stores that only ship paid orders

Add eSewa, Khalti and Fonepay to your WooCommerce shop, Shopify store or your own site. Every payment is checked with the provider on the server, so an order turns paid because the money moved, not because a page said so.

  • Classic checkout and the Checkout block
  • Order reminders after 24 hours
  • Money settles to your own accounts
A smiling woman in a grey sweater holding an open laptop

Three wallets, three panels. One spreadsheet at midnight.

A customer checks out at ten at night and picks Khalti. Another picks eSewa, a third scans a Fonepay QR. By morning you have orders marked pending, a few marked paid, and three merchant panels to log in to before you can tell which ones you should pack.

Most of the work is matching amounts by hand, and the gaps are where mistakes happen.

  1. The customer closes the tab after payingThe store never hears back, so a paid order sits as unpaid until someone checks the provider panel.
  2. A return page is taken as proofA success URL can be opened by anyone. If the store trusts it, an unpaid order can be shipped.
  3. The customer pays twiceA second tab or a second method starts another payment for the same order, and now there is a refund to sort out.

How Paymentsnp fits. Your store keeps the cart, we handle the payment step.

  1. The customer chooses to pay online

    Your store creates a Paymentsnp checkout for the order: the amount in paisa, your order number and an idempotency key, so a retry never creates a second checkout.

  2. They pick a method on hosted checkout

    Only the methods you have connected and switched on appear, in English or नेपाली. The customer then pays on eSewa's, Khalti's or Fonepay's own page.

  3. Paymentsnp checks the payment

    eSewa and Khalti are asked for the payment status with the exact amount. Fonepay's signed return is checked for the exact amount. Only then is the payment recorded as succeeded.

  4. Your store marks the order paid

    A signed webhook, the check when the customer returns, and a scheduled re-check all ask the API for the verified payment, so one missed step does not leave a paid order unpaid.

Your store
Amount to payNPR 3,250.00Order #1001

Choose how to pay

  • eSewaLog in to your eSewa wallet to pay
  • KhaltiKhalti wallet, mobile banking or internet banking
  • FonepayScan a QR code with any mobile banking app
Continue with eSewa

Powered by Paymentsnp

Connect your store. Plugin, app or your own code.

Pick the route that matches your platform. All three send customers to the same hosted checkout and get the same verified result.

WooCommerce plugin

Paymentsnp for WooCommerce 1.0.0 adds a payment method that works on the classic checkout and the Checkout block, and supports HPOS. The store currency must be Nepalese rupee; for any other currency the method is hidden. Orders are confirmed by webhook, on return, and by a WP-Cron job every 10 minutes.

Set up the WooCommerce plugin

PaymentTotal NPR 3,250.00
Cash on delivery
Pay with eSewa, Khalti or FonepayYou will choose a method on the next page.
Place order
  • Your own site, through the API

    Your server creates a checkout session and redirects the customer, or opens it in a popup with checkout.js on domains you approve. SDKs for TypeScript, PHP and Python handle retries, idempotency and webhook signatures.

  • Shopify, through a self-hosted app

    Shopify only admits approved Payments Partners into its checkout, so the app adds a manual payment method and emails the customer a signed Pay now link. The order turns paid once Paymentsnp verifies the payment.

Ways to connect an online store
RouteWhere the customer paysHow the order turns paidYou host
WooCommerce pluginStore checkout, then hosted checkoutWebhook, return check, WP-Cron every 10 minutesYour WordPress site
Your own site (API or popup)Your page, then hosted checkout or a popupYour webhook handler and API callsYour server
Shopify appAfter placing the order, from a Pay now linkAdmin API orderMarkAsPaid after verificationA small Node.js app

After the order. Reminders, receipts and webhooks.

Before a reminder
24 h
Live orders unpaid for 24 hours get one
Reminders at most
2
Per order and per channel
Webhook attempts
8
With retries backing off up to an hour
Khalti minimum
Rs 10
Khalti is hidden below it
  • Unpaid-order reminders

    An hourly job finds live orders left unpaid for more than 24 hours and reminds the customer, at most twice per order and channel. The email carries a fresh checkout link; texts never carry links. You get a daily digest of unpaid orders by email and SMS.

  • Receipts without a plugin

    Every checkout payment gets its own numbered receipt automatically. Customers who leave an email or phone number get it by email or SMS, so your store does not have to send one.

  • Webhooks into your order system

    payment.succeeded, payment.failed and checkout.expired arrive signed with Paymentnp-Signature. Retries back off up to an hour, and you can replay a delivery from the dashboard.

What you need. Before the first live order.

Testing needs only an approved free account and the Sandbox. Live payments need the provider side in place too.

Merchant accountsYour own approved eSewa, Khalti or Fonepay merchant access and credentials. Paymentsnp checks them with the provider before saving.
An approved Paymentsnp accountNew accounts are approved by hand by default, after you verify your email.
Store currencyNepalese rupee (NPR). Paymentsnp handles NPR only, in whole paisa.
A public HTTPS siteLive return addresses must be HTTPS and added to your allowed return origins.
An API keyWith the checkout:create, checkout:read and payments:read scopes, in the same environment as the store.
Provider testingRun payments in test mode first. eSewa asks merchants to pass its own UAT before live access.

Limits. So nothing surprises you later.

Questions from store owners.

What happens if the customer pays and closes the browser?

eSewa and Khalti attempts are re-checked in the background, and a late success is still recorded. Your store then hears about it by webhook or its own scheduled re-check. Fonepay has no lookup, so an unreturned Fonepay payment is confirmed by hand from the Fonepay panel reference.

Can a customer pay twice for one order?

Paymentsnp allows one unresolved attempt per order. Before a second method can start, the first provider is asked what happened. If it is still unclear, checkout says a payment is in progress instead of starting another.

Does my store need to be in NPR?

Yes. Paymentsnp handles NPR only. The WooCommerce plugin hides the method for any other currency, and the Shopify app does not handle non-NPR or multi-currency orders.

Can I put checkout on my own domain?

Yes. Verify a domain with a DNS TXT record and point a CNAME at paymentsnp.com. The certificate is issued automatically, and the WooCommerce plugin sends customers there without any change.

Is there a minimum order amount?

Khalti's minimum is Rs 10, so Khalti is hidden at checkout below it. Paymentsnp sets no minimum for eSewa or Fonepay.