Visa Reason Code 13.2: Cancelled Recurring Transaction

What Visa Reason Code 13.2 Means

Visa reason code 13.2, titled Cancelled Recurring Transaction, is filed when a cardholder claims they cancelled a recurring billing arrangement but continued to be charged. This code applies to any transaction that is part of an ongoing payment relationship — subscriptions, memberships, monthly retainers, SaaS plans, and any other model where the same card is billed on a recurring schedule.

The cardholder's position in a 13.2 dispute is one of three things: they cancelled and should not have been charged; they never authorized recurring charges in the first place; or the merchant's cancellation process was too difficult or unclear for them to complete. All three scenarios result in the same code, but require different defense approaches.

Cross-Network Equivalent Codes

Common Trigger Scenarios

• Cancellation processed late or not at all. The customer submitted a cancellation request through your portal, email, or support team, but the system failed to process it and the next billing cycle charged them anyway. This is the most straightforward scenario and almost always results in a merchant loss if the cancellation request is documented.
• Free trial conversion without clear disclosure. The customer signed up for a free trial, was not clearly informed it would auto-convert to a paid subscription, and disputes the first paid charge. Visa rules require clear, conspicuous disclosure of recurring charge terms at enrollment.
• Difficult cancellation flow. The merchant's cancellation process requires excessive steps, phone calls, or waiting periods. The customer attempted to cancel, gave up, and disputed the next charge. Regulators and networks both frown on intentionally difficult cancellation flows.
• Annual renewal surprise. The customer forgot they had an annual subscription and disputes the renewal charge. If they cancelled after the renewal processed, the dispute still covers the charge they did not expect.
• Friendly fraud / buyer's remorse. The customer simply wants out of a subscription they no longer value and finds disputing faster than cancelling. Continued service access logs are your primary defense here.

Key Deadlines & Timeframes

Evidence You Will Need

• Signed or accepted recurring billing authorization — the agreement (checkbox, signed terms, or recorded consent) showing the customer authorized recurring charges at enrollment
• Terms of service with recurring billing language clearly disclosing the billing frequency, amount, and cancellation process, accepted by the customer at the time of signup
• Cancellation policy documentation showing the process the customer was required to follow and evidence they did not complete it
• Service access logs showing the customer used the service or accessed the platform during the billing period they are disputing
• Cancellation request records (or absence thereof) — if the customer claims they cancelled, you need to show no valid cancellation request was received before the charge
• Prior billing history showing previous undisputed charges from the same recurring agreement, establishing that the customer had accepted and paid for the same billing arrangement before

How Merchants Lose This Dispute

• No documented recurring billing authorization at enrollment. If you cannot produce evidence that the customer agreed to recurring charges at signup, Visa will almost always side with the cardholder. A checkbox buried in terms that the customer scrolled past is not sufficient — you need affirmative, traceable consent.
• Unclear or buried cancellation terms. If your cancellation policy requires the customer to call a phone number, navigate five menu layers, or wait 30 days for processing, Visa will view this as an unreasonable barrier. Clear, easy cancellation is a network requirement.
• No service access logs. Claiming the customer "had access" to the subscription without timestamped logs proving they actually used it is not compelling evidence. Usage logs are what separate winnable 13.2 cases from losses.
• Fighting disputes you should refund. If the customer cancelled and you charged them anyway due to a system error, accept the chargeback or issue a proactive refund. Fighting a dispute you know is valid damages your chargeback ratio without a realistic chance of winning.

Response Framework Overview

1. Establish the recurring agreement. Lead with the signed or accepted authorization showing the customer agreed to recurring charges, the terms disclosed, and the billing frequency.
2. Address the cancellation claim directly. If no cancellation request was received, present the absence of a record as evidence. If a request was received, show it was processed within your stated policy timeline.
3. Demonstrate service access. Present logs showing the customer used the service during the disputed billing period, establishing that value was delivered even if they later claimed they cancelled.
4. Show prior undisputed billing history. Previous recurring charges accepted without dispute establish that the customer understood and accepted the billing arrangement.

Prevention Tips

• Use explicit recurring billing authorization at signup. A standalone checkbox or consent step specifically for recurring charges — separate from general terms acceptance — creates the clearest evidence trail.
• Send renewal reminders before annual or large charges. An email 7–14 days before a renewal processes gives customers the opportunity to cancel without disputing, and creates evidence that they were informed.
• Make cancellation genuinely easy. A self-serve cancellation portal that processes immediately is the single most effective way to reduce 13.2 chargeback volume. Difficult cancellation flows produce chargebacks, not retained customers.
• Send cancellation confirmation with timestamp. Whenever a customer cancels, send an immediate confirmation email. This prevents future disputes about when cancellation was processed.

Frequently Asked Questions

Can I win a 13.2 chargeback if the customer cancelled but I charged them one more billing cycle?

It depends on your cancellation terms. If your policy clearly states that cancellations take effect at the end of the billing period and the customer agreed to those terms at signup, you may have grounds for representment — provided you can prove the customer had ongoing access to the service during that final billing cycle. If the charge came after cancellation with no service access, issue a refund rather than fight it.

What is the difference between Visa 13.2 and 13.7?

Code 13.2 covers recurring/subscription charges where the cardholder claims they cancelled. Code 13.7 covers one-time purchases of merchandise or services where the customer cancelled the order or returned the item. The key difference is the recurring nature of 13.2 disputes versus the single-transaction nature of 13.7.

Does Visa require merchants to send cancellation confirmation emails?

Visa does not mandate cancellation confirmation emails, but they are one of the most effective ways to prevent 13.2 chargebacks. A cancellation confirmation with a timestamp creates unambiguous evidence of when the cancellation was processed, which is critical if a subsequent charge dispute arises.

How long does a cardholder have to file a 13.2 chargeback?

120 days from the transaction date of the disputed charge — not from the cancellation date. This means a customer who cancelled months ago and then sees one more charge has up to 120 days from that charge date to file the dispute.

Related Codes & Resources