When a customer says they were charged but your restaurant cannot find the online order, check the payment and the order as separate records. First, avoid asking the customer to pay again. Then identify the ordering channel, verify the payment status with its provider, and search for the order using the available references.
A bank notification alone may not show whether money was captured, while an order confirmation alone may not prove that the restaurant received a usable order. Your next step depends on which records exist and who controls the payment and order.
1. Confirm the payment and order references separately
Start by asking the customer which website, app, or marketplace they used. A customer may have followed a search result to a different ordering channel than the one your staff is checking. Note the approximate order time, restaurant location, amount, and name or email used at checkout. Ask whether they received an order confirmation and, if so, request the order number.
Ask for the payment reference shown on their receipt or confirmation, if available. Do not ask the customer to send a full card number, security code, or other sensitive payment information. A cropped screenshot that hides sensitive details may help identify the amount and status, but follow your provider's secure support process.
Next, check the restaurant's ordering dashboard for the right location and time window. Search by order number first, then by other available details. Check whether the order is new, accepted, canceled, scheduled for later, or attached to another location. Also check the device or system staff normally use to receive orders; an order can be present in one record without appearing where the kitchen expects it.
Separately, an authorized staff member should check the payment provider's record. The restaurant or ordering provider may have access, depending on how the channel is set up. Record the transaction reference, amount, timestamp, and provider's exact status. If you cannot access that record, ask the provider who can.
The distinction matters: a payment reference identifies a payment event, while an order reference identifies the purchase record. They may be linked, but one is not a substitute for the other. Before contacting support, write down what you found in each system and which record is missing.
2. Use the status to decide what happens next
A customer-facing charge notification can represent different stages of a payment. An authorization or pending hold is not necessarily a completed capture. A captured payment is a different situation, and a reversal or refund has its own status and timing. Use the provider's definitions rather than guessing from the customer's bank display.
The table is a quick decision tree. Read the payment status across from the order result, then take the next step without creating another payment or order until you know what already exists.
| Payment record | Order record | Next step |
|---|---|---|
| No matching payment found | No order found | Recheck channel, location, time, and references. Ask the payment or ordering provider to trace the transaction before suggesting another checkout. |
| Authorization or pending hold | No order found | Ask the payment provider whether the authorization will expire or needs action. Explain that the bank display may change; do not describe the hold as a completed refund. |
| Captured payment | No order found | Ask the ordering and payment providers to trace the linked records and confirm who can resolve the payment. Agree with the customer whether a new order is still wanted. |
| Payment found | Order found but not received by staff | Check its location, schedule, and fulfillment status. Confirm whether it has already been accepted or prepared before taking further action. |
If the provider reports a reversal or refund, record its status and reference too. Do not assume that an initiated action has already appeared on the customer's statement. Ask the provider what status to look for and what timing to communicate.
If the guest still wants food, decide how to serve them without duplicating the original transaction. Staff might take a replacement order after agreeing on how it will be paid for, but first check whether the original order could still arrive or be fulfilled. Do not promise the first payment has disappeared until the responsible provider confirms its status. If the guest no longer wants the meal, focus on confirming the payment outcome rather than creating a replacement order.
3. Contact the provider that controls the missing piece
For an order placed through a marketplace, start with that channel's support process and ask who controls the payment and order records. For an order placed through the restaurant's own ordering site, contact the ordering provider and, where appropriate, the payment provider. If you are unsure which company owns a step, ask the ordering provider to identify the payment processor and the escalation route.
Send a concise case rather than separate fragments. Include the restaurant location, channel, approximate time and time zone, amount, payment reference, order reference if one exists, and the statuses you can see. State that staff searched the ordering dashboard and whether any order appeared. Include the customer's desired outcome: receive the meal or have the payment issue resolved.
Ask specific questions:
- Was the payment authorized, captured, reversed, or refunded, and what is the reference for that event?
- Is there an order linked to the payment? If so, what is its number and current status?
- Did the order reach the restaurant's receiving system, and is any further action required to stop duplicate fulfillment?
- Who can initiate or confirm the appropriate payment action, and what should staff tell the customer next?
Hypothetical example: A guest says a $24 order was charged at 6:15 p.m. Staff find no order under the guest's name or at the expected location. The payment dashboard shows a $24 capture with a transaction reference, but no order number is visible. The owner sends those details to the ordering provider and asks it to trace the transaction. The provider's answer determines whether an order exists elsewhere and which party can handle the payment.
This example includes only the $24 customer payment. It does not estimate processing fees, fixed software costs, or exception-handling costs such as staff time. It also does not establish why the order was missing. A capture alone does not tell staff whether the kitchen should prepare food or whether a refund has already been completed.
4. Close the case and reconcile the outcome
Assign one person to own the case through resolution. Keep a short record of the customer contact, the two references, provider case numbers, decisions, and the next follow-up time. Record who agreed to any replacement order and how it was paid for. Share only the information staff need to act.
For a reversal or refund, note whether the provider reports it as initiated, pending, completed, or unsuccessful, along with its reference. Compare that record with the original payment and the restaurant's payment reports. Follow up on unresolved items rather than marking a case closed because a request was submitted. Tell the customer what is confirmed, what remains pending, and when you will check again.
For a fulfilled order, check that the final order and payment records correspond to what the guest received. If there was a replacement, look for two order records or two payments and investigate any mismatch. Deposits in the restaurant's bank account can combine transactions and fees, so a deposit total alone may not identify the outcome of one customer's payment. Use transaction-level reports and ask the payment provider for help tracing exceptions.
Once the immediate case is settled, review whether staff knew where to look and whom to call. A useful practice drill can use a fictional order and a simulated payment status in a test environment, if your providers offer one. Confirm in advance that the drill cannot create a real card payment, guest message, or courier dispatch. A simulation checks the team's steps; it does not prove what will happen during live service.
If you are reviewing your setup, compare the support path for each channel. The online ordering buying guide covers broader buying questions, while the restaurant website page explains one part of a direct ordering setup. Use the checklist above to evaluate your current process, then ask Fleksa about restaurant online ordering and verified US availability for your location.
Frequently asked questions
Should a customer place the order again immediately?
Not until you have checked for the original order and payment. A repeat checkout could create a second payment or order. If a replacement is needed, agree on the payment approach and keep tracking the original transaction.
Does a pending charge mean the restaurant received the money?
Not necessarily. A pending entry may be an authorization rather than a capture. Check the payment provider's status and ask how any hold or reversal will be handled.
Who should resolve a captured payment with no order?
Start with the provider responsible for the ordering channel and identify the payment provider. Ask them to trace the transaction and confirm which party can take the required payment action. Keep the customer updated until the outcome is confirmed.
