Accept Bitcoin and stablecoins on WHMCS
WHMCS bills the hosting industry, and hosting is one of the few businesses where a meaningful share of customers would rather pay in crypto than hand over a card. The BTCPay module puts those payments straight into your own wallet, with no cut taken on the way.
About 15 minutes. No card and no identity check to start.
Setting it up
Create your store
Sign up for OwnRails and create a store. Note the store URL — the WHMCS module asks for it during configuration.
Connect your own wallet
Give us an extended public key for Bitcoin and a TRON address for USDT. Both are watch-only: they let us generate addresses and detect payments, and neither can move funds. A seed phrase is never required and must never be shared, with us or anyone.
Upload the module
Download the BTCPay Server module for WHMCS and extract it so that the gateway files land in the modules directory of your WHMCS installation. It is a normal file upload; no shell access or composer step is involved.
modules/gateways/btcpayActivate it in WHMCS
In your WHMCS admin, open Apps & Integrations, search for BTCPay, and press Activate. That takes you straight to the configuration screen for the gateway.
Generate a legacy API key
In your store dashboard, open Settings → Access Tokens and generate a key under Legacy API Keys. WHMCS uses this older key format rather than the Greenfield key the WooCommerce plugin uses — if you generate the wrong one the module will not connect, and the error will not tell you why.
Invoice yourself once
Create a test invoice against your own client account and pay it for real, with a small amount. Confirm WHMCS marks it paid, and then confirm the money is in your own wallet. The second check is the one that matters: that is where the funds actually are.
Worth knowing before you hit it
- The module uses Legacy API Keys, not Greenfield keys. Generating the newer kind is the single most common reason the connection fails, and the error message does not point at it.
- Your WHMCS installation must be reachable over HTTPS for payment callbacks to arrive.
- If you run WHMCS behind Cloudflare, make sure the callback path is not challenged or rate-limited. A blocked callback leaves invoices unpaid in WHMCS even though the money arrived.
The money never touches us
You connect a wallet you already control. OwnRails receives an extended public key, which can watch for payments but cannot spend them.
No percentage, on any plan
A flat monthly price and nothing else. The only per-transaction cost is the blockchain network fee, which goes to miners, not to us.
No identity checks
KYC is an obligation that comes with holding other people's money. We do not hold any, so we ask for an email address and nothing more.
WHMCS questions
The ones people actually ask before switching.
Can WHMCS charge my clients automatically each month?
No, and nothing can — this is a property of crypto, not of the module. There is no card on file to debit. WHMCS will issue the recurring invoice on schedule and email it; your client chooses to pay it. In practice you lean harder on invoice reminders than you would with cards.
Is this suitable for a hosting business?
It is one of the better fits. Hosting invoices are predictable, clients are technical enough to pay in crypto, and the customers who specifically want a no-KYC host are exactly the ones who want to pay this way. The flat pricing also matters more here: a percentage-based processor takes a cut of every renewal, forever.
What if a client underpays the invoice?
WHMCS will not mark it paid. The invoice shows as partially paid on the BTCPay side and you decide: credit the difference, ask for the remainder, or refund from your own wallet. Exchange withdrawal fees make this common enough to have a policy for.
Which is the right API key?
The Legacy API Key, generated from Settings → Access Tokens in your store. This trips people up because the newer Greenfield keys are more prominent and are what other integrations use. The WHMCS module predates them.
Do you take a percentage of what I invoice?
No. A flat monthly price, whatever you bill. For a host invoicing $20,000 a month, a processor at 1% costs $200 every month; here it is the same flat figure as a host invoicing $200.
Will you freeze my account?
We could suspend your ability to create new invoices, which is the strongest action available to us — and we have never held your money, so there is nothing for us to freeze. Payments already received are in your wallet and stay spendable whatever happens between us.