WHMCS · Nigeria, Ghana, South Africa, Kenya & Côte d'Ivoire

Accept Paystack
payments on WHMCS

Install the free PaymentHood module for WHMCS, connect your Paystack account, and Paystack appears as a payment option at checkout. No custom gateway code, and no second integration when you add another provider later.

  • NGN
  • GHS
  • ZAR
  • KES
  • USD
WHMCS 7.0+
6 payment methods
Free module
WHMCS
Paystack
Platform
WHMCS 7.0+
Provider
Paystack
Install via
Apps & Integrations
Billing
One-time & recurring
PaymentHood fee
None
Compatibility

Paystack on WHMCS at a glance

WHMCS version
WHMCS 7.0+
Where you install it
WHMCS admin → Apps & Integrations
Coverage
  • Nigeria
  • Ghana
  • South Africa
  • Kenya
  • Côte d'Ivoire
Currencies
  • NGN
  • GHS
  • ZAR
  • KES
  • 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 Paystack'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 Paystack, who set and update them. For the current list see Paystack's own documentation (opens in new tab).

Payment methods

What WHMCS customers can pay with

Each method Paystack supports appears in your WHMCS checkout. Enabling one is a PaymentHood dashboard setting — nothing changes on the WHMCS side.

Cards

Visa, Mastercard and Verve debit and credit cards

Bank transfer

Customer-initiated transfer to a generated account number

USSD

Nigerian bank shortcodes, no smartphone required

Mobile money

M-PESA, MTN, AirtelTigo and Vodafone, in the countries where each operates

QR

Scan-to-pay at checkout

Dedicated Virtual Account

A persistent account number per customer, for recurring collections

Setup

Connect Paystack to WHMCS

Four steps, no code. The full walkthrough with screenshots is in the WHMCS installation guide.

1

Open a Paystack account

Register with Paystack and finish their onboarding. Funds settle from Paystack to your own bank account.

2

Add it in PaymentHood

Paste your Paystack credentials into the PaymentHood dashboard. They stay server-side and never reach your storefront.

3

Install the module

Download the WHMCS module and install it from Apps & Integrations in your WHMCS admin.

4

Enable and test

Paste your PaymentHood API key into the module settings, run a sandbox order end to end, then switch to live.

Why PaymentHood

Rather than a direct Paystack 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
HMAC SHA512 signature on the x-paystack-signature header, verified before any order is marked paid
Payment verification
Server-side transaction re-verification against the Paystack API before fulfilment
Credentials
Secret key, held server-side in PaymentHood — never exposed to the storefront
  • Add a second provider without touching your WHMCS checkout
  • Automatic failover when Paystack 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)
FAQ

Frequently Asked Questions

Paystack supports merchants registered in Nigeria, Ghana, South Africa, Kenya and Côte d'Ivoire. You open the Paystack account yourself in your country of registration, then connect it to PaymentHood — PaymentHood does not resell or sit in the flow of funds.

Nigerian Naira (NGN), Ghanaian Cedi (GHS), South African Rand (ZAR), Kenyan Shilling (KES) and US Dollar (USD). Which of these you can actually charge in depends on the country your Paystack account is registered in.

No. You pay Paystack's own transaction fees directly to Paystack, and PaymentHood takes no percentage and no per-transaction cut at any volume. See PaymentHood pricing and Paystack's pricing page (opens in new tab).

Paystack signs every webhook with an HMAC SHA512 digest in the x-paystack-signature header. PaymentHood verifies that signature and independently re-queries the Paystack API to confirm the transaction before an order is marked paid, so a forged or replayed webhook cannot complete an order.

Yes. Your store talks to PaymentHood, not to Paystack, so switching provider is a change in the PaymentHood dashboard. No plugin update, no code change and no second checkout integration.

Accept Paystack on WHMCS today

Free module, no PaymentHood transaction fee, and room to add another provider whenever you need one.