Accept BitPay
payments on WHMCS
Install the free PaymentHood module for WHMCS, connect your BitPay account, and BitPay appears as a payment option at checkout. No custom gateway code, and no second integration when you add another provider later.
- USD
- EUR
- GBP
- BTC
- ETH
- USDC
- USDT
- Platform
- WHMCS 7.0+
- Provider
- BitPay
- Install via
- Apps & Integrations
- Billing
- One-time & recurring
- PaymentHood fee
- None
BitPay on WHMCS at a glance
- WHMCS version
- WHMCS 7.0+
- Where you install it
- WHMCS admin → Apps & Integrations
- Coverage
- Accepts payments worldwide. Direct bank settlement is available in a defined list of countries and crypto settlement far more widely. Check BitPay's own list for your market.
- Currencies
-
- USD
- EUR
- GBP
- BTC
- ETH
- USDC
- USDT
- Billing models
- One-time checkout and recurring renewals — WHMCS generates both, and the module handles both.
- Cost
- The module is free and open source. You pay BitPay's own fees, published on their pricing page (opens in new tab). PaymentHood adds nothing on top.
Coverage, currencies and payment methods as published by BitPay, who set and update them. For the current list see BitPay's own documentation (opens in new tab).
What WHMCS customers can pay with
Each method BitPay supports appears in your WHMCS checkout. Enabling one is a PaymentHood dashboard setting — nothing changes on the WHMCS side.
Cryptocurrency
A wide range of coins and tokens accepted at checkout
Stablecoins
USDC, USDT, DAI, GUSD and other dollar-pegged tokens
Connect BitPay to WHMCS
Four steps, no code. The full walkthrough with screenshots is in the WHMCS installation guide.
Open a BitPay account
Register with BitPay and finish their onboarding. Funds settle from BitPay to your own bank account.
Add it in PaymentHood
Paste your BitPay credentials into the PaymentHood dashboard. They stay server-side and never reach your storefront.
Install the module
Download the WHMCS module and install it from Apps & Integrations in your WHMCS admin.
Enable and test
Paste your PaymentHood API key into the module settings, run a sandbox order end to end, then switch to live.
Rather than a direct BitPay module
A single-provider module works until you need a second provider. These are the parts you would otherwise build and maintain yourself.
- Webhook security
- Signed IPN callback, validated before an order is released
- Payment verification
- Server-side invoice status re-check against the BitPay API before fulfilment
- Credentials
- API token bound to a merchant identity, held server-side in PaymentHood
- Add a second provider without touching your WHMCS checkout
- Automatic failover when BitPay is unreachable, instead of a failed order
- Idempotent charge creation, so a double-submitted order is not a double charge
- One reconciliation view across every provider you run
- Free and open source — read the module on GitHub (opens in new tab)