Nigeria's recurring-payment landscape should not be described as a copy of East African mobile money. Cards, bank-based methods, USSD and direct-debit mandates can all be relevant depending on the merchant and provider.
Direct debit is a real recurring-payment rail
The Central Bank of Nigeria's direct-debit rules provide for payer mandates that authorize billers to initiate debits through participating banks and licensed payment service providers.
The rules require payer authority and set responsibilities for billers, banks and PSPs. That makes direct debit conceptually different from repeatedly asking a customer to make a new one-off payment.
Cards and bank-based PSP channels remain important
Major PSPs serving Nigeria expose card, bank-account/transfer and USSD payment methods. The exact recurring capability depends on the merchant agreement and the specific provider product.
Do not force a mobile-money thesis onto Nigeria
A regional billing platform should model the recurring obligation above the payment rail. In Nigeria, the preferred rail may be a card mandate, direct debit, bank transfer or another supported method rather than a mobile wallet.
The same recurring controls still matter
- One obligation per billing period.
- Clear mandate or authorization evidence for the chosen rail.
- Separate payment-attempt and invoice state.
- Recovery that respects the payment method's rules.
- Reconciliation back to the invoice and provider evidence.
Questions before launch
- Which entity and merchant categories can the PSP onboard?
- Which recurring or mandate products are actually available to that merchant?
- What customer authorization and cancellation rights apply?
- How are failed debits represented?
- How do settlement and reconciliation records reach finance?
Mandates change the recovery model
A valid direct-debit mandate can let a biller initiate a debit under the rules of that scheme, which is different from a customer manually approving every collection. The billing system should preserve the mandate reference and status separately from each debit attempt.
A failed debit is still one attempt against one invoice
If the debit fails, the merchant should leave the invoice due and apply the retry/recovery rules allowed by its provider and mandate. Do not create another invoice simply because another debit will be attempted.
Bank transfer needs matching discipline
A customer may also pay by bank transfer or another approved route. The system should be able to record external satisfaction with the transfer reference and stop further collection against the same obligation.
Regional products should not force wallet terminology
The reusable objects are customer, invoice, payment attempt, mandate/authorization evidence, recovery and reconciliation. Nigeria may use a different mix of rails from Kenya, but the commercial model can remain the same.
Questions for a provider demo
-
How is a direct-debit mandate created, stored and cancelled?
-
What event proves a debit succeeded or failed?
-
What retry behavior is allowed?
-
How are bank-transfer payments matched to invoices?
-
What settlement and reconciliation files are available?
These questions are more useful than assuming one “recurring payments” label means the same thing across cards, bank debit and transfers.
Sources
Central Bank of Nigeria Regulation for Direct Debit Scheme: https://www.cbn.gov.ng/Out/2018/BPSD/Regulation%20for%20Direct%20Debit%20Scheme%20in%20Nigeria%202018%20%28Revised%29.pdf
Paystack payment channels: https://paystack.com/docs/payments/payment-channels/
