Friendly Fraud
- Friendly fraud is a cardholder knowingly disputing a purchase they really made, without a valid reason
- How common is it? Estimates vary. In the 2026 MRC survey, merchants put first-party misuse, a wider category than this page's, at 17% of their fraud-coded disputes (21% in North America). That's their estimate, not confirmed cases. Your own disputes are the number that counts
- Fight Visa fraud disputes (10.4) with Compelling Evidence 3.0 where your earlier purchase history qualifies
- Prevent with clear descriptors, easy refunds, and purchase confirmations
- A subset of first-party fraud (your own customer, lying). A forgotten purchase or a valid complaint isn't in it. Different from third-party fraud (stolen identity)
- Some sources call this first-party fraud or first-party misuse. Why the terms differ
Check what caused your disputes before buying tools. If real customers are disputing real orders, start with operations. Ask yourself: "Do I have a fraud problem, or a policy problem?" If customers dispute because they can't find how to cancel, your billing descriptor is confusing, or your refund process is slow, fix those first, and compare what each fix costs with the tools. See Refund Policy and Descriptors.
A customer got what they paid for, and the dispute says they didn't. If they knew that when they filed, it's friendly fraud on this site's definition. Other sources use the term more loosely (classification).
Same customer disputing again, or the same charge after a win? Start with the payment and case. Need to identify the allegation? Start with the customer's claim.
What Friendly Fraud Actually Looks Like
If you're not sure whether you're dealing with friendly fraud, here's what it looks like:
Scenario 1, digital goods abuse: Customer buys a course or digital product, accesses it 10 times over 60 days, then disputes as "unauthorized." They got the value and want their money back too.
Scenario 2, and why it usually isn't this: Customer signs up for a subscription, forgets about it, sees the charge 3 months later on their statement, and disputes instead of contacting you. That's confusion, unless they knew. Treat it as a descriptor and reminder problem.
Scenario 3, disputed delivery: Physical item delivered with tracking confirmation, but the customer says it never arrived. The carrier shows it delivered to their address. It's friendly fraud only if they really got it.
Check the records, not a silence deadline. Delivery, access and communications can help explain a claim. Waiting seven days or contacting the bank first doesn't establish that the customer lied. Verify the specific order and allegation.
Before buying a third-party fraud tool, check your own chargebacks. If real customers disputing real orders are your main problem, start with better descriptors, easier refunds, and clearer communication.
Your customer bought it. Used it. Then called their bank and said they didn't.
The Issuer's Reality
When a cardholder calls their bank to dispute, the agent doesn't see your beautiful evidence PDF yet. They see a transaction line item and a frustrated customer on the phone. If your descriptor is vague ("PAY*ACME" instead of "ACME WIDGETS"), you've already lost ground.
The bank's incentive: It wants to keep its cardholder happy. It receives interchange on their card purchases, and you're a stranger who might never transact again. To win a dispute, your evidence has to answer the cardholder's claim under the network's rules.
See also Fraud vs. Friendly Fraud in the Chargebacks section.
Why Customers Do This
Intentional Abuse
- Buyer's remorse disguised as fraud claim
- "Cyber shoplifting": get goods and money back
- Exploiting merchant fear of their chargeback ratio (how it's counted)
- Testing what they can get away with (see refund fraud)
Confusion, Not Friendly Fraud
These aren't friendly fraud on this site's definition. Check the actual complaint before you assign intent.
- Forgot about subscription renewal
- Didn't recognize merchant name on statement (see descriptors)
- Gave the card to a family member, then forgot they'd used it (which class that is)
- Genuinely confused but not malicious
Scale of the Problem
| Statistic | Source |
|---|---|
| 64% of surveyed merchants reported rising first-party misuse | MRC, Visa Acceptance Solutions and Verifi, 2026 survey, Figure 34. This is a share of respondents, not a share of chargebacks |
| Merchants put first-party misuse at 17% of their fraud-coded disputes (21% in North America), at an average $82 to resolve each | Same survey, Figure 34 and methodology pp. 3-4: 1,278 eCommerce payment and fraud professionals, November-December 2025. A merchant estimate of a wider category, and only fraud-coded disputes |
| "Up to 75% of all transaction disputes" are chargeback fraud | Verifi, a Visa company, citing a November 2021 Mercator report. An upper bound from an analyst estimate, not a measurement |
Detection Indicators
Records to Corroborate
Use these in your evidence framework. None alone shows the cardholder took part, so keep ordinary evidence separate from CE 3.0's qualifying history (Visa rules, 24 October 2026, section 11.6.1, pp. 685-690, and sections 11.8.5.3 and 11.8.5.6, pp. 709-716).
| Record | What to Check |
|---|---|
| Delivery confirmed to the shipping address used on earlier orders | Who received it, and whether it fits the allowed route for this claim |
| Digital product accessed post-purchase | Whether the access ties to the cardholder. It could be a takeover |
| Customer contacted support about the order, then disputed it as unauthorized | What they said, and when |
| Device matches prior purchases | Devices get shared, and a device match alone isn't CE 3.0 |
| Customer logged in after purchase | Whether it was them. A compromised account logs in too |
Supporting Signals (Tier 2 Indicators)
| Indicator | Notes |
|---|---|
| Repeat customer | Established relationship |
| Multiple prior successful transactions | Pattern of legitimate use (the history CE 3.0 draws on) |
| IP region near the billing location | Approximate context, within its accuracy radius. It doesn't place a person (MaxMind on accuracy) |
| No velocity alerts | Context only. An attack doesn't have to trip your rules |
Fighting Friendly Fraud
What the Issuer's Analyst Looks For
When representment comes in, the analyst is scanning for reasons to uphold your chargeback reversal. Here's what can make them pause:
- Visa CE 3.0 match: The disputed purchase matches earlier purchases neither reported to Visa as fraud, on the data CE 3.0 checks. That's hard to ignore.
- IP region and billing address: Cardholder claims fraud, but the IP's region is near their billing address? That's context for the bigger picture. IP location is approximate, and it can't place a person at an address.
- Post-purchase login/access: For digital goods: someone used the product after the purchase date. Tie those logs to the cardholder, and rule out a takeover or a shared device first. Then they can undercut an "I never bought it" claim.
- Support ticket before dispute: They contacted you about a problem, you offered a refund, they said "no thanks," then disputed? Document that.
What doesn't help: 15-page PDFs and screenshots of your TOS. Delivery evidence helps when it fits the allowed route for that claim. Keep it short and on the claim.
Pre-Dispute Prevention
- Clear merchant descriptors: "ACME INC" not "PAY*ACME". When the cardholder looks at their statement and doesn't recognize it, they call their bank. By then, you're already behind.
- Purchase confirmations: Email/SMS with line items. Make it obvious what they bought.
- Delivery confirmation: Photos can support a physical-goods case. For a Visa 10.4, check whether CE 3.0 fits before you rely on the photo alone.
- Easy refund path: A refund customers can find can stop a dispute before it's filed. If a chargeback is already open and you've decided to give the money back, don't refund separately. Accept the chargeback through your processor.
Is this another order or the same charge again?
Open the new notice beside the earlier case, then match the payment IDs, amount, currency and payment method. Save the current response deadline with both case records. An earlier response might not cover this notice. The date on your notice wins (deadline basics).
Stripe describes multiple disputes on one payment as extremely rare, and says its card dispute outcome is normally final. It also documents rare issuer-driven changes from lost to won. Stripe doesn't support arbitration through its platform. Other payment methods can follow different processes. VENDOR Stripe's dispute process.
In Stripe Dashboard, open Disputes, then select the case to read its reason and any available bank claim documents. Use the deadline for the active case. VENDOR Stripe's response guide.
Ask your provider:
I've got another notice for payment [ID]. Earlier case [ID] shows [status and date]. Is this a separate case or a later stage? Which claim needs a response, where, and by when?
If it's a different payment, review that order on its own, keeping a new renewal's payment record separate. Check the recurring billing guide. For the case you've already answered, check the dispute stage.
Blacklisting Considerations
Can I block their next order?
One dispute isn't a permanent buyer label, and neither is a fixed count of lost disputes, so check the order, payment and case records first. Was there duplicate billing or a legitimate complaint? Could the identifier have matched the wrong person? Record what you've observed, without guessing at intent.
Choose the narrowest step that fits those records, which might mean no restriction or a manual review. If you're considering a rule, check its scope first. Write down the reason, reviewer and review date, even if it's just your own name because you're handling it alone.
Give the customer a way to request a review:
I've put your next order into review. Please contact [support channel] with the order number so I can check it.
If you've found a mistaken match, check the underlying order before extending the restriction. Remove the mistaken list item or deactivate the rule, then record what changed and when you'll review it again. The provider controls below have different scopes and removal steps.
Check the controls before using them
A menu isn't permission for every account or use. Check the product, country and plan before changing anything.
| Product and scope | Where to check | Correction path and limits |
|---|---|---|
| Stripe Radar, if your plan supports Lists | In Dashboard, open Radar Lists. Create a typed list and reference it in a rule | List items can be added or removed. Check the identifier and rule that used it. Stripe Lists VENDOR |
| Shopify Payments | Shopify admin > Apps > Fraud Control > Rules > Create rule. Saving activates it | Select the rule in Rules to deactivate or delete it. Rules can block legitimate checkouts and don't guarantee chargeback prevention. Shopify Fraud Control VENDOR |
| Square, United States | Dashboard > Orders & payments (or Invoices & Payments or Payments) > Risk Manager > Block list > Add to list | Supports card, email and IP blocks, with removal steps. Shared or recycled IPs can affect unrelated buyers. Square Block List VENDOR |
Square's Risk Manager covers online payments and excludes Afterpay. That scope matters before you use a block. VENDOR Square Risk Manager.
For another product, ask support for its documented steps:
Which payment methods does this control cover? Which identifier does it match? How do I review a mistaken match and remove it?
Can I tell my processor or warn other sellers?
Keep your case record private while you check, because an internal note, a provider-approved report and a public warning are separate actions. A local restriction doesn't establish permission to share buyer details.
Ask your provider:
Is there an approved secure reporting channel? Which fields do you accept, and who receives them? How can I correct a mistaken report?
Don't upload a buyer list or publish identifying details as a warning. Check the provider's published policy and get qualified local advice before disclosure. A reporting feature doesn't establish the permission you need.
The UK's ICO asks organizations to consider necessity, fairness, transparency and risk before sharing personal data. Its guidance is under review following a law change. It doesn't establish permission for sellers in other countries. ICO data-sharing guidance.
Will these disputes get my account closed?
Start with the notice, rather than one buyer's history, and ask which account policy or named program it cites. Save the cases, reporting period and action date together. Check the count and denominator before treating a percentage as a safe limit.
If it's just you
Handling this yourself? Keep one private worksheet for the cases. If staff share the job, name the reviewer and correction contact.
Where blocks go wrong
A shared IP can catch an unrelated buyer. That's why Square warns about shared and recycled addresses. A block won't explain the earlier dispute's claim. Keep the case response and future-order review separate.
Test the worksheet first
Try the worksheet with made-up records, before changing controls. Include different orders, several notices on one payment and a mistaken shared identifier. It should show each current deadline and a correction contact. If a match isn't clear, leave the restriction undecided. Use a supported test environment or a supervised walkthrough. Don't test the rule with risky live orders.
Next Steps
Seeing friendly fraud chargebacks?
- Review Compelling Evidence 3.0: Know what can answer a dispute
- Check your descriptors: Reduce "I don't recognize" claims
- Set up alerts: Resolve before they become chargebacks
Want to prevent friendly fraud losses?
- Defend against fraud losses: Full strategy: 3DS, CE 3.0, evidence collection
- Implement device fingerprinting: Build CE 3.0 evidence
- Make refunds easy: Compare a refund with a chargeback on your own fees and costs
Ratio getting too high?
- Follow the playbook: Crisis response
- Understand network thresholds: Know the limits
- Consider restricting repeat abusers: Protect yourself
Related Topics
- Prevent Fraud: The fraud hub
- What Is a Chargeback?: Dispute basics
- First-Party Fraud: The umbrella category (friendly fraud is a subset)
- Third-Party Fraud: Stolen card/identity fraud
- Representment: How to fight disputes
- Compelling Evidence: Visa CE 3.0 and Mastercard requirements
- Reduce Chargebacks Playbook: Systematic reduction
- Chargeback Metrics: Tracking friendly fraud impact
- Device Fingerprinting: Device-based evidence
- Chargeback Lifecycle: Dispute timeline
- Network Programs: VAMP and ECM thresholds, with their conditions
- Chargeback Alerts: Pre-dispute resolution
- Refund Fraud: Related abuse patterns
Sources
| Source | Supports | Opened |
|---|---|---|
| Mastercard: Interchange rates and fees, US | Interchange flows from acquirers to card issuers; merchants pay their acquirer's merchant discount rate | 2026-10-23 |
| Stripe: How disputes work VENDOR | Multiple disputes per payment, final outcomes, late wins, arbitration and payment-method scope | 2026-10-21 |
| Stripe: Respond to disputes VENDOR | Current case, reason, available bank documents and response deadline | 2026-10-21 |
| Stripe: Lists VENDOR | Plan-dependent typed lists, rules and item removal | 2026-10-21 |
| Shopify: Fraud Control VENDOR | Shopify Payments scope, activation, deactivation and false matches | 2026-10-21 |
| Square: Block List, US VENDOR | Identifiers, Dashboard route, removal and shared-IP caution | 2026-10-21 |
| Square: Risk Manager, US VENDOR | Online-payment scope and Afterpay exclusion | 2026-10-21 |
| ICO: Deciding to share data | UK guidance on necessity, fairness, transparency and risk; under review | 2026-10-21 |
| MRC, Visa Acceptance Solutions and Verifi: 2026 survey REPORTED | Figure 34's merchant estimates, with their survey scope | 2026-10-21 |
| Verifi: Visa Compelling Evidence 3.0 VENDOR | The upper-bound analyst estimate it attributes, and friendly-fraud terminology | 2026-10-21 |