When a guest says your restaurant charged them twice, start with the processor’s record for each payment reference. Two attempts on the POS screen may represent two completed payments, or one completed payment and another attempt that did not complete. A pending item alone is not enough to establish a second completed charge.
Pause before charging again or issuing a correction. Match the order, amount and references, then ask the processor to clarify anything that does not line up. Tell the guest what you are checking and when you expect to update them.
1. Collect identifiers for both attempts
Work from the guest’s report and the order record. Ask for the approximate date, time and amount, and whether the two entries appear as pending or completed in their account. A guest’s account view is useful evidence, but it may not use the same status terms as your processor.
Record the order or check number, location, terminal used, employee on duty and the time zone. Find the payment reference for each attempt in the POS or processor record. If there are receipts, retain their transaction identifiers according to your restaurant’s normal procedures. Note any tip or other adjustment separately so you can compare like amounts.
Do not ask the guest to send a full card number, security code or a photo of the card. Ask your processor what limited information it needs to locate the transactions. If the guest provides a screenshot, suggest obscuring unrelated account information before sharing it through an approved channel.
Keep the order and payment records distinct. One order can have more than one payment attempt; two similar amounts do not, by themselves, prove that two payments were completed. Likewise, a payment record with a different reference might be a legitimate split payment or a separate order. Ask the guest and check the original ticket before treating it as a duplicate.
A restaurant POS can be a starting point for finding the order, but staff should know where the processor’s payment details are accessed and who has permission to see them. If a terminal or connection problem preceded the report, note what staff saw without assuming it caused a duplicate. Keep that note separate from the processor’s actual result.
2. Compare attempts with processor results
For each reference, look at the processor’s status and transaction history. Check whether the amount, time and order match, and whether the record shows an authorization, a completed payment, a reversal, a refund or another result. Status names and timing can vary, so use the processor’s definitions rather than guessing from a label.
In particular, an authorization or pending entry is not automatically a second settled payment. A completed payment is also not the same thing as a refund: a refund is a separate correction that needs its own record. If the screen does not make the distinction clear, ask support to trace both references.
The following is a hypothetical investigation, not a record of an actual transaction. A guest reports two entries of $38 for one dinner check. There was no tip adjustment. The amounts are payment amounts, not processing fees or operating costs; fixed costs, variable fees and exception costs are outside this example.
| Record | What staff find | Next action |
|---|---|---|
| Attempt A | Reference A; $38; processor shows completed | Match it to the dinner check |
| Attempt B | Reference B; $38; processor shows pending | Ask the processor whether it can become a completed payment and when to check again |
| Guest account | Two $38 entries visible; one marked pending | Explain that the pending entry needs clarification |
The table does not establish two completed payments. It establishes one completed payment and a second item whose outcome is still uncertain. Staff should not take another $38 from the guest while that status is being investigated. They should also avoid promising when the pending entry will disappear; ask the processor what to tell the guest and arrange an update.
If the processor instead confirms that both references represent completed payments for the same $38 check, the restaurant has evidence of a $38 overpayment. Follow the processor’s procedure for an authorized correction. If one payment was $38 and the other included a separately approved tip, compare the full transaction details before deciding what amount, if any, needs correction.
3. Escalate uncertainty before another attempt
Give staff a clear stopping point. A declined message, a frozen terminal or a missing receipt can leave people unsure whether to try again. Before retrying, check the order and processor records. If the result is unclear, involve the shift manager and contact payment support using the established support channel.
Have the relevant references, amounts, approximate times, terminal identifier and order number ready. Ask support:
- What is the current status of each reference, and does either represent a completed payment?
- Are the records connected to the same payment attempt, or are they separate attempts?
- Is any pending item expected to change, and when should we check again?
- If there are two completed payments, which correction process applies and which reference should it use?
- What should we tell the guest, and when should we contact support again if the result remains unclear?
Record the support case number, the answer, the person responsible for the next check and the promised update time. If support cannot yet determine the outcome, say so plainly. Give the guest a way to reach the restaurant and avoid a firm deadline unless the processor has supplied one.
If the guest asks for an immediate refund, explain that you are confirming which payment completed so the correction can be linked to the right record. Follow your processor’s and restaurant’s authorized process; do not invent a workaround or ask the guest to make another payment merely to resolve an uncertain status.
For buying or replacing a system, turn this into a practical question: can a manager find transaction references and processor statuses without searching across several screens? Ask how the restaurant POS hardware displays an interrupted attempt and what staff should do before retrying. Also ask who provides payment support and how a manager reaches them during service.
4. Document the outcome and prepare the team
Close the investigation with a short record that another manager can understand. Link the order number to both payment references, the processor’s final status for each, the support case and the date of the guest update. If an authorized refund or other correction was made, record its reference, amount, date and the original payment it relates to. Do not describe a correction as complete solely because someone requested it; check its status through the appropriate system.
Tell the guest the outcome in plain language. For example: “The processor confirmed one completed payment and one pending attempt. We are checking the pending attempt again on the date support provided.” If two payments were confirmed, explain the correction submitted and what the processor says about the next update. Do not include full card details in the note or message.
A daily cash close can reveal that a payment total needs attention, but an aggregate report cannot identify which attempt on a particular check completed. Use the guide to payments and POS reports for the broader reporting decision; keep this investigation tied to the individual references.
Practice the decision path before a busy shift. Use a paper scenario or a vendor-provided training environment with simulated records: one completed attempt and one pending attempt for the same check. Ask a staff member to find the references, state what is known, escalate the uncertain item and draft a guest update. The practice must not create a real payment, send a guest message or dispatch a courier. A live-service pilot is different: it involves actual operating conditions and should follow the provider’s approved procedures, not use a guest’s payment as a test.
Next step: Give your manager this checklist and ask a POS provider to walk through where each reference, status and correction would appear. You can discuss those requirements for your restaurant POS with Fleksa.
Frequently asked questions
Does a pending entry mean the guest was charged twice?
Not necessarily. A pending entry may be an authorization or another unresolved attempt. Check the processor’s status for both references and ask support to explain any uncertainty.
Should staff retry a payment if the terminal freezes?
First check the order and processor records. If the result is unclear, involve a manager and contact payment support before another attempt. A missing receipt alone does not establish that no payment completed.
What should we record after correcting a duplicate payment?
Keep the order number, original payment references, final statuses, support case and guest update. Link any authorized correction to the original payment and record its amount, reference and status.
