Premium / Reason Code Guides / Mastercard 4841
REASON CODE GUIDE · MASTERCARD

Mastercard 4841: Cancelled Recurring Transaction Defense Playbook

Cardholder claims they cancelled before being charged. Winning this requires airtight documentation of your billing cycle, cancellation log, and continued usage evidence.

Response Window 45 days from notification
Network Mastercard all card types
Category Consumer Dispute recurring billing
Threshold $0 no minimum
High-Risk For SaaS, subscriptions, streaming any recurring billing model

What This Dispute Means

Mastercard 4841 is filed when a cardholder claims they cancelled a recurring subscription or payment arrangement before the disputed charge was processed. The cardholder is asserting that the merchant should not have billed them because the relationship was already terminated.

This is one of the most common dispute codes for subscription businesses — SaaS platforms, streaming services, membership sites, gym memberships, and any business that bills customers on a recurring schedule. It is also frequently used as a form of friendly fraud, where a customer who forgot to cancel, or simply regrets their purchase, retroactively claims a cancellation they never actually made.

The key battleground in every 4841 dispute is timing: did the cardholder actually cancel before the billing date? Everything flows from that question. The merchant who controls the timestamp documentation controls the outcome.

Important Warning

If a cardholder actually did request a cancellation before the billing date and you still charged them, you will lose this dispute and may face regulatory scrutiny. 4841 only works in your favor when the facts are genuinely on your side. Do not submit a representment if your own records confirm the cardholder cancelled before the billing date.

Required Evidence

The strength of a 4841 response is directly proportional to the completeness of your billing and cancellation records. Compile the following documentation before submitting your representment.

#1 — Original subscription authorization

The first and most critical piece of evidence: proof that the cardholder explicitly consented to recurring billing at the time of signup.

Evidence Type What to Submit
Signup Authorization The original recurring billing authorization with full timestamp, IP address, and email address, proving the cardholder consented to recurring charges at signup.
Terms of Service The terms of service or checkout consent record as it was displayed at the time of signup — it must have been clearly presented before the customer completed the transaction.
Cancellation Policy The cancellation policy as displayed at checkout, showing the cardholder was informed of the cancellation terms before subscribing.

#2 — Billing cycle record

The issuers evaluating a 4841 dispute are looking for one thing above all else: a clear chronological record showing whether a cancellation request was received before or after the billing date.

Evidence Type What to Submit
Billing Date Record The exact charge date and time from your billing system, with the amount. This establishes when the billing occurred.
Advance Billing Notice Email notification sent to the cardholder before the billing date — showing they received advance notice of the upcoming charge.
Prior Billing History Records of previous billing cycles on this subscription, showing the pattern of recurring charges the cardholder had already accepted without dispute.

#3 — Cancellation log

The most decisive evidence in a 4841 dispute. If the cardholder claims to have cancelled before the billing date, your cancellation log must show either that no cancellation request was received, or that the request came after the billing date.

Evidence Type What to Submit
No Cancellation Record An export from your cancellation log, support ticket system, or CRM showing zero cancellation requests received through any channel (email, portal, support ticket, phone) in the period before the billing date.
Post-Billing Cancellation 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.

Strongly Recommended Evidence

Required evidence establishes the billing timeline. Strongly recommended evidence establishes that the cardholder was actively using and engaged with the subscription — making a pre-billing cancellation claim implausible.

#4 — Continued usage after the billing date

Evidence Type What to Submit
Login Activity Account session logs showing the cardholder logged in after the disputed billing date. Include timestamps, IP addresses, and session durations. A customer who "cancelled" but logged in three times a week after the charge has a very difficult claim to sustain.
Feature Usage API calls, content access, feature interactions, or any platform activity after the billing date. Even low-level engagement (email opens, dashboard views) creates a documented post-billing activity record.
Download or Content Access For content-based services: download logs, content consumption records, or streaming data showing access after the billing date.
Strongest Defense

The strongest defense is a cancellation log showing zero cancellation requests before the charge, combined with continued product usage — logins, API calls, content views, or other activity — after the billing date. These two data points together make it extremely difficult for an issuer to sustain the cardholder's claim.

#5 — Billing notification emails

  • The advance billing notification email sent before the disputed charge, showing the cardholder was notified of the upcoming billing.
  • Open and click records from the billing notification, if available from your email platform.
  • The billing confirmation email sent on the date of the charge, confirming the cardholder was notified of the completed transaction.
  • Prior billing notification emails for previous cycles, establishing that the cardholder received and accepted these notifications consistently.

#6 — Absence of any cancellation attempt

  • State clearly that no cancellation request was received through any channel — email, support portal, live chat, or phone — prior to the billing date.
  • Export your customer support records for the 30–60 days before the billing date to demonstrate the absence of a cancellation request.
  • If your cancellation flow requires logging into the account and clicking through a cancellation workflow, include a screenshot of the process — demonstrating that cancellation requires deliberate action, not accidental omission.

Supporting Evidence

These items reinforce your case and become important at arbitration if the issuer upholds the dispute.

#7 — Subscription history and value delivered

  • Complete billing history showing how many cycles the cardholder accepted without dispute, demonstrating they understood and accepted 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 submitted, feedback forms completed — that indicate an engaged subscriber, not someone who thought they had cancelled.

#8 — Cancellation policy documentation

  • Your cancellation policy as displayed at signup, showing required notice period and process.
  • Screenshot of the cancellation flow within your product, showing the self-service process the cardholder would have needed to follow to cancel.
  • Any confirmation email the cardholder would have received upon successful cancellation — its absence from their inbox (and your send logs) is evidence no cancellation was completed.

Critical Mistakes

These errors consistently turn winnable 4841 disputes into losses. Audit your response against each one before submitting.

Mistake #1: No timestamped cancellation request log

If your system does not record when cancellation requests are received — or if that log is incomplete or easily fabricated — you cannot refute the cardholder's claim with certainty. The absence of a reliable cancellation log is the single biggest structural weakness in a 4841 defense.

What to do instead

Implement a cancellation log as a priority. Every cancellation request submitted through any channel should generate a timestamped, immutable record that includes the customer identifier, date, time, and channel. This log becomes your primary defense in any 4841 dispute.

Mistake #2: Submitting assertions without records

Statements like "the customer never cancelled" or "we have no record of a cancellation request" carry no weight with issuers unless supported by an actual log export or system record. Assertions without documentation are indistinguishable from fabrications to an arbitrator who cannot verify your claim.

What to do instead

Export your support ticket history, CRM communications, and cancellation portal logs for the relevant period. Submit those exports as exhibits — not a summary paragraph that could have been written without any underlying records.

Mistake #3: Terms of service that obscure the cancellation policy

If your cancellation terms are buried in fine print, hidden in a multi-page PDF, or absent from the checkout page entirely, issuers will be skeptical of your position even when the facts favor you. A court-document-style terms of service is not the same as a cancellation policy that is clearly disclosed at checkout.

What to do instead

Ensure your cancellation terms are displayed on the checkout page or subscription signup page in plain language — not just linked in a footer. Include a screenshot of the disclosure as it appeared at the time the customer signed up, showing the policy was front and center before they clicked "Subscribe."

Mistake #4: Not including usage logs

Usage data after the billing date is among the most powerful evidence available in a 4841 dispute — and it is consistently omitted. A customer who logged in, accessed content, or used features after the billing date cannot plausibly claim they had already cancelled before being charged.

What to do instead

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

Mistake #5: Failing to document advance billing notifications

Issuers look favorably on merchants who notify customers before charging. If you cannot show that the cardholder received advance notice of the billing date, the dispute becomes significantly harder to win — even if the cancellation timeline otherwise supports your position.

What to do instead

Archive all billing notification emails sent to customers before each recurring charge. Include the notification for the disputed billing cycle and, if available, notifications for the previous 2–3 cycles to demonstrate a consistent notification pattern the cardholder had previously accepted.

Winning Response Framework

Lead with the billing cycle chronology and cancellation log, then layer in usage data and consent documentation. The most persuasive response is the one that makes the timeline impossible to dispute.

Step 1 — Identify the chargeback clearly

Template Language
Case Number [DISPUTE_REFERENCE_NUMBER] We are submitting this representment in response to Mastercard 4841 chargeback claim against the [MM/DD/YYYY] transaction in the amount of [$AMOUNT] by [CARDHOLDER_NAME]. Please find our response and supporting documentation attached.

Step 2 — Summarize your case explicitly

State the billing chronology in plain language — lead with the cancellation log showing no request was received, and the billing date. Do not make the reviewer infer timing from exhibits.

Template Language
We respectfully dispute this chargeback. Our records demonstrate that no cancellation request was received prior to the billing date, and that the cardholder continued to use the service following the charge. 1. SUBSCRIPTION AUTHORIZATION Original signup date: [SIGNUP_DATE] Signup IP address: [IP_ADDRESS] The cardholder agreed to recurring billing of $[AMOUNT] per [BILLING_PERIOD] at account creation. Signed terms including cancellation policy attached as Exhibit A. 2. BILLING CYCLE RECORD Billing date: [BILLING_DATE] at [TIME] Amount charged: $[AMOUNT] Advance billing notification sent to [EMAIL] on [NOTIFICATION_DATE] — [X] days before billing. 3. CANCELLATION LOG Our cancellation log shows no cancellation request was submitted via any channel (email, portal, support ticket, or phone) in the 48 hours prior to [BILLING_DATE]. Full cancellation log export from [DATE_RANGE] attached as Exhibit B. 4. CONTINUED USAGE AFTER BILLING DATE Account activity logs show the following activity after [BILLING_DATE]: - [LOGIN EVENT] on [DATE] at [TIME] - [FEATURE USE / CONTENT ACCESS] on [DATE] at [TIME] Full activity log export attached as Exhibit C. 5. BILLING COMMUNICATIONS Advance billing notification sent [NOTIFICATION_DATE]. Billing confirmation sent [BILLING_DATE]. Copies attached as Exhibit D. Based on the above, we respectfully request that this chargeback be reversed.

Step 3 — Sequence your evidence by strength, not chronology

Priority Evidence Type
First Cancellation log export showing zero cancellation requests before the billing date.
Second Usage logs showing continued product access after the billing date.
Third Original signup authorization with timestamp, IP, and agreed terms. Advance billing notification email.
Last Prior billing history, cancellation policy display, terms of service.

Step 4 — Label and explain each exhibit

Label all attachments clearly as exhibits and reference them by exhibit letter in the body of your letter. Keep the response concise — include only evidence that directly addresses the cancellation timeline.

Template Language
Exhibit B: Cancellation Request Log — [DATE RANGE] Complete export from our cancellation management system showing all cancellation requests received between [START_DATE] and [BILLING_DATE]. No request associated with account [ACCOUNT_ID] or email [EMAIL] appears in this log.

Real-World Examples

✓ Winning Example — Project Management SaaS

The situation: $129/month project management tool. Cardholder disputed the Month 8 charge claiming "I cancelled this subscription two weeks ago."

Opening statement submitted:

Opening Statement
"Our cancellation log shows the cardholder's cancellation request was received on April 17 at 2:31 PM — three days after the April 14 billing date. The charge processed at 12:00 AM on April 14, before any cancellation request was submitted. Following the April 14 charge, the cardholder's account shows 11 login sessions, 47 task updates, and 3 project completions between April 14 and April 26. The cardholder was notified of the upcoming April 14 renewal via email on April 7 — 7 days in advance. No pre-billing cancellation request was received through any channel."

Evidence provided (in order submitted):

Page Evidence
1 Cancellation log export showing the April 17 cancellation request at 2:31 PM — timestamped 3 days and 2.5 hours after the April 14 billing. Log shows no prior requests for this account.
2 Usage activity log: 11 login sessions, 47 task updates, 3 project completions between April 14 and April 26. Session timestamps and feature interactions included.
3 Advance billing notification email sent April 7. Billing confirmation email sent April 14. Both shown with send and delivery timestamps.
4 Original signup authorization from Month 1, showing cardholder agreed to monthly recurring billing at $129. Terms of service and cancellation policy as displayed at checkout.

Result: Chargeback successfully represented. Claim withdrawn.

Why it won:

  • Timestamped cancellation log proved definitively that the request came after the billing date — the core issue in every 4841 dispute
  • 11 post-billing login sessions directly contradicts any suggestion the customer thought their access had ended before the charge
  • Advance billing notification proves the cardholder had 7 days' notice and chose not to cancel before the billing date
  • Complete evidence package left no gap for the cardholder's narrative to fill
✗ Losing Example — Online Fitness Subscription

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

What they submitted:

Response Submitted
"We searched our records and cannot find any cancellation request from this customer. Our system automatically processes renewals. The customer 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
"Cannot find any record" is not a log export Saying you searched and found nothing is an assertion — not evidence. The issuer has no way to verify whether you actually checked or whether your records are complete.
No usage data submitted If the cardholder was actively using the app before and after the billing date, that usage log would have directly contradicted their cancellation claim. It was never included.
No billing notification evidence No advance billing email was documented. Without proof of advance notice, the issuer cannot confirm the cardholder had an opportunity to cancel before being charged.
Terms of service without cancellation context Submitting the full terms of service document is not the same as showing the cardholder saw and accepted the cancellation policy at checkout. A terms PDF is not evidence of disclosure.

What they should have submitted:

  • An actual export from their cancellation log or support ticket system — even if showing zero records — with a timestamp confirming when the export was run
  • App usage logs showing login activity and workout completions before and after the billing date
  • The advance billing notification email sent before the renewal, with send date and delivery confirmation
  • A screenshot of the cancellation process within the app, showing the required steps — to demonstrate cancellation requires deliberate action that was not taken

Before You Submit

Run through this checklist before finalizing your 4841 response.

Subscription authorization

  • Original signup authorization with timestamp and IP address included
  • Terms of service and cancellation policy as displayed at signup included
  • Screenshot of checkout showing policy disclosure (not just a link to a policy page)

Billing cycle documentation

  • Exact billing date and time documented from your billing system
  • Advance billing notification email included with send date
  • Prior billing cycle history showing the cardholder accepted previous charges

Cancellation log

  • Actual log export — not a summary statement — showing no pre-billing cancellation request
  • Log covers all cancellation channels: email, portal, support ticket, phone
  • Export timestamp is recent and log is clearly labeled as a system export

Post-billing usage

  • Login activity logs for the 30 days after the billing date included
  • Feature usage, content access, or API call records included
  • Most recent post-billing activity date highlighted in opening summary
  • Response submitted within 45 days — target Day 30 internally for review buffer

Proactive Prevention

Subscription merchants face more 4841 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 a timestamped cancellation log as infrastructure Every cancellation request through any channel should generate an immutable, timestamped record. This is non-negotiable for any subscription business. Without it, you cannot defend 4841 disputes with confidence.
Send advance billing notifications 7–10 days before renewal Advance notice gives customers the opportunity to cancel before being charged. It also creates a documented notification record you can submit as evidence. Customers who receive advance notice file fewer disputes — and when they do, you have proof they were warned.
Log all product usage continuously Session logs, feature interactions, API calls, and content access must be recorded with timestamps and linked to the customer account. This data is your strongest post-billing evidence and is automatically generated — you just need to retain it for dispute resolution purposes.
Send cancellation confirmation emails When a customer successfully cancels, send an immediate confirmation email. This creates a definitive cancellation timestamp in your system and gives the customer proof that their cancellation was processed. The absence of this email in a dispute is powerful evidence no cancellation occurred.
Make your cancellation policy prominent at checkout Display your cancellation terms — including the required notice period — on the subscription checkout page, not buried in a terms of service PDF. A clear, visible policy that customers acknowledge before subscribing dramatically reduces "I didn't know" dispute claims.
About This Guide

This playbook is updated at least twice annually to reflect changes in Mastercard's dispute rules and issuer practices. Document Version: 2026.1 · Last Updated: March 2026 · Covers: Mastercard 4841 / Cancelled Recurring Transaction

Related Guides

Reason Code Guide · Mastercard Mastercard 4837: No Cardholder Authorization Reason Code Guide · Visa Visa 10.4: Other Fraud — Card Absent Case Study · SaaS Subscription Cancellation — $890 SaaS