Why food orders are prone to duplicates
Food orders are frequent, small and often placed under pressure. A slow confirmation screen leads to a second tap. A failed payment retries. A pre-authorisation shows as a debit before it is released. The result is two entries of the same amount on the same day, which look like a double charge but may or may not be.
A calm check separates the real duplicates from the temporary ones.
Step one: compare the two entries
Open both transactions and note the time, amount and merchant string. If both are identical and a few seconds or minutes apart, one may be a duplicate. If their times are very different, or one amount differs slightly, they may be separate orders.
Check the order history in the app that placed the order. Does it show one order or two?
Step two: wait for pending entries to settle
Some payments appear first as a hold and are released within a few days. If the app shows a single order and the statement shows two debits, one may be such a hold. Give it the time stated by the bank or app before escalating; typical settlement periods vary, so check the official guidance.
Do not assume it is gone. Set a reminder to look again in a few days.
Step three: gather evidence
If a duplicate persists, collect the order confirmation, a screenshot of the order history and the two transactions. Note dates, times and amounts. Evidence makes the conversation with support shorter and more productive.
| Item | What to note |
|---|---|
| Order confirmation | Order number, total |
| Order history screenshot | One order or two |
| Bank entries | Dates, times, amounts |
| Support contact | Date and reference number |
Step four: raise it with the right party
Contact the app’s support through its official channel, with the evidence. If the issue is not resolved, contact the bank or card issuer to ask about their process for disputed charges. Procedures and timeframes differ, and the official channels give the authoritative answer.
Never share card numbers, PINs or one-time codes with anyone who contacts you unprompted about a refund. Genuine support will not ask for them.
Record it in the app
Mark the second transaction with a note such as “possible duplicate, raised on this date”. Do not delete it until the refund is confirmed, because the statement and the records must continue to match. When the refund arrives, link it to the original charge so that the net cost is correct.
Prevent the next one
Wait for the confirmation screen to finish before tapping again. Check the order history if the app seems stuck. And a monthly scan for identical entries on the same day catches most problems early, while they are still easy to resolve.
Subscriptions that look like duplicates
Some repeated debits are legitimate: a weekly box, a membership renewal and a one-off order from the same app can land close together. Before raising a dispute, check whether any recurring plan is active in the account settings. If so, the second charge may be expected. A quick look at the subscription list prevents an unnecessary complaint and may even reveal a plan that should be cancelled.
Protecting yourself from false refund messages
After a payment problem, scammers sometimes send messages promising a refund if you share a code or install an app. Genuine refunds do not need your PIN, password or one-time code. If a message asks for any of these, ignore it and contact the bank or app through its official channel. Keeping this rule in mind removes the pressure to act quickly, and a calm pause is often the best protection a household has against fraud of any sort.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


