Skip to content
Modules & integrations Verified service · 5.0 rating

WHMCS Payment Gateway Integration

Gateway modules for processors WHMCS lacks: redirect or tokenized payments, verified callbacks, refunds and currencies.

Fixed-price quote in 24h 14-day correction guarantee 1 year free support

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

QuestionThird-party (redirect)Merchant (tokenized)
How customers paySent to the processor's hosted page, then returned to WHMCSCard or account saved as a token and charged without leaving WHMCS
Recurring invoicesCustomer pays each invoice, unless the processor runs subscriptionsCharged automatically when WHMCS processes due invoices
Main WHMCS functions_link plus a callback file_capture, _storeremote and _refund
Card data on your serverNoneTokens 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

ScopePrice
Redirect gateway with a verified callbackFrom $200
Redirect gateway with refunds, fee recording and several currenciesFixed quote within the range
Tokenized gateway with stored payment methods and refundsUp 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.

What's included

Every WHMCS Payment Gateway Integration engagement ships with these.

  • Check for an existing maintained module before any build
  • Redirect (third-party) or tokenized (merchant) gateway module
  • Callback file with signature or API verification
  • Duplicate callback protection with checkCbTransID
  • Pending, failed, canceled and partial payment handling
  • Processor fees recorded on each transaction
  • Refunds from the WHMCS admin area where supported
  • Currency conversion through Convert To For Processing
  • Full sandbox test plan plus one supervised live payment
  • Request and callback logging in the Gateway Log

Business outcomes

What hosting operators report after delivery.

  • Customers can pay with the method they already use locally
  • Invoices are marked paid only after the processor confirms the payment
  • Repeated notifications cannot create duplicate payments
  • Card data stays off your server whenever the processor allows it
  • Recurring revenue can be charged automatically with tokenized gateways

Ready to talk about WHMCS Payment Gateway Integration?

Quick scoping call, fixed-price quote within 24 hours, no commitment.

Related services

Other WHMCS work hosting operators ask us about.