WcPay is the high risk payment gateway for WHMCS that lets your clients pay their invoices by
card, Apple Pay, Google Pay or Revolut — while you receive instant USDT payouts,
with zero chargebacks and no merchant account to lose.
25 independent gateways, each with its own payout wallet
Invoices marked Paid automatically on confirmation
No LLC, no KYC, no underwriting file, no rolling reserve
Zero chargebacks — stablecoin settlements are final
One key unlocks the whole high risk payment gateway for WHMCS suite
Licences from $79.99Lifetime option availableSetup support included
A high risk payment gateway for WHMCS is what keeps a hosting, VPN, IPTV or
reseller business collecting money after Stripe, PayPal or a traditional acquirer has closed the
account. If you bill through WHMCS, you already know the pattern: the platform automates
everything — invoices, reminders, suspensions, renewals — and then the one part it
cannot automate, getting paid, is the part that breaks.
WcPay approaches it from the other side. Instead of asking a bank to underwrite your business,
this high risk payment gateway for WHMCS converts each card payment into a stablecoin transfer that lands directly in a wallet you control,
then tells WHMCS the invoice is paid. No merchant account exists, so there is nothing to freeze.
This page explains exactly how the high risk payment gateway for WHMCS works, what is inside the
module, how to install it, and what it costs.
The problem
Why WHMCS businesses need a high risk payment gateway for WHMCS
WHMCS is the billing and
automation backbone of the hosting industry. It provisions accounts, issues recurring invoices,
sends reminders, suspends overdue services and terminates them on schedule. Almost every
independent hosting reseller, VPN operator, IPTV panel and domain shop runs on it.
That is precisely the customer profile acquiring banks dislike, and it is why a dedicated high
risk payment gateway for WHMCS exists at all. Hosting is a digital, instantly
delivered, subscription product sold worldwide, often by a sole trader in a country the bank has
never underwritten. Those four attributes together put a merchant near the top of every internal
risk list, before anyone has looked at a single transaction.
What the high risk payment gateway for WHMCS has to fix
The account closes mid-cycle. You wake up to an email, your gateway is gone, and
WHMCS keeps generating invoices nobody can pay. Meanwhile your own upstream bills — servers,
bandwidth, licences — are due on their usual date.
The reserve outlives the relationship. A 5 to 10 % rolling reserve held for
six months is normal in high-risk acquiring. On a business running on thin reseller margins, that
reserve is often the entire profit.
Disputes are structural, not occasional. A customer who used a month of hosting
and disputes the charge still received the product. You lose the revenue, the dispute fee, and a
point on the ratio that decides whether the account survives. A high risk payment gateway for
WHMCS that settles irreversibly removes that entire category of loss.
Settlement is slower than your obligations. Seven to fourteen days is common.
For a reseller who must renew upstream services the same week a client pays, that gap is the
difference between operating and scrambling.
The product
What is the WcPay high risk payment gateway for WHMCS?
The WcPay high risk payment gateway for WHMCS is a native gateway module, delivered as a set of files you drop into
modules/gateways. It is the same Card2Crypto engine behind the
WcPay gateway for WooCommerce and the
OpenCart edition, rebuilt
against WHMCS conventions — gateway functions, the callback directory, the local API and
the Gateway Log.
After upload, 25 separate gateways appear under
Configuration › System Settings › Payment Gateways.
Each behaves like any built-in WHMCS gateway: activate it, name it, give it a description and a
payout wallet, and it shows up on the invoice payment page. Each one is fully independent, so you
can offer two methods or twenty-five.
When a client opens an invoice and chooses one, the module converts the invoice total to its
stablecoin equivalent, creates a single-use receiving address for that invoice, and sends the
client to a clean hosted card form. The moment the payment settles, your wallet is credited, the
confirmation comes back to your installation, WHMCS records the transaction ID and marks the
invoice Paid — which releases whatever automation you have attached to that
event.
One key for the whole high risk payment gateway for WHMCS suite
Every licence ships with an activation key tied to your WHMCS domain. You paste it once, into any
one of the 25 gateways, and all 25 unlock together. Until a valid key is accepted, the payment
settings stay hidden and no payment can be started — so a licence never silently lapses into
a half-working checkout.
What's included
25 payment methods in one high risk payment gateway for WHMCS
Every method below is a separate WHMCS gateway with its own display name, description and payout
wallet. Activate the ones that fit your customer base and leave the rest switched off.
RevolutCards · Global
StripeCards · Global
PayPalWallet
Ramp NetworkCards · SEPA
MoonPayCards · Apple Pay
TransakCards · 60+ countries
BanxaCards · Bank transfer
UTORGCards · EU
TransFiLocal rails
SardineCards · ACH
TopperCards · Apple Pay
BitnovoCards · Vouchers
RobinhoodWallet · USA
UPI / IMPSIndia
InteracCanada
SimplexCards · Global
Binance PayWallet
Coinbase PayWallet · Cards
Blockchain.comWallet
Cash AppUSA
KlarnaBuy now, pay later
iDEALNetherlands
Alchemy PayCards · Asia
Particle NetworkWallet
MeldMulti-provider
Coverage inside the high risk payment gateway for WHMCS depends on the client's country and each provider's own reach. Running several methods
side by side is the simplest way to lift approval rates on an international client base.
The flow
How the high risk payment gateway for WHMCS settles an invoice
Four steps, from the moment your client clicks Pay Now on an invoice to the moment WHMCS marks it
as paid and your automation fires.
Invoice conversion
The 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.
Single-use receiving address
A receiving address is generated for that one invoice and stored against it with a short
confirmation token. Because the address is never reused, two clients paying identical amounts
in the same minute can never be mistaken for one another — a real risk on a busy billing
system with many equal-priced plans.
The client pays by card
The client lands on a minimal card form: name, card number, expiry, CVC, email for the
receipt. No account creation, no wallet app, no crypto knowledge. Most clients never realise a
stablecoin was involved; they simply paid an invoice with their card.
Confirmation and automation
As soon as the payment settles, the provider calls back to your installation. The high risk
payment gateway for WHMCS compares what arrived against what was expected, credits your wallet, writes the transaction
ID into WHMCS and marks the invoice Paid. Everything WHMCS attaches to that event —
unsuspension, provisioning, welcome email, renewal — runs as usual.
Inside the module
What you get with the WcPay high risk payment gateway for WHMCS
Nine capabilities that separate a real high risk payment gateway for WHMCS from a redirect link
pasted into an invoice.
⚡
Instant payouts
Funds reach your wallet minutes after the card clears. No settlement cycle, no rolling reserve, no minimum payout threshold.
🔒
Zero chargebacks
Stablecoin settlements are final. A dispute raised at card level cannot pull money back out of the wallet you control.
🌐
Per-gateway wallets
Each of the 25 gateways stores its own payout address — useful for separating brands, partners or accounting streams.
⚙
Native WHMCS automation
Invoices are marked Paid through the WHMCS API, so unsuspension, provisioning and renewal emails fire exactly as they normally do.
🛡
Underpayment protection
The confirmation compares what arrived against what was expected and flags short payments instead of marking the invoice paid.
📝
Full Gateway Log
Every confirmation, success or failure, is written to the WHMCS Gateway Log with the amounts and transaction reference.
🔑
One-key activation
A single licence key, bound to your domain, unlocks all 25 gateways at once and revalidates itself in the background.
🔢
Multi-currency ready
Works with every currency configured in WHMCS. The client sees their own, you always receive the stablecoin equivalent.
📄
Payment reference on file
The reference for each attempt is written to the invoice, so reconciling a payment with a client never turns into guesswork.
Setup
Installing the high risk payment gateway for WHMCS in 6 steps
Setting up the high risk payment gateway for WHMCS takes a few minutes and needs nothing more
than FTP access and your WHMCS admin login. No template edits, no cron changes, no developer.
Upload, activate, paste your key and take a first payment — start to finish.
Upload the files
Unzip the package and upload the modules folder into your WHMCS root over FTP,
keeping the structure intact. Nothing outside modules/gateways is touched, so the
upload is safe on a live billing system.
Open the gateway list
In the admin area go to Configuration › System Settings › Payment
Gateways and open the All Payment Gateways tab. The 25 WcPay entries are listed
there, each with its own name.
Activate the ones you want
Click a gateway to activate it. It moves to the Manage Existing Gateways tab, where
its settings appear. Start with two or three; you can add more at any time without touching
the files again.
Paste your activation key
The activation card sits at the top of the settings. Paste the key you received by email and
press Activate WCPAY. All 25 gateways unlock at the same moment, and the payment
settings appear underneath. Until then they stay hidden.
Enter your payout wallet
Paste your stablecoin address into Payout Wallet Address. Each gateway can use a
different one, or they can all share a single address — whichever suits your accounting.
Test with a real invoice
Create a small invoice for a test client, open it in the client area, pay it with a real card
and confirm three things: the wallet is credited, the invoice flips to Paid, and the
transaction reference appears in the Gateway Log. Then you are live.
The gateway settings screen
This is what your admin sees. Before activation the payment settings are simply not there.
Press Activate WCPAY below to see what appears once a valid key is accepted.
WcPay — Revolut
Configuration › System Settings › Payment Gateways
🔒Not activated — enter a valid license key from wcpay.us to activate.
A valid key activates all 25 WcPay gateways, an invalid one blocks them all.
✓ WcPay activated successfully. All 25 gateways are now unlocked.
Interactive demo of the real admin screen. Each of the 25 gateways has its own copy of this
panel, so nothing is shared between them except the licence.
Eligibility
What you need to run this high risk payment gateway for WHMCS
The list is deliberately short. If you have a WHMCS install and a wallet, you qualify.
A wallet address
Any self-custody or exchange address on the supported network — MetaMask, Trust Wallet, Binance, Bybit or similar.
A WHMCS install
A licensed WHMCS 8.x installation on HTTPS, with outgoing requests allowed from the server.
No company
No LLC, no LTD, no trade register extract. Sole traders and individuals are fully accepted.
No KYC
No identity documents, no proof of address, no bank statements, no underwriting file to defend.
One technical detail worth checking before buying the high risk payment gateway for WHMCS: your
billing domain should be reasonably short. The
payment API limits the length of the confirmation URL it accepts, and the module already uses the
shortest possible path to stay well inside it. If your WHMCS runs on an unusually long domain,
send it to us and we will verify it before you buy.
Use cases
Which businesses run the high risk payment gateway for WHMCS
Card networks maintain internal lists of merchant categories they treat as elevated risk, driven by
dispute rates, regulatory exposure and reputational concern. Being on that list does not make a
business illegitimate — it makes it unbankable through conventional rails. WHMCS is full of
exactly those businesses, and they are the ones the high risk payment gateway for WHMCS was
built for.
Hosting and reseller panels
Shared hosting, reseller accounts, VPS, dedicated servers and offshore or privacy-focused hosting.
IPTV and streaming panels
Subscription reselling, restream panels, credit top-ups and lifetime access plans billed on renewal.
VPN and privacy services
Monthly and annual VPN plans, proxy pools and residential IP packages sold internationally.
Domains and SSL resale
Domain registration, transfers, SSL certificates and the small recurring add-ons around them.
SaaS and licence sales
Software licences, panel access, API credits, white-label tools and developer subscriptions.
Digital agencies
Retainers, maintenance plans and project invoices billed to clients spread across many countries.
Not every product qualifies, and a small number of categories are excluded outright for legal
reasons. If you are unsure whether yours fits the high risk payment gateway for WHMCS, check our
supported countries and regions
page or simply ask before buying — we would rather tell you no in advance than sell you a
licence you cannot use.
Comparison
High risk payment gateway for WHMCS vs traditional processors
The differences that matter are not the headline rate. They are who can switch you off, how long
your money is held, and what happens when a client disputes a renewal.
Criteria
WcPay for WHMCS
Stripe / PayPal
High-risk acquirer
Company registration
Not required
Required
Required
KYC on the seller
None
Full
Full + financials
Approval time
Immediate
Days
2–6 weeks
Payout speed
Minutes
2–7 days
7–14 days
Rolling reserve
None
Possible
5–10 % for 6 months
Chargeback exposure
None
Full
Full + fees
Account termination risk
No account to terminate
High
Medium
Hosting, IPTV, VPN accepted
Yes
Often refused
Case by case
Payment methods included
25
Varies
Cards only
Automatic recurring charge
No — client pays each invoice
Yes
Yes
Settlement currency
Stablecoin
Fiat
Fiat
Two honest trade-offs, stated plainly. The high risk payment gateway for WHMCS settles in
stablecoin, not into an IBAN. And because no
card is stored, WHMCS cannot auto-charge a renewal — it emails the invoice and the client pays
it, exactly as with bank transfer or any other manual gateway. If unattended recurring billing is
non-negotiable for you, a conventional acquirer remains the right tool, assuming one will take you.
Pricing
Choose your plan for the high risk payment gateway for WHMCS
One licence covers the whole high risk payment gateway for WHMCS and all 25 payment methods. No per-transaction plugin fee, no revenue share, no
percentage taken on your sales — an API partner fee of approximately 4.5 % applies at
the provider level.
Monthly
For trying WcPay on a live billing system before committing.
Security behind the high risk payment gateway for WHMCS
The high risk payment gateway for WHMCS never lets card data touch your billing server. The card form is hosted on the payment provider's
PCI-compliant infrastructure, which keeps your WHMCS installation out of scope for card data
handling — and means a compromise of your hosting cannot expose client card numbers.
Confirmations that cannot be forged
Every invoice is issued a single-use confirmation token when its receiving address is created. The
provider's callback must present that exact token, which identifies the invoice and authenticates
the request at the same time. A confirmation without a valid token is rejected outright, and a
token that has already been processed is acknowledged without paying the invoice twice —
important on a billing system where a duplicate payment creates a credit balance to untangle.
Amount verification on every payment
The expected stablecoin value is recorded against the invoice when payment starts. When the
confirmation arrives, the amount actually received is compared against that figure. Anything
meaningfully below it 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.
Everything is logged
Successful and failed confirmations both land in the WHMCS Gateway Log with the amounts, the
provider and the transaction reference. Settlement runs on
Polygon, chosen for low
transfer costs and fast finality, and the reference is written to the invoice so you can match a
payment to a client without leaving the admin area. For anything else,
the WHMCS documentation
covers how gateway logs and transactions are stored.
Questions
FAQ — high risk payment gateway for WHMCS
Which WHMCS versions are supported?
The high risk payment gateway for WHMCS targets WHMCS 8.x, which covers every currently supported release. It uses only documented gateway functions and the local API, so it survives minor updates without changes. You can see your version at the bottom of the admin dashboard.
Does it charge renewals automatically?
No, and this is the one limitation worth understanding before you buy. No card is stored, so WHMCS cannot auto-charge a renewal. It generates the invoice and emails it as usual, and the client pays it — exactly like bank transfer or any other manual gateway. In practice most high-risk sellers already operate this way, because stored-card billing is what their acquirer took away in the first place.
What payment methods can my clients actually use?
The high risk payment gateway for WHMCS covers Visa and Mastercard, Apple Pay, Google Pay, Revolut, PayPal, Klarna, Cash App, Binance Pay, Coinbase Pay, iDEAL for the Netherlands, UPI for India, Interac for Canada, and thirteen more providers — 25 in total, each enabled independently.
How fast do I receive my money?
Within minutes of the client's payment clearing. The high risk payment gateway for WHMCS has no settlement cycle, no minimum payout amount and no rolling reserve. Funds go straight to the wallet address you entered in the gateway settings.
Are there holds, limits or bans?
No volume caps, no holds and no account suspensions are applied by WcPay. Because there is no merchant account in the conventional sense, there is nothing to freeze. Individual providers may apply their own minimum transaction amounts.
Do I need a company or a KYC file?
Neither. No LLC, no LTD, no trade register extract, no identity documents and no proof of address. Individuals and sole traders are accepted on exactly the same terms as registered companies — that is the core reason this gateway exists.
What do I receive after purchase?
The high risk payment gateway for WHMCS module files, an activation key bound to your billing domain, and a step-by-step installation guide. Delivery is by email, normally within minutes of payment confirmation.
Does one key activate all 25 gateways?
Yes. Paste it into any single gateway and all 25 unlock together. The key revalidates itself in the background, and a temporary network problem will not take your invoices offline. Enter an invalid key and all 25 lock again — the check is always live.
Can I use a different wallet for each payment method?
Yes, and it is one of the main advantages of the architecture. Every gateway stores its own payout address, so you can separate revenue by brand, by partner, by country or by accounting stream without running multiple WHMCS installations.
What happens if a client underpays?
The confirmation handler compares the amount received against the amount expected for that invoice. If it falls meaningfully short, the invoice is left unpaid and the attempt is recorded in the Gateway Log with its transaction reference, so you can investigate rather than provisioning against an incomplete payment.
Will the plugin take a cut of my transactions?
No. The licence fee is the only cost we charge — no revenue share and no per-invoice plugin fee. An API partner fee of approximately 4.5 % is applied by the payment infrastructure itself; see the processing fees page for the current breakdown.
Is WcPay the best high risk payment gateway for WHMCS?
We built it for exactly this use case, so our answer is not neutral. What we can point to is concrete: 25 independent gateways rather than one, per-gateway payout wallets, invoices marked paid through the WHMCS API so your automation keeps working, underpayment protection, a full Gateway Log, and settlement no risk department can reverse. If another option gives you more than that for high-risk WHMCS billing, take it — and tell us, because we would like to know.
Start billing again with the high risk payment gateway for WHMCS
Upload the module, paste your wallet address and let your clients pay their next invoice by card
— no company, no KYC, no waiting on an underwriter who was going to say no anyway.
