WHMCS · South Africa

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
WHMCS 7.0+
2 payment methods
Free module
WHMCS
Zapper
Platform
WHMCS 7.0+
Provider
Zapper
Install via
Apps & Integrations
Billing
One-time & recurring
PaymentHood fee
None
Compatibility

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).

Payment methods

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

Setup

Connect Zapper to WHMCS

Four steps, no code. The full walkthrough with screenshots is in the WHMCS installation guide.

1

Open a Zapper account

Register with Zapper and finish their onboarding. Funds settle from Zapper to your own bank account.

2

Add it in PaymentHood

Paste your Zapper credentials into the PaymentHood dashboard. They stay server-side and never reach your storefront.

3

Install the module

Download the WHMCS module and install it from Apps & Integrations in your WHMCS admin.

4

Enable and test

Paste your PaymentHood API key into the module settings, run a sandbox order end to end, then switch to live.

Why PaymentHood

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)
FAQ

Frequently Asked Questions

Both are South African QR wallets and both work the same way from the customer's side — scan, confirm in the app, done. They differ mainly in installed base and in the merchant networks that have adopted them. Since neither reaches every customer, most merchants who offer QR payment offer both, which behind PaymentHood is a dashboard toggle rather than a second integration.

Yes. You register with Zapper directly and connect the merchant credentials to PaymentHood. Funds settle from Zapper to your bank account; PaymentHood never holds merchant money.

On mobile-heavy traffic and on invoice or social selling, where sending a scannable code is faster than asking a customer to type card details on a phone. On a desktop-heavy B2B checkout, cards and pay-by-bank will usually carry more volume.

Yes, and you should. Each method reaches customers the others miss. PaymentHood presents all configured methods through one checkout and one integration.

No. Zapper bills you directly for its own fees. PaymentHood takes no percentage and no per-transaction cut — see PaymentHood pricing.

Accept Zapper on WHMCS today

Free module, no PaymentHood transaction fee, and room to add another provider whenever you need one.