The charge that arrives after the customer thought they were done

There is a specific kind of chargeback that feels almost personal. A customer signs up, uses your product for a while, and then one quiet month the renewal hits their card. Maybe they meant to cancel. Maybe they did cancel, but through the wrong door — an email to support instead of the account settings, or an app-store cancellation that never reached you. Maybe they simply forgot the trial would convert. Whatever the reason, they look at the line item, decide they didn't agree to this, and call their bank.

This is the recurring billing chargeback, and it behaves differently from the fraud disputes most guides obsess over. No one is claiming their card was stolen. The customer is telling their issuer a narrower, stranger story: I had a relationship with this business, and it kept charging me after I thought it ended. Winning it is less about proving identity and more about proving consent — and proving that you held up your end of an agreement the customer forgot they made.

What the reason code is really asking

When a subscription dispute comes through Visa, it usually carries reason code 13.2, Canceled Recurring Transaction. Mastercard files something similar under code 4841. The label is plain, but the implied accusation has three possible shapes, and your evidence has to answer whichever one applies:

  • The customer says they canceled before the disputed charge posted.
  • The customer says they were never told the subscription would renew at all.
  • The customer says they tried to cancel and you made it impossible, or ignored them.

Notice that none of these is "I never bought this." The issuer already assumes a legitimate relationship existed. So a representment that only proves the original purchase — here's the signup, here's the card, here's the IP address — misses the question entirely. The bank isn't asking whether the customer ever subscribed. It's asking whether the charge in front of them was still authorized on the day it happened.

The quiet rule most merchants never read

Here is the part that surprises people. The card networks have spent years writing rules specifically about recurring billing, and most of those rules are about notification, not about the sale itself.

Visa requires merchants running free trials or introductory offers to disclose the terms clearly, get the cardholder's express consent before the trial converts, and send a notice — with the amount, the date, and how to cancel — before that first full charge lands. For ongoing subscriptions, Visa expects a transaction receipt or reminder that includes cancellation instructions. Mastercard has parallel expectations for negative-option billing. These aren't suggestions. When you skip them, you don't just risk a dispute; you weaken the only ground you'd stand on if one arrives.

The logic is worth sitting with. A subscription is a standing instruction to charge a card on a schedule. The networks treat that standing instruction as something that has to be maintained, not just obtained once. If you can't show that you kept the customer informed along the way, the issuer is inclined to read silence as the absence of consent. The cancellation dispute is, at its heart, a disagreement about whether consent was still alive — and the merchant who documents the relationship over time is the one who can prove it was.

The evidence that actually answers a cancellation claim

A strong response to a recurring billing chargeback is a short story told with timestamps. You're reconstructing the life of the subscription from the moment of signup to the moment of the disputed charge, and showing that consent never lapsed. The pieces that carry weight:

The moment of agreement. The terms the customer accepted, the checkbox or the click, and the timestamp it happened. If your flow disclosed the renewal price and cadence on the same screen where they consented, capture that screen as it looked to them. "They agreed to recurring billing" is an assertion. "They agreed at 14:02 on March 3rd, and here is the language they saw" is evidence.

Proof the cancellation didn't happen — through your channel. This is the crux of code 13.2. If the customer claims they canceled, your record of an active account with no cancellation request directly contradicts it. Your cancellation flow exists; they didn't use it. Say so, and show the log.

Use after the alleged cancellation. Login records, API calls, opened emails, downloaded files — anything showing the customer kept using the service after the date they say they walked away. Few facts undercut a cancellation claim faster than the customer signing in two days later.

The notices you sent. Renewal reminders, receipts, trial-conversion warnings. Each one is proof you honored the network's notification rules and that the charge could not have been a surprise.

Assembled together, these don't argue with the customer. They quietly make the customer's version impossible.

Why honest merchants still lose these

Most subscription chargebacks aren't lost because the merchant was wrong. They're lost because the evidence is scattered across systems that don't talk to each other. The terms-acceptance event lives in your signup database. The login history sits in your product analytics. The cancellation logic is somewhere in your billing provider. The renewal email went out through a marketing tool. On the day a dispute lands, all of that has to be found, matched to one charge, and explained in a coherent narrative — and you have a few days to do it.

There's also a subtler failure. A subscription dispute is often the easiest kind to win and the easiest kind to ignore, because the dollar amount is usually small — one month, one renewal. So merchants let it slide. But subscription products live and die by retention math, and chargebacks count against your dispute ratio whether you contest them or not. A pattern of uncontested cancellation disputes does two kinds of damage: it forfeits revenue you had every right to keep, and it pushes your ratio toward the threshold where processors start asking uncomfortable questions.

Prevent what you can, contest the rest

The best recurring billing chargeback is the one that never gets filed, and prevention here is unusually tractable. Make the renewal price and date impossible to miss at signup. Send the reminder before the charge, not after. Make canceling genuinely easy — a hard cancellation flow generates more disputes than it ever prevents, because a customer who can't find the exit goes straight to their bank. Put a clear billing descriptor on the statement so the renewal is recognizable.

But some disputes will come anyway, because forgetting is human and trials end at inconvenient times. For those, the work is evidentiary, not persuasive. You're not trying to win an argument about whether the customer should have remembered. You're showing the issuer a clean timeline: consented here, charged here, used the product here, never canceled. When that timeline is complete, the dispute resolves in your favor on facts alone.

Where Argeback fits

This is exactly the kind of dispute that rewards speed and structure, and punishes the busy. Argeback ingests your Stripe disputes, recognizes a cancellation claim for what it is, and assembles the timeline — the terms acceptance, the absence of a cancellation, the post-charge usage, the notices you sent — into an evidence-backed response, then files it before the seven-day deadline closes. From your phone, in the gap between two other things.

If subscription chargebacks have become a small monthly leak you've stopped fighting, it may be worth seeing what fighting them properly looks like: argeback.lumenlabs.works.