Start with a record someone else can find
Use the shop’s agreed place for payment queries, rather than relying on a verbal message or a loose note at the till. Include the order reference, amount, approximate date and time, and whether the customer used a terminal, online checkout, payment link or QR option. Add a till or device identifier if your team uses one and it helps narrow the search.
Describe the issue in the customer’s words where useful, but distinguish their report from your own checks. For example, “customer says their banking app shows a payment” is different from “payment record shows successful”. If you cannot find a reference or status, say so rather than filling the gap with a guess.
- Check that the reference and amount match the order being discussed.
- Record the status shown and where you saw it.
- Add your name or team identifier and the time you made the note.
Check the payment outcome before promising a resolution
Look for the relevant payment record using the information available to your team. A submitted order or a customer’s return to the website is not proof that payment succeeded. Similarly, an interruption at a terminal does not by itself establish whether a payment went through. Record any message or status accurately, including if it is unclear or unavailable.
Follow the shop’s procedure for checking an uncertain outcome and escalating it. Avoid asking the customer to pay again simply because the first attempt is unclear: first establish what can be checked and who is authorised to decide the next step. Do not promise a refund, approval or a particular settlement time while the facts are still being established.
- Compare the order details with the available payment record.
- Note any mismatch, missing record or unresolved status.
- Pass uncertain outcomes to the person responsible for payment queries.
Keep the note useful without collecting too much
A handover should contain enough information to investigate, not a copy of the customer’s payment credentials. Never record a full card number, security code or PIN. Do not ask a customer to send card details in a message, and avoid adding contact details unless they are needed for the agreed follow-up and your shop’s procedure permits it.
Use the approved system and restrict access according to your shop’s rules. If a customer offers a screenshot, check your procedure before accepting or storing it: it may show information the team does not need. A written description of the relevant status may be sufficient for the handover.
- Remove unnecessary personal information from the note.
- Use the shop’s approved contact method if a reply is needed.
- Tell the next colleague where the authorised record can be found.
Example: a payment status is still uncertain
Hypothetical example: a customer places an order for £24.50 and returns to the shop’s website, but says they are unsure whether the payment completed. A colleague finds the order reference but cannot see a confirmed payment outcome. The colleague records the approximate time, amount, online payment route and the fact that the available status is unclear.
The handover says: “Order reference 4821; £24.50; around 2.15 pm today. Customer returned to the website and asked whether payment went through. Order found; payment outcome not confirmed in the record checked. Please ask the shift manager to investigate before we request another payment. Customer expects an update through the shop’s agreed contact method.” The reference and amount are illustrative; the important point is that the note does not turn a browser return into a payment confirmation.
Make the next action and finish line clear
Name the person or role responsible for the next check, what they need to do and when the customer should expect an update, if one has been agreed. Note any action already taken, such as contacting the shift manager, so the next colleague does not repeat it. If support is needed, pass on the reference, approximate time, amount and observed status through the appropriate channel without sending full card details.
A useful success check is that the next colleague can locate the relevant order, see what remains unconfirmed and know who owns the follow-up without asking the customer to repeat the whole story. Once the outcome is verified, update the same record with what was confirmed, the action taken and whether the customer has been contacted.
- Assign an owner and record the next check.
- Update the customer when agreed, even if the investigation is still open.
- Close the handover only after recording the verified outcome and follow-up.
GOOD TO KNOW
Common questions
What if the customer cannot provide an order reference?
Record that it is unavailable and use other details needed to narrow the search, such as the approximate time, amount and payment route. Follow your shop’s procedure if those details are not enough to identify the right payment.
Does an order confirmation mean payment was successful?
Not necessarily. A submitted order or browser return is not proof of successful payment. Check the available payment outcome and record what it shows.
Should we ask the customer to pay again if the terminal was interrupted?
First check the available payment record and follow your shop’s process for uncertain outcomes. Escalate if you cannot establish what happened rather than assuming the first attempt failed.
What should we send when escalating a query?
Share the order reference, amount, approximate time, payment route, observed status and checks already made through the appropriate channel. Do not include a full card number, security code or PIN.