If you run a hosting company, a VPN service, or any online business built on WHMCS, sooner or later someone asks the same question.
“Do you accept crypto?”
At first it sounds simple. Crypto payments exist. Payment gateways exist. Problem solved.
Except it usually is not.
Most crypto gateways are great at one thing — one-time payments. Someone clicks a button, sends crypto, the payment arrives. Done. But the moment you try to use crypto with a real hosting business — monthly invoices, recurring services, automatic renewals — the whole system starts to feel like duct tape.
The typical “crypto subscription” looks like this: every month the customer gets an invoice and has to manually pay it again. Which means it is not really a subscription — it is just a reminder.
That works for a while, but if you run WHMCS you know how important recurring payments are. Your billing system is literally built around them. That was the starting point for building the WHMCS integration for Zyrox — not another crypto checkout button, but a gateway that actually works with subscriptions.
The problem with crypto payments in WHMCS
Most WHMCS installations support traditional gateways like Stripe, PayPal, or bank cards. Those systems work because they support automatic billing — once a user subscribes, payments continue until they cancel.
Crypto does not work like that. Blockchains do not allow someone to pull money from a wallet the way a credit card processor does. Users must initiate transactions themselves.
So most crypto gateways do something like this:
- Customer receives an invoice every month.
- Customer manually sends crypto.
- WHMCS marks the invoice paid.
Technically it works, but it feels like going back ten years in billing automation. For hosting companies that rely on recurring payments, this is far from ideal.
A different approach to crypto subscriptions
Zyrox handles subscriptions using smart contracts. The customer approves the subscription once. After that, recurring payments execute automatically according to the billing schedule.
In practice the flow looks like this:
- Customer signs up for a service.
- Customer approves the subscription once.
- Payments are executed automatically on schedule.
- WHMCS receives the webhook and marks the invoice as paid.
No monthly manual payments. This makes crypto behave much closer to traditional subscription billing.
At the same time the system remains non-custodial. Funds go directly from the customer wallet to the merchant wallet. Zyrox does not hold funds and does not store private keys — the platform only provides payment infrastructure, monitoring, and integration events. For many hosting companies that matters a lot. It means you stay in control of your funds.
One-time payments still work
Not every service is a subscription. WHMCS also generates invoices for things like:
- Domain registrations
- Setup fees
- Add-ons
- One-time services
Zyrox supports standard crypto payments as well. A payment link is generated, the customer sends crypto, and WHMCS receives a confirmation through webhooks. So the gateway works both ways — subscriptions and normal payments — through the same module.
Installing the WHMCS gateway
The integration is intentionally simple. Download the module, copy the files into your WHMCS installation, enable the gateway, and configure your merchant settings.
The open-source module — with full source code and installation instructions — is on GitLab:
Once enabled, WHMCS will show Zyrox as a payment option on the invoice page, and customers can complete the payment through the Zyrox checkout.
Why hosting companies often want crypto payments
If you spend enough time around hosting communities you notice a pattern. Crypto payments show up most often in businesses that operate globally:
- Hosting companies
- VPN providers
- Developer services
- Infrastructure tools
Customers come from different countries and payment restrictions can vary a lot. Crypto solves a few problems at once:
- International payments become easier.
- Chargebacks disappear.
- Some customers simply prefer paying with crypto.
For small hosting companies it is often not about replacing existing gateways — it is about adding another option that works when traditional methods do not.
Getting started
If you are curious how it works in practice, you can create a Zyrox account and explore the dashboard. The technical documentation covers payment links, webhooks, and integration events. And if you run WHMCS and want to test the integration directly, the open-source gateway is on GitLab:
It is open source and you can install it on your system in a few minutes. If you run a hosting business and have been thinking about accepting crypto payments, this is a good place to experiment. Sometimes the simplest experiments turn into the features your customers appreciate the most.
Frequently asked questions
Does WHMCS support real recurring crypto payments out of the box?
Not really. WHMCS supports recurring billing, but most crypto gateways behind it only handle one-time on-chain transfers. The customer ends up paying every invoice manually, which is technically a subscription but operationally not. To get true automatic recurring crypto charges, the gateway itself needs to use a wallet approval (smart contract) model — that is the gap Zyrox closes for WHMCS.
How does a crypto subscription work without a credit card on file?
The customer approves the subscription once through a smart contract. The approval lets the agreed amount move from their wallet to the merchant wallet on the agreed schedule — daily, monthly, yearly. There is no stored card and no merchant access to the wallet. Each billing cycle, Zyrox executes the payment automatically and sends a webhook to WHMCS so the invoice is marked as paid.
Is Zyrox custodial — does it hold customer funds?
No. Zyrox is non-custodial. Private keys stay with the customer, funds move directly from the customer wallet to the merchant wallet on-chain, and Zyrox never controls either side’s balance. The platform only provides the payment infrastructure, on-chain monitoring, and webhook events WHMCS needs to update invoice status.
Which currencies and networks does the WHMCS integration support?
The gateway supports stablecoin payments (such as USDC and USDT) on the networks Zyrox enables in your merchant account. Stablecoins are used for billing in practice because hosting plans are priced in fiat — paying in volatile assets makes monthly invoices unpredictable for both sides. Network and currency availability can be configured per merchant.
Can the same gateway handle one-time payments (domains, setup fees, upgrades)?
Yes. Recurring subscriptions and one-time invoices use the same module. For a one-time invoice the customer opens it in WHMCS, picks Zyrox as the payment method, completes the on-chain payment via a generated link, and once confirmed the webhook marks the invoice paid. The merchant configures it once and uses the gateway for both flows.
How long does it take to install the WHMCS gateway?
Installation is intentionally short: download the module from the GitLab repository, copy the files into the WHMCS installation directory, and enable Zyrox in the WHMCS payment settings. The module then appears as a payment option on invoices. The full source and step-by-step instructions are at gitlab.com/alentev/zyrox-whmcs-gateway.
Why use crypto subscriptions instead of Stripe or PayPal?
For most hosting businesses crypto is not a replacement — it is an additional channel that works when traditional methods do not. Customers paying internationally avoid card-issuer friction, chargebacks are not possible on confirmed on-chain payments, and some segments simply prefer paying with crypto. Many hosting and VPN providers start it as a small experiment and keep it once a steady share of customers self-selects into it.