Somewhere in a stranger's inbox, a bank alert just lit up a phone. $588. The name next to it is yours. They haven't thought about your product since February, and for one hot second it looks like theft.

They did not forget you because you did something wrong. They forgot you because you worked. The product sat quietly in the background for a year, and nothing in their life reminded them it existed. Then the invoice arrived like a bill from a past self.

That is the shape of an annual subscription chargeback. It is the most emotionally unfair dispute a merchant gets, because the customer is usually not lying. They are surprised. Surprise, to a bank's dispute form, looks a lot like fraud.

Why annual renewals produce the angriest disputes

Monthly charges are small and frequent. A customer sees them often enough that the charge becomes furniture. An annual charge is a single large event after twelve months of silence, so every protective habit fails at once.

Two mechanisms are at work. The first is simple forgetting: the original decision was made a year ago, in a different mood, for a different problem. The second is what behavioral economists call mental accounting. People file a $49 monthly charge under "small recurring cost" and a $588 charge under "big unexpected purchase." Same money over a year, wildly different felt weight.

When the weight lands, the easiest move is the one the bank offers. Calling you means admitting they forgot, which is slightly embarrassing. Tapping "I don't recognize this" or "I cancelled this subscription" takes ten seconds and carries no social cost.

So the dispute you receive is often not a verdict on your product. It is a small act of face-saving. That matters, because it tells you what kind of evidence works: not a combative argument, but a calm, undeniable record that lets the reviewer see what the customer's memory skipped.

What the reviewer is actually deciding

Most of these disputes arrive under a subscription-related reason. On the card networks that means something like Visa's 13.2 (cancelled recurring transaction) or Mastercard's 4841. Stripe surfaces it as "subscription canceled." The claim is that the cardholder ended the arrangement and you charged anyway.

That gives you one narrow question to answer: did the customer cancel before this renewal, and did they agree to be renewed in the first place? Everything you submit should serve those two points. Anything else is noise, and padding the file tends to bury the strong parts.

There are four pieces of proof that carry the case.

1. The agreement to auto-renew. The reviewer needs to see that the customer knowingly signed up for a plan that renews annually. The strongest version is a screenshot of the checkout page as it appeared at the time, showing the renewal term and price next to the pay button, plus a record that they accepted your terms (timestamp, account email, and ideally IP).

2. The notice before the charge. This is the piece merchants most often skip and most often regret. A renewal reminder email sent a week or two before the charge shows you told them, in writing, the amount and the date. Many card-network programs and some local consumer rules expect reminders for long-term plans, so sending one is good practice as well as good evidence. Include the delivery record, not just the template.

3. Proof they never cancelled. Show that your cancellation path existed, was easy to find, and wasn't used. A log showing no cancellation request, no support email asking to stop, no cancellation attempt in your help center is a quiet but powerful absence.

4. Proof they used it. Eleven months of logins, exports, projects, or messages rebuts the idea that this was an unwanted charge. Usage after the stated cancellation date, if they claim one, is the sharpest version.

The trap inside "I already cancelled"

Sometimes the customer genuinely believes they cancelled. They opened the cancel flow, got distracted, and never reached the confirmation. Or they deleted the app, which cancels nothing. Or they cancelled with a competitor, a different tool with a similar name.

Here honesty helps you. Do not claim they never tried. Claim what your records show: no completed cancellation was received. If your funnel logs a started-but-abandoned cancel flow, say so plainly and neutrally. A reviewer trusts a merchant who describes the gap precisely more than one who accuses.

If the cancellation request truly arrived late, after the renewal date, say that too. A clear timeline beats a vague denial. Put the dates in order: signup, reminder sent, charge, first contact, dispute.

What about a partial refund?

Tempting, and sometimes the right call for the relationship. But remember a refund does not automatically close a dispute that's already open. If you refund and also let the dispute proceed, the money can go out twice. If you decide to be generous, handle it through the dispute process rather than beside it, and check the status first.

The deeper question is whether to fight at all. A customer who used the product daily until last week and forgot they bought a year is a very different case from one who used it twice and asked to stop in writing. Fight the first. Consider letting the second go, or better, refunding it before it becomes a dispute.

Your next moves

  • Send a renewal reminder 14 days out, starting with your next batch. State the plan, the exact amount, the date, and a one-click link to cancel. Keep the sent-record in your email tool's logs, since this is your best single exhibit.
  • Screenshot your current checkout page today. Capture the renewal term and price next to the pay button, save it with the date, and repeat whenever you change the page. You can't recreate last spring's version later.
  • Export a usage summary for your five largest annual customers. Last login, key actions, and total sessions in a single page. Learn how long it takes so you're not hunting through dashboards when a dispute lands with a seven-day clock.
  • Audit your cancellation path as a stranger would. Count the clicks from the logged-in app to confirmed cancellation, and make sure every attempt sends a confirmation email. A cancellation without a receipt is a future dispute.
  • Write a short timeline template. Signup date, terms accepted, reminder sent, charge date, last product use, cancellation status. Fill it in as the first move on any annual-plan dispute, then attach the evidence behind each line.

Why this one deserves the time

Annual disputes are the largest tickets in a subscription business, and they are the most winnable because the paper trail is long. A year of logins and an unopened reminder email are hard to argue with. What goes wrong is not the evidence, it is the clock: seven days from a notification you may not see, with records spread across Stripe, your email tool and your app database.

That gap is why we built Argeback. It pulls your Stripe disputes in, drafts an evidence-backed response from the records you already have, and files it before the deadline, from your phone, so a surprising renewal doesn't quietly become a surprising loss. If annual plans are a big slice of your revenue, you can see how it works at argeback.lumenlabs.works.