Blog
WHMCS payments in Nepal: a practical guide
Hosting companies in Nepal bill in rupees, and customers expect to pay with the wallet or bank they already use.
The options
| eSewa, Khalti | Popular wallets. Each has its own API and callback behaviour. |
|---|---|
| NCHL ConnectIPS | Bank account payments through the national clearing house. |
| OnePG | Nepal Payment Solution gateway covering many wallets and banks. |
| Stripe | International cards for customers abroad. |
The problem with one module per provider
Every provider integration needs its own callback handling, retries and refund logic. Write that five times and you maintain five sets of bugs. The failure that hurts most is a payment that succeeds at the provider while the callback never reaches WHMCS, leaving a paid customer with an unpaid invoice.
What to require from any setup
- An invoice is marked paid only when the provider confirms it, not on a browser redirect.
- A job that re-checks pending payments when callbacks go missing.
- A ledger entry for every payment, so you can reconcile.
- Refunds capped at the amount paid.
- Provider secrets encrypted, and administrator sign-in with a second factor.
That is the design of Dhuri Gateway: one signed API in front of all the providers, with a WHMCS module included.
Questions
Which payment methods can WHMCS take in Nepal?
With a gateway such as Dhuri Gateway: eSewa, Khalti, NCHL ConnectIPS, OnePG, Hamro Pay, and Stripe for international cards.
Keep reading
Correspondence
Tell us what you are building.
Sign-in, payments or point of sale: one message to a real person.