What friendly fraud is
Friendly fraud, sometimes called first-party misuse, happens when the cardholder made or authorized the purchase but disputes it anyway — often as 'I don't recognize this charge,' 'I never received this,' or 'I already returned it.' The card itself was never stolen or misused by a third party.
It shows up for reasons ranging from a genuinely confusing statement descriptor, to a forgotten subscription, to a shared household card where one family member does not recognize another's purchase, to deliberate misuse of the dispute process to get a purchase for free.
What true fraud is
True fraud, or third-party fraud, is a transaction the actual cardholder never authorized at all — a stolen card number, a compromised account, or a card physically taken and used without the owner's knowledge.
These disputes tend to arrive with less ambiguity from the cardholder's side, since the person filing the dispute genuinely was not the one who made the purchase.
How each shows up in reason codes
Card networks generally group both under fraud-related reason codes rather than separating friendly fraud into its own category, which is part of why the two get conflated. The practical difference surfaces in the evidence available to respond, not in the code itself.
A neutral read of published network reason codes and how they map to your transaction types is a useful starting point before assuming a dispute is one type or the other.
Why descriptor and receipt clarity matters so much
A large share of 'unrecognized charge' disputes are resolved simply by the cardholder recognizing the transaction once it is described clearly — a billing descriptor that matches your storefront name, a digital receipt sent at the time of sale, or a reminder before a recurring charge posts.
Because friendly fraud so often starts as confusion rather than intent, tightening descriptors and receipts is one of the few prevention steps that addresses both a share of friendly fraud disputes and general customer service friction at the same time.
What evidence differs between the two
True fraud responses lean on verification data collected at the time of sale: EMV chip data for card-present transactions, and AVS/CVV results, device data or delivery-address matching for card-not-present orders.
Friendly fraud responses lean more on proof the cardholder engaged with the purchase: delivery or pickup confirmation, signed authorization forms, communication logs showing the customer used the product or service, or records showing a subscription was disclosed and not cancelled before the billing date.
How monitoring programs treat elevated fraud ratios
Card networks run monitoring programs that track a merchant's ratio of fraud-coded disputes to overall volume, generally without distinguishing between friendly and true fraud in that ratio. A merchant with a high proportion of friendly fraud disputes can still be flagged the same as one facing true third-party fraud.
That makes prevention work — clear descriptors, verification checks, delivery documentation — relevant to monitoring-program standing even when the underlying dispute was a cardholder misunderstanding rather than a stolen card.
Frequently asked questions
Is friendly fraud actually illegal?
Intentional misuse of the dispute process to get goods or services for free can constitute fraud, but many friendly fraud cases stem from genuine confusion rather than intent, which is part of why they are hard to prevent with a single fix.
Do card networks use a separate reason code for friendly fraud?
Generally no. Friendly fraud and true third-party fraud are typically coded under the same fraud-related reason codes, so the distinction shows up in the evidence rather than the code.
Can better receipts really reduce friendly fraud?
Clear, itemized digital receipts and recognizable billing descriptors address a meaningful share of 'I don't recognize this charge' disputes that originate from confusion rather than intent.
Does a high friendly fraud rate hurt my monitoring standing?
Monitoring programs generally track overall fraud-coded dispute ratios without separating friendly fraud from true fraud, so both can affect standing in a program.
What is the best evidence for a friendly fraud dispute?
Proof the cardholder engaged with the purchase — delivery confirmation, signed authorization, or communication records — tends to matter more than the verification data used for true fraud.
Can BSV Solution tell me which type of fraud I'm seeing?
A review of your dispute history and reason codes can help identify patterns, though classifying any individual dispute is ultimately determined through the network's dispute process.
Want a second opinion on your setup?
Tell us how you take payments today and a BSV Solution specialist will walk through the options with you. Eligibility and processor selection are reviewed individually, subject to underwriting approval.