WHMCS payment gateway module for high-risk billing: 25 methods, instant payouts, no KYC
This is the WcPay WHMCS payment gateway module: twenty-five payment
gateways you drop into modules/gateways, which take card payments on your
client invoices and settle in stablecoin to a wallet you control. Invoices mark themselves
Paid through the WHMCS API, so unsuspension, provisioning and renewal emails fire exactly
as they always have. No merchant account, no underwriting file, no chargebacks.
Billing systems fail differently from shops. A storefront loses one sale when a payment
breaks; a WHMCS installation loses a recurring customer, a provisioned service and the
renewal behind it. That is the problem this WHMCS payment gateway module is built around:
keeping the automation intact while removing the processor that can switch you off.
Your client pays by Visa, Mastercard, Apple Pay, Google Pay, Revolut, Cash
App, Klarna, iDEAL, UPI or Interac, in whichever currency their invoice is in. You receive
the payout minutes later. Most clients never realise a stablecoin was involved.
Why hosting and service businesses lose their processor
WHMCS runs the billing for a very particular slice of the internet: hosting resellers,
IPTV panels, VPN providers, domain and SSL resale, SaaS licences, agency retainers. Several
of those sit on an acquirer’s internal watchlist regardless of how the business is run.
Recurring billing makes it worse, not better. Every renewal is another card
authorisation, another opportunity for a dispute, and a dispute ratio that is measured
against a denominator you cannot grow quickly. A hosting reseller with four hundred clients
and eleven disputes in a quarter is a statistic before it is a business.
And the consequences land harder than on a shop. When an account is frozen mid-month,
your invoices stop clearing, suspensions start firing on clients who did try to pay, and
your support queue fills with people who think you took their money. The processor’s
decision becomes your outage.
What the WHMCS payment gateway module changes
There is no account to freeze. Settlement goes to a wallet you hold the
keys to. No risk committee reviews it, no reserve is withheld, and no email arrives at
eleven at night announcing a termination.
Renewals stop being a dispute surface. A settled stablecoin transfer
has no reversal mechanism at the issuing bank. The client’s card decision, whatever it is,
does not reach funds that already arrived.
Cash arrives when the invoice clears. Not on a seven-day cycle, not
after a reserve is released. For a business paying upstream datacentre invoices monthly,
that timing is the whole difference.
What the WHMCS payment gateway module installs
The WHMCS payment gateway module lists twenty-five gateways natively
After the upload, Configuration › System Settings › Payment Gateways
› All Payment Gateways lists twenty-five WcPay entries, each under its own name.
Activate the ones you want and they move to Manage Existing Gateways, exactly like any
other WHMCS gateway. Nothing about the admin workflow is unusual — that is deliberate.
Each gateway in the WHMCS payment gateway module is configured on its own and shares
nothing with the others:
| Per gateway | What it controls |
|---|---|
| Display name | What the client reads on the invoice payment list. |
| Payout wallet address | Where this gateway’s settlements land. Each gateway can use a different address, or they can all share one — whichever suits your accounting. |
| Activation state | Which methods appear to clients at all. |
Per-gateway wallets matter more on a billing system than on a shop, and they are the
reason agencies pick this WHMCS payment gateway module over a single-method one. A reseller splitting
revenue with an upstream provider, an agency separating retainers from project work, a
white-label operator keeping two brands apart — all of that becomes a configuration choice
rather than a spreadsheet exercise.
The WHMCS payment gateway module has nothing to half-configure
Before activation, the payment settings of the WHMCS payment gateway module are simply
not rendered. You see one activation card and a licence field. Paste the key you received
by email, press Activate, and all twenty-five gateways unlock at the same moment with their
settings appearing underneath.
A valid key activates the whole suite; an invalid one blocks all of it. There is no
state in which some gateways work and others silently do not, and no way to leave a gateway
enabled with an empty wallet. The key revalidates itself in the background, so a brief
network problem on your host never takes your invoices offline.
How the WHMCS payment gateway module settles an invoice
1. Invoice conversion
The WHMCS payment gateway module reads the invoice balance in the client’s own currency — euro, pound, dirham,
rupee, whatever you have configured in WHMCS — and converts it to its stablecoin equivalent
at a live rate. Nothing is estimated locally, so the figure the provider receives always
matches the invoice.
2. A single-use receiving address
An address is generated for that one invoice and stored against it with a short
confirmation token. Addresses are never recycled. On a billing system that is not a
theoretical nicety: when forty clients are on the same $12 plan, identical amounts arriving
in the same minute are routine, and a reused address would make them indistinguishable.
3. The client pays by card
From the client area, the invoice opens a clean hosted form: name, card number, expiry,
security code. No account creation, no wallet, no crypto knowledge. Card details are typed
on the provider’s own PCI-compliant infrastructure, so your WHMCS installation never
handles a card number.
4. Confirmation, and everything WHMCS does next
When the payment settles, the provider calls back. The WHMCS payment gateway module
compares what arrived against what was expected, writes the transaction ID into WHMCS, and
marks the invoice Paid through the WHMCS API rather than by touching the database.
That distinction is the whole point: unsuspension, provisioning, the welcome email, the
renewal cycle and every hook you have attached to a paid invoice all fire exactly as they
normally do.
A gateway that marks invoices paid by any other route leaves you with a Paid invoice and
a suspended service. The WHMCS payment gateway module does not.
What the WHMCS payment gateway module protects you from
Underpayment on a renewal
Rates move between the moment a client clicks and the moment funds settle, which is why
the WHMCS payment gateway module never compares on strict equality. and the
provider’s fee is taken on the way through. Strict equality would reject honest payments; no check at all would mark renewals paid for
a fraction of their value. The WHMCS payment gateway module compares against what was recorded when payment started, writes short payments to the
Gateway Log, and leaves the invoice unpaid — so a client cannot pay a tenth of a renewal
and keep the service running.
The duplicate confirmation
Providers sometimes send the same confirmation twice. On a shop that means a second
shipment; on WHMCS it means a credit balance on the client’s account that somebody has to
notice and untangle, usually a month later. A token that has already been processed is
acknowledged and ignored, and the invoice is never paid twice.
The payment nobody can trace
The WHMCS payment gateway module writes every attempt’s reference to the invoice, and
every confirmation — successful
or failed — lands in the WHMCS Gateway Log with the amounts, the provider and the
transaction reference. When a client insists they paid, you answer from the admin area in
thirty seconds instead of opening a wallet explorer.
The payment methods your client sees
The WHMCS payment gateway module ships with twenty-five methods, in three families.
Activate two, or activate all of them.
| Family | Methods |
|---|---|
| Cards and wallets | Credit card through Stripe, credit card through PayPal, Apple Pay, Google Pay, Revolut Pay, Cash App, Binance Pay |
| Local rails | iDEAL (Netherlands), UPI and IMPS (India), Interac (Canada), Klarna (parts of Europe) |
| On-ramps | Coinbase Pay, Blockchain.com, Ramp Network, MoonPay, Transak, Banxa, Topper, Bitnovo, Robinhood, Simplex, Sardine, UTORG, TransFi, Meld, Particle Network, Alchemy Pay |
Each provider in the WHMCS payment gateway module has its own country coverage and its
own minimum, from around two dollars
up to a hundred. Keeping several active is the practical defence: when one rail pauses a
country without notice, your renewals keep clearing through the others. Twenty-five
independent gateways fail independently.
Multi-currency works the way WHMCS expects. Every currency you have configured is
supported; the client sees their own, and you always receive the stablecoin equivalent.
Installing the WHMCS payment gateway module in six steps
Installing the WHMCS payment gateway module takes a few minutes and needs nothing more
than FTP access and your admin login. No template edits, no cron changes, no developer.
- Buy the licence and download the package. You receive the files and
your activation key by email. - Upload the files. Unzip and upload the
modulesfolder
into your WHMCS root over FTP, keeping the structure intact. Nothing outside
modules/gatewaysis touched, which is what makes the upload safe on a live
billing system — no core file, no template, no cron. - Open the gateway list. Configuration › System Settings
› Payment Gateways › All Payment Gateways. The twenty-five WcPay entries
are listed there. - Activate the ones you want. Click a gateway and it moves to Manage
Existing Gateways. - Paste your activation key. The activation card sits at the top of
the settings. All twenty-five unlock at once and the payment settings appear
underneath. Then paste your payout address into Payout Wallet Address. - Test with a real invoice. Create a small invoice for a test client,
open it in the client area and pay it with a real card.
On that last step, confirm three things before you call it live: the wallet was
credited, the invoice flipped to Paid, and the transaction reference appears in the Gateway
Log. Three checks, five minutes, and you find out now rather than on a real client’s
renewal.
What it touches, and what it leaves alone
A billing system is no place for a module that rewrites core files. The WHMCS payment gateway module lives entirely in modules/gateways and talks to WHMCS through its own API. Your
templates, your cron, your other gateways, your automation settings, your client accounts
and your invoice statuses are untouched.
That matters at upgrade time. A WHMCS payment gateway module that patches core breaks on
the next release, usually at the worst moment — WHMCS upgrades are rarely done on a quiet
afternoon. This one carries no core patches to break.
It also matters on the day you install the WHMCS payment gateway module. The upload adds files; it changes nothing
that is already running, so a live installation taking payments keeps taking them while you
work. If you want to read what the platform guarantees about gateway modules and the
Gateway Log, the
WHMCS documentation
covers both.
Requirements for the WHMCS payment gateway module
| You need | You do not need |
|---|---|
| A licensed WHMCS 8.x installation on HTTPS Outgoing HTTPS requests allowed from the server FTP or file-manager access A wallet address you control |
A company — no LLC, no LTD, no trade register extract A KYC file — no ID, no proof of address, no bank statements A merchant account application Any crypto knowledge |
The WHMCS payment gateway module accepts any self-custody or exchange address on the
supported network — MetaMask, Trust
Wallet, Binance, Bybit or similar. One address is enough to begin; give each gateway its
own later, once you know which rails your clients actually use.
Which businesses run this WHMCS payment gateway module
These are the categories that bring people to a WHMCS payment gateway module in the
first place — not because the businesses are dubious, but because recurring billing in
these sectors is where acquirers draw their line.
- Hosting and reseller panels — shared hosting, VPS, cPanel and
DirectAdmin resale, white-label plans. - IPTV and streaming panels — subscription reselling and panel
access billed monthly. - VPN and privacy services — monthly and annual plans, proxy pools,
residential IP packages sold internationally. - Domains and SSL resale — registrations, transfers, certificates
and the small recurring add-ons around them. - SaaS and licence sales — software licences, panel access, API
credits, white-label tools, developer subscriptions. - Digital agencies — retainers, maintenance plans and project
invoices billed to clients spread across many countries.
A short list of categories is refused outright, for legal rather than commercial
reasons, and rail coverage varies by country. The
supported countries and
regions page has the detail; if your case sits near the edge, write to us first. A no
before you pay is worth more to both of us than a refund afterwards.
Licence plans for the WHMCS payment gateway module
One licence covers all twenty-five gateways. There is no per-transaction module fee and
no revenue share; an API partner fee of roughly 4.5 % applies at the provider level,
and the current breakdown is on the
processing fees page.
| Plan | Price | Installations | Best for |
|---|---|---|---|
| Monthly | $79.99 / month | 1 WHMCS installation | Running the rails against real renewals before committing. |
| Annual | $169.99 / year | 1 WHMCS installation | An established billing operation. Cheaper than three months of the monthly plan. |
| Lifetime | $399.99 one-time | 3 installations | Several brands or installations, and anyone done with renewals of their own. |
The plans differ only in duration and in how many installations they cover. All
twenty-five gateways, instant settlement, zero chargebacks, Apple Pay and
Google Pay, Revolut Pay and setup support are in every plan — nothing is held
back for a higher tier. The payment and refund
policy applies to all three.
If you also sell through a storefront, those platforms have their own modules: the
WooCommerce edition,
PrestaShop and
OpenCart. Licences
are per platform; write to us for a multi-platform
bundle rather than buying them separately. For a custom panel with no WHMCS at all, the
integration kit is the same
engine as PHP and Node.js source.
Security: what never reaches your installation
Ask what an attacker would find if they got into your WHMCS hosting tomorrow. With this
WHMCS payment gateway module installed, the answer does not include a single card
number.
No card data exists on your server to steal. The form where the number,
expiry and security code are typed belongs to the payment provider and runs on their
PCI-compliant infrastructure. Those values never post to your installation and never land
in a log file, which keeps your billing system out of scope for card data handling. That
same redirect model is what puts a merchant in the shortest self-assessment questionnaire,
PCI DSS SAQ A. Which one really applies to
you is your acquirer’s call, not ours.
A stranger cannot mark your invoices paid. Each invoice gets a token
nobody else holds, generated with its receiving address. The callback has to carry that
exact token: it is how the WHMCS payment gateway module recognises the invoice and how it knows the request is
legitimate at the same time. Anything without it is dropped before an invoice status
changes.
Nothing happens unlogged. Successful and failed confirmations both land
in the Gateway Log with amounts, provider and reference. A misconfiguration shows up as a
readable line rather than as a quiet run of unpaid invoices.
Settlement runs on
Polygon, chosen
for low transfer cost and fast finality, so a $9 renewal is not eaten by network fees.
What this WHMCS payment gateway module does not do
A product page that only lists strengths is not worth trusting.
Your money lands in a wallet, not in an IBAN. If your upstream
suppliers must be paid from a bank account that receives card settlements directly, a
conventional acquirer is the right tool — supposing you can get one.
The Refund button will not move the funds. Irreversibility runs both
ways: nobody can pull a settled payout back out of your wallet, and neither can you.
Refunding means sending a transfer yourself, or applying a credit on the client’s WHMCS
account. Publish that policy in your terms before you open payments.
It does not take recurring payments automatically. This is the honest
limitation that matters most on WHMCS, so it should be stated plainly: there is no stored
card and no automatic capture on renewal. Each invoice is paid by the client when it is
issued. If your business depends on charging a card on file without the client acting, this
module does not do that, and no card-free settlement rail can.
No availability figure is promised. Providers suspend a country or a
vertical from time to time without warning. Running several gateways is the real defence —
but quoting an uptime percentage for infrastructure we do not operate would be
dishonest.
Bookkeeping stays yours. The WHMCS payment gateway module records that
money arrived, against
which invoice, and when. VAT, reconciliation and your accounts are your side of the
line.
Questions asked before purchase
Which WHMCS versions does the payment gateway module support?
WHMCS 8.x, licensed, on HTTPS.
What exactly do I receive when I buy?
The WHMCS payment gateway module files, an activation key bound to your domain, and the installation guide —
by email, usually within minutes.
Does one key activate all twenty-five gateways?
Yes. A valid key unlocks the entire WHMCS payment gateway module at once; an invalid one
blocks all of it. The key revalidates itself in the background.
Do invoices mark themselves Paid automatically?
Yes, through the WHMCS API — which is why unsuspension, provisioning and renewal emails
fire exactly as they do with any other gateway.
Will the WHMCS payment gateway module charge clients automatically on renewal?
No. There is no card on file and no automatic capture. The client pays each invoice when
it is issued. This is the one thing a traditional merchant account does that this does
not.
Can my client pay with an ordinary bank card?
Yes, and that is the normal case. Visa, Mastercard and American Express, in the invoice
currency, on a standard card form.
How fast do I receive the money?
Minutes after the payment clears. No settlement cycle, no minimum payout, no rolling
reserve.
Do I need a company or a KYC file?
Neither. Individuals and sole traders are accepted on exactly the same terms as
registered companies — that is the reason this WHMCS payment gateway module exists.
Can I use a different wallet for each gateway?
Yes, or one address for all twenty-five. Separate wallets are how resellers split
revenue with an upstream provider without a spreadsheet.
Is the WHMCS payment gateway module safe to upload on a live billing system?
Yes. Nothing outside modules/gateways is touched — no core file, no
template, no cron — so an installation taking payments keeps taking them while you
upload.
What happens if a client underpays an invoice?
The shortfall is written to the Gateway Log and the invoice is left unpaid, so a client
cannot pay a fraction of a renewal and keep the service running.
What happens if the same confirmation arrives twice?
The second is acknowledged and ignored. The invoice is never paid twice, so you never
have to untangle a credit balance a month later.
Can I try it before buying?
There is no trial build, because the licence key is what renders the payment settings.
What you can do is read the whole flow on the
WHMCS gateway page,
which shows the real settings screen in both states and the installation video, then ask us
anything still unclear.
Support, updates and what happens next
Setup support for the WHMCS payment gateway module is included on every plan, and updates are free. The WHMCS payment gateway module is versioned, so you can see what changed before you upgrade a
live billing system.
If something is broken, we would rather hear about it than have you work around it. Four
checks resolve most of what reaches us, and you can run them yourself first: does the
Gateway Log show the confirmation arriving, is the payout address the one you intended, is
the installation on HTTPS, and did the invoice ever change status.
If you are weighing this WHMCS payment gateway module against a conventional acquirer,
or you are not sure which plan fits, ask us before you
buy — a pre-sales question costs you nothing and saves a refund request.
Reviews
There are no reviews yet.