Accept Paga
payments on WHMCS
Install the free PaymentHood module for WHMCS, connect your Paga account, and Paga appears as a payment option at checkout. No custom gateway code, and no second integration when you add another provider later.
- NGN
- Platform
- WHMCS 7.0+
- Provider
- Paga
- Install via
- Apps & Integrations
- Billing
- One-time & recurring
- PaymentHood fee
- None
Paga on WHMCS at a glance
- WHMCS version
- WHMCS 7.0+
- Where you install it
- WHMCS admin → Apps & Integrations
- Coverage
-
- Nigeria
- Currencies
-
- NGN
- 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 Paga'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 Paga, who set and update them. For the current list see Paga's own documentation (opens in new tab).
What WHMCS customers can pay with
Each method Paga supports appears in your WHMCS checkout. Enabling one is a PaymentHood dashboard setting — nothing changes on the WHMCS side.
Paga wallet
The customer authorises payment from their Paga wallet
Bank USSD
One-time-use bank shortcode collection
Payment links
A shareable link created through the payment request API
Cards
Card payment through Paga Checkout
Connect Paga to WHMCS
Four steps, no code. The full walkthrough with screenshots is in the WHMCS installation guide.
Open a Paga account
Register with Paga and finish their onboarding. Funds settle from Paga to your own bank account.
Add it in PaymentHood
Paste your Paga 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 Paga 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 an order is released
- Payment verification
- Server-side transaction status query against the Paga API before fulfilment
- Credentials
- Principal, credential and API key with request hashing, held server-side in PaymentHood
- Add a second provider without touching your WHMCS checkout
- Automatic failover when Paga 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)