WHMCS Crypto Payment Gateway: Renewals, Access and Refunds
WHMCS can create and chase a crypto invoice, but it doesn't collect the customer's money automatically. Choose a connector for a payment service your hosting business can use, then decide who confirms payments and who checks that the service really came back. BitPay Acceptance and CoinGate Standard are the two managed options here. Both depend on approval, their account rules differ and each leaves questions about the connector open. A paid invoice, an active hosting service, a renewed domain and money you can spend on your bills are four different things, and you need someone watching each.
Which WHMCS crypto payment gateway should you consider?
Look for a managed service you can qualify for, with a connector and ongoing support that fit a hosting business. BitPay Acceptance and CoinGate Standard each have their own approval rules, so they aren't interchangeable accounts. Our processor selection guide helps you start from what your customers can pay with and the currency you need to receive, which matters when your suppliers want something other than the coins your customers hold.
| Product and connection (if approved) | Payment evidence | Refunds | Where the money lands | Still open |
|---|---|---|---|---|
| BitPay Acceptance with the selected WHMCS connector | BitPay's guide describes a pending payment before confirmed Paid. WHMCS's module page lists one-time use. | The module's native refund command is unsupported. BitPay's guide describes a dashboard refund that updates the status. | An approved BitPay account, settled in crypto or to a business bank account. | Which exact package, who supports it, and whether it works with your WHMCS install. |
| CoinGate Standard with its advertised WHMCS offering | CoinGate advertises status mapping, but your developer has to check how the package you pick handles it. | Use CoinGate's merchant refund process and reconcile the result once it's complete. | A CoinGate account, an enabled receiving currency and a withdrawal method CoinGate approves. | Current package, runtime requirements, native refund behaviour and support coverage. |
BitPay's WHMCS guide still names WHMCS 7.x, while WHMCS's own 9.0 module page lists third-party, one-time payments and says recurring, refund and reversal commands aren't supported.[2] The two pages may not describe the same package, and a 7.x package isn't proven to work on 9.0.
CoinGate says it maintains its plugin in-house, but its page still shows a platform placeholder, with no package we could inspect and no PHP version. The quick-setup, instant-status and no-reconciliation promises are marketing, not results measured on your installation.[4] The BitPay review and CoinGate review cover the broader service decisions.
Can your hosting business get the account?
Find out whether you'd be approved before you pay for the connection. BitPay takes US and Canadian merchant applications, has paused new onboarding in the EEA, UK and Australia, and adds state and product restrictions.[10] Its verification guide asks for business, owner, website and settlement information. Bank settlement needs an account in the business's name, not the personal account an owner might use to cover company expenses.[11]
CoinGate's merchant list includes Canada, Germany and the UK but leaves out the US and UAE.[12] Its processing terms cover legal persons selling goods or services, and its verification guide asks for company documents, ID for directors and significant owners, proof of an operating address and a tailored questionnaire.[20][13] A virtual registered office alone doesn't show where the business operates.
When you apply, describe your company, its owners and controllers (where they live, where they're based and their citizenship), your customers' countries and states, and the lawful hosting or registrar services you sell. Selling your own hosting is a different thing from VPN sales, regulated services, handling client money or collecting for other merchants, and approval for one doesn't cover another.
These are provider conditions as we read them on October 18, 2026. A country missing from a list doesn't make crypto payments illegal there, and a licence logo or software download doesn't mean your business is approved. This is general information, not legal advice.
What must match your WHMCS installation?
Whoever maintains your WHMCS needs to check the platform, the PHP runtime and the connector together. This guide uses a self-hosted WHMCS 9.0 reference from the General Availability documentation, as read on October 15, 2026. It doesn't certify the latest release or a working installation, so your own setup still needs checking.
| What | Who handles it | What the docs say | What's still open |
|---|---|---|---|
| Platform and deployment | Whoever administers WHMCS | The 9.0 self-hosted reference. Cloud is a different setup. | Your installed release, plan and what support covers |
| PHP runtime | Your host and developer | WHMCS 9.0 names PHP 8.2 or 8.3 and matching ionCube requirements | Your environment, your extensions, and the PHP used by the website versus scheduled tasks |
| Connector | Your developer and the publisher | BitPay's guides and CoinGate's advertised offering | Exact package, version, compatibility and who handles updates |
| Merchant account and receiving money | You | Each provider's eligibility, activity and receiving conditions | Whether you'd be approved for your people, customers, product and payment pair |
| Matching a payment to the right invoice | Whoever handles orders, and your developer | Provider confirmation and a WHMCS transaction for the full balance | How missing, repeated, short, late or wrong-network payments get handled |
| Service and domain | Whoever runs the hosting, plus your registrar contact | The configured service action and the domain renewal command | Whether the service came back, whether an overdue balance remains and why it was suspended |
| Refunds and upkeep | Whoever handles refunds, and your developer | The provider's refund process, funding and reconciliation | Permissions, what customer data the connector needs, backups and who you escalate to |
WHMCS warns that custom modules can add requirements, and that the PHP environment for scheduled tasks can differ from the website's.[1] The BitPay module also needs GMP or BCMATH. Its Cloud availability is limited to Growth and Expansion in that document, and self-hosted access says nothing about Cloud-plan access.
Give your developer the official guides and ask for a plain compatibility check that names the package you'd use and the customer data and permissions it needs. Meeting the minimum requirements, having a package available and a successful install are three different things. Our WooCommerce integration guide covers another platform; its compatibility claims don't carry over to WHMCS.
How should you organise the setup?
Follow the publisher's instructions for your connector, and plan around the results you need. Your hosting payment plan should say who owns access and overdue customers as well as checkout.
- 01
Choose what you can use
Match your platform, connector, company, owners, customers, activity, payment pair and where the money lands. Settle approval and compatibility before you rely on the method.
- 02
Hand out the setup jobs
Your WHMCS administrator and developer follow the official guide for your connector, and work out what the provider, host and publisher each handle, plus permissions, data handling and escalation.
- 03
Decide what counts as paid
Pick which provider record counts as confirmation, how full payments get matched to the right invoice, and who owns exceptions. Then work out whether the service really activates, how domain renewal works and what happens when an action fails.
- 04
Cover renewals and refunds
Decide who handles reminders, overdue access, cancellations, funded refunds and reconciliation, and who covers updates, backups and absences. Track the live service and whether the customer received any refund.
When is the invoice paid, and can access start?
A paid invoice and a working service are two checks. BitPay's WHMCS guide describes Unpaid, then Payment Pending, then Paid after BitPay confirms.[3] CoinGate's confirming means network-confirmed, and its paid means credited to the merchant. Your connector's own status mapping still needs checking.[18]
The invoice reference, full amount, asset and network all have to match the provider's own record. In WHMCS 9.0, a transaction that fully clears the invoice triggers payment automation; changing the Paid label alone doesn't.[5] A browser redirect, an email, a screenshot or a broadcast transaction isn't enough on its own, even when the customer has closed their wallet and expects your support team to explain why the account still shows an unpaid bill.
For setting up a new service, WHMCS can activate on order, on first payment, on manual acceptance, or not automatically at all. Its Auto Release option can simulate activation, and an Active label can also release associated downloads.[6] Your host still has to confirm the service really works. If activation fails after an accepted payment, the customer case is yours while your developer and host look into their own systems, and customer service shouldn't just send the buyer back to the processor.
Can crypto renewals run automatically?
Invoices and reminders can run automatically, but that doesn't give anyone permission to pull the payment from an outside wallet. WHMCS's scheduled tasks run invoices, reminders, suspension, termination and cancellation as individual jobs.[8] A recurring label or another provider's subscription product doesn't give this connector a collection mandate.
Automatic unsuspension depends on your configuration and the overdue suspension reason. A suspension for manual policy or an identity check doesn't clear automatically on payment.[7] An older unpaid balance can still block restoration, and paying doesn't recreate a terminated service. So tell the customer what's still in the way instead of promising that paying a recent invoice brings the service back. Our SaaS and membership guide explains the wider access decision.
A domain invoice is one thing and the registrar's renewal is another. WHMCS describes a renewal command that runs on payment under the relevant configuration, but that doesn't show the registrar completed it.[9] The provider's payment window, the invoice due date, the scheduled tasks, your overdue policy and the real domain deadline can all differ.
Does a WHMCS refund return the customer's money?
The money only goes back when a supported refund completes. WHMCS can send a refund command when the gateway supports it, or create internal credit and refund bookkeeping, so find out which one happened. A Refunded label and a confirmation email don't prove the customer received anything.
The BitPay module's native refund command is unsupported, but BitPay's own guide describes a dashboard refund that updates the invoice status. Don't assume the WHMCS Refund button sends crypto. BitPay's refund reference lists preview, created, pending and success stages, with full or partial requests and funding conditions.[19]
CoinGate's refund page describes an available balance, wallet details and customer email confirmation. It values the refund at the merchandise price and the current crypto rate, so the original coin quantity isn't guaranteed. The page describes refund charges in conflicting ways, so ask CoinGate which applies.[14] None of this means there's a native WHMCS command.
Settle who approves the refund, whether it's full or partial, the currency, the destination, how it's funded and who bears any permitted costs. A normal refund on a completed sale and a failed or suspended payment follow different provider procedures and deadlines, and information requests should be answered promptly. A missing command or an irreversible payment doesn't decide what the customer is owed. This is general information, not legal advice.
What will the whole setup cost?
Budget the processing fee, receiving costs and the daily running work as three different things. A quote only fits the business it was written for, so compare offers on the same company, owners, customer countries and states, hosting or registrar activity, WHMCS plan, module, asset and network, and way of receiving money.
Ask what the headline rate leaves out: application, setup and monthly fees, minimums, network costs on both sides, and what you lose to conversion. CoinGate describes an added payment quote margin without pricing its size.[15] Running it also costs module and support charges, hosting, staff time and backups, and banks, refunds and closing the account add more. Custom or higher-risk terms nobody has quoted are a cost you can't see yet. Our BitPay fees and CoinGate fees guides explain why a processing quote isn't a complete operating bill.
Where the money lands matters too. BitPay's guide treats a settlement being issued and the money arriving in your bank as different events.[21] CoinGate's custody summary puts key management with CoinGate and describes withdrawal checks, and its General Terms allow ongoing information requests and transaction restrictions.[17][16] A balance held by the provider isn't something you control or can spend as bank credit. We read those policies on October 18, 2026.
Reconcile invoice payments, provider credit, withdrawals, money that has reached the bank and completed refunds, so you know which sales can pay the next hosting bill and which still depend on a transfer or an open account request. We reviewed public documentation without installing modules or measuring payments, security, support or registrar outcomes; our methodology explains that limit.
WHMCS crypto payments FAQ
Which WHMCS crypto gateway should a hosting business choose?
Does WHMCS 9.0 documentation prove the module works on my server?
Does installing the connector approve my business?
Will WHMCS collect every crypto subscription automatically?
Does a paid invoice mean hosting and its domain are active?
Who handles a short, late or wrong-network payment?
Is internal credit the same as a crypto refund?
What should I include in the ongoing budget and support agreement?
Sources
21
Numbers in square brackets in the text link to these sources.
- WHMCS 9.0 self-hosted requirements and module requirements · Checked 2026-10-18
- WHMCS 9.0 BitPay module: one-time support and excluded commands · Checked 2026-10-18
- BitPay WHMCS guide: 7.x requirements, invoice states and dashboard refunds · Checked 2026-10-18
- CoinGate WHMCS offering: publisher claims and unclear package · Checked 2026-10-18
- WHMCS 9.0 billing logic: payment, credit, refunds and unsuspension · Checked 2026-10-18
- WHMCS 9.0 products: configured activation and associated downloads · Checked 2026-10-18
- WHMCS 9.0 automation settings: overdue actions and policy exceptions · Checked 2026-10-18
- WHMCS 9.0 system cron: scheduled tasks · Checked 2026-10-18
- WHMCS 9.0 domain renewals: invoice versus registrar action · Checked 2026-10-18
- BitPay merchant onboarding countries and product limits · Checked 2026-10-18
- BitPay business, owner and receiving-account verification · Checked 2026-10-18
- CoinGate supported merchant countries · Checked 2026-10-18
- CoinGate business and operational-address checks · Checked 2026-10-18
- CoinGate merchant returns: funding, customer confirmation and valuation · Checked 2026-10-18
- CoinGate Commercial Policy: unpriced payment quote margin · Checked 2026-10-18
- CoinGate General Terms: account review and ongoing checks · Checked 2026-10-18
- CoinGate custody policy: provider control and withdrawal checks · Checked 2026-10-18
- CoinGate order states: confirming versus paid · Checked 2026-10-18
- BitPay refund requests, funding and completed states · Checked 2026-10-18
- CoinGate processing terms: merchant service and return conditions · Checked 2026-10-18
- BitPay settlement: account credit, transfers and bank arrival · Checked 2026-10-18
