Give customers a receipt that helps resolve prepaid issues
When a customer comes back to the till, the receipt should let any cashier find the sale. Print a unique receipt number, date, product, value and the status the system can confirm. Give the customer one contact for help. Add a supplier reference only if it helps the lookup and is safe to share.
If the till has only sent the order, say so on the receipt. Keep full mobile numbers, passwords and API keys off it. If the product itself is a voucher, hand over the PIN through the supplier's secure process.
Receipt field review
| Field | Purpose | Check before use |
|---|---|---|
| Business and outlet | Identifies who made the sale | Correct branch and contact details |
| Date and time | Narrows the search | Local time convention is clear |
| Product and value | Shows what was requested | Use accurate product wording |
| Internal receipt ID | Finds the local transaction | Unique and searchable |
| Status | Sets expectations | Match the current evidence |
| Support route | Lets customer ask for help | Contact is monitored |
| Supplier reference | Supports lookup if appropriate | Safe and necessary to disclose? |
By Freepaid · Published
Make status wording accurate
A submitted request is not automatically a completed transaction. If the till has only recorded that the request was sent, the receipt should not claim fulfilment is complete. Use status labels that match the provider's documentation and the point in the workflow. If the result is pending or unknown, say the result is being checked and provide a way to follow up.
Avoid wording that suggests a guarantee beyond what the business can verify. “Completed” should be supported by the recorded status. If a system cannot provide a reliable status at the point of sale, define a separate receipt or follow-up message rather than leaving staff to improvise. The support team should know how to find the underlying order from the receipt ID.
Worked example
An illustrative receipt might read:
Outlet A01 · Sale 004218 · 3 Nov 2026 · Airtime R20 · Status: submitted, result being checked. For help, contact the outlet using the details below and quote sale number 004218.
The customer can read the sale number back to support without sharing their mobile number or a redeemable code. If they bought a voucher, use the provider's secure process to issue the PIN and keep it out of receipt histories or reports that others can view.
With sale number 004218, support can look up the original supplier reference and check the result. If another branch can issue the same number, include the branch code on the receipt and use both fields in the lookup.
Protect personal and redeemable information
Review every field with the staff who handle support. Ask whether the business actually needs to print the full destination or whether a masked version is enough. Avoid exposing recipient details on receipts left at a counter or visible to nearby customers. Keep PINs, temporary credentials and access tokens out of transaction receipts and screenshots unless a verified delivery process requires a code to be handed directly to its intended recipient.
Set a correction procedure. If a receipt contains an error, issue a corrected document that points to the original sale ID and records who made the change. Do not delete the original order history to make later records line up. A corrected customer-facing receipt and the underlying transaction evidence serve different purposes.
Make the receipt usable at the counter
Print a receipt on the till staff actually use. Check that the sale number is legible after a shift and ask a different cashier to find the order from that number alone. If the sale included a voucher, check that its PIN can be handed over securely while the support copy still identifies the sale.
Test the receipt with support
- Give a support colleague a sample receipt without extra context.
- Check whether they can find the matching local sale and original order reference.
- Confirm the status wording is understood and does not overstate the result.
- Ask which fields are unnecessary or too sensitive to show.
- Verify the support contact route is active and the branch identifier is clear.
- Test how a corrected receipt is produced and how the original is retained.
Review receipt design when a product, supplier workflow or support channel changes. For transaction disputes, preserve the original reference and investigate it before placing another order. See what evidence to collect for a wrong-number report for a focused escalation checklist.