Duplicate Transactions | How to Resolve
Caused by network timeouts or staff double-tapping. How to identify, void, and prevent duplicate transactions.
Updated 2026-02-11
Why duplicates happen
- Customer's card declined the first time, staff re-ran it, original came through later.
- Wi-Fi dropped mid-transaction → terminal re-sent the request.
- Staff double-tapped "Charge" on a touchscreen.
How to fix
- Identify the duplicate in your transactions list (same amount, same last-4, within minutes).
- If the batch hasn't closed → Void the duplicate (no fee).
- If already batched → Refund the duplicate.
- Apologize to the customer; refunds typically take 3–10 business days to show on their statement.
Preventing duplicates
For terminals running on Wi-Fi, move to Ethernet at the counter. Train staff to wait for the "Approved" prompt before assuming a tx failed.
Frequently Asked Questions
Will the customer get charged twice on their statement?
Temporarily, yes — but most issuers drop the pending duplicate within 24 hours. If they don't, refund the duplicate so it settles cleanly.
Related
Still stuck? Ask MSC AI
Answers grounded in MSC docs only.
Open a ticket / schedule a call
Get a real MSC specialist in <30 min.
Was this helpful?
Your feedback shapes future articles. Takes 5 seconds.
Ease of use