A payment can reach the right account and still leave a person waiting for a service, especially when the receiving team cannot connect the transaction to the correct application.
A transaction reference gives that team a way to find the payment without relying on a name, an amount or a screenshot that might resemble several other records.
Two customers might pay the same amount on the same day, or one customer might make several payments, leaving staff with information that looks similar until they check the individual references.
The reference needs to stay attached to the application, the payment confirmation and the receipt, so the customer and the receiving team can follow the same transaction through their records.
When a payment needs checking
A delayed receipt or an incorrect status can send a customer between several teams, with each asking for the same details if they have no shared record of the problem.
Staff need to see the amount expected, the amount received and the application concerned, together with any earlier attempt to resolve the issue or correct the information on file.
A useful support process keeps those details together and identifies the person or team handling the next step, giving the customer a clear contact for an unresolved payment.
Changes need a record of their own, so a corrected amount or updated status can be followed back to the original entry and the reason it was amended.
The form, payment screen and receipt should present the reference clearly, giving people something they can retain and use when they need help completing the service they paid for.