Internet Payment Receipts and Transaction Records

WayaDesk / M-Pesa payments

A useful receipt lets the customer and operator identify the same purchase. It should communicate the amount, the relevant service and the evidence behind the recorded payment. Clear labelling matters when some payments are confirmed through an integration and others are entered by an authorised operator.

Preserve the source of the record

LinkDesk receipts distinguish provider receipt numbers from internal STK references and operator-entered payments from authenticated gateway confirmation. Those distinctions should remain visible when a receipt is printed or saved as a PDF.

Connect the receipt to service

Keep the subscriber or purchase reference, package and payment date available. For recurring service, the entitlement record helps explain the period funded by the payment. A receipt alone does not prove that the customer’s current device is online or that its present package matches an older purchase.

• Check that the displayed amount matches the verified transaction.
• Keep internal and merchant references labelled separately.
• Ensure staff understand the meaning of a manually recorded payment.

Handle customer questions consistently

If a customer presents a receipt for an earlier period, inspect that period before extending service. If the issue concerns a missing receipt, locate the original transaction and provide the existing record rather than entering a new payment to produce another document.

Know the document’s purpose

The software’s printable payment receipt is an operational record. It is not presented as an eTIMS tax invoice. Where a business needs a specific tax or accounting document, use the appropriate process and confirm its requirements independently.