When a guest says an online payment went through twice, check each payment attempt before promising a refund. Two entries can represent two settled payments, but one or both may be pending authorizations. An order confirmation alone does not establish what settled.
Start with the order reference and the approximate payment time. Match every related attempt in the payment provider's records, note its current status and amount, and escalate any result you cannot interpret. Tell the guest what you have verified, not what you assume their bank will do.
1. Match the order to each payment attempt
One order can have more than one payment attempt. A guest might retry after a slow page, an unclear error or a request to use another payment method. The investigation is about the money associated with those attempts, even if the kitchen received only one order.
Ask the guest for the order number, the approximate time, the amounts shown and what they see next to each entry, such as pending or completed. The last four digits of the card can help identify a payment when needed. Do not ask the guest to send a full card number, security code or bank login.
Next, find the order in the ordering system and note its total, time and any payment references displayed. Check the payment provider's records for matching attempts. Depending on the setup, the manager may need access to a separate provider dashboard or help from the account owner.
Record a separate reference for each attempt. Match the amount, time and available card identifier, but do not rely on amount alone: two guests can place orders for the same total. If a reference or timestamp does not match, keep looking rather than attaching an unrelated transaction to the complaint.
For a restaurant online ordering setup, ask who can see payment attempts, who can issue refunds and which provider handles payment questions. The person answering the phone may be able to collect details without having permission to make financial changes.
2. Read the payment status before taking action
A pending authorization is a request to reserve funds; it is not by itself proof that the restaurant received a settled payment. A captured payment has been submitted for collection, but the provider's terminology and reporting stages matter. Look for the provider's settlement or funding record before describing a payment as settled.
The guest's bank view and the restaurant's provider view can use different labels and update at different times. A pending entry may later disappear, but do not promise a release date. The guest's bank controls what appears on its statement, while the payment provider can help explain the restaurant-side transaction.
Use the table as a starting point, not as a substitute for the provider's definitions. Each row describes what staff can say or do after matching the relevant records.
| What you find | What it establishes | Next step |
|---|---|---|
| One settled payment and one pending authorization | One payment is verified as settled; the other entry is not verified as a second settlement. | Check the pending attempt's provider status and explain the distinction to the guest. |
| Two matched settled payments for one intended purchase | Two payments have settled; the order and attempt references still need to be confirmed. | Follow the restaurant's approval process and ask the provider about the appropriate refund. |
| Attempt is captured but settlement is unclear | A capture is recorded, but the final settlement result has not been verified. | Check the provider's reporting definitions or contact support. |
| Guest sees an entry that staff cannot match | The restaurant has not identified the transaction. | Collect safe identifying details and escalate; do not refund an unrelated payment. |
Do not treat a pending hold as a completed refund, either. Releasing or voiding an authorization and refunding a settled payment are different actions. Ask the provider which action is available for the specific attempt and what confirmation staff should expect.
3. Escalate an unclear or duplicated payment
Send the provider enough information to locate each attempt: merchant account or location, order reference, transaction references, amounts, approximate times and the statuses visible to staff. Include the last four card digits only if requested through an appropriate channel. Keep sensitive payment details out of ordinary email and internal notes.
Ask direct questions: Did either attempt settle? If both did, which transaction should be refunded? If one remains pending, is there an action the restaurant can take, or must it wait? What reference will confirm the next action? Ask when to check again, rather than promising the guest a particular bank posting time.
Hypothetical example: A guest places one $28 order and retries after the payment page appears to stall. The guest sees two $28 entries. The restaurant finds attempt A, marked settled for $28, and attempt B, marked pending for $28. That is $28 verified as settled, not $56 verified as settled. The second $28 is a pending authorization in this example, not an additional confirmed sale.
The manager records both references and asks the provider whether attempt B can be voided or needs further monitoring. Until the provider confirms an action or a later settlement, the manager should not describe the pending entry as a second settled charge. If both attempts later appear as settled, the manager can follow the restaurant's refund approval process for the duplicate payment.
This example covers the payment amounts only. It excludes processing fees, other operating costs and any exception-handling costs; it is not a refund or fee calculation. Real statuses may differ, and the provider's records must determine the outcome.
Practice the decision with a simulated scenario before a busy shift: give staff fictional references and statuses, then ask them to identify what they know, what remains unclear and whom they would contact. Use a training environment or a paper exercise. It must not create a real payment, send a guest message or dispatch a courier. A live service pilot is a separate activity using real orders and the restaurant's normal controls; it is not required for this practice.
4. Record the result and close the loop with the guest
A short, consistent record helps the next employee continue the investigation without asking the guest to start over. Store it in the restaurant's approved location and limit access to staff who need it. Avoid retaining full card details or screenshots containing sensitive information.
Use this checklist for each reported retry:
- Identify: Record the order reference, location, order total and approximate time. Ask what entries the guest sees.
- Match: List each relevant payment attempt with its provider reference, amount and current status. Flag anything that does not match.
- Verify: Check which attempts are authorized, captured or settled using the provider's definitions. Note the time of the check.
- Escalate: Assign an owner for unclear statuses or a possible duplicate settlement. Record the provider case reference and next check time.
- Act: If a void or refund is appropriate, follow the restaurant's permission and approval process. Record the action and its confirmation reference.
- Update: Tell the guest what was verified, what remains pending and when the restaurant expects to check again.
A useful update might be: “We found one settled payment and another attempt listed as pending. We have asked our payment provider to check the pending attempt, and we will follow up after our next check.” If the result is still unknown, say so. If a refund is issued, share the confirmed action without guaranteeing when it will appear on the guest's bank statement.
Before changing providers, check how payment references move between the ordering screen and the provider dashboard, how staff permissions work and how support handles an unmatched attempt. The online ordering buying guide can help frame those questions, while the restaurant website page covers the guest-facing ordering context.
Use the checklist on your current setup, identify who owns each escalation, and ask Fleksa about its ordering setup and verified US availability if you are evaluating a change.
Frequently asked questions
Do two entries on a guest's statement mean two payments settled?
No. One or both entries may be pending. Match the attempts and check the payment provider's settlement records before deciding whether there was a duplicate settled payment.
Should staff refund a pending authorization?
Not without checking the provider's status and available actions. A pending authorization and a settled payment are different; a void, release or refund may apply in different circumstances.
What if the restaurant cannot find the second entry?
Recheck the order details and safe identifiers, then contact the payment provider with the information available. Tell the guest the entry is unmatched rather than claiming it is or is not a duplicate charge.
