Shopify
WooCommerce
WHMCSThe whole payment, in context
No trip to a checkout page.
Click through the moments that matter: wallet choice, provider approval, a slow response and a verified payment. Your page stays behind the window the whole way. Approval still happens with the wallet, which is where it belongs.
Patan Loom cart
Dhaka table runner
Rs 4,850
Wallet credentials
Stay with the provider
Settlement
Direct to your merchant account
Success state
Backed by a verified webhook
Four steps, one paste
Two of these four are the overlay.
The first and last are the same as any payment button. The middle two turn a redirect into an overlay.
- Create a button
- Amount, label and fields, in the dashboard.
- Turn the overlay on
- Tick Open over my own page. Existing buttons keep redirecting until you do.
- Allow your domain
- Add your exact origin under Project, Embed domains.
- Paste the script
- One tag beside your buy button. Fulfil on payment.succeeded.
<script
src="https://api.paybridgenp.com/js/v1/button.js"
data-button-id="btn_xxx">
</script>- Your domain is not allowed
- The checkout takes the full page instead of opening blank. The payment still completes.
- The buyer closes it halfway
- Reopening resumes the same payment. One order, one charge.
- A wallet needs approval
- Fonepay finishes inside, and eSewa on the Intent rail. Khalti opens its app and returns.
- A returning buyer arrives
- Recognised once they type, not before. Browsers withhold our cookie inside your page.
The details
Questions before you put it on the cart page.
Straight answers on wallet approval, recovery, security and plans.
What is Embedded Checkout?
It is a payment window that opens over your own page instead of sending the buyer to a separate checkout page. Your shop stays behind it and the window closes when payment finishes. PayBridgeNP builds, hosts and secures everything inside the window.
How is it different from Hosted Checkout?
The checkout is the same, but the entry point is different. Hosted Checkout sends the buyer to a PayBridgeNP-hosted page. Embedded Checkout opens the payment step over your website. Both accept eSewa, Khalti and Fonepay and verify payments the same way.
Does the buyer still open eSewa or Khalti?
For wallet approval, yes. The wallet opens its own app or site so the buyer enters their PIN with the provider, never with you or PayBridgeNP. On a phone the wallet opens and returns. Fonepay QR confirms inside the checkout.
What if the buyer closes checkout halfway?
Reopening checkout restores the same payment instead of creating another one. Details already entered are still there, so the buyer can continue without paying twice for the same order.
Are returning buyers recognised inside the overlay?
Mostly. A returning buyer types their number, gets a code, and their saved details fill in, exactly as on the hosted checkout. What the overlay cannot do is greet them before they type: that needs a cookie on our own domain, and browsers withhold it from a page running inside another site.
Do I have to build the payment form?
No. Add the Payment Button script and PayBridgeNP handles the fields, validation, Nepali translation, QR, expiry countdown and error states. Your site never handles payment credentials.
Can I use it on a cart page with a changing total?
Only if your server sets the amount. A fixed-price button is safe anywhere. A custom-amount button reads its amount from the page, which means the browser can change it before it reaches us, so it must never drive a real cart total. For a cart whose total your server calculates, use Hosted Checkout and state the amount when you create the session.
Which plan includes Embedded Checkout?
Growth or higher. Hosted Checkout works on the Free plan, so it is the checkout route to use there.
Keep the store.
Keep the customer.
Try the sandbox on this page, then create the button your own store will use.