How PayBridgeNP works - PayBridgeNP

PayBridgeNP gives your server one checkout API for eSewa, Khalti, and Fonepay. It handles each provider’s request format, callback, and verification flow while you keep your own provider accounts.

Payments settle directly into your eSewa, Khalti, or Fonepay merchant account. PayBridgeNP does not hold or settle your funds.

Start with your goal

Run a sandbox payment: follow the Quickstart.
Build a custom flow: create a session with the Checkout API.
Connect an existing store: use the Shopify, WooCommerce, or WHMCS integration.

Payment flow

Sequence from checkout creation through provider verification and the signed webhook sent to your server — PayBridgeNP verifies the provider result before your server receives a signed webhook.

Your server creates the checkout and sends the buyer to its URL. PayBridgeNP handles the provider handoff; your server fulfills only after verifying the signed webhook and matching the payment’s status, amount, and currency.

Key concepts

Concept	What it means
Amounts	Send integer paisa. `10000` represents NPR 100.00.
Settlement	Funds move to your provider merchant account, not to PayBridgeNP.
Projects	Each project has isolated API keys and provider credentials.
API keys	Use `sk_test_` for sandbox and `sk_live_` for live payments. A key’s mode cannot change.
Sandbox	eSewa and Khalti use test environments. Fonepay uses real money within test caps.

Supported providers

Provider	Sandbox	Live
eSewa	✓	✓
Khalti	✓	✓
Fonepay	✓ (real money, capped)	✓

Get started

Create a sandbox project in the PayBridgeNP Dashboard, then follow the Quickstart.