Accept crypto payments in WHMCS with MakePay

WHMCS payments are invoice-first. A customer opens an unpaid invoice, chooses a gateway, and expects the billing system to mark the invoice paid when the payment clears. MakePay follows that model with a third-party gateway module.

The gateway renders a crypto payment button, creates a MakePay payment link for the invoice, redirects the customer to hosted checkout, and uses a signed callback to call WHMCS invoice payment helpers.

How MakePay maps to WHMCS invoices

The gateway signs the invoice payment form, validates it in the checkout handler, loads the invoice through WHMCS local API helpers, and creates a MakePay payment link with invoice metadata.

When MakePay reports a completed payment, the callback verifies the webhook signature, checks the invoice ID and transaction ID, and records the invoice payment in WHMCS.

Why WHMCS is a strong crypto-payment fit

WHMCS merchants often sell hosting, domains, subscriptions, retainers, or technical services. These are invoice-driven purchases where a hosted crypto payment link can fit naturally.

Support teams can keep invoice history in WHMCS while MakePay handles asset routing, payment instructions, and status events.

Security and recovery

Connect MakePay creates a connection for that WHMCS billing domain. API-key fallback remains available if a merchant cannot complete the guided connection during an incident.

If a billing domain changes, reconnect MakePay so callback URLs match the new WHMCS System URL.