If you sell shared hosting, VPS plans, dedicated servers, domains or reseller accounts, you have probably had the ticket: "Can I pay with crypto?" For hosting providers, crypto is not a novelty. It solves specific problems in the business, and it creates a few new ones you should plan for. This guide walks through both, based on how billing systems like WHMCS actually behave.
Why do hosting customers ask to pay in crypto?
Hosting is sold worldwide from a single website. A reseller in Lagos, a developer in Buenos Aires and an agency in Istanbul may all want the same VPS plan, and not all of them have a card your processor will accept. Crypto, and dollar stablecoins in particular, gives those clients a way to pay that works across borders.
There are also privacy-minded customers who would rather not hand card details to every provider they try, and developers who already keep part of their income in crypto. None of this means you should drop cards. It means crypto is a second rail that catches clients the first rail misses.
What problems does crypto solve for a hosting business?
Chargebacks after the service is delivered
Hosting is delivered instantly. A fraudster can pay with a stolen card, get a server provisioned in seconds, use it for abuse and leave you with a chargeback and a dispute fee weeks later. A confirmed blockchain payment cannot be reversed by the sender, so that particular pattern goes away for crypto orders.
Processor risk
Payment providers often put hosting in a higher-risk bucket because of that fraud profile. Reserves, rolling holds and sudden account reviews are common complaints in the industry. A self-hosted gateway has no underwriting team: coins go from the client to your wallet, with nobody in between who can pause payouts.
Fees on recurring revenue
Hosting revenue is small invoices repeated for years. Any percentage fee is paid again on every renewal. With a one-time license, a client who renews monthly for five years costs you the same in gateway fees as one who paid once: nothing per payment. The card side of that math is covered in crypto vs card payment fees.
How do crypto renewals work in WHMCS and other billing systems?
This is the part to understand before you launch. Cards and PayPal subscriptions are pull payments: you store a token and charge it on the due date. Crypto is push: only the client can send coins from their wallet. There is no way to auto-charge a crypto wallet.
In practice the flow looks like this:
- Your billing system generates the renewal invoice on its normal schedule and emails it.
- The client opens the invoice and clicks Pay with Crypto. The module creates a matching invoice on your gateway, server to server, in the invoice currency.
- The client picks a coin and pays. Your gateway confirms the transaction on the blockchain and sends a signed webhook back.
- The module verifies the signature, re-checks the invoice with the gateway, and records the payment with the blockchain transaction hash as the transaction ID. In WHMCS that goes through the normal
addInvoicePayment()path, so automation (unsuspension, renewal, domain registration) runs exactly as it would for any other gateway.
Because nothing is charged automatically, make your reminder emails do more work. Send the first reminder earlier than you would for card clients, include a direct invoice link, and consider a slightly longer grace period before suspension for clients who pay in crypto.
Which billing platforms can take crypto with Payfim?
| Billing system | Payfim module | Compatibility | Price (lifetime) |
|---|---|---|---|
| WHMCS | WHMCS module | WHMCS 7.10 to 8.x | $15 |
| Blesta | Blesta gateway | Blesta 5.x | $15 |
| FOSSBilling | FOSSBilling gateway | FOSSBilling 0.6 to 0.8 | $15 |
| HostBill | HostBill gateway | Current HostBill releases | $19 |
| ClientExec | ClientExec gateway | ClientExec 6.x | $15 |
| Paymenter | Paymenter extension | Paymenter v1.x | $15 |
The All-Access Bundle ($99) covers every module, which is handy if you are migrating between billing systems or run more than one brand. Setup guides for each are in the docs. If you are comparing crypto options specifically for WHMCS, see the best WHMCS crypto payment gateways.
Which coins should a hosting company accept?
Start small. A sensible first set for most hosts is:
- USDT on TRON (TRC20) for clients who think in dollars and want low network fees. See how to accept USDT TRC20.
- Bitcoin, because it is what people ask for by name.
- Litecoin as a fast, low-fee alternative that works without API keys.
Add Ethereum-based coins (ETH, USDT ERC20, USDC) once you have created a free Etherscan API key. Privacy-focused clients, common in VPS and VPN reselling, may ask for Monero; our Monero guide explains the extra setup. The full reasoning is in how to choose which coins to accept.
How should you price hosting plans for crypto?
Keep your plans priced in your billing currency (USD, EUR and so on). The gateway converts at the live rate when the client picks a coin and locks that rate for 30 minutes by default, so the client sees a fixed amount while they pay. You do not need separate crypto price lists.
Payfim also has an optional price adjustment. A negative value, for example −5%, gives a crypto discount that nudges clients toward a rail with no chargebacks and no percentage fee. A positive value adds a buffer if you are worried about volatility between payment and conversion. Most hosts leave it at zero with stablecoins and consider a small discount only if they want to shift annual prepayments to crypto.
What should you watch out for?
- Partial payments. Clients paying from exchanges sometimes send slightly less because of withdrawal fees. Payfim marks those invoices Underpaid and never applies them as paid. Decide in advance whether you ask for the difference or add the received amount as credit. Our underpayment and refund guide has templates for both.
- Double payments. Occasionally a client pays the same invoice twice. WHMCS rejects a duplicate transaction ID, and the second transfer is not applied to any invoice; it simply sits in your wallet, so spot it there and refund or credit it.
- Abuse still happens. Crypto removes chargebacks, not bad actors. Keep your usual fraud checks, order review and acceptable-use enforcement.
- Refunds are manual. There is no "refund" button that reverses a blockchain payment. You send a new transfer from your wallet, so write your refund policy with that in mind.
How do you tell existing clients that crypto is available?
Most clients will only notice a new payment method when they next open an invoice, so a short announcement helps. Add a line to your renewal reminder template ("You can now pay this invoice with Bitcoin, USDT or Litecoin"), mention it on your order form and pricing pages, and post a knowledgebase article that explains which networks you accept. Be specific about networks: "USDT on TRON (TRC20)" prevents far more support tickets than "USDT".
If you run a crypto discount, say so plainly and state whether it applies to renewals, new orders or both. Clients who prepay a year of VPS hosting are often the ones most willing to switch, and they are also the invoices where a missed chargeback would have hurt most.
Where should the gateway live on your infrastructure?
You are a hosting company, so this part is easy. The Payfim Gateway needs PHP 7.4 to 8.4, MySQL or MariaDB, cURL and HTTPS, and it runs happily on a cPanel account. Many hosts install it on a subdomain next to the billing panel, such as pay.yourhost.com, or in a folder like billing.yourhost.com/payfim. Add the one-minute cron job, enable 2FA and the admin IP allowlist, and consider the $10 white-label option so the checkout carries only your brand. The installation guide covers the rest.
Taxes and invoicing rules for crypto income differ by country, so check with a qualified accountant how to record these payments before you switch them on.

