Cancelled Subscription Chargebacks: Building a Case You Can Win

Suppose a customer cancels on June 18, three days after their monthly payment went through. A week later, a chargeback arrives saying you billed them after cancellation.

Your billing platform may show June 18 while your support inbox holds an earlier cancellation request. Before sending a response, you need to know what the customer asked for, when they asked and which payment they are disputing.

For subscription merchants, those records start at signup: what the customer agreed to pay, when the next charge was due and how they could cancel. Visa and Mastercard set requirements for consent, billing notices and dispute responses, with differences that affect the case you can make.

Which subscription dispute are you answering?

The evidence you need depends on why the customer is disputing the payment. “I cancelled” calls for the cancellation history. “I never agreed to a subscription” calls for the terms shown at checkout and the customer’s acceptance. Check the reason code and the explanation from the issuer, the institution that issued the card.

Visa’s policy explanation distinguishes cancellation under 13.2 from the trial-related 13.5 claim. Mastercard’s Chargeback Guide, pp. 260–262, covers the common recurring-transaction allegations and responses. Codes and procedures can differ by processing system and region.

Which subscription rules apply to your business?

A recurring service, a discounted introductory period and a physical-product trial can carry different requirements. Visa’s definitions also distinguish free-trial subscriptions from its negative-option merchant category. A trial that renews does not automatically put a merchant in that category. Visa subscription policy.

Mastercard’s subscription standards can apply to both business and consumer subscriptions, regardless of merchant category code. The standard subscription-billing rule excludes utilities, telecommunications, insurance and existing-debt payments. For charities and nonprofits, the standards are best practice until the specified monitoring condition makes them mandatory. Mastercard FAQ, questions 3, 6, 8 and 10; Transaction Processing Rules §5.4.1.1.

Your acquirer, the financial institution responsible for your card acceptance, can confirm which requirements apply to your business. Your payment processor manages the transaction and dispute workflow.

Consumer-protection laws, including US ROSCA, can add requirements. The comparison in this article covers card-network rules.

What Visa and Mastercard require

Sources: Visa §§5.8.11.1, 5.8.17.2 and 5.9.1.1; Mastercard §§5.4.1 and 5.4.2. For standard subscriptions, Mastercard’s receipt requirement takes effect after at least four months in the same audit period as an Excessive Chargeback Merchant, High Excessive Chargeback Merchant or Excessive Fraud Merchant. Mastercard FAQ, questions 10–13.

Physical-product trials

Mastercard’s physical-product negative-option requirements include a further consent step. After the trial expires and before authorizing the first regular-price recurring product, obtain explicit consent to the subscription start, amount, payment date, statement name and cancellation instructions. The acquirer must also preserve the required merchant ID and name across the trial and later charges. Mastercard §5.4.2 standard 2.

Trial reminder timing

Receipts and cancellation confirmations

The receipt should show the amount, billing date and how to manage or cancel the subscription. Visa requires an emailed receipt’s subject to include the merchant name as it appears on the card statement and wording indicating that the email contains a receipt or receipt link. For a wirelessly delivered message, that information belongs in its title or first line. A receipt link must go directly to the receipt and remain available for at least 120 days. Visa §5.9.1.2.

Keep a copy of any notice changing the billing terms and record when you sent it. A cancellation confirmation should give the effective end date and explain any access the customer retains.

The evidence to send with your response

For a Visa 13.5 dispute about further billing after the relevant trial purchase, provide both the customer’s initial agreement to future charges and the notice sent at least seven days before the charge.

For Visa 13.2, check when the customer asked to cancel and the last day they were allowed to use the service. Someone who cancels a monthly plan may still have access until the end of that month. Using that paid-for access does not, by itself, establish the separate post-cancellation usage defense. Visa §§11.10.6.6 and 11.10.3.6.

For a Visa 13.2 claim that the customer withdrew billing permission, compare the issuer’s stated withdrawal date, the contact details used to reach the merchant and any alternative payment method supplied with your own records. Visa requires those certifications in that branch of the dispute process; account-closure and European branches differ. Visa §11.10.3.5.

Mastercard says a statement that “the customer never contacted us to cancel” is insufficient on its own. Send the records supporting the applicable defense, such as the terms disclosed at signup, the customer’s acceptance or the cancellation history. Mastercard Chargeback Guide, pp. 262–263.

Subscription records to keep

Keep the payment reference with the cancellation request and relevant support messages. Your team needs to be able to match them to the same customer and charge.

Keep the message content and send log, along with delivery status where available.

Visa requires retention of the relevant agreement information for the duration of the agreement. Set a retention schedule for supporting records with your privacy and legal teams, taking account of the applicable dispute windows. Visa §5.8.11.1; Mastercard FAQ, question 16.

How the cancellation dates affect the response

The fictional meal-planning app in the opening example offers a 14-day trial followed by a $29.99 monthly subscription. Its account history shows:

For this Visa 13.2 dispute, the merchant can submit the payment record and June 18 cancellation request to show that cancellation came after the June 15 charge. Visa lists cancellation after the transaction date as an invalid basis for 13.2 for disputes processed on or after April 18, 2026. Visa §11.10.3.3.

A sample response for the June 15 charge

Suppose the issuer identifies June 18 as the cancellation date and alleges no earlier request. A response based on this fictional account history could read:

The attachments should let the reviewer check that explanation:

When the customer used the service after asking to cancel

Consider a second fictional customer on a $29.99 plan billed on the first of each month. Their June payment covers June 1–30. On June 10, they cancel renewal. The confirmation says billing will stop and access will continue through June 30. They log in on June 20.

A billing error then triggers a July 1 renewal for July service. The customer disputes it under Visa 13.2.

The June 20 login does not justify the July charge. It falls within the access the customer had already paid for and was still permitted to use. Visa’s 13.2 usage provision treats the cancellation date as the last date the cardholder was allowed to use the service. Here, that date is June 30. Visa §11.10.3.6, footnote 2.

This example concerns a new July renewal. If a merchant bills in arrears, a payment collected after cancellation may cover services already received. The response would need records establishing that service period.

When your records are incomplete or conflicting

An account log showing June 18 does not resolve a claim that the customer emailed support on June 10. Search the channel named in the claim, including closed tickets, and match the conversation to the disputed account. Check time zones before putting events in order. A delayed update to the billing platform can make a timely request look late.

Missing consent records need the same care. A screenshot of today’s checkout cannot establish what someone accepted six months ago. Look for the checkout version in use at signup and the corresponding acceptance event. A notice’s send log establishes sending; it is not proof that the customer received or opened it.

Challenge the dispute on a defense the records support. If they show a billing error, resolve it through your processor. Check for an existing credit or refund first, so the same payment is not returned twice.

Subscription dispute costs and reporting

Measure how often recurring payments turn into disputes and how comparable challenged cases resolve. Report refunds used to prevent a chargeback separately from won disputes. Check your acquirer’s monitoring calculation, too: it may use different events or periods from a general dashboard ratio. See Visa’s VAMP overview and Braintree’s Mastercard ECP guidance.

Using Chargeflow for subscription disputes

Chargeflow Automation collects disputes from connected payment processors, adds available evidence, creates a response and submits it through the processor workflow. If you hold activity logs or other relevant records in your own systems, you can supply them through the enrichment API.

Subscription records can come from connected Recharge, Recurly or Chargebee accounts. The Gmail and Gorgias integrations retrieve relevant conversation text. Screenshots and documents attached to those conversations need to be uploaded separately. The evidence available for a response depends on what the connected tools expose and what you supply.

If you use Recharge, enabling Automated subscription cancellation lets Chargeflow cancel active disputed subscriptions. The Recharge guide explains the setting.

Mastercard can also permit an issuer to dispute a later recurring charge when, before that charge, it had sent the required cancellation notice, listed the account in its Payment Cancellation Service or already charged back a prior recurring transaction on the same account at the same merchant. Check the applicable branch and regional conditions before continuing to bill. Mastercard Chargeback Guide, pp. 276–278.

Chargeflow Alerts supports Verifi RDR, CDRN and Ethoca workflows for resolving eligible cases before a formal chargeback, often through a refund. Handling depends on the service and configuration you enable.

Chargeflow Insights provides a view across connected processors and sends proactive ratio notifications. Check those notifications against your acquirer’s program-specific reporting.

How HomeFi changed its dispute workflow

HomeFi, an internet service provider, had been handling cancellation disputes manually. Its team struggled to keep up with response deadlines and evidence gathering. Chargeflow’s published HomeFi case study describes replacing that workflow with automated responses and reports recovery rising from 23% to 45%, with 175 hours saved.

Robert Anthony, HomeFi’s VP of Accounts & Billing, said:

The case covers Chargeflow Automation alongside Alerts and Insights. These are account-level results; the story does not separate outcomes for cancelled subscription disputes or measure the effect of compliance changes.

Frequently asked questions

What is a cancelled or canceled subscription chargeback?

It is a dispute over a recurring payment the customer says should have stopped, often because they cancelled. Visa’s relevant condition is 13.2. Mastercard’s common dual-message recurring disputes use 4853. A claim that future billing was never disclosed may follow a different route.

How long can a customer dispute a subscription payment?

For Visa 13.2, the issuer generally has 120 calendar days from transaction processing. For the common Mastercard recurring branches, it is generally 120 days from settlement or the applicable Central Site Business Date, with regional exceptions.

Visa 13.5 has receipt and negotiation triggers, with a 540-day outer limit in specified cases. Your processor will give you a separate deadline for the merchant response. Visa §§11.10.3.4 and 11.10.6.4; Mastercard Guide, pp. 261 and 277.

Does Visa require a reminder before every renewal?

Visa requires reminders in particular circumstances, including billing after a trial or introductory period, certain changes to an agreement and specified European renewals. Check which requirement applies to your offer and region. Visa §§5.8.11.1 and 5.8.17.2.

Does Compelling Evidence 3.0 apply to subscription payments?

CE 3.0 can apply to qualifying recurring payments disputed as Visa 10.4 fraud, using initial-setup data. It does not provide the remedy for a 13.2 cancellation allegation. Visa CE 3.0 FAQ, Merchant/Acquirer questions 4 and 8.

What should I do after a Visa R0, R1 or R3 decline?

Stop retrying the same payment credential. Visa prohibits reattempts after these stop-payment and authorization-revocation declines. For a declined merchant-initiated payment using a stored credential, notify the customer in writing and allow at least seven calendar days to pay another way. The payment stop does not automatically terminate the underlying contract. Visa §§7.3.6.3 and 5.8.11.1.