Stripe won't share friendly-fraud evidence across merchants, leaving sellers exposed

A small merchant selling cigar glue describes losing back-to-back chargebacks to a customer who admitted, in writing, to running a friendly-fraud scheme. Despite delivery proof, customer communications, and a screenshot of the buyer bragging about the scam, the bank sided with the customer and Stripe declined to act beyond the merchant’s own account.

When pressed, Stripe confirmed it does not feed chargeback-abuse evidence from one merchant into cross-merchant fraud signals, nor flag the offender’s card or email for other sellers. The recommended remedy is for the merchant to write their own Radar rules — a feature that typically requires a paid upgrade — to block that specific buyer from returning.

The merchant’s complaint targets the gap between Stripe’s marketing pitch for Radar, which leans on network-wide machine learning, and its actual handling of post-transaction abuse. Friendly fraud happens after checkout passes every signal, so prevention requires sharing evidence across merchants. Without that, each new victim starts from zero and serial abusers face no platform-level consequence.