Visa 13.2 / MC 4853 · spec §3.3
cancelled subscription chargebacks (Visa 13.2): evidence that wins
Visa 13.2 (Mastercard 4853, recurring) is the “cancelled recurring transaction” code: the cardholder says they cancelled a subscription before it renewed and were billed anyway. It is a code the payment networks are steadily tightening — advance-notice and proof-of-consent expectations are rising — so the evidence has to show the renewal was validly billed under terms the cardholder accepted.
What actually wins it
The evidence that carries a Visa 13.2.
The network rules that decide this code, in plain language — each claim named to its source and flagged where the source is less than primary.
Show the renewal was valid — usage after cancellation is decisive
A cancellation that post-dates the billing period, or usage after it, wins outright.
- You win if there was no cancellation on record, if the billing period ended on or before the cancellation date, or — most decisively — if the account was used after the claimed cancellation date.Visa 13.2 win conditions
- Pair that with a click-to-accept policy log (checkbox event with timestamp and IP) proving the cardholder agreed to the subscription terms.Visa 13.2 — proof of consent
- The Mastercard recurring format specifically wants the goods description, the original authorization date and approval code, a CIT reference, and the click-to-accept terms.Mastercard recurring representment format
- Networks increasingly require advance renewal-notice, so including the reminder email the cardholder received before the charge is becoming close to mandatory.Spec §3.3 — advance-billing notice trend secondary source
The fatal mistakes
What loses a Visa 13.2 on sight.
- On Mastercard, resting your case on “the cardholder never called to cancel” — that bare statement is explicitly invalid, so it wins nothing on its own.Mastercard 4853 invalid statement
- No proof the cardholder ever agreed to recurring billing — without a click-to-accept policy log, the consent half of the argument is missing.Spec §3.3 fatal shape
Proof, published
A real Visa 13.2 packet, redacted.
This is the same structure, exhibits, and citations a live Visa 13.2 dispute gets — with every figure fabricated.
The cardholder disputes a recurring charge as cancelled. The cancellation record, an accepted click-to-accept subscription policy, and an advance renewal reminder show the renewal was validly billed under the terms the cardholder agreed to.
| Amount | USD 19.00 |
|---|---|
| Transaction date | 2026-06-01 |
| Transaction ID | ch_SAMPLE_rec01 |
| Subscription ID | sub_SAMPLE_9f22 |
| Cancellation date | 2026-05-20 |
| Usage after cancellation | 2026-05-28 |
- Exhibit A — Subscription / cancellation record with post-cancellation usage.
- Exhibit B — Click-to-accept policy log with timestamp and IP.
- Exhibit C — Advance renewal-reminder email sent before the charge.
Fabricated sample data — the only merchant is the fictional Example Threads Co.. Read the complete packet: full letter (HTML) · download PDF.
Honest triage
Should you even fight it?
Fight it when you can show usage after the claimed cancellation, a valid click-to-accept consent log, and an advance renewal reminder — that combination is strong and this is another wedge code the bank’s own tools handle poorly. Think twice on a low-dollar subscription with no proof of consent on file: at ~$20 a month you are close to the $25–50 net-negative floor once Stripe’s $15 + $15 fees are counted.
- ~20% of contested disputes overall (Mastercard 2025 issuer-side data)
- 9–17% on true third-party fraud
- ~44% on friendly fraud
- ~47% on sub-$30 items vs ~28% on $300+
- Stripe's $15 dispute fee plus a $15 'countered' fee (US, since June 2025)
Questions
Straight answers on Visa 13.2.
What single fact most reliably wins a Visa 13.2 cancelled-subscription dispute?
Usage of the product or service after the date the cardholder claims they cancelled. It directly contradicts the dispute and is the most decisive win condition, ahead of a cancellation that simply post-dates the billing period.
Why isn’t “the customer never contacted us to cancel” enough for Mastercard?
Because Mastercard explicitly treats the bare statement “cardholder never called to cancel” as invalid. You need positive evidence — a consent log, the billing timeline, and ideally post-cancellation usage — not the absence of a cancellation request.
What does Mastercard want in a recurring-billing representment?
The goods or service description, the original authorization date and approval code, a CIT (cardholder-initiated transaction) reference, and the click-to-accept terms the cardholder agreed to at signup.
Do I need to prove I sent a renewal reminder?
It is increasingly expected. The networks are tightening advance-notice rules for recurring billing, so including the renewal-reminder email the cardholder received before the charge materially strengthens the response.
More reason-code guides
Every code gets its own playbook.
Counterproof publishes one guide and one real packet per reason-code family. Browse the others, or see the full sample-packet library.
Get this for every dispute
Counterproof drafts this packet for you — and shows it before it's sent.
Flat fee, no success cut. Deterministic evidence selection cited to the network rule, with the letter you can edit and a triage verdict when a case isn't worth fighting.