Quickstart
Accept your first payment in under 5 minutes.
Sandbox Testing
Test payments without real credentials.
Webhooks
Get notified the moment a payment succeeds or fails.
TypeScript SDK
Install the SDK and start building.
How it works
1
Merchant creates a checkout session
Your server calls
POST /v1/checkout with the payment amount and a return URL. PayBridgeNP returns a checkout_url.2
Customer pays on the hosted page
Redirect the customer to
checkout_url. They see a branded payment page and pick a provider (eSewa, Khalti, or Fonepay).3
PayBridgeNP verifies the payment
After the customer pays, the provider redirects back to PayBridgeNP. PayBridgeNP calls the provider’s verification API to confirm the payment is genuine.
4
Your server is notified
PayBridgeNP fires a signed webhook to your endpoint and redirects the customer to your
returnUrl with the payment result.Key concepts
Amounts are in paisa. NPR 1 = 100 paisa. An amount of10000 represents Rs. 100.00. This avoids floating-point issues in monetary arithmetic.
PayBridgeNP never holds money. Payments go directly from the customer into your own eSewa, Khalti, or Fonepay merchant account. PayBridgeNP handles the integration complexity only.
Projects are isolated environments. Each project has its own API keys and provider credentials. A single project supports both sandbox and live keys simultaneously - use your sk_test_ key to test and your sk_live_ key for real payments.
API keys start with sk_test_ for sandbox mode and sk_live_ for live mode. The mode is fixed per key - a sandbox key can only create sandbox sessions.
Sandbox mode uses built-in test credentials. You can simulate full payment flows without a real merchant account and without charging anyone.