Food delivery disputes are not automatically scams. A real missing item can produce a late complaint, while a dishonest claim can arrive with a neat screenshot. The useful test is whether the order record, story, and requested remedy line up.
That applies to Uber Eats, DoorDash, Grubhub, and similar services. Customers should report genuine problems accurately; drivers and restaurants should preserve the timeline. A chargeback is a separate card-issuer process, not a magic second refund button.
What a red flag actually tells you
One odd detail proves nothing.
A red flag is a reason to verify, not a finding of fraud. Look for contradictions, pressure to leave the app, or a pattern that the order record cannot explain.
| Possible red flag | Why it deserves review | Safer response |
|---|---|---|
| The customer changes the story after support asks questions | The first account and later explanation may not match | Save the full conversation and report the exact inconsistency |
| A non-delivery claim conflicts with the delivery record | The photo, status, instructions, address, and timing may tell different stories | Compare the records carefully; GPS is context, not proof by itself |
| Someone asks for cash, a personal transfer, or an off-app refund | Side deals remove the platform's records and protections | Stop the side conversation and use the app's support route |
| Screenshots are cropped, edited, or missing the order number | The image may not show the original time, amount, or order | Keep original files and submit the complete order record |
| Several claims use different explanations or accounts | A repeated pattern may point to abuse or an account compromise | Send the pattern to the platform instead of confronting the person |
| An email, phone number, address, or password changed before the dispute | The account may have been taken over | Secure the account and notify the card issuer if an unauthorized charge appears |
An expensive order, a new account, a busy dinner rush, or a report made the next morning is not enough on its own. Real deliveries go wrong. Turns out, timing only helps when it sits beside other facts.
A refund request is not the same as a chargeback
These routes overlap, but they are not interchangeable.
| Route | Who handles it | What it usually concerns |
|---|---|---|
| In-app refund or credit request | The delivery platform or its support process | Missing items, wrong orders, delivery problems, cancellations, or other service complaints |
| Credit card billing dispute | The card issuer | A billing error, an unauthorized transaction, or another dispute category recognized by the issuer |
| Account security report | The platform and payment provider | Suspicious logins, changed account details, or an order the account holder did not authorize |
| Fraud report | A government reporting system such as the FTC's tool | A record of suspected fraud or a bad business practice |
Thing is, a platform denial is not a court ruling, and a bank credit is not a finding that a driver or restaurant committed fraud. The decisions run on separate tracks.
For U.S. credit card users, Regulation Z includes rules for billing-error notices. The CFPB's billing-error regulation generally requires written notice to the card issuer's billing-inquiries address within 60 days after the statement containing the error was sent. The rule covers certain unauthorized transactions and other billing errors, but it is not a universal refund law for every delivery complaint.
Use the address and instructions in your card's billing-rights notice. Debit cards, prepaid cards, bank transfers, and buy-now-pay-later products may follow different procedures and deadlines.
Do not call an order "unauthorized" simply because it was late, cold, incomplete, or disappointing. Use that description only when you did not authorize the transaction.
If you are the customer
A precise complaint is easier to review than a general accusation. Say what was missing, where the order was left, when you noticed the problem, and what remedy you are requesting.
- Use the order's support flow promptly. Reporting windows and refund procedures vary by app, order type, account, and market. Follow the instructions shown for that order rather than relying on a general deadline found online.
- Describe one problem at a time. "The bag contained one of two meals" is more useful than "the order was wrong." Add photos of the food, packaging, receipt, delivery location, or damage when they help.
- Save the record before it changes. Keep the order page, itemized receipt, delivery status, messages, photos, support replies, and payment statement. Do not alter the originals.
- Ask for a review through the available appeal route. Include the case number and a short timeline. Repeating the same request through several accounts can make the record harder to follow.
- Consider your card issuer only for a genuine billing dispute. Send the order record and the platform's response if you open a credit card dispute. Tell the issuer about any refund or credit you later receive.
- Treat account takeover as a security problem. Change the password, sign out unknown sessions, check the email and phone number, and contact the card issuer about charges you did not authorize.
A chargeback should not become a way to obtain a second payment after the platform has already refunded the order. If both processes produce a credit, report the duplicate promptly.
If you are a driver or restaurant
Drivers and restaurants are often pulled into a dispute they did not initiate. Their strongest response is a clean factual record, not an argument with the customer.
| Role | Records worth preserving | Practical next step |
|---|---|---|
| Driver | App delivery photo, status changes, timestamps, GPS details shown in the app, pickup notes, and messages | Respond through the platform and explain the sequence without guessing about the customer's motives |
| Restaurant | POS ticket, order ID, preparation and handoff times, item count, bag or seal details, and platform messages | Identify whether the issue concerns preparation, missing contents, the handoff, or delivery, then submit the records through the case |
| Both | Case numbers, support replies, and the original order details | Keep the file private and use the platform's appeal or support process |
Drivers should not ask a customer to falsely mark an order delivered, cancel after handoff, or pay through a personal account. Restaurants should not assume that every missing-item claim is deliberate; packing mistakes and handoff errors happen.
Use only records you are allowed to access. Do not post a customer's name, address, phone number, or private messages in public groups while trying to prove a point.
Build an evidence packet that answers the basic questions
Good evidence connects the order to a time, place, item, and conversation. More screenshots do not always make a stronger case.
| Evidence | What it can show | What it cannot show by itself |
|---|---|---|
| Order receipt and itemization | The items, total, fees, and order number | Whether the food arrived in good condition |
| Delivery photo and app status | The recorded drop-off and approximate timing | Who retrieved the order or what was inside the bag |
| App chat or support messages | What each person reported and when | That every statement in the chat is true |
| Restaurant ticket and preparation record | What was prepared and handed over | That the customer received the correct bag |
| Card statement | The transaction date and amount | Why the service problem happened |
| Doorbell video or witness information | Additional context about the handoff | Facts outside the period or location recorded |
To be honest, a huge screenshot folder is not automatically persuasive. A short chronology tied to the order number often works better: order placed, prepared, picked up, delivered, problem reported, support response.
Keep original files, preserve timestamps where possible, and remove unnecessary personal information before sharing records.
Mistakes that make a dispute harder
Avoid these common errors:
- Describing an authorized order as an unauthorized transaction.
- Filing an app complaint and a card dispute without explaining that both are open.
- Editing screenshots or submitting images from a different order.
- Asking a driver, restaurant worker, or customer to bypass the app.
- Threatening staff or publishing private information.
- Treating an automated denial as proof that another person committed fraud.
Platforms may review or restrict accounts under their own policies. A restriction can affect access even when the underlying facts remain disputed, so use the platform's stated appeal route and keep every case number.
Escalating a suspicious or unresolved case
Start with the order's support page. Ask what information is missing, which decision is being reviewed, and whether the platform has an appeal process for the account or order. Account access and driver deactivation are company-policy issues; a card issuer generally cannot reinstate an app account.
If the conduct looks like an impersonation, payment scam, or broader bad business practice, the FTC's ReportFraud guidance explains how to submit a report. The FTC says the tool accepts reports about scams, fraud, and bad business practices and provides a report number. Keep that number with your case file.
For an unauthorized card transaction, contact the issuer promptly and secure the related account. For an ordinary delivery problem, use the platform record first, then ask the issuer which dispute category, evidence, and deadline apply.
Before sending anything, write down the order number, the key timestamps, the exact problem, and the remedy you want. Attach the original records, then use the support route shown in the order.