What it means
The term sounds harmless, but it can cost merchants revenue, goods and dispute fees, and it should not be used to accuse every cardholder who files a chargeback. The facts and dispute reason matter.
Visa and Mastercard describe friendly fraud or first-party misuse and merchant responses, noting situations such as forgotten purchases or unrecognised descriptors, and rules and evidence requirements vary by network and region. A chargeback is a cardholder-initiated dispute handled through their issuer and card network, and it is not the same as a merchant refund.
The issuer's process and deadlines govern the response. A fictional shopper receives a package, then disputes the charge as "not received", which may be deliberate misuse, but the merchant checks delivery and identity evidence first because a delivery scan alone may not settle every case.
Confusion causes many disputes. A fictional buyer contacts their bank after seeing a strange merchant name, but the charge is a legitimate subscription billed through a parent company, so a clearer statement descriptor could have prevented the dispute.
Family use can create similar confusion, because a household member may make a permitted purchase that the cardholder does not recognise, and the merchant should follow the network process rather than assuming criminal intent, as with a fictional parent who disputes a gaming purchase that the account log shows another family member made, where the cardholder's authorisation and applicable rules still need review. Some disputes reflect a real failure, such as goods not delivered, a cancellation not processed or quality different from the offer, and calling these "friendly fraud" erases the customer's complaint.
A fictional customer cancels a trial but is billed afterward, so the merchant investigates cancellation records and refunds when appropriate instead of contesting every dispute on principle. Prevention starts with clear billing descriptors, receipts, delivery updates, cancellation terms and accessible support, which help customers recognise charges and give merchants evidence if a dispute arises.
A fictional subscription service emails a reminder before renewal and makes cancellation visible, so fewer customers call their bank because they know what the payment is for, which is a service improvement and not just fraud control. Keep order, authentication, delivery and customer-contact records according to privacy rules and make the evidence match the dispute reason, because sending irrelevant personal data can harm customers without strengthening the response.
Representment is the merchant's response to a chargeback with evidence; it may recover funds if accepted but there is no guarantee, and filing must meet network and processor deadlines, so a fictional merchant with seven days under its processor's notice checks the live deadline and evidence checklist, since a generic copied letter would risk missing the actual claim. Track disputes by reason and outcome, since a high rate may signal unclear billing or operational failures, not only bad actors, and a fictional retailer that finds many disputes after a courier change may do better to improve tracking and support than to tighten payment screening.
Do not retaliate against customers who dispute charges, because account action, debt collection or legal claims require applicable terms and law, and a fictional marketplace with repeated suspicious disputes escalates through a documented risk process and obtains advice instead of posting the cardholder's name on social media. Use careful language in reporting, since "suspected first-party misuse" is more accurate than "fraud" when intent is unproven, and friendly fraud is best treated as a category of potential dispute risk where clear communication, evidence and fair complaint handling reduce avoidable chargebacks while protecting legitimate customers.
In practice
Real-world examples.
Example
A subscriber disputes a renewal because the billing name is unfamiliar. The company behind the subscription trades under a different brand name from the one on the card statement. The merchant shows the order record and updates its descriptor so the next renewal is recognised.
Example
A merchant answers a non-delivery dispute with relevant shipment evidence, such as the order confirmation, carrier tracking and earlier support messages. It does not attach unrelated customer records. The response is filed before the processor's deadline.
Example
A genuine cancellation error is refunded rather than branded fraud. The customer cancelled a trial in time, but the system billed the next period anyway. The merchant fixes the cancellation workflow and reviews other accounts for the same fault.
Formula
Calculation
No universal formula. Dispute rate can be measured as disputes / relevant transactions x 100 for a defined period, using the processor or network's specified denominator.
Worked example: a fictional merchant processes 1,500 card transactions in a month and receives 30 disputes. The dispute rate is 30 / 1,500 x 100 = 2%. If 12 of those 30 disputes turn out to be unrecognised descriptors, 12 / 30 x 100 = 40% of the disputes trace to a billing-clarity problem that the merchant can fix.Case study
Seen in the real world.
In this fictional case, Beacon Games sees chargebacks after a subscription renewal. Several customers did not recognise the statement name. It updates descriptors and reminders, reviews individual complaints and submits evidence only where appropriate. It does not label every dispute intentional.
The finance team also splits disputes by reason code and outcome each month. Disputes caused by the unfamiliar descriptor fall after the change, while a small group of repeat claimants is escalated through a documented risk review. The company treats the exercise as customer service and risk management together, and the case does not promise that any steps remove disputes entirely.
Watch out
Common mistakes.
- Calling every customer dispute deliberate fraud.
- Submitting irrelevant evidence or missing the processor deadline.
- Ignoring service failures that drive chargebacks.
Questions
People also ask.
Is friendly fraud always intentional?
No. Confusion or an unrecognised charge may explain some cases.
Can a merchant always reverse a chargeback?
No. The response depends on evidence, rules and issuer review.
What can reduce avoidable disputes?
Clear descriptors, receipts, delivery information and responsive support.
From the founder's library

Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%