Subscription Cancellation: $890 SaaS

Outcome WON dispute reversed

Network + Code MC 4841 cancelled recurring

Dispute Amount $890 monthly subscription

Industry SaaS B2B software

Resolution Time 38 days

The Dispute

A B2B SaaS platform received a Mastercard 4841 dispute for an $890 monthly charge. The cardholder — a business owner — claimed they had cancelled their subscription before the billing date. The merchant had no record of a cancellation request in any form: not through the in-app cancellation portal, not through customer support, not via email.

What made this case particularly winnable: the customer had continued logging into the product after the billing date they claimed to have cancelled before. Seven logins. Timestamped. From the same IP address the account had always used.

Mastercard 4841 disputes — “Cancelled Recurring Transaction” — are among the most common subscription chargebacks. They are also among the most winnable, provided the merchant maintains clean cancellation logs and captures post-billing usage data. This merchant did both.

Case Timeline

Day 1 $890 monthly charge processed. Billed per the contracted monthly cycle. No cancellation request had been received at this point.

Day 5 Chargeback filed. Cardholder contacts bank claiming they cancelled before the billing date. Mastercard 4841 code filed.

Day 10 Dispute received by merchant. Payment processor forwards the 4841 dispute notification with the cardholder’s stated reason.

Day 20 Response compiled and submitted. Cancellation logs, post-billing usage records, and subscription documentation assembled and submitted.

Day 38 Dispute resolved in merchant’s favor. Issuer reviewed the evidence and reversed the chargeback. Funds returned to merchant.

The Evidence

The merchant’s evidence package was built around two pillars: the complete absence of a cancellation request, and the documented presence of post-billing product use. Together, these made the cardholder’s claim implausible.

No cancellation request found in the support ticketing system (timestamped export provided, showing zero entries from this customer)
No cancellation found in the in-app cancellation portal (full portal log provided, showing zero cancellation events on this account)
Customer logged in 7 times after the billing date, with timestamps and IP addresses for each session
Original subscription agreement with explicit cancellation terms signed at onboarding
Terms of service shown at signup with “cancel anytime via portal or support” language — cardholder was informed of the cancellation process
Billing cycle documentation showing the $890 charge aligned exactly with the contracted monthly billing cycle
Three previous billing cycles on the same card with no disputes filed

The Response Strategy

The merchant’s response focused on two pillars: (1) the absence of any cancellation request in their logs, and (2) the presence of post-billing logins proving the customer was actively using the product after the alleged cancellation date.

The opening argument was direct:

Core Argument

“The simplest and most powerful evidence in a 4841 dispute is a timestamped cancellation log showing zero entries before the billing date. The merchant maintains cancellation records for every request made through any channel. This customer made no such request.”

The response then moved to the usage data. A cardholder who cancelled before the billing date does not then log into the product seven times after that date. The usage logs made the timeline implausible.

The response structure:

Lead with the cancellation log. Present the timestamped export showing zero cancellation events from this account. This is dispositive on its own.
Follow with post-billing usage. Seven logins after the alleged cancellation date, with timestamps and IPs. This is the secondary argument that makes the claim implausible even if the cardholder claims they “tried” to cancel.
Present the subscription agreement. Show that the cardholder signed an agreement with clear cancellation terms, demonstrating they knew how to cancel and chose not to.
Document three prior billing cycles. Three months of accepted charges on the same card, with no disputes — establishing this was a recognized and accepted recurring charge.

Why It Won

Post-billing logins are the smoking gun in a 4841 dispute. A customer who “cancelled before being billed” does not log into the product seven times after the billing date. The usage data made the cardholder’s claim implausible. Combined with a clean cancellation log showing zero requests, the issuer had no basis to rule in the cardholder’s favor.

The Mastercard 4841 code requires the cardholder to demonstrate that they cancelled the subscription before the disputed billing date. When the merchant can show (a) no cancellation request exists in any channel and (b) the cardholder used the product after the date they claim to have cancelled, the cardholder’s position collapses. Issuers are not required to take a cardholder’s word against documented merchant records.

Key Takeaways

Lessons From This Case

Build a timestamped cancellation log — every request must be recorded. Whether via portal, email, phone, or chat, every cancellation request must be logged with a timestamp. The absence of a log entry is your evidence.
Usage data after the billing date defeats cancellation claims. Log every login with IP and timestamp. Post-billing access is nearly impossible for a cardholder to explain if they truly cancelled before the charge.
In-app cancellation flows create a paper trail that email cancellations don’t. If a cardholder must click through a cancellation flow in your product, that non-event is documented. Email cancellations are easier to dispute. Build in-app flows and log every step.