Accept Zapper
without building the integration
Zapper is a South African QR-code payment app. The customer scans a code at checkout — on screen, on an invoice or at a point of sale — and confirms the payment inside the Zapper app, so no card details are entered on the merchant's site. It competes directly with SnapScan and has a substantial installed base in South African retail and hospitality.
- ZAR
- Region
- South Africa
- Methods
- 2
- Credentials
- Server-side only
- PaymentHood fee
- None
- Status
- Live
Zapper in summary
- Coverage
-
- South Africa
Among the markets Zapper serves — their own list is authoritative (opens in new tab).
- Currencies
-
- ZAR
Among those supported. Which ones your account can charge in depends on its registered country.
- Fees
- Set and billed by Zapper, who publish current rates on their own site (opens in new tab). PaymentHood adds nothing on top, at any volume.
- Official resources
- Website (opens in new tab)
Written against Zapper's own documentation on . This page deliberately states no fees, no counts and no completeness claims, because those change without notice — for anything you are about to build on, Zapper's own documentation (opens in new tab) is the authority.
What your customers can pay with
Every method below runs through the same PaymentHood checkout. Turning one on or off is a dashboard setting, not a code change.
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
What PaymentHood handles for you
A direct Zapper integration is not just an API call. These are the parts every team ends up rebuilding — and the parts PaymentHood ships already done.
- Credentials
- Merchant API credentials, held server-side in PaymentHood
- Webhook security
- Payment notification validated before the order is released
- Payment verification
- Server-side payment status re-check before fulfilment
- Idempotent charge creation, so a retried request never double-charges a customer
- Automatic failover to another configured provider when Zapper is unreachable
- One reconciliation view across Zapper and every other provider you run
- Provider credentials never reach the storefront or the customer's browser
- Adding or switching a provider later is a dashboard change, not a re-integration
Use Zapper on your platform
Install the free PaymentHood plugin for your store, then enable Zapper in your dashboard.
Connecting Zapper takes three steps
Open your Zapper account
Register directly with Zapper and complete their onboarding. Funds settle from Zapper into your own bank account — PaymentHood never holds merchant money.
Add the credentials to PaymentHood
Paste your Zapper API credentials into the PaymentHood dashboard. They are stored server-side and never exposed to your storefront.
Enable it at checkout
Install the PaymentHood plugin for your platform, paste your PaymentHood API key, and Zapper appears as a payment option. Test in sandbox, then switch to live.