Three peak-load payment artifacts: the retry double (customer retries a 'failed' payment that actually succeeded), the pending-auth mirage (an uncaptured authorization showing alongside the real charge on the customer's app), and genuine duplicates from race conditions. The first two aren't your bug but become your 12.6 disputes; the response is proactive duplicate-detection sweeps during peak weeks and receipt communication that explains pending-vs-posted. Genuine duplicates: refund the moment detected, never wait for the dispute.
The three artifacts
- The retry double: checkout times out under load, customer sees an error, retries, and both attempts eventually succeed → two orders, two charges. Root cause is load; the customer experience is 'charged twice' — accurately.
- The pending-auth mirage: a failed-then-retried checkout can leave an uncaptured authorization beside the settled charge. Banking apps show both; the authorization drops off in days, but the customer screenshots it first. Not a real double charge — a real dispute anyway.
- The true race: rare double-capture under concurrency. Genuine, rare, and entirely yours to refund instantly.
Detection and response
- The daily duplicate sweep during peak weeks: query same-customer-same-amount orders within short windows; refund genuine doubles proactively with the visibility email. A refunded duplicate never becomes a dispute; a disputed one costs the $15 even though you'd have refunded anyway.
- Receipt clarity on pendings: confirmation emails noting 'you may briefly see a pending authorization alongside this charge — it drops off automatically' preempts the mirage screenshots.
- When the 12.6 files anyway: both-records evidence — one settled charge, one voided/expired authorization, timestamps attached — wins at 80–90%. Aurai assembles duplicate-claim packets from the payment records automatically; the sweep just makes most of them unnecessary.
Frequently asked questions
A customer says they were charged twice but I only see one order — what happened?
Almost certainly a pending authorization from a failed checkout attempt showing beside the real charge. It expires automatically within days; explain it and offer to verify — most 'doubles' are this mirage.
Should I refund duplicates before the customer notices?
Immediately, with a visibility email. A proactively refunded duplicate is a support win; a disputed one costs $15 plus rate impact for money you owed anyway.
Post reflects public documentation and industry surveys as of the publish date. Win rates and other figures are indicative ranges, not guarantees and not Aurai results; outcomes vary by merchant, evidence, and issuer. Visa, Mastercard, American Express, Discover, Stripe, PayPal, and Shopify are trademarks of their respective owners; Aurai is independent and not endorsed by any of them. Network rules change — always verify current official rules before acting on any specific tactic.