WHMCS · Nigeria

Accept Kuda
payments on WHMCS

Install the free PaymentHood module for WHMCS, connect your Kuda account, and Kuda 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+
2 payment methods
Free module
WHMCS
Kuda
Platform
WHMCS 7.0+
Provider
Kuda
Install via
Apps & Integrations
Billing
One-time & recurring
PaymentHood fee
None
Compatibility

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

Payment methods

What WHMCS customers can pay with

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

Virtual accounts

A dedicated account number per customer or per transaction

Bank transfer

Collection and instant settlement over Nigerian bank rails

Setup

Connect Kuda to WHMCS

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

1

Open a Kuda account

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

2

Add it in PaymentHood

Paste your Kuda 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 Kuda 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 credit notification, validated before an order is released
Payment verification
Server-side transaction confirmation before fulfilment
Credentials
API key and client credentials, held server-side in PaymentHood
  • Add a second provider without touching your WHMCS checkout
  • Automatic failover when Kuda 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

No — and this is the thing to get straight before choosing it. The Kuda Open API is built around bank transfers and virtual accounts, not card acquiring. If you need cards, pair it with a card provider; behind PaymentHood both run through one checkout.

Collections and payouts over Nigerian bank rails, with a real banking licence behind them. Virtual accounts per customer make reconciliation straightforward, which is why it suits recurring collections and marketplace payouts.

Card penetration is lower than transfer usage, and card declines are common. A checkout offering a one-time virtual account number — the customer transfers from any bank app and the payment confirms in seconds — will convert materially better than one offering cards alone. It is the single most important local method to enable.

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

Accept Kuda on WHMCS today

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