WHMCS payment gateway integration means building, or installing and configuring, a gateway module so customers can pay invoices through a processor that WHMCS does not support out of the box. Hosting and IPTV businesses need it when they sell in regions where Stripe and PayPal are unavailable or expensive, or where buyers expect a local wallet, bank payment network or crypto. Projects are fixed price from $200 to $500.
First question: does a module already exist?
Many processors publish their own WHMCS module, and WHMCS bundles a number of gateways. Before quoting a build, we check whether a maintained module exists for your processor and your WHMCS version. If one does, installing and configuring it costs less than writing a new one, and we will tell you so. Our own ready-made options, including NOWPayments for crypto, Square, Clover and CashApp, are listed with our payment gateway modules.
Where this usually applies
Typical candidates are regional card and wallet processors such as Razorpay, Paystack, Flutterwave, Mercado Pago, iyzico or Xendit, local bank payment networks, mobile money services and crypto processors. Several of those publish their own WHMCS modules, which is exactly why the existence check comes first. Where a vendor module exists but is outdated or fails on PHP 8.1, fixing or replacing it is also in scope.
Two kinds of WHMCS gateway
| Question | Third-party (redirect) | Merchant (tokenized) |
|---|---|---|
| How customers pay | Sent to the processor's hosted page, then returned to WHMCS | Card or account saved as a token and charged without leaving WHMCS |
| Recurring invoices | Customer pays each invoice, unless the processor runs subscriptions | Charged automatically when WHMCS processes due invoices |
| Main WHMCS functions | _link plus a callback file | _capture, _storeremote and _refund |
| Card data on your server | None | Tokens only, when the processor offers hosted fields |
Which type you get depends on what the processor's API allows. For recurring hosting revenue, tokenized payments are preferable, because renewals do not wait for the customer to click a link.
What the module handles
- Payment creation carrying the invoice ID, amount and currency
- A callback in /modules/gateways/callback/ that verifies the signature, or queries the processor, before marking anything paid
- Duplicate protection with checkCbTransID, so a repeated notification never records a second payment
- Correct treatment of pending, failed, canceled and partially paid states
- Processor fees recorded against each transaction
- Refunds issued from the WHMCS admin area, where the API supports them
- The Convert To For Processing setting for processors that accept only one currency
- Every request and callback written to the Gateway Log
How we test it
All testing starts in the processor's sandbox: a successful payment, a declined payment, an abandoned checkout, the same callback delivered twice, a callback with a tampered amount, a refund, and an invoice in a second currency. Once those pass, we make one low-value live payment together with you before the gateway is shown to customers.
Security choices we make for you
Callbacks are never trusted on their word. The module confirms the payment with the processor, by signature or by an API lookup, and checks that the amount and currency match the invoice. Card fields on your own pages widen your PCI DSS scope, so we use the processor's hosted page or hosted fields whenever they exist. API secrets live in the gateway settings, never in the module code.
What you receive
- The gateway module files, as source or encoded according to the quote
- A settings sheet listing each field in the gateway configuration and where its value comes from
- The sandbox test results, so the same cases can be repeated after future WHMCS updates
What we need from you
- An approved merchant account with sandbox and live API keys
- The processor's API documentation
- The currencies you invoice in, and whether refunds should be possible from WHMCS
Merchant approval is between you and the processor. Some processors look closely at hosting or IPTV businesses, so apply early.
Pricing and timeline
| Scope | Price |
|---|---|
| Redirect gateway with a verified callback | From $200 |
| Redirect gateway with refunds, fee recording and several currencies | Fixed quote within the range |
| Tokenized gateway with stored payment methods and refunds | Up to $500 |
A redirect gateway usually takes three to five business days once sandbox keys arrive; tokenized gateways take longer because there are more cases to test. Processor features such as split payments, marketplace payouts or direct debit mandates are quoted separately. If you invoice in several currencies, combine this with multi-currency setup so exchange rates and rounding are right before the gateway sees them. Name your processor on the project form and we will check for an existing module before the call.