Code13.2TypeConsumer disputeFiling window120 daysMonitoringDispute count (VAMP)What does Visa 13.2 mean?
The cardholder's bank is claiming one of two things: the customer withdrew permission for the recurring charge and you billed anyway, or you had been told the account was closed and charged it regardless.
A customer who says they never agreed to be charged at all, such as when a free trial converts, is making a different claim with a different code: 13.5.
Visa files it under consumer disputes, not fraud. The bank isn't claiming a criminal used the card. It's passing along a service complaint: this charge shouldn't have happened.
What causes a 13.2 chargeback?
- A cancellation request that was never actioned, for example because it went to an inbox nobody monitors.
- One more rebill going out after the customer canceled, because billing stops at the end of the cycle instead of immediately.
- A cancellation flow hard enough that the customer gave up and asked their bank instead.
- A notice period or minimum term the customer didn't know they had agreed to.
Why do subscription businesses get 13.2?
Every 13.2 is a customer who tried to leave and ended up at their bank instead of your cancel button. This code lands on subscription businesses for a simple reason: you cannot get a canceled-recurring dispute without recurring billing.
The pattern to watch is the race: the customer cancels, one more rebill escapes, and their dispute reaches the bank before your refund does. The money was probably coming back either way. The dispute mark on your ratio didn't have to.
Can a chargeback alert stop 13.2?
Alerts catch 13.2 before it becomes a chargeback.
A customer disputing a canceled subscription calls their bank first, which is exactly the moment Visa RDR and CDRN see it. Refund through the alert and the dispute is resolved before it files: no chargeback, and it stays out of the VAMP dispute count. The alert buys you the save; fixing the cancellation flow stops the next one from existing.
Alerts are one of the two levers here. See how RDR, CDRN and Ethoca work together, and check where your ratio stands before the letter checks it for you.
How do you respond to a 13.2 dispute?
You win 13.2 by proving the charge came before any valid cancellation, or that no cancellation ever arrived. Since April 18, 2026, Visa treats a 13.2 as invalid when the customer canceled after the date of the charge, so the two dates can end the dispute on their own. Send:
- The date and channel of any cancellation request you received, or a statement that none exists in your records.
- The terms the customer agreed to at signup, with the cancellation policy highlighted.
- The charge date next to the cancellation date. If the customer canceled after the charge, Visa's rules make the 13.2 invalid for disputes processed from April 18, 2026.
- If the bank used 13.2 for a fraud claim or for a purchase the customer made themselves rather than a recurring rebill, say so. Visa lists both as invalid under 13.2.
- Usage logs showing the customer kept using the service after the cancellation date. Visa treats that date as the last day the cancellation let them use the service, so use within a period they had already paid for doesn't count.
- Your cancellation confirmation email, if the customer did cancel and is disputing an earlier valid charge.
Your processor sets the deadline, and it varies: Stripe usually gives 7 to 21 days, and Mastercard says processors' deadlines average 10 to 35 days. The date on your dispute notice is the one that counts.
How do you prevent 13.2?
- Make canceling self-serve and instant. Every step between the customer and the cancel button is a step toward their bank.
- Stop billing the moment the cancellation lands. Honoring the paid period is fine; charging again is how 13.2 happens.
- Send written cancellation confirmation. It is the evidence that ends the dispute before it starts.
- Put a cancellation link in every receipt and renewal reminder, so the bank is never the easier path. Visa and Mastercard both require an online way to cancel, and our subscription rules guide lists what else they require.
The cardholder gets 120 days to file. Your window to respond is far shorter: Stripe, for example, usually gives 7 to 21 days. And the dispute counts the day it files, win or lose, which is why prevention beats response.
FAQ
Is reason code 13.2 fraud?
No. Visa classifies 13.2 as a consumer dispute, not fraud. The cardholder is saying the charge shouldn't have happened after their cancellation, not that their card was stolen. It counts toward your VAMP dispute ratio, but it does not generate a fraud report.
How long do I have to respond to a 13.2 chargeback?
Your processor sets the exact deadline, and it varies: Stripe usually gives 7 to 21 days. The cardholder's side is longer: they can dispute a charge up to 120 days after it was processed, which is why a cancellation from months ago can still surface today.
Can a customer file 13.2 for a charge made before they canceled?
Not since April 18, 2026. For disputes processed from that date, Visa treats a 13.2 as invalid when the customer canceled after the date of the charge. Where a 13.2 is valid, the dispute is limited to the unused portion of the service.
Can chargeback alerts stop 13.2?
Yes, and it is one of the codes they stop best. The customer contacts their bank first, so RDR and CDRN see the dispute before it becomes a chargeback. Refunding through the alert resolves it, and it stays out of the VAMP dispute count.
Does winning a 13.2 dispute remove it from my ratio?
No. Winning recovers the money, but the dispute already counted the day it was filed. Card networks measure how many disputes you get, not how many you win. That is why preventing 13.2 beats fighting it.
Checked against Visa's Core Rules (April 2026) and Visa's Dispute Management Guide for Merchants (October 2026). Last reviewed October 23, 2026.
