Friendly Fraud: Causes, Evidence and Merchant Prevention

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.

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:

1. 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.
2. 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.

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.

Ejemplos de fraude «amigable» a los que deben estar atentos los comerciantes

• 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 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:

*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:

1. Lost revenue and inventory, since goods are rarely returned.
2. 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.
3. Labor to gather evidence and file responses.
4. Ratio exposure. Disputes count toward network monitoring programs such as Visa VAMP. See the chargeback thresholds guide.
5. 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.

Cómo prevención el fraude prevención

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. Antes de las transacciones:

• 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.

2. Después de las transacciones:

• 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. Para pedidos realizados por teléfono y a través del centro de atención al cliente:

Phone orders (MOTO) leave no delivery-tracking or IP trail like ecommerce orders, so a later claim of "I never placed this order" is harder to answer.

• 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.

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 324 million chargebacks globally by 2028, a 24% increase. The U.S. Treasury credits machine learning with helping prevent and recover more than $4 billion in fraud in FY24 (U.S. Treasury). The same logic applies across different industries. For example, ScienceSoft’s experience shows that insurance fraud detection solutions can unlock 200% to 1,000% ROI when supported by the right automation and analytics factors.

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.

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

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.

Preguntas frecuentes sobre el fraude amistoso

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.