Payment route design
Give customers the right ways to pay.
The method mix is designed around your customers, product, merchant category, checkout, and settlement model. It is confirmed commercially—never assumed from a logo list.
Digital wallets
Nepali checkout runs on wallets.
The NPR routes an eligible merchant can be configured for are eSewa, Khalti, and IME Pay. Each is enabled per approved project, and each carries its own minimum and maximum deposit amount rather than a single site-wide limit.
Operational considerations
- Show only the routes returned as active for the current project and amount.
- Keep clear success, pending, failure, and refund states against the merchant reference.
- Remember that IME Pay services are being integrated into the wider Khalti ecosystem.
- Product, pricing, support, fulfilment, and refund policy stay with the merchant even when the wallet completes the payment step.
Bank-led journeys
Move from checkout to bank approval and back again.
A bank-led payment journey can take a customer to an approved internet- or mobile-banking environment before returning a usable status to the merchant checkout. The integration needs to handle both the customer return and independent payment confirmation.
Merchant systems should rely on the confirmed gateway status or server-side notification defined for the approved integration.
QR-linked payments
Use QR only when the payment state stays connected.
FonePay QR lets a customer pay by scanning from a supported Nepali banking or wallet app. QR is useful in web, invoice, counter, and assisted-payment scenarios, but the important part is not the square itself—it is how the payment reference and final status return to merchant operations.
Limits and availability
Read the live method list; do not hardcode it.
Route availability, direction (deposit or payout) and the minimum and maximum amount per method are published programmatically and change over time. A checkout that polls that list can hide a wallet that is temporarily out of service instead of sending the customer into a payment that cannot complete.
A hosted payment page handles incoming NPR payments only. Sending money back out to customers requires the server-side withdrawal integration, with its own notifications and limits.
Availability rules
Every payment method is conditional until approved.
Route availability can vary with business model, merchant category, documentation, technical compatibility, customer location, currency, partner capacity, and the current regulatory environment.
The initial merchant discussion produces a proposed payment mix. Activation follows the required review, agreement, integration, and testing.