Understanding Visa Chargeback Reason Code 13.2: Cancelled Recurring

Visa Reason Code 13.2 covers disputes tied to cancelled recurring transactions. It applies when a cardholder says a subscription or instalment was billed after permission was withdrawn. The code often arises from late cancellations, forgotten policies or friendly fraud. Understanding the causes, timelines, and remedies helps merchants protect revenue.

Key Takeaways

‍

• What it means: A cardholder claims you billed a subscription after they cancelled or closed their account.
• Causes: Late processing of a cancellation, unclear policies, account closure, or friendly fraud.
• How to respond: Gather proof of service use. Show the customer broke your stated policy. Provide evidence of a prior refund.
• How to prevent: Offer clear online cancellation. Send renewal reminders. Act on requests fast. Use chargeback alerts.

‍

What is a Visa Reason Code 13.2 Chargeback?

A 13.2 chargeback happens when a cardholder disputes a repeat payment, saying they had already cancelled. Common examples include software licences, gym fees or streaming plans. The dispute belongs to Visa’s “Consumer Disputes” group and replaces the legacy code 41. It covers any case where permission to debit the card was withdrawn. 

‍

This includes if the card or account was closed, or the issuer stopped the account before you attempted the charge. If the merchant processes the debit anyway, the issuer can reclaim the funds and pass them to the cardholder. Because these payments are automatic, a single oversight can trigger multiple future disputes. For subscription businesses that rely on steady income, each chargeback can chip away at margins and brand confidence. Understanding what the code includes and what it does not is crucial to effective chargeback management.

‍

Primary Causes for a Code 13.2 Chargeback

Most disputes begin with a customer action. They may email support, click a “cancel” button, or phone the bank to stop a charge. When the request is not handled before the next billing cycle, a chargeback can follow. Common causes include late processing of cancellation requests or a forgotten subscription. This dispute also arises when customers don't realise a one-off trial will automatically roll into a paid plan. 

‍

Another trigger is account closure. If a cardholder blocks the card after suspected fraud, any further attempts to bill it can be disputed. Issuers can also cancel accounts for their own reasons, and they will file 13.2 if a debit slips through. Finally, friendly fraud appears when a customer knowingly approved the service but files a claim to recover funds. Each cause links to gaps in policy clarity, customer communication, or internal billing controls.

‍

Time Limit for Disputing a Visa Reason Code 13.2 Chargeback

Visa allows a cardholder up to 120 days from the original transaction date, or from the date they became aware of the issue, to raise a dispute. Once the issuer files the chargeback, the acquirer forwards it to the merchant. Merchants then have 30 days to submit a response package with compelling evidence. 

‍

Missing that 30-day window almost always means the case is lost by default. Merchants need disciplined back-office routines to spot incoming disputes and collect evidence quickly. This gives them time to prepare a clear rebuttal. Assigning specific ownership within the finance or customer care team helps ensure deadlines are met.

‍

What 13.2 Means for Consumers & Issuers

For consumers, the code is a safety net. It lets them halt unwanted payments without lengthy arguments, especially if cancellation forms are hard to find. It also protects cardholders when a subscription service ignores a legitimate cancellation request. Issuers, on the other hand, must balance customer care with network rules. 

‍

They investigate proof of cancellation and decide if the dispute fits the 13.2 criteria. If documentation shows the customer used services after the cut-off date, the issuer can reject the claim. But if a merchant cannot prove compliance, issuers debit the merchant account and return funds to the cardholder. Maintaining clear evidence helps issuers resolve cases faster and keep dispute volumes low.

‍

What 13.2 Means for Merchants

Recurring revenue models thrive on predictable cash flow. A 13.2 chargeback disrupts that flow and can carry extra fees. High ratios may also lead processors to raise reserve requirements or, in severe cases, terminate accounts. The code highlights weak points in subscription management. These may be unclear cancellation paths, lagging refund batches, or outdated card data. Addressing these gaps helps merchants fight disputes and also improves customer satisfaction. 

‍

The more effectively merchants communicate with customers, the fewer disputes occur. Implementing transparent policies for recurring payments and sending payment reminders is advisable. If offering a free trial of a service, ensure that explicit consent is received for any charges that follow the initial trial period. This helps ensure customers aren't surprised by unexpected charges.

‍

How to Respond to a Code 13.2 Chargeback

First, confirm the customer’s cancellation history. If they still used the product after the date they claim to have cancelled, you have a solid reason to fight the dispute. Gather logs, access records or delivery confirmations to prove usage within the last billing cycle. If they cancelled late, include a copy of your clearly displayed policy showing notice periods. 

‍

If a refund was already issued, attach proof of the credit with date, amount and authorisation number. If the cardholder has since withdrawn the dispute, add their signed email or ticket. Format the response concisely. Include a cover letter explaining the case, accompanied by organised evidence. Send all files to your acquirer within the 30-day time limit. Staying factual, polite and policy-focused increases the chance of reversing the chargeback.

‍

Proactive Prevention: The Ultimate Defence

Preventing 13.2 chargebacks from occurring costs less than fighting them later. Provide an easy-to-find online cancel link. Send advance renewal alerts. Process cancellations the same day they arrive. Use the Visa Account Updater to refresh expired card data. This helps avoid surprise declines. 

‍

For additional protection, try out Chargeback.io for early warnings of disputes. Once you receive an alert, you can issue a refund before the dispute is finalised as a chargeback. These steps keep your customers happy and your dispute ratio low.

‍