M-Pesa Payment References for Internet Accounts

WayaDesk / M-Pesa payments

Payment references connect a financial event to the service it should fund. Without a clear reference, two customers buying the same-priced package can be difficult to distinguish, especially when one person pays on behalf of someone else.

Define what the reference represents

Decide whether a particular workflow identifies an invoice, subscriber or purchase attempt. Staff should use the meaning assigned by the system rather than replacing references with informal nicknames. Preserve the merchant receipt identifier separately from internal application identifiers so either side can be traced later.

Payer and subscriber may differ

A relative may pay a household’s internet charge. The payer’s phone number is useful evidence, but it does not necessarily identify the account that should receive access. Check the intended subscriber and the package before assigning payment or helping with a disputed renewal.

• Keep the internal purchase reference and merchant receipt together.
• Record the intended account and package at the time of purchase.
• Confirm the required Paybill account field before giving manual instructions.

Example to discuss with staff

Two homes each owe the same monthly amount. A payment screenshot showing only the amount and time is not enough to choose the right home. Staff should locate the merchant transaction and its reference, then match it to the correct application record.

Keep references out of public examples

Training materials can use invented reference values and anonymised accounts. Customer payment records belong in the authorised operating workflow. For WayaDesk licence purchases, use the automated checkout for Paybill 4025833. Checkout creates the order reference; check the plan and amount before approving the M-Pesa prompt.