Binance Pay for WHMCS

Binance Pay for WHMCS is a payment gateway module by WHMPress that lets your hosting or service business accept cryptocurrency payments directly on WHMCS invoices through the official Binance Pay Merchant API. Invoices stay priced in your own fiat currency; the module creates a Binance Pay order for the invoice total, and your customer settles it in crypto from their Binance account, either through the Binance-hosted checkout window or by scanning an inline QR code with the Binance app. Payments are confirmed automatically in the background, so the invoice is marked paid within seconds of the customer completing payment — no manual reconciliation, no waiting on block confirmations on your side.

The module handles the full payment lifecycle inside WHMCS: order creation, expiry and re-issue, paid/cancelled/expired status tracking, admin-initiated refunds through the Binance Pay refund API, and Binance commission recorded as the transaction fee on the invoice payment. It supports both Live and Sandbox environments, optional sub-merchant IDs for Binance Pay channel partners, and detailed gateway logging for troubleshooting.

New in version 1.1.0: built-in proxy server support, so merchants whose WHMCS is hosted in a country where Binance Pay is restricted can now use the module by routing its API traffic through an allowed region — plus guaranteed Live/Sandbox separation, so test payments remain viewable and refundable after you go live.

Key Features

Admin Area Features

• Proxy server support for restricted countries — if your WHMCS is hosted in a country where Binance Pay is unavailable, route the module's API traffic through a proxy server in an allowed country. Supports HTTP/HTTPS and SOCKS5 with optional authentication. Only the module's Binance API calls are proxied; the rest of your WHMCS traffic is untouched
• Live and Sandbox records stay correctly separated — every order and refund remembers which environment created it, so Sandbox test payments remain fully viewable and refundable after you switch the gateway to Live, and Live payments are never queried with Sandbox credentials
• Live and Sandbox environments — maintain two complete sets of credentials and switch between them from a single dropdown, so you can test checkout end-to-end before going live
• Full Binance Pay Merchant API integration — order creation, order status lookups, order cancellation, and refunds
• Secure, signed transactions — every request to Binance is cryptographically signed and every incoming payment notification is verified against Binance's own certificates before it's trusted, so payment confirmations can't be spoofed or tampered with
• Refunds from the WHMCS invoice screen — issue full or partial refunds directly through the standard WHMCS refund flow; the module confirms the refund with Binance, verifies it belongs to the invoice being refunded, and returns success, pending or declined accordingly
• Pending refund tracking — refunds that Binance returns as still processing are tracked automatically and finalised the moment Binance confirms them
• Transaction Information support — WHMCS's transaction lookup returns live data for both payments and refunds, including amount, type, status, fee, currency and transaction date
• Extended transaction metadata — Binance transaction ID, merchant trade number, settlement amount and currency, Binance commission, and refund reference all recorded against the transaction
• Commission recorded as invoice fee — the Binance commission is automatically converted back into your invoice currency and recorded as the payment fee
• Duplicate payment protection — built-in safeguards prevent an invoice from ever being credited twice
• Automatic database setup — all required data storage is created on first use and upgraded in place
• Order lifecycle management — outdated orders are automatically closed and expired orders flagged, so a single invoice never carries more than one live payment order
• Optional debug logging, with the active proxy recorded in each log entry for easy verification
• Webhook activity logging — incoming payment notifications are always recorded for auditing
• Sub-merchant ID support for Binance Pay channel partners
• Configurable API base URL per environment
• Off-site payment method — WHMCS never presents a card entry form

Client Area Features

• Pay Now button — opens the Binance-hosted checkout in a centred pop-up window, keeping the customer on your invoice page behind it
• Inline QR code payment — renders the Binance Pay QR code directly on the invoice with a "Scan with the Binance App to pay" prompt
• Choice of both — display the Pay Now button and the QR code together, or either one on its own
• Live countdown timer — an optional on-invoice timer counts down to the order's expiry
• Automatic payment detection — the invoice page checks payment status in the background and redirects the customer to the paid invoice as soon as Binance confirms, without a manual refresh
• Automatic recovery on expiry — if an order expires or is cancelled, a fresh payment order is generated
• Order re-use — returning to an unpaid invoice re-uses the existing live order when the amount and currency still match
• Unsupported currency notice — a clear message instead of a broken checkout
• Localised Pay Now label — uses your WHMCS language file's Pay Now string

Gateway Configuration Options

• Environment — Live or Sandbox (Test Mode)
• Live Merchant ID — optional sub-merchant ID for channel partners
• Live API Key / Certificate SN, Live API Secret, Live API Base URL
• Sandbox Merchant ID, Sandbox API Key / Certificate SN, Sandbox API Secret, Sandbox API Base URL
• Checkout Method — Modal, QR Code Only, or Modal & QR Code
• Order Expiry (Minutes) — 1 to 21600 minutes (default 60)
• Display Countdown Timer
• Debug Logging
• Use Proxy Server — route Binance Pay API requests through a proxy
• Proxy Type — HTTP/HTTPS or SOCKS5
• Proxy Host / Proxy Port
• Proxy Username / Proxy Password — optional proxy authentication

Important: Binance Pay Country Restrictions

Binance Pay cannot be accessed from servers located in the countries and regions listed below. This is a restriction from Binance, applied to your server's IP address.

This module includes built-in proxy support for exactly this situation. If your WHMCS is hosted in one of these locations, enter the details of a proxy server based in an allowed country in the gateway configuration, and the module will route its Binance Pay API traffic through it.

List of Prohibited Countries as described in Binance's Terms of Use: Canada · Netherlands · United States · Cuba · Democratic People's Republic of North Korea ("DPRK") · Iran · Syria · Crimea region and any non-government-controlled areas of Ukraine

Why Choose WHMPRESS?

WHMPRESS builds WHMCS modules the way integrations should be built: against the provider's real API, with the security work done properly rather than skipped. This module signs every outbound request, verifies every inbound payment notification against Binance's own published certificates, guards against duplicate payment postings, keeps Live and Sandbox records rigorously separated, and maintains its own payment history independently of gateway logs. You get a clean, honest integration — and a team that supports it.

General Compatibility:

• WHMCS Compatibility: Supports WHMCS Versions 8.7 to 9.X

• PHP Versions: Supports PHP 8.4, 8.3, 8.2, and 8.1

• Themes Supported: Works with WHMCS themes such as Six, Twenty-One, and Lagom WHMCS Client Theme

• System Requirement: Requires ionCube Loader v13 or later

Module Price

Monthly Price: $5

Annually Price: $29

One-Time Price: $75

OPEN-SOURCE VERSION: $149 One-time Price