Friendly Fraud: Causes, Examples, and Merchant Prevention

Friendly fraud happens when a real customer disputes a legitimate, delivered purchase with their card issuer instead of asking the merchant for a refund. Nothing about the transaction was fraudulent: the payment was authorized and the order arrived, but the customer files a chargeback anyway.

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

The most-cited estimate of the annual cost, $132 billion, traces back to a 2020 FIS Global report cited by Mastercard. More recent data shows why the problem keeps growing regardless of the exact total: friendly fraud is now the dominant driver of chargebacks in eCommerce, real customers disputing real transactions.

This guide breaks down why it happens, how to prevent it, and how to win when it does.

That distinction, a real customer disputing a real transaction, is what separates friendly fraud from every other chargeback category.

What is Friendly Fraud?

Friendly fraud, also known as chargeback abuse or first-party fraud, is when a cardholder disputes a legitimate purchase by claiming it is unauthorized or fraudulent to obtain a refund, while often retaining the product.

Friendly fraud differs from every other type of chargeback because the instigator is your own customer, not a third-party fraudster, and the disputed transaction warrants no chargeback at all.

While the triggers and circumstances vary from case to case, cardholders commit friendly fraud for two main reasons:

1. They Forgot About the Transaction: Cardholders may not recognize a charge due to unclear merchant names on the statement or forgotten subscriptions. Cases resulting from this scenario are known as unintentional friendly fraud.‍
2. They Want to Steal From the Business: Some cardholders exploit the chargeback system to obtain free goods or services by disputing a purchase even when there is no merchant misrepresentation. They use this strategy to get their money back if they regret or dislike a purchase. This scenario is the dictionary definition of chargeback fraud.

“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

Friendly fraud covers the whole spectrum of first-party disputes, from an honest cardholder mistake to deliberate abuse. Chargeback fraud is the deliberate end of that spectrum: a cardholder who knowingly disputes a valid charge to keep the goods and the money. True fraud is different in kind, because the cardholder never made the purchase. Our guide to chargeback fraud covers the deliberate subset in depth; this page covers the full friendly fraud spectrum and how to prevent it.

Source: Visa, Friendly fraud explained. True fraud almost always arrives through card-not-present fraud, which is why the prevention stack for it sits before authorization, while friendly fraud prevention sits after the sale.

Examples of Friendly Fraud Merchants Should Watch For

Friendly fraud shows up in a handful of recurring patterns. Recognizing the pattern helps merchants pick the right prevention tactic and the right evidence to fight it, instead of treating every dispute as a one-off.

• Shared-card confusion: A family member or authorized user makes a purchase the primary cardholder does not recognize, so the cardholder disputes it as unauthorized instead of asking a household member first.
• Forgotten subscriptions: A recurring charge appears under an unfamiliar billing descriptor, and the cardholder files a dispute rather than checking their inbox for the original confirmation email.
• Received-but-disputed goods: The order arrives on time and as described, but the cardholder claims it never showed up, betting that the merchant will not produce tracking and delivery proof in time.
• Buyer's remorse after the return window: The cardholder decides they no longer want the item once the merchant's return period has closed, and disputes the charge as a workaround instead of requesting a late return.
• Continued use, then dispute: A cardholder keeps using a digital subscription or streaming service while simultaneously disputing the charge that pays for it.
• No-show and incidental-fee disputes: In hospitality and dining, a cardholder disputes a no-show fee or incidental charge they agreed to at booking.
• Bank-transfer recall abuse (Europe): The European Payments Council's 2023 Payments Threats and Fraud Trends Report records a card-free variant: payers recall settled SEPA credit transfers after receiving the goods, and some banks process SCT Recall requests without consulting the payee.

None of these patterns require the cardholder to be a criminal, which is exactly why documentation, not accusation, wins the case. The behavior is also increasingly normalized: social-media "chargeback hack" content and mainstream coverage such as Bloomberg Businessweek's July 2026 report on cardholders using friendly fraud against retailers treat the dispute button as a first resort, not a last one.

Friendly Fraud Consequences for Merchants

Friendly fraud is now the main driver of rising cardholder disputes. The Merchant Risk Council's 2026 Global eCommerce Payments and Fraud Report, surveying 1,278 merchants across 37 countries, found 64% report rising rates of first-party misuse, with one in four seeing increases of 25% or more. Mastercard puts the average cost of a dispute at $74, and it climbs with the ticket size of the category:

*Merchants in high-risk categories provide services related to gaming, gambling, and cryptocurrency exchange. Source: Mastercard.

For the full trend picture across every dispute category, see our chargeback statistics breakdown. The consequences for a merchant go well beyond the refunded order:

1. Lost revenue and inventory, since the goods are rarely returned and often resurface on secondary markets.
2. Chargeback fees of $15 to $100 per dispute, charged by your processor whether you win or lose.
3. Labor cost of gathering evidence and filing representments, or extra headcount to do it.
4. Ratio penalties: fraud-coded friendly fraud disputes count toward Visa VAMP and Mastercard ECM thresholds, and excessive ratios bring monitoring fees, fines, and in extreme cases loss of processing privileges.
5. Lost sales from over-correction, when stricter refund and verification policies push honest customers away.

Despite network fixes like Visa's Compelling Evidence 3.0, merchants still report first-party fraud growing faster than most other dispute types:

Source: Mastercard, 2025.

Cardholders are not immune. Under federal billing-error rules a cardholder has 60 days to dispute a charge in writing, but if the issuer finds the dispute unfounded it must reinstate the charge and tell the cardholder what they owe (CFPB). Repeat filers risk merchant blacklists, restricted dispute privileges, and account closure, though criminal prosecution for a single dispute is rare. That leaves the burden where it has always been: on the merchant to close the loopholes before the dispute is filed.

How to Prevent Friendly Fraud

Friendly fraud is hard to prevent because some claims are valid: a minor placed the order, or the cardholder tried to reverse it and your refund process was too slow. Prevention has to reduce confusion for honest customers while collecting the evidence that defeats deliberate abuse. Visa's own guidance is to verify the consistency of device IDs and IP addresses across repeat purchases, send purchase, renewal, and delivery notifications, and keep fulfillment and communication records ready for representment (Visa). Below are the preventive measures (part of a broader chargeback mitigation strategy) you can implement to stop friendly fraud from burning a hole in your balance sheet.

1. Before Transactions:

• Authenticate the buyer's identity (3DS2 on new or high-value orders) so a later "I never authorized this" claim has to survive the issuer's own verification record.
• Require customers to review and confirm orders before finalizing their purchase.
• Outline your return policy and ensure the customer accepts the terms.
• Consider making a phone call to confirm the purchase and address discrepancies when a high-value transaction or new customer is involved.
• Use secure payment service providers that comply with necessary security standards.
• Collect as much data as possible, including order history and contact information, to help address potential fraud (see our ecommerce fraud prevention guide for a full framework), and use AI based identity and behavior checks to detect first-party misuse before a dispute occurs.
• For hospitality and travel bookings, use pre-authorization holds and clear incidental-charge disclosures at check-in or booking to head off no-show and incidental-fee disputes before they are filed.

2. After Transactions:

• Send the buyer a detailed order receipt, including transaction description, order number, and details, and ensure they can access the same online.
• Provide real-time tracking to limit buyer's remorse or delivery doubts.
• Follow up with customers after delivery to confirm receipt and satisfaction; that confirmation becomes evidence if a chargeback arrives.
• Encourage customer reviews and feedback to identify lapses or showcase your brand image to prospects.
• Follow industry best practices for posting and recording transactions.
• Use chargeback alerts to prevent friendly fraud before it happens.

3. For Phone and Call-Center Orders:

Phone orders (MOTO, or mail order/telephone order) don't leave the delivery-tracking and IP-address trail that e-commerce transactions do, which makes them an easy friendly fraud target if a cardholder later claims they never placed the order.

• Record the verbal order confirmation, including the amount, item, and shipping address the caller stated.
• Read the order back to the caller before charging the card, and note in your system that you did.
• Use agent-assisted authentication tools that capture a callback number and cross-check it against the billing address on file.
• Send an order confirmation by email or text immediately after the call, the same way you would for an online order, so there's a timestamped record the cardholder can't claim they never saw.

Digital goods and subscriptions face the highest friendly fraud exposure because there is no physical delivery to prove; see how digital goods sellers combat fraudulent chargebacks for the usage-log evidence that works in that category.

How Visa and Mastercard Define First-Party Misuse

Visa and Mastercard do not use the phrase "friendly fraud" in their rules. 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 treats it as a data problem: the issuer sides with the cardholder because it cannot see the merchant's evidence that the cardholder made the purchase. Both networks answered with a rule set that lets merchants prove the link between cardholder and transaction with structured data instead of a narrative rebuttal.

The practical takeaway: both rule sets reward merchants who store device, IP, login, and delivery data on every order, not just disputed ones. Visa reports first-party misuse at roughly 20% of all fraudulent disputes globally and up to 30% for high-volume online merchants, so a repeat-customer base with clean transaction history is exactly the population these rules were built to protect.

Card Network Programs That Catch Friendly Fraud Before It Becomes a Chargeback

Beyond manual representment, Visa, Mastercard, and Visa-owned Verifi each run a program built specifically to resolve first-party disputes before or without a full chargeback. Card network resources tend to explain only their own program, so here is how the four compare and when each one applies:

None of these programs replace prevention or automated representment on their own. Use them as an additional layer: enroll in whichever your processor supports, keep collecting the transaction data CE3.0 and First-Party Trust need, turn on Consumer Clarity if you sell subscriptions, and set RDR rules conservatively so refunds only go out on cases you would likely lose anyway.

Liability Shift and 3D Secure: Who Pays When a Cardholder Disputes an Authenticated Transaction

3D Secure (3DS2 in the US, mandatory under PSD2 Strong Customer Authentication in the EU) is one of the few controls merchants can turn on before a transaction happens rather than fight after the fact. When a cardholder completes a 3DS2 challenge and the transaction is later disputed under a fraud reason code, liability for that fraud shifts to the card-issuing bank, not the merchant. Visa and Mastercard both extend this protection for 90 days after authentication, per Adyen's regulatory documentation.

3D Secure does not stop a cardholder from filing a friendly fraud dispute. It changes what that dispute can claim. A cardholder who completed a 3DS2 challenge cannot credibly argue they never authorized the transaction, since the issuer's own systems verified the cardholder at checkout. That pushes the dispute into a different reason code, such as goods not received or not as described, where the merchant's delivery and product evidence, not authentication data, decides the case.

Enable 3DS2 challenges for new customers, high-value carts, and any transaction pattern flagged by the card network programs above. Skip forcing a challenge on repeat, trusted customers: it adds checkout friction without meaningfully reducing dispute risk. One emerging edge case: when an AI shopping agent completes checkout on the cardholder's behalf, the authentication trail looks different, which raises new AI agent chargeback liability questions and calls for the evidence approach in our agentic commerce chargebacks playbook.

How to Dispute Friendly Fraud Chargebacks Successfully

Friendly fraud claims are winnable, but only with robust evidence and a repeatable process. Writing the losses off as a cost of sales tells repeat filers to keep going, and every lost fraud-coded dispute still counts against your ratio. If you can't keep your chargeback ratio under the card network-approved margin, you'll move into the card network monitoring programs and face severe fines.

So, how do you dispute friendly fraud and win? There are two strategies you can explore:

Option A: Manual Chargeback Representment

If you choose to pursue manual representment, be prepared to gather comprehensive, compelling evidence, such as:

1. Delivery proof (e.g., signed receipts, order tracking),
2. Cardholder signatures or IP address match for online transactions,
3. Copies of purchase receipts,
4. Return policy screenshots from checkout.
5. Relevant customer communication, e.t.c.

You need to submit your documentation promptly in the correct format, adhering to card network rules, and follow up if additional evidence is requested.

That said, traditional chargeback management practices are becoming increasingly ineffective, as cardholders can now file disputes with a single click. The process is time-consuming and often yields inconsistent results.

Even major financial institutions and card networks acknowledge the complexity of the traditional chargeback process. Mastercard says, “The chargeback process is costly and time-consuming. So, it should not be surprising that Financial Institutions (FIs) are steering away from manual human review toward analysis supported by automation or AI-based models.”

Option B: Automated Chargeback Dispute

Automated systems like Chargeflow handle the entire chargeback lifecycle so you can win disputes without lifting a finger. The outcome is typically more consistent, since automation removes the manual formatting errors and missed deadlines that sink individual cases.

The advantage of an automated chargeback management system like Chargeflow is that it:

1. Uses AI to scrutinize customer footprint in real-time to pinpoint impending friendly fraud, focusing on customer intent rather than identity.
2. Trains machine learning models on historical data to track inconsistencies between real transactions and fraudulent chargebacks, staying ahead of the curve in dispute prevention.
3. Streamlines chargeback processing, minimizing manual tasks and empowering merchants to recover revenue with ease.
4. Helps you block unwanted customers or stop chargebacks before they happen.

If you are comparing automated dispute options, look for:

• Transparent, verifiable win-rate reporting, not just a marketed average.
• Support for the card network programs above (CE3.0, First-Party Trust, RDR), not manual representment alone.
• Pay-on-success pricing instead of flat per-dispute fees.
• Direct integration with your payment processor and order data, so evidence submission does not require manual exports.

With global chargeback volume on track to climb from 261 million transactions in 2025 to 324 million by 2028 (Mastercard), automation is no longer optional at scale. 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 pattern-detection approach is what separates a friendly fraud dispute from a genuine one at the transaction level.

Stop Absorbing Friendly Fraud as a Cost of Doing Business

You cannot stop every friendly fraud dispute, but you can stop most of them before they are filed and win most of the rest. Close the confusion gaps (descriptors, confirmations, tracking), turn on chargeback alerts, store the device and login data that CE 3.0 and First-Party Trust reward, and let automated representment handle the evidence. Chargeflow's pre-transaction fraud screening flags high-risk orders before authorization, and its automated recovery files evidence-backed representments on the chargebacks that still land. Automate your chargebacks today.

Friendly Fraud FAQ

What is friendly fraud in simple terms?
‍Friendly fraud is when a real customer disputes a legitimate charge with their bank instead of asking the merchant for a refund. The purchase was real, the product was delivered, and the payment was authorized, but the customer files a chargeback anyway. Despite the name, there's nothing friendly about it for merchants.

What is accidental friendly fraud?
‍Accidental (or unintentional) friendly fraud happens when a cardholder genuinely doesn't recognize a charge, often because of an unclear merchant name on their statement or a forgotten subscription, and disputes it without meaning to defraud the merchant. It differs from intentional friendly fraud, where the cardholder recognizes the purchase but disputes it anyway to get free goods or a refund. Clear billing descriptors and proactive order confirmations are the best way to prevent the accidental kind.

What's the difference between friendly fraud and chargeback fraud?
‍Friendly fraud is the umbrella term for any dispute a real cardholder files against a legitimate transaction, whether by honest mistake or on purpose. Chargeback fraud is the deliberate subset: the cardholder knows the charge is valid and disputes it anyway to keep the goods and get the money back. Both differ from true fraud, where a criminal used stolen card details and the cardholder never made the purchase.

Is friendly fraud illegal?
‍Intentional friendly fraud, where a customer knowingly files a false dispute to keep goods or get a refund they're not entitled to, is technically fraud under the law in most jurisdictions. In practice, prosecutions are rare. But consequences do exist: merchants can blacklist repeat offenders, and banks can close accounts or restrict dispute privileges for customers with a pattern of abuse.

How do I prove friendly fraud to my bank?
‍You can't go directly to the bank, you respond through the chargeback representment process to the card network. The evidence that matters most is: proof of delivery (carrier timestamps, signature confirmation), proof of authorization (IP address, device fingerprint, login history for digital goods), customer communication logs, and a clear record of your refund policy shown at checkout. The goal is to connect the cardholder to the transaction in a way the issuer can't ignore.

Can you go to jail for friendly fraud?
‍Criminal prosecution for a single friendly fraud dispute is rare. Banks seldom refer individual first-party cases to law enforcement, the burden of proof is high, and pursuing one small transaction rarely justifies the cost for an issuer. That is exactly why merchants should not rely on the threat of legal consequences to stop repeat offenders: dispute alerts, compelling evidence, and the card network programs above do far more to change cardholder behavior than the possibility of prosecution ever will.

How do merchants detect friendly fraud before it becomes a chargeback?
‍Merchants detect friendly fraud by matching the disputing cardholder to their own transaction history: the same device ID, IP address, or account login on prior undisputed orders, continued product or subscription usage after the dispute, and a history of repeat disputes or refund requests on the account. Chargeback alerts surface the dispute the moment the cardholder contacts the bank, which is the window to refund a confused customer or gather evidence against a deliberate one.