WHMCS · Nigeria

Accept Monnify
payments on WHMCS

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

  • NGN
WHMCS 7.0+
4 payment methods
Free module
WHMCS
Monnify
Platform
WHMCS 7.0+
Provider
Monnify
Install via
Apps & Integrations
Billing
One-time & recurring
PaymentHood fee
None
Compatibility

Monnify 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 Monnify'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 Monnify, who set and update them. For the current list see Monnify's own documentation (opens in new tab).

Payment methods

What WHMCS customers can pay with

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

Bank transfer

A one-time virtual account number generated per transaction

Cards

Verve, Mastercard and Visa with 3-D Secure

USSD

A dial string returned alongside the account details

Cash at agents

Payment in cash at a Moniepoint agent location

Setup

Connect Monnify to WHMCS

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

1

Open a Monnify account

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

2

Add it in PaymentHood

Paste your Monnify 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 Monnify 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 completion webhook, validated before an order is released
Payment verification
Server-side transaction status re-check against the Monnify API before fulfilment
Credentials
API key and secret key exchanged for a bearer token, held server-side in PaymentHood
  • Add a second provider without touching your WHMCS checkout
  • Automatic failover when Monnify 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

Monnify generates a dedicated account number for that specific transaction. The customer transfers the exact amount from any Nigerian bank app or USSD code, and the payment is matched and confirmed automatically. The account is short-lived — around 40 minutes — so an abandoned checkout does not leave a payable account lying around.

This is the flow's main edge case and the thing worth testing before launch. Confirm Monnify's current behaviour for late and partial transfers, and make sure your order handling matches it.

Yes, at Moniepoint agent locations nationwide — an unusual and genuinely useful option for customers with no bank app.

No. Monnify bills you directly for its own fees, and PaymentHood takes no percentage and no per-transaction cut at any volume. See PaymentHood pricing.

Accept Monnify on WHMCS today

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