Connect once
A shared checkout API brings enabled providers into the same payment journey, without separate checkout code for every method.

The way Nepal pays.
Finally, connected.
Your customers' favourite payment methods.
One checkout. Directly to your account.



Payment providers work differently. Your business shouldn't have to rebuild its checkout for each one.
A shared checkout API brings enabled providers into the same payment journey, without separate checkout code for every method.
Use your own merchant credentials. Payment providers credit or settle funds to your configured account under your agreement.
The planned dashboard brings verified transactions, payment methods, order references, and delivery history together.
Server-side verification establishes payment status before your business receives confirmation. A browser redirect is never enough.
Let your customer choose a wallet or QR flow they already know. Paymentnp routes the payment using your connected merchant account.
Your server sends an amount and order reference to one checkout API.
The checkout offers only the methods your business has connected and enabled.
Your application receives a signed confirmation after provider verification.
A consistent payment foundation for the different ways businesses in Nepal sell, bill, and grow.
Bring payment choices into your order journey. Match a verified transaction to the right order and keep fulfillment independent of browser returns.
Explore commerceKeep your own customer experience and hand off payment selection to hosted checkout. Use the same result contract across your web and app services.
Explore the APIConnect invoice references to payment records. Future WHMCS and billing adapters will use the same Paymentnp API as custom integrations.
Explore billingStart with an order reference, an amount in paisa, and your allowed methods. The proposed API returns a checkout link your customer can open.
curl -X POST "$PAYMENTNP_API_URL/v1/checkout/sessions" \
-H "Authorization: Bearer $PAYMENTNP_SECRET_KEY" \
-H "Idempotency-Key: order-1001" \
-H "Content-Type: application/json" \
-d '{
"order_id": "order-1001",
"amount_minor": 150000,
"currency": "NPR",
"allowed_methods": ["esewa", "khalti"]
}'Paymentnp is designed to coordinate checkout and report verified activity. Your payment provider remains responsible for crediting and settling your merchant account.
Through their chosen provider.
Using your merchant connection.
Funds through your provider. Activity in Paymentnp.
What to know before planning your Paymentnp integration.
Paymentnp is in development. Merchant accounts, the connected dashboard, payment links, and hosted sandbox checkout are available locally. Real payment processing, message delivery, and platform adapters are not live yet.
No. The architecture uses your own payment provider credentials. Funds are credited or settled by the provider to your configured merchant account, subject to provider schedules and charges.
Yes. Your business needs approved merchant access with each payment provider you want to offer. Paymentnp brings those connections into one checkout; it does not replace provider onboarding.
The first complete checkout targets eSewa and Khalti by IME. Fonepay and NEPALPAY QR are planned after approved API access and reliable verification are confirmed.
A shared payment workspace for your existing platform, customer communications, and branded checkout. Payment links and merchant branding are available in sandbox; automated delivery and adapters are the next integrations.
Match verified payments to order and invoice references through the API. A planned WHMCS adapter will confirm payments against invoices and prevent duplicate fulfilment. Reporting is available now; automated platform reconciliation follows verified callbacks.
Choose SMS updates for transaction results. Delivery will use a configured messaging provider with consent, recipient validation, and retry tracking. Preferences are available now; SMS sending is not active yet.
Send the customer an invoice after an authoritative payment confirmation. Invoice generation and delivery will share the payment reference, merchant identity, amount, and currency. Email delivery remains a planned integration.
Use a hosted checkout page or open it in a popup. Set your merchant display name, accent color, and hide platform branding for a merchant-branded experience. Full custom-domain white-label checkout is planned.
Create a reusable payment link with a fixed amount, or let the customer enter an amount within your limits. Set an expiry and disable links when needed. Each payment opens its own tracked checkout, with sandbox support today.
Set reminder preferences for both the customer and the vendor or merchant. Scheduled delivery will target unpaid orders and stop after verified payment, with duplicate suppression and opt-out support. The scheduling worker is planned.
Explore a simpler way to connect your business with the payment methods your customers know.