Service Cancelled Defense Playbook

Customer Timeframe 120 days from billing date

Customer Difficulty Low easy to claim cancellation

Merchant Difficulty Medium winnable with log records

High Risk For SaaS subscriptions · memberships

Networks All 4 Visa · MC · Amex · Discover

What This Dispute Means

A Service Cancelled chargeback is filed when a cardholder claims they cancelled a recurring service, subscription, or membership before the disputed charge was processed — and asserts the charge should never have occurred. This is the defining dispute type for subscription businesses: SaaS platforms, streaming services, gym memberships, digital memberships, and any merchant who bills customers on a recurring schedule.

Unlike fraud disputes, the cardholder is acknowledging they originally authorized the service. They are not claiming someone else made the purchase. They are claiming the relationship was terminated before the billing date, and that the merchant charged them anyway. That distinction matters for how you build your defense: you are not defending authorization, you are defending that no valid cancellation existed at the time of the charge.

The dispute is also one of the most commonly used vehicles for friendly fraud in subscription businesses — where a customer who forgot to cancel, or simply regrets their purchase, retroactively claims a cancellation they never made. The evidence requirements are the same either way: a timestamped cancellation log showing no request was received before the billing date, combined with continued usage after the charge, makes these disputes difficult to sustain.

Important

If a cardholder genuinely cancelled before the billing date and you still charged them, you should issue a refund — not submit a representment. This guide covers cases where the facts are on your side: where your records show no pre-billing cancellation request was received, and the charge was valid when it was processed.

Network Coding

Each network codes this dispute type differently. The evidence requirements are similar across networks, but Mastercard's specific code (4841) is the most common in subscription contexts.

Network	Code	Official Name
Visa	13.6	Credit Not Processed – Cancelled Recurring
Mastercard	4841	Cancelled Recurring Transaction
American Express	C28	Cancelled Recurring Billing
Discover	AA	Does Not Recognize / Recurring Charge

Required Evidence

The strength of a Service Cancelled response is directly proportional to the quality of your cancellation and billing records. These three categories form the foundation of every response — they establish the billing timeline and prove no valid cancellation existed at the time of the charge.

#1 — Original subscription authorization

Proof that the cardholder explicitly consented to recurring billing at signup. Without this, you cannot demonstrate the recurring arrangement was authorized in the first place.

Evidence Type	What to Submit
Signup Authorization Record	The original recurring billing authorization with full timestamp, IP address, and email address — proving the cardholder consented to the recurring billing arrangement at signup.
Cancellation Policy Disclosure	The cancellation policy as it was displayed at the time of signup, showing the cardholder was clearly informed of the terms before subscribing. A screenshot of the checkout page showing the policy in plain language — not buried in a linked PDF.
Terms of Service	The terms accepted at signup, showing the cardholder agreed to the billing terms including the cancellation notice period and process.

#2 — Billing cycle record

Documentation of the specific billing cycle in dispute — establishing when the charge occurred and that the cardholder received advance notice.

Evidence Type	What to Submit
Billing Date and Amount	The exact billing date and time from your billing system, with the charge amount. This establishes the precise moment the charge occurred.
Advance Billing Notification	The renewal notification email sent to the cardholder before the billing date, with send date and delivery confirmation. Advance notice is a material factor in how issuers evaluate these disputes.
Prior Billing History	Records of previous billing cycles showing the pattern of recurring charges the cardholder had already accepted without dispute. A history of accepted prior charges establishes the ongoing subscription relationship.

#3 — Cancellation log

The most decisive evidence in a Service Cancelled dispute. An actual export from your cancellation management system — not a summary statement — showing no cancellation request was received before the billing date.

Scenario	Evidence to Submit
No cancellation received	An export from your cancellation log, support ticket system, or CRM showing zero cancellation requests from this account through any channel (email, portal, support ticket, phone) in the period before the billing date.
Cancellation received after billing	If a cancellation request was received, documentation showing the timestamped request clearly came after the billing date — proving the charge was valid when it was processed. The chronological gap between billing and cancellation request is the key evidence.

Strongly Recommended Evidence

Required evidence establishes the billing timeline. Strongly recommended evidence establishes that the cardholder was actively engaged with the service — making a pre-billing cancellation claim implausible regardless of what they assert.

#4 — Continued usage after the billing date

Service Type	Evidence to Submit
SaaS / Software	Login session logs with timestamps and IP addresses after the billing date. Feature usage records showing meaningful platform engagement. A customer who logged in multiple times after the "cancelled" date has a very difficult claim to maintain.
Content / Streaming	Content access records, view counts, download logs, or playback data after the billing date with timestamps. API call logs for developer-facing services.
Professional Services	Any service delivery, communications, or deliverable interactions after the billing date showing the service relationship continued.
Membership / Community	Forum posts, messaging activity, event attendance records, or any community participation after the billing date.

Strongest Defense

The combination of (1) a cancellation log showing zero pre-billing requests, and (2) usage logs showing active product engagement after the billing date, makes a Service Cancelled claim extremely difficult to sustain. These two data points together tell the complete story: the customer had not cancelled, and they continued using the service they were charged for.

#5 — Billing notification communications

The advance renewal notification email sent before the billing date, showing the cardholder received notice and had opportunity to cancel.
Open and click records from the billing notification if available from your email platform.
The billing confirmation sent on the date of the charge.
Prior renewal notification emails from previous cycles, showing the cardholder had been receiving — and apparently accepting — these notifications before the dispute.

#6 — Absence of a cancellation attempt through any channel

Export your customer support records for the 30–60 days before the billing date to demonstrate no cancellation request was received via any channel.
If your cancellation flow requires deliberate action through your product or portal, include a screenshot of the process — showing that cancellation requires intentional steps, not accidental omission.
If your system sends a cancellation confirmation email upon successful cancellation, note that no such confirmation was triggered for this account — and that a legitimate cancellation would have generated one.

Supporting Evidence

These items round out your case and become important at arbitration.

#7 — Subscription history and value delivered

Complete billing history showing all cycles the cardholder accepted without dispute — establishing the ongoing subscription relationship and their awareness of the recurring billing arrangement.
Evidence of value delivered during the subscription period: content accessed, features used, projects completed, reports generated.
Any customer satisfaction signals — positive support interactions, feature requests, feedback submissions — that indicate an engaged subscriber.

#8 — Cancellation process documentation

Your cancellation policy as displayed at signup, showing the required notice period and process steps.
Screenshot of the self-service cancellation flow within your product, showing the steps a customer would need to complete to cancel.
The cancellation confirmation email template that would have been sent automatically upon successful cancellation — its absence from your send logs is evidence no cancellation was completed.

Critical Mistakes

These mistakes consistently turn winnable Service Cancelled disputes into losses. Audit your response against each before submitting.

Mistake #1: Submitting a statement instead of a log export

Telling an issuer "we have no record of a cancellation request" carries no weight without an actual system export to back it up. An assertion without documentation is indistinguishable from fabrication to an arbitrator who cannot verify your records.

What to do instead

Export your support ticket history, CRM records, cancellation portal logs, and email records for the relevant period and submit those exports as exhibits. A timestamped export with a visible date range is evidence — a paragraph summary is not.

Mistake #2: No cancellation log infrastructure at all

The most common structural weakness in subscription businesses: cancellation requests are handled manually or through informal email, with no systematic log. When a dispute arrives, there is no reliable record to export — and the merchant cannot definitively prove a cancellation request was or was not received.

What to do instead

Implement a cancellation log as critical infrastructure. Every cancellation request through any channel — email, support ticket, portal, phone — must generate an immutable, timestamped record. This is non-negotiable for any subscription business that wants to defend these disputes reliably.

Mistake #3: Cancellation policy buried in fine print

If your cancellation terms are not clearly visible on the subscription checkout page, issuers are skeptical of your position even when the facts favor you. A terms-of-service PDF linked in a footer is not the same as a cancellation policy disclosed at checkout.

What to do instead

Display your cancellation terms on the checkout page in plain language — not just linked. Include a screenshot of the disclosure as it appeared at signup, showing the policy was clearly visible before the cardholder subscribed. If customers must actively acknowledge the cancellation policy before subscribing, include that acknowledgment record.

Mistake #4: Not including post-billing usage evidence

Usage logs after the billing date are your most persuasive evidence — and they are consistently omitted. A cardholder who logged in, accessed content, or used features after the billing date cannot credibly claim they had already cancelled before the charge.

What to do instead

Pull usage logs for the 30 days following the billing date. Even minimal usage — a single login, a dashboard view, one API call — creates documented post-billing activity. Include the log export and highlight the most recent activity date in your opening summary.

Mistake #5: No advance billing notifications

Issuers view merchants who notify customers in advance of recurring charges favorably. If you cannot show that the cardholder received advance notice of the billing date, the dispute becomes harder to win — even when the cancellation timeline supports your position.

What to do instead

Send renewal notification emails 7–10 days before each recurring charge. Archive these send records with timestamps. For the disputed billing cycle, include the advance notification email, its send date, and any delivery or open record available.

Winning Response Framework

Lead with the cancellation log and billing chronology. The most persuasive response makes the timeline impossible to dispute — no cancellation before the billing date, and continued usage after.

Step 1 — Identify the chargeback clearly

Template Language

Case Number [DISPUTE_REFERENCE_NUMBER] We are responding to the [NETWORK CODE] chargeback against the [MM/DD/YYYY] transaction made by [CARDHOLDER_NAME] in the amount of [$AMOUNT]. Please find our response and supporting documentation attached.

Step 2 — Lead with the cancellation timeline

State the facts of the billing and cancellation chronology in plain language before presenting exhibits. Make the timeline clear and unambiguous from the first paragraph.

Template Language

We respectfully dispute this chargeback. Our records demonstrate that no cancellation request was received before the billing date, and that the cardholder continued to use the service following the charge. BILLING CHRONOLOGY - Subscription signup: [SIGNUP_DATE] (IP: [IP_ADDRESS]) - Advance renewal notification sent: [NOTIFICATION_DATE] — [X] days before billing - Billing date: [BILLING_DATE] at [TIME] — $[AMOUNT] charged - Cancellation request received: [DATE, IF APPLICABLE — must be AFTER billing date] OR: No cancellation request received prior to this dispute filing. CONTINUED USAGE AFTER BILLING DATE Our activity logs show the following usage after [BILLING_DATE]: - [LOGIN / FEATURE USE / CONTENT ACCESS] on [DATE] at [TIME] - [LOGIN / FEATURE USE / CONTENT ACCESS] on [DATE] at [TIME] Full activity log export attached as Exhibit C. The cardholder consented to recurring billing at signup, was notified of the upcoming renewal, and actively used the service after the billing date. We respectfully request that this chargeback be reversed.

Step 3 — Sequence your evidence by strength

Priority	Evidence Type
First	Cancellation log export — showing no pre-billing request was received through any channel.
Second	Usage logs showing continued service access after the billing date.
Third	Advance billing notification email with send date. Original signup authorization with timestamp and agreed terms.
Last	Prior billing history, cancellation policy display, terms of service, cancellation flow screenshot.

Step 4 — Label and explain each exhibit

Label all attachments clearly and reference each by exhibit letter in your response. Keep the response focused on the cancellation timeline — do not include irrelevant documentation.

Template Language

Exhibit A: Cancellation Request Log — [DATE RANGE] Export from our cancellation management system covering [START_DATE] through [BILLING_DATE]. No cancellation request associated with account [ACCOUNT_ID / EMAIL] appears in this log during this period.

Real-World Examples

The situation: $79/month subscription. Cardholder disputed the month 6 charge claiming "I cancelled this subscription before being charged."

Opening statement submitted:

Opening Statement

"Our cancellation log shows no cancellation request was received from this account prior to the March 1 billing date. The cardholder's renewal notification was sent February 21 — 8 days in advance. The charge processed at 12:00 AM on March 1. The first cancellation request in our system is dated March 4 at 11:43 AM — 3 days and 11 hours after billing. Following the March 1 charge, the cardholder logged in 7 times and completed 2 course modules between March 1 and March 9, before submitting the cancellation request."

Evidence provided (in order submitted):

Page	Evidence
1	Cancellation log export (Feb 1 – Mar 4) showing zero requests before billing, and one request on March 4 at 11:43 AM — timestamped 3 days after the March 1 charge.
2	Platform activity log: 7 login sessions between March 1 and March 9, with 2 course modules completed on March 3 and March 7 — both after the billing date and before the cancellation request.
3	Advance renewal notification email sent February 21, showing the cardholder had 8 days' notice of the March 1 renewal before it processed.
4	Original signup authorization from Month 1, with IP address and explicit agreement to monthly recurring billing at $79. Screenshot of cancellation policy as displayed at checkout.

Result: Chargeback successfully represented. Claim withdrawn.

Why it won:

Timestamped cancellation log proved definitively that the only request came 3+ days after billing — the cardholder's claim of pre-billing cancellation was directly contradicted by the system record
7 post-billing logins and 2 completed courses make it implausible the cardholder thought their access had ended before the charge
8-day advance notice proves the cardholder had ample opportunity to cancel before the billing date and chose not to

The situation: $49/month fitness app. Cardholder disputed claiming "I sent an email to cancel weeks ago and they still charged me."

What they submitted:

Response Submitted

"We searched our records and could not find any cancellation request from this customer. Our terms state customers must cancel through the app. We have attached our terms of service which explain the cancellation process. This dispute should be denied."

Result: Dispute ruled in cardholder's favor.

Why it lost:

Mistake	Explanation
Statement instead of log export	"We searched our records" is not evidence. The issuer has no way to verify whether the search was complete or whether the records are reliable.
No usage data	If the cardholder was actively using the app after billing, those logs would have directly contradicted their cancellation claim. They were never included.
No billing notification evidence	Without proof of advance billing notice, the issuer cannot confirm the cardholder had an opportunity to cancel before being charged.
Terms of service as primary evidence	A full terms document is not the same as showing the cardholder saw and accepted the cancellation policy at checkout. It does not prove disclosure.

What they should have submitted:

An actual export from their support log and CRM — even if showing zero records — with a timestamp confirming the export date and range
App usage logs showing login activity and workout completions after the billing date
The advance billing notification email sent before the renewal
A screenshot of the cancellation process within the app, demonstrating it requires deliberate steps

Before You Submit

Run through this checklist before finalizing your response.

Subscription authorization

Original signup authorization with timestamp and IP address included
Cancellation policy as displayed at checkout — screenshot, not a link to a PDF
Checkout consent record showing the cardholder agreed to recurring billing terms

Cancellation log

Actual system export — not a summary statement — with timestamp showing export date and coverage period
Export covers all cancellation channels: email, portal, support ticket, phone
If a cancellation request exists, timestamp clearly shows it postdates the billing

Billing cycle documentation

Exact billing date and time from billing system documented
Advance billing notification email included with send date
Prior billing history showing cardholder accepted previous cycles

Post-billing usage

Login or usage activity logs for 30 days after the billing date included
Most recent post-billing activity date called out in opening summary
Response submitted within the applicable network deadline

Proactive Prevention

Subscription merchants face more Service Cancelled exposure than any other business category. These steps reduce your dispute rate and ensure the evidence you need is captured before a dispute arrives.

Action	Why It Matters
Implement timestamped cancellation logs as infrastructure	Every cancellation request through any channel must generate an immutable, timestamped record. This is the single most important operational requirement for any subscription business. Without it, you cannot reliably defend these disputes.
Send advance billing notifications 7–10 days before renewal	Advance notice gives customers the opportunity to cancel before being charged and creates a documented notification record. Customers who receive advance notice file fewer disputes — and when they do, the notification record is your evidence they had the opportunity to cancel.
Send cancellation confirmation emails immediately	When a customer cancels, send an instant confirmation email. This creates a definitive cancellation timestamp in your system. In a dispute, the absence of this email from your send logs is evidence that no cancellation was completed.
Log all product usage continuously	Session logs, feature interactions, and content access with timestamps must be retained and linked to the customer account. This data is automatically generated by most platforms — you just need to archive it for dispute resolution purposes.
Display cancellation policy prominently at checkout	Cancellation terms — including the required notice period and process — should be visible on the subscription checkout page, not buried in a terms link. A clear, visible policy that customers acknowledge before subscribing significantly reduces claim volume.

About This Guide

This playbook is updated at least twice annually to reflect changes in network rules and issuer practices. Document Version: 2026.1 · Last Updated: March 2026 · Covers: Visa 13.6 / Mastercard 4841 / Amex C28 / Discover AA

Network-Specific Guide

For the complete response framework, real-world examples, and process walkthrough specific to Mastercard’s cancelled recurring transaction code: