One API call becomes a full Nepali checkout.
Create a session and redirect. Your customer pays with eSewa, Khalti, or Fonepay QR on a page we host, in Nepali or English, on whatever phone they are holding.
- 0% platform fee
- PayBridgeNP ID built in
- Free sandbox
eSewa, Khalti, Fonepay QR, and every Fonepay bank app, on one page.
The life of Rs 2,499.
One request. Four things happen before the money reaches you.
1
The request
Amount in, URL out.
We return a mobile-ready checkout for the amount and customer.
2
The payment
The buyer approves.
Fonepay QR stays here. eSewa and Khalti open their own checkout.
3
The proof
Verified, then signed.
We verify server-side and retry your webhook until it lands.
4
The money
It never passes through us.
The provider settles it into your merchant account, never into ours.
The real checkout in a desktop browser: recognised, filled in, Nepali and back, Fonepay QR, paid.
Provider selected. Payment verified. Webhook delivered.
More than a redirect URL.
The hosted page ships with the details merchants usually bolt on later: recognition, language, sandbox, and your own domain.
- 1
PayBridgeNP ID built in
Returning buyers are recognised on our domain. Their details prefill and their preferred wallet is preselected, with nothing for you to wire up.
- 2
Your domain on Pro
Serve checkout from pay.yourbrand.com.np so the address bar matches your store while PayBridgeNP still hosts and secures the page.
- 3
Nepali and English
The page ships in both languages. Buyers switch with one tap, and you never maintain translation files.
- 4
Sandbox on every plan
Test the full flow with sk_test_ before you connect live merchant accounts. Same page, same webhooks. eSewa and Khalti cost nothing to test; Fonepay has no free sandbox, so its test payments move real money and are worth keeping small.
Hosted checkout questions
Read the quickstartWhat is a hosted checkout page?
A payment page that PayBridgeNP hosts and maintains for you. You create a checkout session with one API call, redirect your customer to the URL you get back, and they pay with eSewa, Khalti, or Fonepay on a page that is already built, tested, and mobile-ready. You never build a payment UI.
How do I add hosted checkout to my website in Nepal?
Send one POST request to create a checkout session and redirect to the returned URL, using the TypeScript, PHP, or Python SDK or plain REST. On Shopify, WooCommerce, or WHMCS the plugin does this for you, and payment links and Payment Buttons use the same hosted page with no code at all.
Which payment methods does the hosted checkout support?
eSewa, Khalti, and Fonepay Dynamic QR on one page. The customer picks their method; Fonepay QR confirms instantly on the page with no redirect. Enable or disable providers per project from the dashboard without changing your integration.
Can the checkout run on my own domain?
Yes. Pro merchants can serve the hosted checkout from their own custom domain, so customers see your brand in the address bar while PayBridgeNP still runs and secures the page.
Do I need to worry about PCI or handling payment credentials?
No. Payments run on the providers' own NRB-licensed rails, and your customer authenticates inside eSewa, Khalti, or their banking app. Wallet passwords and PINs never touch your servers or ours, and every payment is verified server-side before you get a signed webhook.
Do returning customers have to type their details every time?
No. PayBridgeNP ID is built into the hosted checkout: returning buyers are recognised, their name and address prefill, and their preferred wallet is preselected. It is on automatically, with nothing for you to integrate.
0% platform fee
Hand us the checkout, keep the money
One session call, every way Nepal pays, and settlement straight to your own merchant accounts.