Friendly Fraud, also known as "Chargeback Fraud" or "Claims Fraud," occurs when a legitimate customer makes an authorized purchase but later disputes the charge with their bank instead of seeking a refund from the merchant. Unlike criminal fraud involving stolen cards, friendly fraud involves the actual cardholder. This behavior is often driven by:
- Forgetfulness or Confusion: The customer doesn't recognize the Billing Descriptor on their statement.
- Buyer's Remorse: Attempting to reverse a purchase after the fact without going through the return process.
- Policy Avoidance: Trying to bypass a restrictive No Refund Policy or Unclear Refund Policy.
- Family Fraud: A family member makes a purchase without the primary cardholder's immediate knowledge.
Merchants defend against friendly fraud by maintaining deterministic proof of fulfillment, such as Insufficient Delivery Proof fixes and clear Website Trust and Disclosures. Excessive friendly fraud leads to a High Dispute Rate and potential Payout Holds and Rolling Reserves.
Why this term matters for Stripe account risk
Friendly Fraud is not only a vocabulary item. It is a live risk signal that influences how Stripe evaluates dispute exposure, payout predictability, and verification confidence for your account. When this signal appears together with abnormal refund velocity, delivery uncertainty, or weak policy disclosures, account controls can become stricter. Treat Friendly Fraud as an operational metric that should be monitored, documented, and explained with evidence.
Diagnostic signals to review weekly
- Track trend direction, not just a single snapshot. A persistent rise is more important than one isolated spike.
- Compare this signal with fulfillment timing, support response speed, and billing clarity to identify root causes.
- Document the exact trigger conditions so your team can reproduce, audit, and resolve the issue consistently.
- Escalate early when this term appears alongside dispute-heavy reason codes or repeated verification requests.
Practical actions to improve confidence
- Define an internal threshold and owner for this signal so actions are not delayed.
- Link this signal to a checklist in your operations workflow (checkout, fulfillment, support, and evidence retention).
- Update website disclosures and receipts so customer expectations match real delivery and billing behavior.
- Keep a short incident log with timeline, root cause, and remediation to support future platform reviews.
Further reading
- Problem: Friendly Fraud
- Problem: Card Testing Attacks
- Guide: Evidence Packets for Fraud Disputes
- Hub: Fraud Signals and Risk Patterns
- Glossary Index: All glossary terms
Where This Appears
Friendly Fraud commonly appears in the following Stripe risk scenarios: