The business problem
A cashier sees a payment request or customer message but cannot confidently match a confirmed receipt to the sale. Collections need references, confirmation and a daily reconciliation.
Plan the cost and scope
Published M-Pesa setup: KES 10,000 without STK push or KES 20,000 with STK push. These are alternative integration options, separate from the base software.
Hardware, applicable tax and separately scoped integrations or custom work are additional. Ask for a written breakdown covering deployment, training and recurring services.
Explore a connected workflow
Choose the payment workflow you need
Published integration prices are KES 10,000 without STK push or KES 20,000 with STK push. Confirm merchant onboarding, payment references and connectivity requirements in the quotation. The business receiving customer payments needs its own agreed merchant arrangement.
A practical workflow
- Match the payment reference and amount to the sale.
- Test delayed confirmation, a wrong amount and a failed request.
- Reconcile till totals with the merchant statement and investigate unmatched payments.
What to verify in your demo
STK initiation is not proof of settlement. Ask what staff see before a payment is confirmed, how repeat callbacks are handled and who resolves unmatched receipts. Website software payments use the published Paybill and manual verification.
Questions before you decide
Is this included in every installation?
Confirm the edition, configuration and integration scope in your written quotation. Published add-ons and messaging services have separate charges.
How do I evaluate this for my business?
Bring a sample transaction or document and ask the team to run it from entry to reporting.