A canceled-recurring chargeback asks whether the customer was charged after a cancellation that should have stopped billing. Reconstruct the customer-facing terms and the actual event history for the specific payment. If the customer canceled on time and your system still charged them, accept the dispute or refund through the processor’s permitted workflow, then fix the billing path.
Reconstruct the subscription from signup forward
Build a short record of the enrollment that led to this renewal:
- signup date and the version of the screen or terms shown;
- plan, price, billing interval, and any trial-to-paid conversion;
- affirmative acceptance of recurring billing;
- cancellation method and cutoff shown to the customer;
- renewal reminders and receipts relevant to this billing cycle.
Use the version that applied at enrollment. A later policy change does not prove what the customer accepted unless you can show the change became effective and was communicated as required. Keep the actual disclosure and acceptance record; a copy of today’s generic terms is weak evidence of what appeared at checkout.
Put the request, charge, and effective date on one line
Compare the customer's first cancellation request, the disputed payment, and the effective cancellation time. For example:
`Request received: Aug 14 09:22 PT → payment captured: Aug 15 02:00 UTC → cancellation effective: Aug 15 09:30 PT`
Preserve each original timestamp and its source, then show a readable sequence with the time zones labeled. Do not silently convert or round times. Tie the payment to the exact invoice or processor transaction ID so a retry, pending authorization, or later renewal is not mistaken for the disputed settled charge.
A cancellation flow may record a page visit, an initial click, a final confirmation, and a state change as separate events. Explain what the customer saw and which step the accepted policy required. If the customer selected “cancel at period end,” show the effective date and the confirmation they received. Do not use an internal status label to imply a customer completed a step the interface did not clearly request.
- Terms acceptedIdentify cutoff and billing terms.
- Cancel requestKeep customer and system event times.
- RenewalTie charge to processor event.
- Effective cancellationCompare cutoff and timezone.
- ResolutionAccept timely cancellation charged afterward.
Include notices and customer communications when relevant
Some subscription programs and laws require or encourage specific renewal notices. Check the rules and processor requirements that apply to the business and customer; do not present a reminder as proof that the customer read it.
Include relevant trial-ending or renewal notices, payment receipts, cancellation confirmations, and support messages. For each email, show the content, destination, and sent time; delivery or open data can add context, but a sent record alone does not establish that the customer saw or understood it. If support received a cancellation request, include the original request and the action taken, even when it exposes a processing failure.
Use post-renewal activity as context, not a substitute
For digital services, dated logins, downloads, or feature use after the disputed renewal can support that access continued. The logs should identify the account and the relevant billing period. Usage does not erase a timely cancellation or make an otherwise improper charge valid.
For a physical subscription, fulfillment and delivery can explain what the renewal purchased, but they do not resolve whether cancellation should have stopped that payment. Keep this evidence secondary to the terms and event timeline.
Make free-trial conversion easy to verify
Preserve the enrollment screen or versioned record showing the trial length, conversion date, post-trial price, recurring interval, and cancellation method. Match it to the customer’s enrollment event and the first paid invoice. If those terms were hard to find or the conversion disclosure is missing, a dispute packet assembled later cannot repair the signup experience.
Track disputes and support contacts by signup cohort and page version. A rise after a pricing or checkout change is a reason to inspect that exact flow and correct unclear or missing disclosures.
Accept when the records show a valid cancellation
If the customer followed the disclosed process before the applicable cutoff and the disputed payment settled afterward, do not defend the charge with unrelated usage or a long packet. Correct the subscription, stop further renewals, and use the processor’s permitted refund workflow where appropriate. Shopify likewise advises reviewing the records and considering a refund when a customer followed the cancellation process but was still charged.
If the customer’s request came after the disclosed cutoff, build a concise explanation from the accepted terms and timestamped records. State the relevant date and policy plainly; avoid claiming that a bank must decide in your favor. The issuer reviews the submitted evidence.
Prevent the next dispute at the product level
Make the cancellation route easy to find and complete. State whether cancellation is immediate or takes effect at period end, show the effective date before final confirmation, and send a confirmation that repeats it. Store an immutable event trail for consent, cancellation requests, confirmation steps, effective status, notices, renewal creation, and payment outcomes.
Have the billing job read the authoritative subscription state. Make retries idempotent so a retry or delayed webhook cannot create another renewal after cancellation. Monitor failed cancellations, duplicate renewals, and support messages containing “cancel” or “stop charging”; test the flow from the customer account through the processor event.
Reconcile records and build a reviewer-ready chronology
Before contesting, compare the subscription platform, processor, and support history. For the disputed billing cycle, connect the account and plan to the invoice, payment ID, request or ticket ID, cancellation event, and any retry or webhook event. Keep source exports or audit logs alongside concise screenshots; a current “active” or “canceled” badge does not show when the state changed.
If systems disagree, investigate before submitting. A support agent may have canceled the plan while billing remained active; a request may have failed to reach the subscription service; or a cancellation may have been set for the end of the paid period. Explain which event actually triggered the charge, whether it settled, and what the customer was told. Acknowledge a system error when the evidence shows one. If the records agree that the charge preceded an effective cancellation under terms the customer accepted, present that chronology with the policy and the most relevant notice or activity record.
