Subscription Win: $450 Cancelled Recurring Billing

Outcome WON dispute reversed

Network + Code Visa 13.2 cancelled recurring

Dispute Amount $450 monthly subscription

Industry SaaS subscription software

Resolution Time 29 days

The Dispute

A subscription SaaS company received a Visa 13.2 dispute for a $450 monthly charge. The cardholder claimed they had cancelled their subscription before the renewal date and should not have been billed. The merchant had no record of a cancellation request through any channel: not through the in-app cancellation flow, not via email, not through the support desk.

What made this case clear-cut: the merchant had sent a renewal notification email 14 days before the billing date, per their standard pre-renewal workflow. The customer had not responded to cancel. More damning still — the customer had logged into the product on 9 separate occasions during the two weeks after the renewal date they claimed to have cancelled before.

Visa 13.2 disputes — “Cancelled Recurring Transaction” — require the cardholder to demonstrate that they cancelled the recurring billing arrangement before the disputed charge. When the merchant can show a renewal notification was sent and acknowledged through continued product use, the cardholder’s position is difficult to sustain.

Case Timeline

Day −14 Renewal notification sent. Merchant sends automated pre-renewal email to the customer confirming the upcoming $450 charge in 14 days. Email delivery confirmed; no cancellation request received in response.

Day 1 $450 renewal charge processed. Billed per the contracted monthly cycle. No cancellation request on record at time of billing through any channel.

Days 1–14 Customer continues using the product. Nine login events recorded across the two weeks following the disputed renewal date, all from the customer’s known IP address and device.

Day 16 Chargeback filed. Cardholder contacts bank claiming they cancelled before the billing date. Visa 13.2 dispute filed.

Day 19 Dispute received by merchant. Payment processor forwards the Visa 13.2 dispute notification with the cardholder’s stated reason.

Day 25 Response compiled and submitted. Renewal notification email, cancellation log export, and post-billing usage records assembled and submitted via the payment processor’s dispute portal.

Day 29 Dispute resolved in merchant’s favor. Issuer reviewed the evidence and reversed the chargeback. Funds returned to merchant account.

The Evidence

The merchant’s evidence package was built around three pillars: advance notice of the renewal, the complete absence of a cancellation request, and documented continued product use after the disputed billing date. Together, these three elements made the cardholder’s claim implausible at every step.

Pre-renewal notification email sent 14 days before billing — full email with timestamp, delivery receipt, and subject line included in response package
No cancellation request found in the support ticketing system (timestamped export provided, showing zero entries from this customer in the 30 days prior to billing)
No cancellation found in the in-app cancellation portal (full portal log provided, showing zero cancellation events on this account)
Customer logged in 9 times across the 14 days following the disputed renewal date, with timestamps, IP addresses, and session durations for each event
Original subscription agreement with explicit auto-renewal and cancellation terms, signed at onboarding
Terms of service displayed at signup showing “cancel anytime by visiting Account Settings or contacting support” — cardholder was informed of the cancellation process
Billing cycle documentation showing the $450 charge aligned exactly with the contracted monthly renewal date
Two prior billing cycles on the same card with no disputes, establishing this as a recognized recurring charge

The Response Strategy

The merchant’s response was structured around a simple, three-part argument: advance notice was given, no cancellation was received, and the customer used the product after the date they claim to have cancelled. The response opened by establishing the renewal notification — a piece of evidence that many subscription merchants overlook — before moving to the absence of a cancellation and the post-billing usage data.

Core Argument

“The merchant sent a renewal notification to the cardholder’s email address 14 days before the disputed charge. No cancellation was received through any channel. The cardholder then logged into the platform nine times in the 14 days following the charge. A customer who cancelled before billing does not subsequently use the product they claim to have cancelled.”

The response structure:

Lead with the renewal notification. The pre-renewal email is advance notice. It demonstrates the merchant acted in good faith to inform the cardholder of the upcoming charge. A cardholder who received notice and did not cancel cannot later claim surprise at the charge.
Present the cancellation log. The timestamped export showing zero cancellation events across all channels (portal, email, support) is the affirmative evidence that no cancellation was made.
Follow with post-billing usage data. Nine logins in 14 days after the disputed renewal date. Timestamps, IP addresses, session durations. A cardholder who cancelled before being billed does not then log in nine times.
Present the subscription agreement. The cardholder signed an agreement with clear cancellation terms and was sent advance notice. The failure to cancel was the cardholder’s, not the merchant’s.

Why It Won

The renewal notification email is the piece of evidence most subscription merchants forget to include. It transforms the dispute from “did the merchant have the right to charge?” into “did the cardholder receive notice and choose not to cancel?” The answer here was clearly yes — and nine post-billing logins made the claim of prior cancellation impossible to sustain. The issuer had no basis to rule for the cardholder against timestamped, documented evidence on every element of the dispute.

Visa 13.2 requires the cardholder to demonstrate they cancelled the recurring billing arrangement before the disputed charge. When the merchant can show (a) advance notice was sent, (b) no cancellation was received through any channel, and (c) the cardholder continued using the service after the date they claim to have cancelled — all three elements of the cardholder’s claim collapse simultaneously.

Key Takeaways

Lessons From This Case

Send renewal notifications and keep delivery records. A pre-renewal email sent 7–14 days before billing is advance notice. Store the send timestamp, delivery status, and email content. This single piece of evidence changes the framing of every recurring billing dispute you will ever face.
Document continued usage after billing — always. Post-billing logins, API calls, feature usage, content downloads: any evidence of service use after the date a customer claims to have cancelled is devastating to their dispute. Log it automatically; retrieve it at dispute time.
Your cancellation log is only as good as its coverage. Log every channel: in-app portal, email, support tickets, live chat, phone calls. A cancellation log showing zero entries across all channels is far stronger than one showing zero entries in only one channel.
Prior billing cycles without disputes establish pattern. Two months of accepted charges on the same card builds the case that this was a recognized recurring relationship, not an unauthorized charge the cardholder never noticed.