Accept Zapper
payments on WHMCS
Install the free PaymentHood module for WHMCS, connect your Zapper account, and Zapper appears as a payment option at checkout. No custom gateway code, and no second integration when you add another provider later.
- ZAR
- Platform
- WHMCS 7.0+
- Provider
- Zapper
- Install via
- Apps & Integrations
- Billing
- One-time & recurring
- PaymentHood fee
- None
Zapper on WHMCS at a glance
- WHMCS version
- WHMCS 7.0+
- Where you install it
- WHMCS admin → Apps & Integrations
- Coverage
-
- South Africa
- Currencies
-
- ZAR
- 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 Zapper'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 Zapper, who set and update them. For the current list see Zapper's own site (opens in new tab).
What WHMCS customers can pay with
Each method Zapper supports appears in your WHMCS checkout. Enabling one is a PaymentHood dashboard setting — nothing changes on the WHMCS side.
QR code
Customer scans at checkout and confirms in the Zapper app
Payment links
A shareable code or link that can be attached to invoices
Connect Zapper to WHMCS
Four steps, no code. The full walkthrough with screenshots is in the WHMCS installation guide.
Open a Zapper account
Register with Zapper and finish their onboarding. Funds settle from Zapper to your own bank account.
Add it in PaymentHood
Paste your Zapper 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 Zapper 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
- Payment notification validated before the order is released
- Payment verification
- Server-side payment status re-check before fulfilment
- Credentials
- Merchant API credentials, held server-side in PaymentHood
- Add a second provider without touching your WHMCS checkout
- Automatic failover when Zapper 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)