Stripe is friendly to “friendly fraud”
Merchants using Stripe are frustrated that “friendly fraud” chargebacks—where a customer disputes a legitimate purchase—are routinely decided in favor of cardholders, leaving sellers to absorb product, shipping, and dispute fees. Many argue Stripe does too little with clear post-transaction evidence and cross-merchant signals unless merchants pay for add-on tools like Radar, while others note that card networks, banks, regulations, and Stripe’s incentives all favor maximizing successful payments over aggressively policing abuse. Alternatives like crypto or third‑party fraud services are mentioned, but each comes with its own adoption, usability, or regulatory challenges.
Overall framing: “Friendly fraud” and card networks
- Many see chargeback-friendly rules as a property of the entire card ecosystem, not just one processor.
- “Friendly fraud” = real cardholder makes a purchase, receives goods, then disputes as unauthorized to keep both item and money. Several merchants say this now dominates their chargebacks.
- Banks and networks are perceived to default to siding with cardholders, even when merchants claim strong evidence (delivery confirmation, attendance at a class, emails admitting fraud).
Stripe’s behavior and responsibilities
- Some argue Stripe simply passes through network/bank decisions and isn’t the primary culprit; the real issue is card brands and issuing banks.
- Others argue Stripe is large and well‑positioned to:
- Use cross‑merchant signals about abusers.
- Lobby or design better consumer/merchant‑balanced protections.
- A key complaint: Stripe reportedly does not use post‑dispute merchant evidence (even explicit admissions of fraud) to generate cross‑merchant risk signals.
- Several merchants report consistently losing disputes “no matter the evidence,” making Stripe feel “friendly to fraud.”
Radar, fraud tools, and incentives
- Stripe offers Radar as an extra anti‑fraud product, which some view as something that should be core.
- Merchants complain Radar scores clearly suspicious transactions as low risk; others say Stripe is balancing false positives vs approvals.
- There’s suspicion that Stripe has little economic incentive to fight chargebacks aggressively if merchants eat the cost.
Merchant countermeasures
- Common suggestions: automatically ban customers after a dispute (card, email, device), fingerprint devices, use 3DS/CVV, captchas, IP/country rules, and logs‑based pattern blocking.
- Pushback: these don’t help against “friendly fraud” where identity and details are legitimate.
- Some merchants accept that small losses are cheaper than heavy anti‑fraud engineering; others are enraged enough to build bans anyway.
Alternatives and complements
- Crypto (especially Monero) is proposed as a no‑chargeback, privacy‑preserving alternative.
- Counterpoints: poor mainstream adoption, UX hurdles, regulatory/sanctions risk for merchants, and practical difficulty obtaining privacy coins.
- Third‑party fraud/guarantee services (e.g., Signifyd, others) are mentioned as options that pre‑filter risk and sometimes insure merchants against lost chargebacks.
Geography and regulation
- Experiences with chargebacks vary by country: some report U.S./Canada as very cardholder‑friendly; others in Europe/Asia say disputes are rare and procedurally harder.
- Concerns raised about building cross‑merchant “bad customer” lists potentially conflicting with consumer‑reporting laws and creating PR blowback.