Accept crypto payments on your WHMCS invoices

SnapEX Pay adds a crypto payment method to WHMCS. Your client clicks Pay Now on an unpaid invoice, pays on the SnapEX Pay payment page, and the invoice is marked Paid in WHMCS automatically. You don't need wallets, nodes or any blockchain setup on your side: funds arrive in your SnapEX Pay merchant balance in USDT.

What your clients can pay with

• USDT on TRON (TRC20), Ethereum (ERC20), BNB Smart Chain (BEP20), Solana, TON and other networks
• 70+ other coins, automatically converted to USDT: BTC, ETH, LTC, SOL, XMR, TON, TRX, DOGE, XRP, USDC and more (for payments from $8)

The client picks the coin and network on the payment page, sees the exact amount and address, and pays from any wallet or exchange.

Built for billing that must not miss a payment

An invoice is marked paid by whichever of these happens first:

1. Signed webhook from SnapEX Pay (HMAC-SHA256 signature and timestamp are verified).
2. Client returns from the payment page: the module checks the payment status right away.
3. WHMCS cron: on every cron run the module re-checks recent unpaid crypto payments, so a lost webhook never leaves a paid invoice unpaid. It works even if you never configure a webhook.

The payment status is always re-read from the SnapEX Pay API before anything is applied. Each payment is added exactly once, even if the webhook, the return page and the cron run at the same moment.

Fits how WHMCS works

• Multi-currency. Bill in EUR, GBP or any other currency: set Convert To For Processing to USD and the payment is recorded in the invoice currency.
• Transaction ID. The SnapEX Pay invoice ID is used as the WHMCS transaction ID, so every payment can be traced both ways.
• Partial payments. If a client sends less than required and does not top up in time, nothing is applied automatically. The Gateway Log gets a clear entry with the received amount for you to review.
• Extra payments after an invoice is closed are logged as well.
• Repeat clicks. Pressing Pay Now twice reuses the same open payment instead of creating duplicates. An expired payment window is replaced with a fresh one automatically.
• Gateway Log. Everything the module does is recorded in Billing → Gateway Log.

Test mode

Turn on Test mode to try the full flow without real money: test payments confirm by themselves within seconds. While test mode is on, only logged-in administrators see the payment button, so clients can never pay with test funds. Test payments are ignored once test mode is turned off.

Settings

Setting Description API key Created in your SnapEX Pay merchant cabinet (scopes invoices.read and invoices.write). Webhook secret Optional but recommended. The exact webhook URL to use is shown right under the field. Network fee paid by Merchant: the client pays exactly the invoice amount. Client: the fee is added on top. Payment window How long the payment page stays valid, 1 to 1440 minutes (default 60). Test mode Test payments, visible to administrators only.

Fees

SnapEX Pay charges 1% per payment plus a small fixed network fee that depends on the network. You choose whether you or your client pays it.

Installation

1. Upload the contents of the archive to your WHMCS root folder, keeping the folder structure (modules/gateways/… and includes/hooks/…).
2. Go to System Settings → Payment Gateways → All Payment Gateways and activate SnapEX Pay (Crypto).
3. Paste your API key from the SnapEX Pay merchant cabinet.
4. Optionally set the webhook URL shown in the module settings in your SnapEX Pay cabinet and paste the webhook secret.
5. If your default currency is not USD, set Convert To For Processing to USD.
6. Enable Test mode, pay an unpaid invoice as an administrator, check that it turns Paid, then switch Test mode off.

Requirements

• WHMCS 8.x or 9.x
• PHP 7.4 or newer with cURL
• A SnapEX Pay merchant account

Support

Our team helps with setup and integration. Use the support link on this listing to get in touch.