Friendly Fraud: Causes, Evidence and Merchant Prevention

Chargebacks?
No longer your problem.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
TL;DR:
- Friendly fraud is a dispute a cardholder files over a transaction they or someone in their household made (Visa). Cases range from honest confusion to deliberate abuse, so delivery alone does not prove a claim invalid.
- Visa puts friendly fraud at around 20% of fraudulent disputes globally, and up to 30% for high-volume online merchants. 64% of merchants report rising first-party misuse (Merchant Risk Council, 2026).
- Match evidence to the stated claim: unrecognized purchase, not received, cancellation, digital use or refund missing.
- Prevent confusion with clear descriptors, confirmations, tracking and alerts that surface a dispute before it posts.
- Visa Compelling Evidence 3.0 and Mastercard First-Party Trust help in specific cases only. Neither guarantees a win on every reason code.
Friendly fraud is a dispute a cardholder files against a legitimate transaction that they, or someone in their household, made. Some cases come from honest confusion, such as an unrecognized billing descriptor. Others are deliberate abuse. Delivery alone does not prove a claim invalid, and not every dispute is dishonest.
Ecommerce brands carry much of this problem, which is why friendly fraud prevention for ecommerce combines alerts with evidence-backed recovery.
The most-cited cost estimate is $132 billion, a 2020 FIS Global figure cited by Mastercard. It is a historical estimate, not a current annual loss. More recent data shows the problem is still growing.
This guide covers why it happens, what evidence answers each type of claim, how to prevent it and how the card network programs fit in.
$132B Cited 2020 estimate (FIS Global, via Mastercard). Historical, not a current annual figure | 64% Merchants reporting rising first-party misuse (Merchant Risk Council, 2026) |
{{cta}}
What Is Friendly Fraud?
Friendly fraud, also called first-party misuse or chargeback abuse, is when a cardholder disputes a transaction that was legitimate, often claiming it was unauthorized or never received. Visa defines it as a dispute over a transaction the cardholder or a household member made. Unlike third-party fraud, no criminal used stolen credentials.
Cardholders file these disputes for two broad reasons:
- They do not recognize the charge. An unclear merchant name on the statement, a forgotten subscription or a purchase by a family member can lead to an honest mistaken dispute.
- They want the money back and the goods. Some cardholders knowingly dispute a valid purchase after regret or after use. This deliberate subset is chargeback fraud.
The label does not decide the case. The claim in the dispute and your evidence do. See what a chargeback is for the basics.
"First-party misuse has become more widespread and more damaging, both to merchant businesses and to the issuers, acquirers, and other payment partners that support eCommerce transactions." (Merchant Risk Council)
Friendly Fraud vs True Fraud vs Chargeback Fraud
These terms overlap, and providers do not use them identically. In this guide, friendly fraud covers the whole range of first-party disputes, from honest mistakes to deliberate abuse. Chargeback fraud is the deliberate end of that range. True fraud is different in kind: the cardholder never made the purchase.
| Dimension | Friendly fraud | True (third-party) fraud | Chargeback fraud |
|---|---|---|---|
| Who made the purchase | The cardholder or a household member | A criminal using stolen card details | The cardholder or a household member |
| Intent | Ranges from honest confusion to deliberate abuse | The cardholder is a genuine victim | Deliberate: keep the goods and get the money back |
| Example reason codes | Visa 10.4, 13.1 or 13.3, and Mastercard 4837 or 4853, depending on the claim | Visa 10.4 and Mastercard 4837 | Often the same codes as friendly fraud |
| Typical merchant response | Clear descriptors, alerts and confirmations. Respond with evidence that matches the claim | Authentication, AVS, CVV and velocity rules before authorization | Compelling evidence and repeat-filer detection |
Reason codes are examples and change between network rule versions. They do not show intent. Visa puts friendly fraud at around 20% of all fraudulent disputes globally, and up to 30% for high-volume online merchants (Visa, friendly fraud explained). True fraud usually arrives through card-not-present fraud, which is why its controls sit before authorization.
Examples of Friendly Fraud Merchants Should Watch For
- Shared-card confusion: A family member makes a purchase the primary cardholder does not recognize.
- Forgotten subscriptions: A recurring charge appears under an unfamiliar descriptor.
- Received-but-disputed goods: The order arrives, but the cardholder claims it did not.
- Buyer's remorse after the return window: The cardholder disputes instead of requesting a late return.
- Continued use, then dispute: A cardholder keeps using a digital service while disputing the charge.
- No-show and incidental-fee disputes: A guest disputes a fee agreed at booking.
- Bank-transfer recall abuse (Europe): The European Payments Council's 2023 Payments Threats and Fraud Trends Report records payers recalling settled SEPA credit transfers after receiving goods.
Not every pattern involves a bad actor, which is why documentation, not accusation, builds the response.
Friendly Fraud During Black Friday and Cyber Monday
Peak weekends raise friendly fraud for reasons that have little to do with fraud rings. ACI Worldwide expected friendly fraud to rise 25% between Thanksgiving and Cyber Monday in 2025, with the average friendly fraud transaction at $291, $52 higher than the same period a year earlier. Black Friday 2026 is November 27 and Cyber Monday is November 30, and the disputes from those orders arrive mostly from December through March.
Four patterns show up often at peak:
- Gift purchases: the item ships to someone else, and the cardholder or a household member does not connect the charge to the gift.
- Rushed checkouts and unfamiliar descriptors: a flash-sale purchase appears weeks later under a name the cardholder does not recognize.
- Late deliveries: a parcel that arrives after the occasion, or a carrier scan that lags, turns into a not-received claim.
- Remorse after the return window: the customer misses the holiday return deadline and disputes instead.
What to do before and during the peak:
- Check that your billing descriptor matches the name on your site.
- Send an order confirmation and tracking updates for every order. For gifts, include the item and ship-to details so the buyer can recognize the charge.
- Enroll in pre-dispute alerts before Black Friday, so you can refund while a dispute is still avoidable.
- Capture delivery evidence: carrier scans, plus a signature or delivery photo on high-value gifts.
- Publish dated holiday return terms on product pages, at checkout and in the confirmation email.
Plan for the lag. Cardholders commonly have up to 120 calendar days from the transaction date to dispute a charge (Adyen, dispute timeframes), which is about March 27, 2027 for Black Friday orders and March 30 for Cyber Monday orders. The full calendar, and how November disputes move your Visa VAMP ratio in January, are in our Black Friday and Cyber Monday chargeback guide. For the Q1 timing, see why Q1 is the real chargeback season. If a refunded customer disputes anyway, see holiday return and refund fraud, and for the full prep list, our BFCM readiness guide.
Friendly Fraud Consequences for Merchants
The Merchant Risk Council's 2026 Global eCommerce Payments and Fraud Report, surveying 1,278 merchant professionals across 37 countries, found 64% report increasing first-party misuse, with one-quarter reporting increases of 25% or more. Mastercard puts the average cost of a chargeback at $128 for the merchant, made up of $82 internal and $46 third-party costs. By industry, the averages are:
| Industry | Average chargeback cost |
|---|---|
| Travel and hospitality | $120 |
| High-risk categories* | $99 |
| Retail | $84 |
| Digital goods | $77 |
| Subscription services | $69 |
*Merchants in categories such as gaming, gambling and cryptocurrency exchange. Source: Mastercard.
See the chargeback statistics breakdown for the wider trend. Consequences go beyond the refunded order:
- Lost revenue and inventory, since goods are rarely returned.
- Processor dispute fees. At Stripe in the US, the received fee is $15 and is not returned. A $15 countered fee applies if you respond and is returned if you win. Other processors differ, as the chargeback fees guide shows.
- Labor to gather evidence and file responses.
- Ratio exposure. Disputes count toward network monitoring programs such as Visa VAMP. See the chargeback thresholds guide.
- Lost sales from over-correction when strict policies push honest customers away.
For cardholders, federal billing-error rules give 60 days to dispute a charge in writing, and if the issuer finds a dispute unfounded it must reinstate the charge and tell the cardholder what they owe (CFPB). Repeat filers may face merchant blacklists or restricted dispute privileges.
How to Prevent Friendly Fraud
Some claims are valid, such as a minor placing the order or a refund that was too slow. Prevention should reduce confusion for honest customers and collect records that answer deliberate abuse. Visa's guidance includes transparent billing language, clear purchase confirmations, detailed usage records for digital services and detection systems that spot patterns before chargebacks occur (Visa). It belongs to a broader chargeback mitigation strategy and an ecommerce fraud prevention framework.
1. Before Transactions:
- Authenticate buyers with 3DS2 on new or high-value orders where it fits your risk profile.
- Require customers to review and confirm orders before payment.
- Show your return policy and capture acceptance of the terms.
- Consider a confirmation call for high-value orders or new customers.
- Use secure payment service providers that meet security standards.
- Store order history, contact data, device and IP data to support later evidence.
- For hospitality and travel, use pre-authorization holds and clear incidental-charge disclosures at booking.
After payment, before fulfillment
A paid order still leaves a decision window before goods ship. Review the order’s risk signals and history, then approve it, request verification or cancel it according to the merchant’s configured workflow. Check the fulfillment system before treating a cancellation or hold as effective; a warehouse action may already be underway.
The Chargeflow Prevent documentation places this workflow after payment and before fulfillment. It can help flag potential abuse at that stage, but it cannot establish that a customer is dishonest or replace delivery evidence, return inspection and the later dispute response process. Keep the decision and its supporting records attached to the original order.
2. After Transactions:
- Send a detailed receipt with the transaction description, order number and details, and let the buyer access it online.
- Provide real-time tracking to limit delivery doubts.
- Follow up after delivery to confirm receipt. That confirmation becomes evidence if a dispute arrives.
- Collect reviews and feedback to spot lapses early.
- Record transactions consistently so reconciliation matches evidence.
- Use chargeback alerts to learn of a dispute while a refund is still possible. For post-purchase abuse screening, see Chargeflow Prevent.
3. For Phone and Call-Center Orders:
Phone orders (MOTO) may lack the browser device or IP trail available for an ecommerce checkout, but shipped phone orders can still have carrier tracking and delivery records. Record the purchase confirmation, relevant customer communication and fulfillment details so a later “I never placed this order” claim can be assessed against the actual transaction.
- Record the verbal confirmation, including amount, item and shipping address.
- Read the order back before charging the card and note that you did.
- Capture a callback number and cross-check it against the billing address.
- Send an email or text confirmation right after the call for a timestamped record.
Digital goods and subscriptions face high exposure because there is no physical delivery to show. See how digital goods sellers combat fraudulent chargebacks for the usage-log evidence that works in that category.
Claim-to-Evidence Matrix: What to Submit for Each Dispute Claim
Match your response to the stated claim. Each record below supports a defensible response. None of them proves intent on its own.
| Claim | Evidence to submit | Why it matters | What it does not establish |
|---|---|---|---|
| Unrecognized purchase | Billing descriptor, order confirmation, prior customer communications, login and device data | Links the cardholder or household to the order | Who in the household placed it |
| Not received | Carrier tracking, delivery confirmation, recipient and address details | Shows the item reached the stated address | That the cardholder personally received it |
| Cancellation | Terms shown at checkout, cancellation policy, cancellation request timestamps | Shows what the customer agreed to and when they asked to cancel | That the terms were clear to this customer |
| Digital use | Access records and usage logs tied to the account | Shows the service was used | That the cardholder, not someone else, used it |
| Refund missing | Refund IDs and timestamps | Shows the refund was issued and when | That the bank has posted it to the cardholder |
How to Dispute Friendly Fraud Chargebacks
Friendly fraud claims can be answered, but only with relevant evidence and a repeatable process. Lost fraud-coded disputes still count toward your chargeback ratio. Per Stripe, once a dispute is active the only way to overturn it is to submit evidence in a response.
Option A: Manual representment
Prepare compelling evidence that matches the claim, such as delivery proof, receipts, IP and device matches, checkout policy screenshots and customer communication. Submit it in the required format before the processor's due date. See the chargeback management guide for the full workflow.
Manual work is time-consuming and results vary. Mastercard notes that "the chargeback process is costly and time-consuming," and that financial institutions are moving toward automation and AI-based analysis.
Option B: Automated dispute response
Automated systems such as Chargeflow's evidence automation pull order, delivery and communication data and submit responses before the due date. If you compare options, look for:
- Transparent win-rate reporting with stated denominators, not only a marketed average.
- Support for the card network programs below, not manual representment alone.
- A clear pricing basis, including what you pay on lost cases.
- Direct integration with your payment processor and order data.
Mastercard projects global chargeback volume to grow 37% from 2025 to 2029, reaching 359 million a year. The U.S. Treasury credits machine learning with helping prevent and recover more than $4 billion in fraud in FY24 (U.S. Treasury).
How Visa and Mastercard Define First-Party Misuse
Visa calls it first-party misuse: a cardholder falsely claiming a purchase was unauthorized or fraudulent, as distinct from third-party fraud with stolen credentials. Mastercard calls it first-party fraud and runs a program that shares merchant data with issuers. Both programs reward merchants who store device, IP, login and delivery data on every order.
| Rule | Visa Compelling Evidence 3.0 | Mastercard First-Party Trust |
|---|---|---|
| Dispute type covered | Dispute condition 10.4, Fraud: Card-Absent Environment | First-party fraud disputes on card-not-present transactions |
| Evidence | Two prior undisputed transactions with the same cardholder, 120 to 365 days old, matching at least two of: user ID, IP address, shipping address, device ID or fingerprint. One match must be IP address or device ID. | Purchase history, device details, delivery information, identity elements and geographic location, shared with the issuer |
| When data is shared | Before a dispute through Order Insight, or after it in the pre-arbitration response | At transaction authorization or during the dispute process |
| Availability | Effective April 15, 2023 | US launch, expanded to Canada, Latin America, the Caribbean and Asia Pacific in June 2025 |
| Effect | Structured data can help overturn an invalid dispute that meets the criteria. The issuer and network rules decide | Includes merchant chargeback protection for disputes that follow the data-sharing requirements, per Mastercard |
Sources: Visa and Mastercard. Read the current Compelling Evidence 3.0 guidance before relying on it, since eligibility depends on the dispute type and your data.
Network Programs That Resolve First-Party Disputes Early
| Program | Network | How it works | When it applies |
|---|---|---|---|
| Compelling Evidence 3.0 | Visa | Uses prior undisputed transactions as structured evidence against a 10.4 dispute | Merchants with repeat customers and strong transaction history |
| First-Party Trust | Mastercard | Merchant and issuer data sharing before or during a dispute | Merchants whose processor can share transaction and device data with issuers |
| Rapid Dispute Resolution (RDR) | Visa (via Verifi) | Resolves a filed dispute before it becomes a chargeback, using merchant-set rules | High-volume merchants who want to refund cases they expect to lose |
| Ethoca Consumer Clarity | Mastercard (Ethoca) | Shows merchant name, logo and receipt details in the cardholder's banking app | Subscription and recurring-billing merchants |
None of these programs replaces prevention or a sound response process. Enroll in the ones your processor supports and set RDR rules conservatively.
3D Secure: What It Does and Does Not Change
3D Secure (3DS2) is a control you can apply before a transaction. When a cardholder completes authentication, liability for certain fraud-coded disputes can move to the issuer. The rules vary by network, region, card type and reason code, so check your processor's terms.
Authentication does not stop a cardholder from filing a dispute, and it does not cover non-fraud claims. A dispute can shift to a reason such as goods not received or not as described, where delivery and product evidence decide the case. Apply 3DS2 challenges where your risk is highest, and weigh checkout friction for trusted repeat customers. When an AI shopping agent completes checkout, the authentication trail looks different. See AI agent chargeback liability and the agentic commerce chargebacks playbook.
Reduce Friendly Fraud Without Treating Customers as Suspects
You cannot stop every dispute, but you can reduce the confusion behind many of them and answer the rest with evidence. Fix descriptors, confirmations and tracking, use alerts, store the data the network programs use, and match your response to the claim. Chargeflow Prevent screens orders after checkout and before fulfillment, and automated recovery handles evidence for the cases that still arrive.
{{cta}}
Friendly Fraud FAQ
What is friendly fraud?
Friendly fraud is a dispute a cardholder files over a transaction that they or someone in their household made. Some cases are mistaken, such as an unrecognized descriptor. Others are intentional. The purchase was legitimate in both situations.
Is friendly fraud the same as chargeback fraud?
The terms overlap. Friendly fraud covers any first-party dispute over a legitimate transaction, whether by mistake or on purpose. Chargeback fraud usually means the deliberate subset. Both differ from true fraud, where a criminal used stolen card details. What matters in practice is the claim and your evidence.
What is accidental friendly fraud?
It happens when a cardholder does not recognize a charge, often because of an unclear merchant name or a forgotten subscription. Clear descriptors and prompt order confirmations reduce it.
What evidence helps with a friendly fraud chargeback?
Match the evidence to the actual claim: transaction and authorization records, delivery confirmation, customer communication, and usage logs for digital goods. See the claim-to-evidence matrix above. The goal is to connect the cardholder to the transaction in a way the issuer can verify.
Is friendly fraud illegal?
Knowingly filing a false dispute can be treated as fraud in many jurisdictions, depending on the facts. Prosecutions are rare. This is general information, not legal advice.
How do merchants detect friendly fraud before it becomes a chargeback?
Compare the disputing cardholder against your own history: device ID, IP address and login on prior undisputed orders, continued usage after the dispute and repeat disputes on the account. Chargeback alerts surface the dispute while a refund is still possible.
Does friendly fraud increase during Black Friday and Cyber Monday?
It can. ACI Worldwide expected friendly fraud to rise 25% between Thanksgiving and Cyber Monday in 2025. Gifts, rushed checkouts, unfamiliar descriptors and late deliveries all raise the odds of a dispute, and those disputes typically arrive from December through March. Clear descriptors, alerts and delivery evidence reduce the exposure. See the Black Friday and Cyber Monday section above.
Recover Chargebacks Without the Paperwork
Chargeflow Automation builds and submits evidence for the chargebacks that still arrive.

Chargebacks?
No longer your problem.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.













.png)


