Friendly fraud in subscriptions: why customers dispute charges they made

Most chargebacks on subscription businesses are not stolen cards. They are real customers, using their own card, disputing a charge for a service they signed up for. The industry calls this “friendly fraud”; Visa and Mastercard increasingly use the more precise term first-party misuse. Sometimes it is deliberate. Much more often it is confusion: a forgotten trial, an unrecognized descriptor, a cancellation the customer thought had worked.

This guide explains why it happens in subscriptions, what the card networks have put in place to deal with it, and what you can do on your side. Network facts come from Visa’s friendly fraud explainer and Order Insight page, Mastercard’s First-Party Trust page and its 2024 article on first-party fraud, and Stripe’s docs on Visa Compelling Evidence 3.0 and dispute prevention (all accessed November 2026).

What counts as friendly fraud

Mastercard describes first-party fraud as a cardholder making a legitimate purchase, receiving the goods or services, and then claiming it was fraud. The intent varies:

Type	What happened	Typical reason code family
Honest confusion	The customer does not recognize the charge or forgot the subscription	Fraud (Visa 10.4, Mastercard 4837 or 4863)
Family or team use	A partner, child or colleague used the card	Fraud
Cancel confusion	The customer believes they cancelled, or tried to	Cancelled recurring (Visa 13.2, Mastercard 4841)
Buyer’s remorse	The customer regrets the purchase and uses the bank instead of asking for a refund	Fraud or “not as described”
Deliberate abuse	The customer uses the service and disputes to get it free	Any

The table matters because your response depends on it. Honest confusion is mostly a prevention problem. Deliberate abuse is an evidence problem.

Why subscriptions attract it

Subscription billing has features that make friendly fraud more likely than a one-off purchase:

• The charge comes without a fresh action. A renewal happens months after the customer last thought about you. Nothing on their side marks the moment.
• The descriptor may not match the brand. If the statement shows your legal entity name instead of the product name, the line looks foreign. See billing descriptors.
• Trials convert silently. A free trial that becomes a paid plan is a classic “I never agreed to this” moment. Visa’s trial rules require a reminder with a cancel link at least seven days before the first charge after a trial or promotional period.
• Cancelling is hard to find. If the cancel path is buried, the bank’s dispute button is easier. That is how a cancel request becomes a 13.2 chargeback.
• Annual renewals are large. A $600 surprise is far more likely to be disputed than a $10 one.
• Digital goods leave no parcel. There is no delivery confirmation; your proof is logs.

What the networks now offer merchants

Both major networks have moved in recent years to give merchants a fairer hearing on first-party misuse.

Visa Compelling Evidence 3.0

For card-absent fraud disputes (Visa reason code 10.4), Visa’s Compelling Evidence 3.0 lets a merchant show that the same cardholder made earlier, undisputed purchases. Stripe’s CE 3.0 docs list the core conditions: at least two prior undisputed transactions on the same payment method, between roughly 120 and 364 days before the disputed one, with matching identifiers such as IP address, device ID, customer account ID or address. For a subscription with a year of history, those prior renewals are exactly what you have. Details in Visa Compelling Evidence 3.0 explained.

Visa Order Insight

Order Insight lets issuers and cardholders see purchase details when a cardholder asks about a charge, so the question can be answered before it becomes a dispute. On Stripe, this is part of the dispute prevention product (Order Insights for Visa via Verifi, Consumer Clarity for Mastercard via Ethoca).

Mastercard First-Party Trust

Mastercard’s First-Party Trust program lets merchants share data, either at authorization or during the dispute, to show that the cardholder made the purchase. Mastercard says merchants must send at least one data point from a device category and one from a delivery category to qualify for its liability protection. Participation is optional. Mastercard’s 2026 press release describes the rollout to Europe; check availability in your region with your processor.

What you can control

The network programs help with evidence. Most of the gains are still in your own product and billing.

1. Make the charge recognizable

• Use a descriptor that matches the name customers know, and add a product suffix where your processor allows.
• Send a receipt for every charge, with the amount, the plan, the next billing date and a link to manage or cancel.
• Before annual renewals, send a reminder. Mastercard’s recurring billing standards require notices for subscriptions billed every six months or less frequently; see annual plan renewal reminders.

2. Make cancelling easier than disputing

A visible cancel button costs you a subscription; a dispute costs you the payment, a fee and some standing with the networks, and you lose the customer anyway. Offer a retention step if you want, but keep a one-click “cancel now” on every screen. See cancel flow best practices and click-to-cancel rules.

3. Make refunds easy to ask for

Many friendly-fraud disputes are refund requests that went to the bank because the customer did not see another option. A clear “request a refund” path, or a support reply within a day, catches some of them. A refund you issue is cheaper than a chargeback you lose.

4. Collect the data that wins

For subscriptions, the winning evidence is almost always the same, and you can only use it if you recorded it at the time:

• IP address and device identifier at signup and at each login.
• The customer account ID and email tied to each payment.
• Acceptance of terms, with timestamp and the exact text shown.
• Product usage with dates: logins, sessions, key actions.
• The full history of cancellation attempts, including flows that were started and abandoned.
• Every email and support conversation.

Pass IP address, customer email and product descriptions on each payment where your processor supports it; Stripe’s dispute prevention onboarding asks for these so CE 3.0 can work.

When the customer is not friendly

Some cases are genuinely abusive: a customer who used the product for months and disputes every charge. For these:

1. Stop future renewals on that card. Do not let the next charge add another dispute.
2. Defend the chargeback with the full usage record. The bank cannot see your logs unless you send them.
3. Keep the decision consistent. Write down your policy (for example, accounts with disputes are closed until the balance is settled) and apply it the same way every time.

Do not treat every dispute as abuse. A customer who could not find the cancel button is telling you something about your product.

A quick diagnostic

Look at your last 20 disputes and ask, for each one:

• Did the customer contact support first? If not, why not?
• Was it the first charge after a trial, or an annual renewal?
• Did the descriptor match the brand name?
• Did the customer start a cancel flow before the charge?
• Was there usage after the charge?

Clusters in these answers tell you where to fix things. For the decision on each individual case, see refund or fight.

Doing this with NoChurn

NoChurn’s cancel flows keep a one-click cancel visible at every step and record each answer, so a cancellation never turns into “I tried to cancel”. When a dispute arrives on Stripe or Braintree, NoChurn gathers the evidence automatically (cancel flow answers, emails sent, usage you send by API, help desk conversations read only) and drafts a reply with AI that a person reviews before it is sent. On Stripe, early fraud warnings come with a one-click refund. Every feature is on every plan; see pricing.