A recurring charge that gets disputed is a different animal from a one-off purchase gone wrong. The customer agreed to the first charge, used the service, and is now contesting a renewal they either forgot about or could not cancel cleanly. From the merchant seat, the dispute is rarely about whether the transaction happened. It is about whether you can prove the billing relationship was still live and authorized at the moment you charged.
The sibling course covers the four-party dispute system end to end. Here we stay in the recurring lane: how a subscription chargeback enters the lifecycle, the codes that mark it as recurring, and the clock that runs the moment it lands.
Where a recurring dispute sits in the lifecycle
Every card dispute moves through the same skeleton: the cardholder raises a claim with their issuer, the issuer files a chargeback against your acquirer, you get a window to respond with evidence (the merchant response, which Mastercard calls second presentment and Visa calls a dispute response), and if the issuer rejects your response the case can escalate to pre-arbitration and arbitration. We cover representment mechanics in the next module and the escalation path after that.
What makes the recurring case distinct is the trigger. Most subscription disputes start when a renewal hits a card the customer thought was no longer on the hook. The customer did not contest a fraudulent charge. They contested a charge they believe should not have run because they canceled, the account closed, or the price changed without their say-so.
That framing matters because it tells you what evidence wins. You are not proving identity. You are proving a continuous, consented billing relationship and that no valid cancellation reached you before the charge.
The reason codes that flag a recurring charge
The reason code the issuer assigns tells you which story the customer is telling and which clock you are on.
Visa 13.2: Cancelled Recurring Transaction
Visa routes cancelled-subscription claims to reason code 13.2. It applies when the cardholder says you billed a recurring transaction after they submitted a cancellation, closed the account, or withdrew permission to charge the card on file. It also applies when you did not process a cancellation in the timeframe your own terms promised.
Two numbers anchor this code. The cardholder generally has up to 120 calendar days from the transaction date to file. Once the chargeback lands, the acquirer or merchant has 30 days to respond with representment. Miss that 30-day window and the case is effectively lost by default.
Mastercard: 4853, formerly 4841
Mastercard historically used reason code 4841 ("Canceled Recurring or Digital Goods Transactions") for the same pattern. Mastercard has consolidated that older code into 4853, Cardholder Dispute, and instructs issuers to file under 4853 instead. You will still see 4841 referenced in legacy documentation and older processor dashboards, so recognize it, but expect new recurring disputes to arrive as 4853.
Mastercard's merchant response deadline is 45 days from the chargeback notification, and that window applies across reason codes. The escalation path that follows, pre-arbitration and arbitration, lives in a later module.
A practical note on both clocks: the deadline is measured from when the chargeback is created, not from when it reaches your dashboard. Your acquirer and processor consume part of that window receiving and forwarding the case, so your real working time is shorter than the headline number. Treat 30 days as roughly three weeks of usable time, and 45 as a month.
A worked example
A DTC fitness app bills $19.99 monthly. A customer signs up in January, uses the app through April, and cancels through the in-app flow on May 2. Your system logs the cancellation and stops billing. But a charge for $19.99 already settled on May 1, one day before the cancel, and the customer disputes it.
The issuer files Visa 13.2. The chargeback is created on May 20. Your 30-day clock starts there, so your representment is due by roughly June 19, and your real working window closes earlier because the acquirer needs its own handling time.
Your defense is the timeline. You hold the signup timestamp and the accepted terms, the IP and device that logged in across four months of sessions, the cancellation log showing May 2, and the billing log showing the disputed charge settled May 1. The charge predates the cancellation, the relationship was live, and the customer used the service in the period billed. That is a defensible representment.
Now flip one fact. Suppose the cancellation actually arrived April 28 and your dunning queue billed anyway on May 1. You have no defense, and you should not fight it. You should refund, fix the cancellation-to-billing handoff, and treat the dispute as a signal that your cancel flow has a race condition.
The records that make or break the response
The codes above all turn on the same question: can you show what the customer agreed to and what reached you before you charged. Build the case before the dispute, not after.
Keep, at minimum: the consent record for recurring billing (terms accepted, date, amount, cadence), session or usage evidence showing the customer used the service in the billed period, your cancellation log with timestamps, and proof you honored your own stated cancellation timeframe. A 13-month retention floor is a sensible default since it covers the full 120-day filing window plus the arbitration tail.
If your terms promise to process cancellations within a set period, that promise becomes your deadline. If you state no timeframe, the schemes expect you to stop billing on the spot. A cancellation you logged but kept billing against is a loss, every time.
Closing takeaway
A recurring-charge dispute is won or lost on two things: a clean, timestamped record of consent and cancellation, and a calendar discipline that treats the response deadline as shorter than it looks. Know which code you are on (Visa 13.2, Mastercard 4853), start the clock from chargeback creation rather than dashboard arrival, and only fight the cases where the charge genuinely predates a valid cancellation. The next module takes those records into the representment file itself.