Friendly Fraud: Examples, Consequences and Prevention (2026)

Friendly fraud is a cardholder dispute over a legitimate purchase made by that person or someone in their household. Some cases start with honest confusion, such as an unrecognized billing descriptor. Others involve deliberate abuse. Delivery alone does not invalidate a complaint, and not every dispute is dishonest.

In short, friendly fraud is the full range of first-party disputes, from honest mistakes to deliberate abuse. Chargeback fraud is the deliberate end of that range. This guide shows how to tell the cases apart, what evidence answers each claim, and when to fight, refund or accept.

Ecommerce brands carry much of this problem, which is why friendly fraud prevention for ecommerce combines alerts with evidence-backed recovery.

What Is Friendly Fraud?

The friendly fraud definition is simple. Friendly fraud, also called first-party misuse, first-party fraud 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. So in the friendly fraud vs chargeback fraud question, every chargeback fraud case is friendly fraud, but not every friendly fraud case is chargeback fraud.

Reason codes are examples and change between network rule versions. They do not show intent. For the deliberate subset, see friendly fraud and chargeback fraud compared. 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.
• In-game and in-app purchases: A child buys items on a stored card, and the cardholder disputes them as unauthorized.

Not every pattern involves a bad actor. Some friendly fraudsters act on purpose, but many disputes start with a family member, a forgotten renewal or a late parcel. That is why documentation, not accusation, builds the response.

Friendly Fraud by Industry: Where It Shows Up and What Evidence Works

The pattern changes by vertical, and so does the evidence that answers it. Use this table to pick the controls that fit your business.

Friendly fraud in gaming also shows the cost of a hard line. The FTC said Epic Games made it easy for children to rack up charges without parental consent and locked the accounts of consumers who disputed unauthorized charges; its $245 million settlement went to refunds (FTC, 2023).

The lesson for gaming merchants: add purchase confirmation and parental controls before a dispute, rather than punishing cardholders after one. See video game chargebacks for the full playbook.

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

Friendly fraud chargeback consequences reach well past the refunded order. Three numbers set the scale:

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. Newer data shows the problem is still growing.

The Merchant Risk Council's 2026 Global eCommerce Payments and Fraud Report, surveying 1,278 merchant professionals across 37 countries, found 64% report rising first-party misuse. One-quarter report increases of 25% or more.

Mastercard puts the average cost of a chargeback at $128 for the merchant: $82 in internal costs and $46 in third-party fees. The average disputed amount varies by industry:

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

How friendly fraud counts toward Visa's VAMP ratio

Friendly fraud disputes count toward Visa's Acquirer Monitoring Program (VAMP), whether the cardholder files them as fraud or as a dispute. Visa calculates the ratio like this:

Two exclusions matter for friendly fraud. Disputes resolved through pre-dispute solutions are excluded, and so are fraud reports that qualify for Compelling Evidence 3.0. Both depend on the timing of Visa's data extract, so resolve early (Visa VAMP fact sheet). For the full rules, see the Visa Acquirer Monitoring Program guide.

For cardholders, federal billing-error rules give 60 days to dispute a charge in writing, and if the issuer finds the cardholder was wrong, it must explain why in writing and state what they owe (CFPB). Repeat filers may face merchant blacklists or restricted dispute privileges.

For two common prevention decisions, compare 3D Secure with friendly-fraud prevention and chargeback prevention without broadly blocking good customers. Authentication evidence, remaining order risk and customer cost need separate answers.

Cómo prevención el fraude prevención

Start with your own operations. A 2022 Ethoca and PYMNTS study cited by Mastercard found that 71% of the ecommerce disputes it evaluated began with service errors. Fixing descriptors, delivery and support removes many disputes before any fraud tool is needed.

Some claims are valid, such as a minor placing the order or a refund that was too slow. If the refund already went through, see what to do when receiving a chargeback after a refund. 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).

Automated detection also pays for itself: ScienceSoft estimates that custom fraud detection systems in insurance return 200% to 1,000% ROI. It belongs to a broader chargeback mitigation strategy and an ecommerce fraud prevention framework.

Before the transaction

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

After delivery

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

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.

Reason codes friendly fraud disputes arrive under

The same friendly fraud claim gets a different code on each network. Match the code to the claim, then pull the evidence from the matrix above.

Networks revise codes, so confirm against the current rules. See the Visa chargeback reason codes, Mastercard chargeback reason codes and American Express chargeback reason codes guides, and how to use reason code data against friendly fraud.

Is Friendly Fraud Hard to Prove? Why Issuers Often Side With the Cardholder

Yes, friendly fraud is hard to prove. A merchant can show that a purchase happened and that goods arrived. It can rarely show who in a household placed the order, or what the cardholder intended. The dispute process also starts in the cardholder's favor.

• Zero-liability policies: Mastercard notes that many issuers file a chargeback by default unless the transaction is confirmed as legitimate.
• Billing-error rights: US cardholders can dispute in writing within 60 days, and the issuer must acknowledge the dispute within 30 days and investigate.
• Bad data loops: Mastercard warns that friendly fraud coded as true fraud can lead to false declines of good customers later.

What moves an issuer is structured, verifiable data. That means prior undisputed orders that match the device or IP address, merchant data shared through the network programs below, and delivery or usage records tied to the exact claim. A strong story without those records rarely wins.

How to Deal With Friendly Fraud: Fight, Refund or Accept?

Deal with friendly fraud one case at a time. Confirm the claim, fix anything valid, and fight only when your records answer the exact claim before the deadline.

Deadlines decide more friendly fraud cases than evidence does. Cardholders get months to file, but merchants get days to answer. One processor's published windows show the gap:

Source: Adyen dispute timeframes. Some travel and pre-order cases extend to 540 days. Your processor sets its own due dates, so check them, and see chargeback time limits for more networks.

Example (hypothetical): a $77 digital-goods dispute on Stripe in the US. The $15 dispute fee applies either way. Responding adds a $15 countered fee, returned only if you win, plus staff time. If access logs and prior orders match the claim, fighting can recover the $77. If they do not, accepting limits the loss.

How to Dispute Friendly Fraud Chargebacks

You can fight friendly fraud claims, 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. Start from a friendly fraud chargeback response template, and 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.

For a vendor-by-vendor view, see tools that prevent friendly fraud chargebacks.

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. When the dispute is deliberate and the shopper keeps the goods, merchants often call it digital shoplifting.

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. For a fuller side-by-side, see Visa CE3.0 vs Mastercard First-Party Trust.

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. For how Ethoca Consumer Clarity compares with Visa's pre-dispute tool, see our Order Insight vs Consumer Clarity comparison.

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.

Match the Friendly Fraud Control to the Cause

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.

Put this into practice with the fraud and abuse diagnostic, the repeat-abuse playbook and subscription renewal prevention.

More Friendly Fraud Prevention and Evidence Guides

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?
‍Accidental friendly fraud 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, as does broader consumer clarity on pricing and product details.

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 hard to prove?
‍Friendly fraud is hard to prove because a merchant can show a purchase and a delivery, but rarely who in a household ordered or what the cardholder intended. Issuers respond best to structured records: prior undisputed orders with matching device or IP data, delivery confirmation, and usage logs tied to the claim.

How should merchants deal with friendly fraud?
‍Merchants should deal with friendly fraud case by case. Refund valid complaints, use pre-dispute alerts on low-value orders, and fight with representment when records answer the exact claim. Clear descriptors, confirmations and tracking prevent many cases in the first place.

Is friendly fraud illegal, and can cardholders go to jail for it?
‍Knowingly filing a false chargeback can be treated as fraud in many places, but criminal cases against individual cardholders are rare. For merchants, the practical remedies are a strong dispute response, pre-arbitration where allowed, and declining future orders from repeat filers. This is general information, not legal advice.

How do merchants detect friendly fraud before it becomes a chargeback?
‍Friendly fraud detection starts with your own records. Compare the disputing cardholder against them: 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.

What is friendly fraud in gaming?
‍Friendly fraud in gaming is a dispute over an in-game or in-app purchase the account holder or a household member made, often a child using a stored card. Purchase confirmation, parental controls, receipts and login and usage logs reduce these disputes and support the response.

How long does a cardholder have to file a friendly fraud chargeback?
‍A cardholder usually has up to 120 days from the transaction date to file a friendly fraud chargeback on Visa, Mastercard or American Express. The merchant gets far less time to respond, often 9 to 40 days depending on the network and processor.

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.