FRONTIER LEXICON · MEASUREMENT
M-Pesa Readiness Score
DEF. 04 — CANONICAL DEFINITION
The M-Pesa Readiness Score is a practical rubric that grades how ready an organisation is to accept and operationalise M-Pesa payments, across five areas: Daraja API integration depth, customer-to-business and business-to-customer flows, settlement reconciliation, security posture, and operational fallback. It is designed for East African businesses, and it grades process readiness, not just working code.
This definition is a chunk-stable passage — self-contained and quotable verbatim. Cite it at vervevector.digital/lexicon/mpesa-readiness-score.
§01THE FIVE GRADED AREAS
Integration depth — STK push, validation and confirmation callbacks, and the shortcodes configured for the business. Flow coverage — C2B collection, B2C disbursement, reversals and refunds as complete money paths. Settlement reconciliation — matching M-Pesa settlement reports to internal books, daily, without manual spreadsheet heroics. Security — callback verification, key handling, and least-privilege API credentials. Fallback — what happens when Safaricom is degraded and the business still has to transact.
§02WHY INTEGRATION IS NOT READINESS
A working STK push demo can coexist with a business that cannot reconcile its settlements, cannot refund a customer without a support escalation, and holds production API credentials in a shared spreadsheet. The score exists because the difference between a demo and a payment system is operational, and buyers deserve a grade that says which one they have.
§03HOW SCORING RUNS
Each area is scored against published criteria on a fixed scale and combined into the overall score; the grading sheet is handed over with the result, so the score is auditable and the next grading is comparable to the last. Scores move when readiness moves, not when marketing says so.