On the first of the month, a customer's card is declined. Maybe it's expired, maybe it's a bad week. They get an email, glance at it, and mean to deal with it later. Later never comes. Nine days on, their card works again, your billing system tries once more, and the charge goes through.
To you, that's a subscription doing what it was built to do. To them, a charge has appeared out of nowhere, on a date that matches nothing they remember. They don't think "my payment finally cleared." They think "I never agreed to this." So they open their banking app and tap Dispute.
This is the failed payment retry chargeback. It's easy to lose, because it combines a customer who feels ambushed with a merchant who feels obviously in the right.
Why a late success feels like theft
People anchor on the date a payment should happen. A charge that arrives on the expected day gets absorbed into the month's background noise. A charge that arrives on an unexpected day is read by the brain as an anomaly, and anomalies in a bank statement feel like danger.
There's a second pull. The declined attempt registered as a small failure, and the customer's mind filed it as resolved: it didn't go through, so nothing happened. Psychologists describe this kind of incomplete-but-forgotten task as something the mind quietly closes when no reminder keeps it open. When the money moves anyway, it reads as a violation of that closed loop.
That's why the dispute is rarely about the product. It's about surprise. And surprise is something you can address with evidence, because the reviewer is asking one question: did this cardholder agree to be charged this amount, and was the timing of the charge consistent with that agreement?
What the reviewer is actually weighing
A card dispute reviewer doesn't know what Smart Retries are. They see a charge dated on the 10th and a cardholder who says they didn't authorize it. Without context, the gap looks suspicious.
The merchant's job is to turn that gap into a story the reviewer can follow in under two minutes:
- The customer agreed to recurring billing.
- The charge was due on a specific date.
- That first attempt failed for a documented reason.
- The customer was told, in writing, that you would try again.
- A later attempt succeeded, on a schedule you can show was part of the original terms.
Every link in that chain needs a document behind it. A gap in any link is where the "I didn't authorize this" claim slips through.
Link one: the original agreement
A retry is not a new charge. It's the same charge, attempted again, and it inherits its authority from the original signup or plan selection. So the first piece of evidence is still the foundation: the checkout or subscription confirmation showing the customer chose a recurring plan, the price, and the billing cadence.
If your terms mention that failed payments are retried, include that exact passage, with the date the customer accepted the terms. Many merchants never think to add this line to their terms. If yours doesn't have it, it's worth fixing going forward, but don't claim it exists in a dispute if it doesn't. Reviewers can tell, and an overreach costs you credibility on everything else.
Link two: the failed attempt, in plain sight
The most persuasive exhibit is often the failure itself. In your Stripe dashboard, the invoice or payment record shows the original attempt, its date, and the decline. Screenshot that timeline so the reviewer sees attempt one fail and a later attempt succeed, with both attached to the same invoice.
This matters because it answers the claim that the charge came from nowhere. It didn't. It came from an invoice the customer was already liable for, and the earlier decline proves the billing was live before the dispute.
Keep the screenshot tight. Show the invoice number, amount, dates and outcomes of each attempt. Crop out everything else.
Link three: proof the customer was told
This is where most retry disputes are won or lost. If you sent a failed-payment email, that email is your best evidence that the customer wasn't ambushed. Include:
- The email itself, showing the send date and the wording about the declined payment and next steps.
- Any delivery or open record your email tool keeps.
- Any follow-up reminders, such as an upcoming-retry notice.
Be honest about what an open record proves. It shows the email was likely opened, not that the customer read it carefully, so present it as supporting detail rather than a certainty. The send itself, to the address on file, is the stronger fact.
If you never sent a notice, say nothing about one. Lead with the agreement and the invoice timeline instead, and fix the gap afterward.
Link four: the success is consistent with the terms
Finally, show that the retried charge matches what was owed. Same amount as the original invoice, same customer, same card. A retry that quietly charged a different amount, or added a fee the customer never saw, is a different dispute and a weaker one. If the amounts match, say so in one line.
If the customer used your service during the gap, add that. Login or usage records spanning the days between the decline and the successful retry show they were still receiving what they were billed for. For a deeper look at that kind of proof, a usage-based approach works well with this one.
When you should let it go
Sometimes the honest read is that the customer is right to be upset. If your retry fired after they'd cancelled, or after they'd emailed asking you to stop, the retry may have been a mistake on your side. Check the cancellation record before you build anything. If the cancellation predates the successful charge, refund it rather than fight. A dispute lost on an obvious facts gap teaches the reviewer to doubt you next time.
Your next moves
- Open your last three failed-then-recovered invoices today. For each, check whether the customer received a failed-payment email and note the date it went out. This tells you whether your best exhibit exists.
- Save a template screenshot of an invoice timeline. Capture one showing attempts, dates and outcomes, so you know exactly which view to grab when a dispute arrives.
- Add one sentence to your terms. State that failed payments may be retried automatically over a period of days, and make sure the customer accepts the terms at signup.
- Check your cancellation records against retry dates. Before disputing any retried charge, confirm no cancellation request came earlier.
- Make the failed-payment email unmissable. Put the amount, the plan name and the next retry window in the subject line or first line, so a quick glance is enough to remember.
Where this fits
Retry disputes are the kind that get lost to timing, not to substance. The facts are usually on your side, but they're spread across a billing timeline, an email tool and a terms page, and the deadline keeps running while you collect them. Argeback pulls a dispute's invoice history, attempts and customer record into one draft response and files it from your phone before the window closes, so a late-landing retry doesn't become an automatic loss. If that sounds useful, you can look at it at argeback.lumenlabs.works.