Visa 13.2 chargeback (cancelled recurring transaction): what evidence wins

What a 13.2 dispute actually claims

Reason code 13.2 is Visa’s “cancelled recurring transaction” dispute. The cardholder tells their bank one of two things: they cancelled the subscription and were charged afterwards, or they never wanted it to renew. For subscription brands it is the most common dispute, and it is usually the “I forgot I subscribed” case: the customer didn’t recognize the charge, didn’t cancel through you, and called the bank instead.

The bank’s question is simple: did the merchant have a valid, agreed recurring arrangement, and did the customer cancel before this charge? Your response has to answer both with records, not explanation.

You get one submission. On Shopify Payments and Stripe the evidence you send is final, so assemble everything before you submit, and submit before the due date shown in the dispute.

The evidence that wins

Evidence for this dispute splits into what a bank expects to see and what tips a close case. Zevron’s renewal and cancellation playbook treats the first group as required: without it, the response shouldn’t be filed.

The order to argue it in

Banks read dozens of these a day. Lead with the strongest point and keep every claim tied to a document.

1. The cardholder agreed to recurring terms at checkout (terms version, timestamp, checkbox).
2. A pre-renewal reminder was sent before the disputed charge, with a link to manage or cancel.
3. No cancellation request was received before the renewal date.
4. The renewal order was shipped and delivered, or the account was used after renewal.

A response template

Replace the bracketed parts with your own records and attach each exhibit by letter. Keep it factual and short; a long narrative loses the reader.

Cardholder [name] subscribed to [product] on [date], agreeing to recurring billing of [amount] every [interval] (Exhibit A: checkout consent, terms version [x], captured [timestamp]).

On [date], [n] days before the disputed charge, we emailed a renewal reminder to [email] with a link to manage or cancel (Exhibit B).

Our records show no cancellation request, by email, support ticket or account change, before the renewal on [date] (Exhibit C).

The renewal order [order #] shipped on [date] and was delivered on [date] (Exhibit D) [or: the cardholder logged in on [dates] after the renewal (Exhibit D)].

The charge was authorized under the terms the cardholder accepted, and no cancellation preceded it. We ask that the dispute be resolved in the merchant’s favor.

Mistakes that lose winnable cases

• Sending a policy page instead of the cardholder’s own record. The bank wants this customer’s consent, not your general terms.
• No reminder email, or a reminder sent after the charge. The reminder has to predate the renewal.
• Missing the cancellation log. If you can’t show nothing arrived before the charge, the bank assumes something did.
• Arguing the customer should have read the terms. State what they agreed to and when, with the record.
• Submitting a partial response and planning to add more. There is no second submission.
• Contesting a case where the customer really did cancel first. Refund it and fix the cancellation flow; fighting it costs more than it recovers.

Visa Compelling Evidence 3.0 applies to fraud disputes (Visa 10.4), not to 13.2. For a 13.2 dispute, prior undisputed orders help as supporting context but don’t trigger the CE 3.0 liability shift.

The same dispute on other card networks

Customers on other networks raise the same claim under a different code. The evidence and argument above apply to each.

Stop getting 13.2 disputes

Most cancelled-recurring disputes are avoidable. The pattern across subscription brands is the same four leaks:

• Send a reminder before every renewal (especially annual plans and after free trials), and make cancelling one click from that email.
• Make the statement descriptor recognizable so customers don’t dispute a charge they can’t place.
• Accept cancellation everywhere customers ask: email, chat and the account page, and log each request with a timestamp.
• Record consent at checkout with the terms version, so the proof exists before you need it.

Our free chargeback audit reads your disputes export and shows which of these is costing you most. If the customer simply forgot, see what to do when a customer says they forgot they subscribed.

Questions

Related guides