What does Visa 13.5 mean?
The cardholder told their bank that what they were sold was not what they agreed to. Not a fraud claim, and not quite a cancellation claim either: a claim about the terms themselves.
In subscription billing this almost always means one thing: a trial or introductory offer converted into a paid charge, and the customer says the conversion was never made clear.
What causes a 13.5 chargeback?
- Trial terms that lived in fine print instead of next to the signup button.
- A free trial converting at a price or date the customer didn't expect.
- An introductory rate stepping up to a full rate without a reminder.
- Marketing that promised one thing and billing that did another.
Why do subscription businesses get 13.5?
13.5 is the code that prices bad trial UX. Every one of them is a customer who hit the first real charge and felt tricked, whether or not the terms were technically on the page.
The line between 13.5 and 13.2 is worth knowing: 13.2 says I canceled and you charged me. 13.5 says I never understood I would be charged at all. Different claim, different evidence, same root: the customer didn't see the charge coming.
Can a chargeback alert stop 13.5?
Alerts catch 13.5 before it becomes a chargeback.
The customer calls their bank first, which is when Visa RDR and CDRN see the dispute. Refund through the alert and it resolves before filing, staying out of the VAMP dispute count. Then fix the disclosure: an alert saves the dispute, but only clearer trial terms stop the next customer from feeling tricked.
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.5 dispute?
You win 13.5 by proving the terms were clearly disclosed and accepted. Send:
- A capture of the signup page as the customer saw it, with the trial price and conversion date visible.
- The acceptance record: when and how the customer agreed to those terms.
- The reminder email, if you sent one before the conversion charge.
- Usage records showing the customer kept using the service after converting.
- Your refund and cancellation policy as displayed at purchase.
Your processor sets your response deadline, usually 20 to 30 days from the chargeback.
How do you prevent 13.5?
- Put the price and the conversion date next to the signup button, not in a linked page of terms.
- Send a reminder before the trial converts, with the amount, the date, and a cancel link.
- Use Visa's End Trial allowance: since April 2026, the first charge after a trial can carry an End Trial indicator in the statement line, so the charge explains itself.
- Make the first invoice say what it is: trial ended, plan started, here is how to cancel.
The cardholder gets 120 days to file. You usually get 20 to 30 days to respond. And the dispute counts the day it files, win or lose, which is why prevention beats response.
FAQ
What is the difference between Visa 13.5 and 13.2?
13.2 is a cancellation claim: the customer says they canceled and were charged again. 13.5 is a terms claim: the customer says they never understood they would be charged at all. Trial-conversion disputes usually arrive as 13.5; post-cancellation rebills arrive as 13.2.
Does 13.5 apply to free trials?
It is the code free trials generate. When a trial converts to a paid subscription and the customer says the conversion was never made clear, the bank files it as misrepresentation. Clear pricing at signup and a pre-conversion reminder are the two fixes.
Can chargeback alerts stop 13.5?
Yes. 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 keeps it out of the VAMP dispute count.
What evidence wins a 13.5 dispute?
Proof of clear disclosure: the signup page showing the trial price and conversion date, the customer's acceptance record, any pre-conversion reminder you sent, and usage after the conversion. The dispute is about what the customer was told, so the evidence is what they saw.
Checked against Visa's Dispute Management Guidelines (June 2024) and Visa's Merchant Data Standards effective April 2026. Last reviewed August 28, 2026.