Subscription Canceled or Not Recognized: Chargeback Evidence Guide
Subscription chargebacks are among the most common disputes for SaaS and recurring revenue businesses. The cardholder may claim they canceled before the charge, that the renewal was unexpected, or that they simply don't recognize the billing. This guide covers what evidence matters most and how to structure your response.
What this dispute type covers
Stripe surfaces this under labels like “subscription canceled” or “subscription not recognized,” often corresponding to Visa reason code 4841 or Mastercard reason code 4853. The dispute usually falls into one of these scenarios:
- The customer claims they canceled before the renewal date but was still charged
- The customer doesn't recognize the charge on their statement (unfamiliar billing descriptor)
- The customer expected a cancellation to be immediate but the billing cycle had already started
- The customer forgot they had an active subscription
- The customer is disputing a renewal after not using the product for a period of time
In all of these cases, your evidence should show that the subscription was active, that the customer agreed to recurring billing, and — critically — whether a valid cancellation request was made before the disputed charge.
Key evidence to include
Subscription signup and billing agreement
The original signup confirmation showing that the customer agreed to recurring billing. Include any pricing page screenshots showing the billing cycle, renewal terms, and what the subscription includes. If you use a Stripe-hosted checkout, the subscription terms Stripe shows at checkout are also relevant.
Renewal notification emails
If your platform sent an upcoming renewal notice or a receipt after the renewal charge, include records showing those emails were sent. Delivery timestamps and open/click records are particularly useful. Proactive renewal notifications significantly strengthen your position.
Cancellation policy and process
A screenshot of your cancellation policy or help documentation, showing how customers are expected to cancel and what the effective date of cancellation is. If cancellations take effect at the end of the billing period, this should be documented clearly.
Cancellation records (or absence of one)
If the customer claims they canceled, show your cancellation logs. If no cancellation request exists before the billing date, document that clearly. If a cancellation was requested after the charge was processed, include the date and time to show it was submitted after the billing cycle had already started.
Subscription history and billing timeline
A clear record of prior billing cycles — showing previous charges that the customer did not dispute. Multiple prior renewals without complaints demonstrate that the customer was aware of and accepting the recurring billing.
Usage activity during the billing period
Login records or feature usage during the disputed billing period show that the customer was actively using the product — even after the renewal charge. This is useful evidence that contradicts a claim of cancellation before the charge.
Billing descriptor explanation
If the customer claims they don't recognize the charge, include a note explaining what your billing descriptor looks like and why it matches your business. A clear explanation of the descriptor string that appears on bank statements can resolve “not recognized” disputes before they escalate.
Handling different cancellation scenarios
Customer claims they canceled before renewal
Show your cancellation log with timestamps. If no cancellation exists for the email or account associated with the disputed payment, document that clearly. If there is a cancellation log entry after the charge was processed, note the exact time difference.
Customer doesn't recognize the subscription
Show the original signup, billing terms, prior invoices or charges, and login history. Multiple prior charges without disputes show the customer was aware of the billing.
Customer requested cancellation but billing was already processed
If your policy bills at the start of a period and cancellation takes effect at the end, document both the policy and when the cancellation request was received relative to the billing event. If applicable, note any refund that was already issued.
Build your subscription dispute evidence pack with ProofPack
ProofPack organizes your subscription history, cancellation records, billing timeline, and supporting files into a structured PDF ready for Stripe. $4.99 one-time, no account required.