A WHMCS payment gateway for Nepal
Nepali hosting companies bill in WHMCS but get paid through local wallets and banks. Dhuri Gateway connects the two.
The problem
WHMCS ships with international gateways. Customers in Nepal expect to pay with eSewa, Khalti or their bank. Adding one module per provider means one integration, one callback and one set of bugs per provider.
What Dhuri Gateway does
- Providers built in. eSewa, Khalti, NCHL ConnectIPS, Nepal Payment Solution OnePG, Hamro Pay, plus Stripe for international cards.
- One WHMCS module. The customer can choose the provider at checkout. Adding a provider later does not touch WHMCS.
- Confirmed payments only. An invoice is marked paid when the provider confirms the payment, not on the browser redirect.
- Ledger and refunds. Each payment writes a balanced entry, and a refund can never exceed the payment.
Requirements
WHMCS 8 or later, PHP 7.4 or later with curl, and a WHMCS that is reachable over HTTPS from the internet so the gateway can call it back. The module download is on the release page and the steps are in the release notes.
Provider guides
- eSewa for WHMCS
- Khalti for WHMCS
- ConnectIPS for WHMCS
- OnePG and Hamro Pay for WHMCS
- Stripe cards for WHMCS
- Self-hosted gateway
Questions
Which WHMCS payment gateway works in Nepal?
Dhuri Gateway is payment middleware for WHMCS with eSewa, Khalti, NCHL ConnectIPS, OnePG, Hamro Pay and Stripe built in, behind one WHMCS module.
What does WHMCS need to run Dhuri Gateway?
WHMCS 8 or later, PHP 7.4 or later with curl, and HTTPS reachable from the internet.
Can I self-host the gateway?
Yes. Dhuri Gateway is built to run on your own server as well as hosted.
Keep reading
Tell us what you are building.
Sign-in, payments or point of sale: one message to a real person.