Accept OPay
payments on WHMCS
Install the free PaymentHood module for WHMCS, connect your OPay account, and OPay 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
- OPay
- Install via
- Apps & Integrations
- Billing
- One-time & recurring
- PaymentHood fee
- None
OPay 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 OPay'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 OPay, who set and update them. For the current list see OPay's own documentation (opens in new tab).
What WHMCS customers can pay with
Each method OPay supports appears in your WHMCS checkout. Enabling one is a PaymentHood dashboard setting — nothing changes on the WHMCS side.
OPay wallet
Payment from the customer's OPay balance, including QR
Cards
3-D Secure card payments
Bank transfer
Transfer confirmed against the order
USSD
Bank shortcode payment
Agent reference
A reference code paid at an agent location
Connect OPay to WHMCS
Four steps, no code. The full walkthrough with screenshots is in the WHMCS installation guide.
Open a OPay account
Register with OPay and finish their onboarding. Funds settle from OPay to your own bank account.
Add it in PaymentHood
Paste your OPay 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 OPay 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 callback, validated before an order is released
- Payment verification
- Server-side order query against the OPay API before fulfilment
- Credentials
- Merchant ID with public and private keys and request signing, held server-side in PaymentHood
- Add a second provider without touching your WHMCS checkout
- Automatic failover when OPay 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)