Accept SnapScan
payments on WHMCS
Install the free PaymentHood module for WHMCS, connect your SnapScan account, and SnapScan 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
- SnapScan
- Install via
- Apps & Integrations
- Billing
- One-time & recurring
- PaymentHood fee
- None
SnapScan 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 SnapScan'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 SnapScan, who set and update them. For the current list see SnapScan's own documentation (opens in new tab).
What WHMCS customers can pay with
Each method SnapScan 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 approves in the SnapScan app
Payment links
A shareable link for invoices, email and social selling
Connect SnapScan to WHMCS
Four steps, no code. The full walkthrough with screenshots is in the WHMCS installation guide.
Open a SnapScan account
Register with SnapScan and finish their onboarding. Funds settle from SnapScan to your own bank account.
Add it in PaymentHood
Paste your SnapScan 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 SnapScan 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
- Signed payment notification, validated before the order is released
- Payment verification
- Server-side payment status re-check against the SnapScan merchant API before fulfilment
- Credentials
- Merchant API key, held server-side in PaymentHood
- Add a second provider without touching your WHMCS checkout
- Automatic failover when SnapScan 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)