# Friendly Fraud: What It Is and How Digital Sellers Can Fight It > Learn what friendly fraud is, why it costs digital businesses billions, and 10 practical strategies to prevent and dispute friendly fraud chargebacks. - **Author**: Ayush Agarwal - **Published**: 2026-04-05 - **Category**: Payments, Fraud Prevention, SaaS - **URL**: https://dodopayments.com/blogs/friendly-fraud-prevention --- A customer buys a software subscription, uses it for two weeks, then calls their bank and says they never authorized the charge. The bank sides with the customer. You lose the revenue, pay a chargeback fee, and have no easy way to recover either. The customer keeps access until you manually revoke it. That scenario plays out millions of times per year across digital businesses. It has a name: friendly fraud. And unlike true fraud, it is committed by real customers, often using perfectly valid payment methods, which makes it significantly harder to detect and stop before it happens. This guide breaks down what friendly fraud is, the specific scenarios that create it, and 10 concrete strategies for [friendly fraud prevention](https://dodopayments.com/blogs/chargeback-fraud-prevention) that digital sellers can put into practice now. ## What Is Friendly Fraud? Friendly fraud (also called first party fraud or first-party chargeback fraud) occurs when a legitimate customer makes a genuine purchase and then disputes the charge with their bank rather than seeking a resolution directly with the merchant. The word "friendly" is misleading. There is nothing friendly about it from the seller's perspective. The term simply distinguishes it from third-party fraud, where a criminal steals someone's card information to make unauthorized purchases. With friendly fraud, the cardholder and the fraudster are the same person. The customer authorized the transaction but later denies it or claims it was not fulfilled. Because card networks and banks almost always default to the customer's account of events, merchants absorb the loss. ### Friendly Fraud vs. True Fraud Understanding the distinction matters because the prevention strategies are completely different. | | True Fraud | Friendly Fraud | | ----------------------------- | ------------------------------------------- | ---------------------------------------------- | | Who initiates the transaction | A criminal using stolen card data | The actual cardholder | | Card authorization | Unauthorized | Fully authorized | | Dispute reason stated | Unauthorized transaction | Non-receipt, not as described, or unauthorized | | Merchant prevention lever | 3DS, velocity checks, device fingerprinting | Delivery proof, clear descriptors, usage logs | | Chargeback reason code | 10.4, UA02 (Visa/Mastercard) | 13.x, 12.x, 4853 | | Recoverable via dispute? | Rarely | Sometimes, with strong evidence | True fraud gets caught by fraud detection tools. Friendly fraud slips past them because the card is real, the customer is real, and the transaction looked completely normal at the time of purchase. ## Why Friendly Fraud Is a Growing Problem for Digital Businesses Digital products carry elevated risk for several interconnected reasons. **No physical delivery.** Disputing a purchase from a physical retailer requires claiming a package never arrived, which carriers can disprove. With software, games, SaaS seats, or digital downloads, there is nothing to track. Merchants need to build their own proof of delivery through login data, access logs, and usage records. **Frictionless purchasing.** One-click checkout and stored payment methods reduce the deliberate intent behind a purchase. Customers sometimes dispute charges that they made impulsively and then regretted, rather than accepting that they made a decision they want to undo. **Subscription confusion.** Customers who sign up for a trial and forget to cancel, or who do not recognize a billing descriptor months into a subscription, frequently reach for a dispute instead of contacting support. This type of dispute is often unintentional but produces the same financial outcome as deliberate fraud. **Low chargeback friction for consumers.** Filing a dispute with a bank takes a two-minute phone call or a few taps in a banking app. Customers face no documentation requirement, no deadline, and almost no risk. The structural imbalance between how easy it is to dispute and how hard it is to defend makes this problem self-reinforcing. [Revenue leakage from friendly fraud](https://dodopayments.com/blogs/revenue-leakage-saas) compounds in subscription businesses because the same customer can dispute multiple billing cycles before you identify the pattern. > Friendly fraud is the cost nobody budgets for. A 1% dispute rate on a $50 subscription sounds manageable until you add the chargeback fee, the lost revenue, the operational cost of responding, and the threat to your merchant account if the rate climbs. It compounds fast. > > - Rishabh Goel, Co-founder & CEO at Dodo Payments ## Four Common Friendly Fraud Scenarios ### 1. Forgot About the Subscription A customer signs up during a free trial, the trial converts to a paid plan, and the first charge hits three months after they last logged in. They see an unfamiliar amount on their statement, do not connect it to the product they trialed, and dispute it as unauthorized. This is probably the most common friendly fraud scenario in SaaS. It is not always intentional, but it creates the same chargeback as deliberate fraud. Proactive [dunning management](https://dodopayments.com/blogs/dunning-management) and renewal reminder emails before each billing cycle cut this significantly. ### 2. Buyer's Remorse A customer purchases a lifetime deal or an annual plan, uses the product for a few weeks, decides it is not for them, and discovers the refund window has closed. Rather than accepting the loss, they call their bank and claim the charge was unauthorized or that the product was not as described. This type of first party fraud chargeback is deliberate. The customer knowingly misrepresents the situation to recover money they willingly spent. ### 3. Family Member Purchased A child, partner, or other family member makes a purchase using a shared payment method. The primary cardholder sees the charge, does not recognize it, and disputes it as unauthorized without asking anyone in the household first. This is frequently unintentional but difficult to distinguish from deliberate fraud without transaction context. It is especially common with in-app purchases and gaming platforms where children access a parent's payment method. ### 4. Confused by the Billing Descriptor The name that appears on a bank statement is often not the product name the customer remembers. A billing descriptor showing "ACME HOLDINGS INC" for a product called "TaskFlow" creates genuine confusion. The customer disputes the charge assuming it is fraud, when it is actually their legitimate subscription. Billing descriptor confusion contributes to a measurable share of chargebacks that have nothing to do with intent. Fixing your descriptor alone can reduce your dispute rate noticeably. ## How Friendly Fraud Chargebacks Flow Understanding the mechanics of a chargeback helps you understand where prevention and evidence submission fit in the process. ```mermaid flowchart TD A[Customer disputes charge with bank] --> B[Bank issues provisional credit to customer] B --> C[Acquirer notifies merchant of chargeback] C --> D{Merchant decision} D -->|Accept| E[Loss confirmed, chargeback fee applies] D -->|Dispute| F[Merchant submits evidence within deadline] F --> G{Issuing bank reviews} G -->|Merchant wins| H[Funds returned, chargeback reversed] G -->|Customer wins| I[Loss confirmed] H --> J[Customer may file pre-arbitration] J --> K[Card network arbitration] K --> L[Final decision, additional fees apply] ``` The window to submit dispute evidence is typically 20-30 days from the chargeback notification date, depending on the card network and reason code. Missing that window means automatic loss regardless of how strong your evidence is. ## 10 Strategies to Prevent Friendly Fraud ### 1. Fix Your Billing Descriptor Your billing descriptor is the first line of defense against confusion-driven chargebacks. Most payment processors allow both a static descriptor and a dynamic descriptor that changes per transaction. - Use your product or brand name as the customer recognizes it, not your legal entity name - Keep it within 22 characters (the Visa/Mastercard limit) - Add a support phone number or URL in the descriptor where the processor allows it - Test it by making a real purchase and checking how it appears on an actual bank statement This single change eliminates a meaningful share of friendly fraud that stems from confusion rather than intent. ### 2. Send Clear Purchase Confirmations Every transaction should trigger an immediate confirmation email that includes: - The exact product or service purchased - The amount charged - The billing cycle (monthly, annual, one-time) - The next renewal date if applicable - A clear way to contact support - A link to cancel or manage the subscription A customer who receives a well-structured confirmation email the moment a charge processes is far less likely to dispute that charge because they do not recognize it. You can automate this entirely using [webhooks](https://docs.dodopayments.com/developer-resources/webhooks) tied to successful payment events. ### 3. Send Renewal Reminders Before Every Billing Cycle Subscription customers who are surprised by a renewal charge dispute at dramatically higher rates than customers who expected the charge. A reminder email three to seven days before each renewal gives customers the chance to cancel rather than dispute. This is especially critical for annual subscriptions, where twelve months can pass between charges. [Subscription fatigue](https://dodopayments.com/blogs/subscription-fatigue) is real, and customers who would have continued subscribing if they remembered they were paying may dispute an annual renewal simply out of surprise. The reminder should include the amount, the date it will process, and a direct link to cancel. Making cancellation easy sounds counterintuitive, but it produces far fewer chargebacks than making it difficult. ### 4. Make Cancellation Genuinely Easy The harder you make cancellation, the more customers escalate to their bank instead. From the customer's perspective, calling their bank takes two minutes. Navigating a confusing cancellation flow, sending emails that bounce, or sitting in a support queue for 30 minutes all feel worse. This does not mean removing cancellation safeguards entirely. It means putting a clear, reachable cancel option in your product and support channels so customers can leave without fighting you. Every customer who cancels cleanly is one who does not file a chargeback. ### 5. Collect and Retain Usage Evidence For digital products, "proof of delivery" means proof of use. Before a chargeback even happens, you should be collecting and storing: - IP address and device information at the time of purchase - Login timestamps and session durations - Feature usage records (pages visited, actions taken, exports created) - Support tickets, chat logs, and emails exchanged with the customer - Download records for downloadable products This data is your dispute evidence. Without it, you cannot prove the customer accessed what they paid for. With it, you have a strong case against almost any non-authorization chargeback. Store this data in a format you can export quickly when a dispute arrives. > The merchants who consistently win disputes are the ones who built evidence collection into their product from day one. IP addresses, device fingerprints, login timestamps, feature usage logs - all stored automatically so an evidence package can be assembled in minutes when a dispute arrives, not reconstructed from scattered systems after the fact. > > - Ayush Agarwal, Co-founder & CPTO at Dodo Payments ### 6. Use 3D Secure for High-Risk Transactions [3D Secure authentication](https://dodopayments.com/blogs/3d-secure-3ds-payment-authentication) adds a verification step between the customer and the card network before a transaction completes. When a transaction passes 3DS, the liability for unauthorized transaction disputes typically shifts from you to the card issuer. This means chargebacks filed under reason codes like "unauthorized transaction" can be deflected automatically because the issuing bank approved the authentication. 3DS is most effective on high-value or unusual transactions where the risk of fraudulent use is elevated. Note that 3DS does not protect against friendly fraud filed under non-authorization reason codes (like "not as described"). It is one layer in a broader prevention strategy, not a complete solution on its own. ### 7. Maintain a Clear Refund Policy and Honor It Fast A generous refund policy sounds expensive, but it is almost always cheaper than a chargeback. Chargeback fees typically run $15-$50 per dispute, plus the lost transaction value, plus the operational cost of responding. A refund costs only the transaction value. More importantly, a customer who contacts support and receives a prompt refund does not file a chargeback. Make your refund policy visible on your pricing page, checkout page, and in your onboarding sequence. When a refund request comes in, process it within one business day. A clean refund record also strengthens your dispute cases when you do contest chargebacks. Card networks view merchants with generous refund practices more favorably than those with restrictive policies. ### 8. Respond to Every Chargeback with Evidence Accepting chargebacks without disputing them signals to card networks that the disputes are valid, which makes it easier for future customers to dispute successfully and harder for you to win cases you should win. For every friendly fraud chargeback, build a response package that includes: - Transaction details (amount, date, IP address, device fingerprint) - The signed terms of service or checkout confirmation the customer agreed to - Login and usage records showing the customer accessed the product - All communication between you and the customer - Your refund policy and evidence that you honored it if applicable - The delivery confirmation email sent to the customer Submit this within the response deadline. Even if you do not win every case, winning a meaningful share reduces your overall dispute rate and shows the card networks you take fraud seriously. For more detail on how this process works, see our guide on [merchant of record chargebacks](https://dodopayments.com/blogs/merchant-of-record-chargebacks). ### 9. Monitor Your Chargeback Rate by Reason Code Not all chargebacks require the same response. Visa and Mastercard categorize chargebacks by reason code, and the reason code tells you what the customer (or their bank) claims happened. - Reason codes in the 10.x range (Visa) indicate fraud claims - Reason codes in the 13.x range indicate customer disputes like non-receipt or not as described - First party fraud chargebacks typically arrive under 13.1 (merchandise not received) or 13.5 (misrepresentation) Track your chargebacks by reason code monthly. A spike in a specific code tells you exactly where to intervene. A surge in 13.1 disputes might indicate a delivery confirmation problem. A surge in 10.4 disputes might indicate your card-not-present controls need tightening. This kind of segmented monitoring turns your chargeback data from a lagging loss indicator into a leading signal for operational issues you can fix proactively. ### 10. Use a Merchant of Record The most comprehensive approach to [friendly fraud prevention](https://dodopayments.com/blogs/chargeback-prevention-saas) for digital businesses is working with a [Merchant of Record](https://dodopayments.com/blogs/what-is-a-merchant-of-record). An MoR sits between you and your customers as the legal seller of record, which means the MoR, not you, owns the merchant account and absorbs the chargeback liability. When a customer disputes a charge processed through an MoR like [Dodo Payments](https://dodopayments.com), the dispute goes to the MoR's merchant account, not yours. The MoR handles evidence submission, dispute resolution, and absorbs the chargeback fee. Your dispute rate at the card network level is zero, because you do not have a direct merchant account to report against. MoRs also bring scale advantages you cannot replicate as a single business. They have dedicated dispute teams, established relationships with acquiring banks, pre-built evidence collection systems, and the transaction volume to negotiate favorable terms. They also handle chargeback-adjacent issues like [disputes and RDR (Rapid Dispute Resolution)](https://docs.dodopayments.com/features/transactions/disputes), which can resolve certain disputes automatically before they become chargebacks. If your chargeback rate is already above 0.5%, or if managing disputes is consuming meaningful time from your team, an MoR is likely the highest-leverage change you can make. See [Dodo Payments pricing](https://dodopayments.com/pricing) for what this looks like in practice. ## Building a Dispute Evidence Package When a friendly fraud chargeback arrives, you typically have 20-30 days to respond with evidence. Having a template ready in advance means you can respond within hours rather than scrambling at the deadline. A strong evidence package for a friendly fraud dispute includes: **Transaction evidence** - Date, amount, and card details of the transaction - IP address and geographic location at the time of purchase - Device fingerprint or user agent string - AVS (Address Verification System) and CVV match results **Customer identity evidence** - The email address the customer used to create their account - Any identity verification steps completed during signup - The billing address provided versus the card's registered address **Delivery and access evidence** - Confirmation email delivery record (with timestamp) - Login records showing the customer accessed the product after purchase - Feature usage data showing the product was actively used - Download records for downloadable products **Agreement evidence** - Screenshot of the checkout page showing what the customer agreed to purchase - Link to or copy of the terms of service accepted at checkout - Your refund policy as displayed to the customer at the time of purchase **Communication evidence** - Any support tickets, chat logs, or emails from the customer - Absence of any cancellation or refund request prior to the dispute Organize these into a single PDF and submit via your payment processor's dispute portal before the deadline. For disputes managed through an MoR, this process is handled on your behalf. ## FAQ ### What is the difference between friendly fraud and chargeback fraud? Friendly fraud and chargeback fraud refer to the same behavior: a customer who made a legitimate purchase disputes the charge with their bank. "Friendly fraud" is the industry term used by payments professionals. "Chargeback fraud" or "first party fraud" is used interchangeably. The term "friendly" does not imply the behavior is harmless. It simply distinguishes it from third-party fraud where a criminal uses stolen card data. ### How common is friendly fraud for digital products? Industry estimates vary, but friendly fraud accounts for 60-80% of all chargebacks at digital merchants, depending on the product category. Subscription software and digital downloads see some of the highest rates because there is no physical delivery to prove and the purchase flow is frictionless. The problem has grown as one-click purchasing and digital banking apps have made both buying and disputing transactions easier. ### Can I win a friendly fraud chargeback dispute? Yes, but win rates vary significantly based on the reason code, the evidence you submit, and the card network's policies. For disputes where you can demonstrate the customer accessed the product after purchase, win rates of 30-50% are achievable with a complete evidence package. Disputes filed under unauthorized transaction reason codes (where the customer claims they never made the purchase) are harder to win unless you have strong authentication evidence like 3DS completion records. ### Will banning a customer after a friendly fraud chargeback help? It prevents future transactions with that specific customer, which reduces future exposure. But it does not recover the disputed amount, and it does not prevent the chargeback from counting against your dispute rate. If you identify a customer who has disputed multiple transactions, terminating their account and blocking their payment method is reasonable. Some merchants also submit their details to fraud consortium databases, which can prevent the same customer from abusing other merchants. ### Does using a Merchant of Record protect against friendly fraud entirely? Using an MoR like [Dodo Payments](https://dodopayments.com) means the MoR handles all chargeback liability, so friendly fraud disputes do not appear on your merchant account or affect your dispute rate with card networks. The MoR disputes the chargeback on your behalf using their established processes and relationships. This does not eliminate the cost entirely, since MoRs price their protection into their fees, but it removes the operational burden, protects your merchant account health, and gives you access to dispute infrastructure that would be expensive to build independently. --- - [More Payments articles](https://dodopayments.com/blogs/category/payments) - [All articles](https://dodopayments.com/blogs)