M-Pesa Payments Pro for WHMCS
Give your customers a faster way to pay their WHMCS invoices with M-Pesa Payments Pro. Accept payments directly from the invoice page or your M-Pesa Paybill, then intelligently match incoming payments to the correct WHMCS invoice without relying on manual reconciliation.
M-Pesa Payments Pro for WHMCS is a powerful M-Pesa payment gateway and payment matching module for WHMCS designed for Kenyan web hosting companies, domain registrars, SaaS providers, and online businesses. The module allows customers to pay their WHMCS invoices directly using M-Pesa without leaving the invoice page, while also automatically processing payments made directly through your M-Pesa Paybill. With support for M-Pesa payment requests, direct Paybill payments, and Buy Goods Till payments, businesses can provide customers with a convenient local payment experience while keeping all transactions connected to WHMCS.
What makes M-Pesa Payments Pro different is its intelligent M-Pesa payment matching engine. Receiving a payment is only part of the challenge—correctly identifying which WHMCS invoice the payment belongs to is equally important. The module evaluates multiple factors including invoice numbers, customer phone numbers, payment amounts, previous payment history, account references, and common typing mistakes to determine the most likely invoice. Payments that meet the required confidence and matching criteria are automatically applied, while uncertain transactions are placed into a clear review queue instead of being incorrectly assigned. This helps prevent duplicate payments, incorrect invoice allocations, and manual reconciliation work.
The module also provides powerful M-Pesa reconciliation and payment management tools for WHMCS, including CSV statement reconciliation, partial payments, overpayments, automatic client credit handling, payment verification, refunds with approval controls, transaction logs, admin permissions, payment notifications, and a real-time payment dashboard. Every M-Pesa receipt is uniquely tracked to prevent duplicate processing, while callbacks are handled efficiently so payments can be received without unnecessary delays. With M-Pesa Payments Pro for WHMCS, hosting companies can automate M-Pesa collections, reduce payment-related support tickets, simplify financial reconciliation, and give customers a faster and more reliable way to pay their WHMCS invoices.
M-Pesa Payments Pro collects M-Pesa payments inside WHMCS and, more importantly, works out which invoice each one belongs to. Clients pay from the invoice page without leaving it, paybill payments made straight from a phone are matched automatically, and anything the module is not certain about waits in a queue that explains itself instead of guessing.
Version 1.11.1 · WHMCS 8.x · PHP 8.1+ · by Hostnali · Documentation
The client presses your normal Pay Now button, types their number, and approves the payment on their phone. The invoice page updates itself the moment the money lands — no reloading, no "have you paid yet".
Someone who pays your paybill from their phone, with no browser involved, still gets their invoice marked paid within seconds — provided they quoted the invoice number, which the module checks and corrects for common typing mistakes.
Taking a payment is the easy half. The hard half is a payment that arrives with the wrong account number, the right number but the wrong amount, or nothing useful at all. Most modules either guess or give up. This one scores every plausible invoice and tells you why.
| What the module found | Score |
|---|---|
| The account number matches an invoice | 70 |
| It matches after fixing a typo, such as O for zero | 50 |
| The phone belongs to a client, or has paid before | 40 |
| Exactly one open invoice has that balance | 35 |
| The amount equals the balance exactly | +20 |
| Paid from the number on that client's account | +15 |
| It would leave a balance owing | +5 |
| It is more than the balance | −10 |
| That invoice is already settled | −45 |
A payment is only recorded automatically when it clears your confidence threshold and beats the next best candidate by a clear margin.
Without that second rule, a client with two identical monthly invoices would get a coin toss recorded as a decision. Two close candidates always go to a person.
Anything not applied automatically appears with the invoice the payer actually named pinned to the top, the reason it is waiting stated in plain English, and one-click actions: apply it, apply it to a different invoice, hold it as client credit, mark it as already recorded, or set it aside.
Recorded against the invoice with the balance left owing, or held for review. Your choice.
Settle the invoice and push the excess to the client's credit balance, record the lot, or hold it.
M-Pesa only accepts whole shillings, so an invoice ending in cents always collects a little over. A tolerance absorbs it silently instead of dripping cents into credit balances.
Upload the CSV from the M-Pesa portal and see four answers: matched, in the statement but not in WHMCS, in WHMCS but not the statement, and payments you know succeeded but were never named. Bring any of them in with one click.
Money can only ever go back to the number that paid — there is no field to type a destination. Large refunds need approval, the requester cannot approve their own, and a daily ceiling applies across every admin.
Buy Goods tills carry no account number, so clients confirm a payment by entering the code from their M-Pesa message. Every code is checked against your records and, if needed, with Safaricom directly — never simply trusted.
Decide which admin roles can see transactions, work the queue, change credentials or send refunds. Fourteen separate capabilities, off by default, with Full Administrators always keeping access.
Email on a payment received, a payment needing matching, or a failed request — each switched on or off separately. Sent through your WHMCS SMTP settings, so they come from your own address and land in inboxes.
Collected today and this month, completion rate on payment requests, anything waiting, your paybill balance, a fourteen-day collections chart and the split between invoice-page and direct paybill payments.
| WHMCS | 8.x |
| PHP | 8.1 or newer, with curl, json and mbstring |
| Safaricom | A production Daraja app on your own paybill or till, with Lipa na M-Pesa Online enabled |
| Your server | Reachable from the internet over HTTPS, so Safaricom can deliver callbacks |
| Currency | Kenya Shillings, or another currency with an exchange rate configured in WHMCS |
| Optional | An API operator name and security credential, needed only for refunds, live balance checks and code verification |
One licence covers one WHMCS domain. An expired licence pauses the admin screens and stops new payments being started — but payments already on their way are still received and recorded, so money never goes missing while a renewal is sorted out.
Read the full documentation · Questions before buying? [email protected]
Feature releases for M-Pesa Payments Pro, newest first. Maintenance releases that only correct behaviour are not listed. Every release upgrades in place — replace the files and the database updates itself the next time you open the module.
Licence behaviour separated from payment collection, and callbacks answered before the heavy work starts.
Till support, customer-supplied payment codes, and a paybill balance that keeps itself current.
Licensing, and settings reorganised into sections.
Reconciliation, refunds, the client area page, and role-based access.
A dashboard worth opening.
Paybill balance.
The invoice page updates itself, and email notifications arrive.
Callback addresses Safaricom will actually accept.
Money rules, the invoice payment window, and transaction reporting.
The matching engine.
Paybill payments made without touching the invoice.
Payment requests from the invoice page.
Dates are omitted deliberately: releases are made when they are ready. Upgrading is always a file replacement — no database work, no reconfiguration.
