Live M-Pesa Billing Acceptance Checklist

WayaDesk / Buyer decisions and pilot

A live payment test should connect the merchant outcome to the correct account and access result. Perform it with the operator’s approved configuration and a controlled purchase whose expected behaviour is documented in advance.

Write the expected result first

Record the test account, package, amount and service period. Identify who authorises the test and who verifies the merchant evidence. The test should not depend on an unlabelled screenshot or a payment made to an assumed support number.

Observe each stage

Check the payment request, provider result, application record, entitlement and access action. Record which component produced each observation and its time. This helps identify whether a failure belongs to payment verification or later network provisioning.

• Verify one completed purchase reaches the intended account once.
• Confirm a failed or cancelled attempt does not grant paid service.
• Test recovery after an agreed interruption without creating another charge.

Include the customer’s view

Inspect the receipt or account history and confirm the displayed package and dates. If notifications are configured, treat their delivery as a separate check. An SMS arriving is not the evidence that verifies the payment.

Keep the result usable

Retain a concise test record with private details removed from any public copy. List unresolved issues before accepting the integration. A successful payment on another website using the same merchant account does not by itself validate this application’s checkout and access path.