Accept SeerBit
payments on WHMCS
Install the free PaymentHood module for WHMCS, connect your SeerBit account, and SeerBit appears as a payment option at checkout. No custom gateway code, and no second integration when you add another provider later.
- NGN
- GHS
- KES
- UGX
- XOF
- ZAR
- USD
- Platform
- WHMCS 7.0+
- Provider
- SeerBit
- Install via
- Apps & Integrations
- Billing
- One-time & recurring
- PaymentHood fee
- None
SeerBit on WHMCS at a glance
- WHMCS version
- WHMCS 7.0+
- Where you install it
- WHMCS admin → Apps & Integrations
- Coverage
-
- Nigeria
- Ghana
- Kenya
- Uganda
- Benin
- Senegal
- Côte d'Ivoire
- South Africa
- Currencies
-
- NGN
- GHS
- KES
- UGX
- XOF
- ZAR
- USD
- 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 SeerBit'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 SeerBit, who set and update them. For the current list see SeerBit's own documentation (opens in new tab).
What WHMCS customers can pay with
Each method SeerBit supports appears in your WHMCS checkout. Enabling one is a PaymentHood dashboard setting — nothing changes on the WHMCS side.
Cards
Verve, Visa and Mastercard
USSD
Bank shortcode payment
Bank transfer
Transfer confirmed against the order
Direct debit
Authorised recurring debit from the customer's account
Mobile money
Regional wallets in the markets where SeerBit operates
Connect SeerBit to WHMCS
Four steps, no code. The full walkthrough with screenshots is in the WHMCS installation guide.
Open a SeerBit account
Register with SeerBit and finish their onboarding. Funds settle from SeerBit to your own bank account.
Add it in PaymentHood
Paste your SeerBit 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 SeerBit 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 transaction notification, validated before an order is released
- Payment verification
- Server-side transaction query against the SeerBit API before fulfilment
- Credentials
- Public and secret keys exchanged for a bearer token, held server-side in PaymentHood
- Add a second provider without touching your WHMCS checkout
- Automatic failover when SeerBit 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)