Stripe is friendly to 'friendly fraud'

Source: Hacker News

Background

Friendly fraud is a term for chargebacks that the payment system struggles to prevent, even though large providers like Stripe have many signals that could help.

Case Study: Ciglue

I sold a product called Ciglue (cigar glue). A customer placed an order that was shipped via DHL and delivered with proof of delivery. The customer never requested a refund or a re‑delivery, but a dispute was filed.

The customer claimed the bank had mistakenly bundled the payment with other fraudulent transactions from the Philippines and offered to repay me through PayPal. I submitted all the evidence—delivery confirmation, customer communication, website policies—exactly as required.

It turned out the customer was deliberately lying, pretended not to have received the product, and the bank sided with them. The dispute was granted, and I lost the money, the product, shipping costs, and the dispute fee.

Before the dispute, the same customer placed another order with untracked shipping. A few days after the first dispute, a second dispute was filed. After the first dispute was granted, the customer emailed me to brag about the scheme.

Reporting to Stripe

I sent the screenshots to Stripe and asked whether the evidence could be reported to the bank, a fraud‑reporting network, or used internally. I did not expect Stripe to reverse the closed dispute, but I hoped the report would matter.

Stripe’s response indicated that they do not use evidence of chargeback abuse from one merchant to create cross‑merchant fraud signals or to take action against the customer’s card, email, or other details for other merchants.

Implications for Fraud Detection

Stripe markets Radar as a machine‑learning‑driven fraud‑prevention system that leverages a large network of signals. In theory, evidence that a customer is abusing chargebacks could improve those signals. In practice, the evidence appears to have no impact beyond the individual merchant’s account.

The recommended solution is to create Radar rules to block the offending customer from purchasing again, which may require an upgrade to a paid plan. This approach does not help other merchants who may encounter the same abusive customer.

Challenges for Small Merchants

Small merchants have limited leverage in disputes: the issuing bank makes the final decision, Stripe points to the bank, and the merchant bears the loss of money, product, dispute fees, and time. If new evidence emerges after the dispute deadline, it may be too late to submit.

When a fraudulent customer repeats the abuse with another merchant, the lack of shared fraud signals means the next merchant starts from scratch, unable to benefit from prior evidence.

Conclusion

The current handling of friendly fraud by Stripe leaves merchants without effective recourse. While Stripe’s Radar system is promoted as a robust anti‑fraud solution, evidence of chargeback abuse does not feed into broader fraud‑prevention mechanisms, leaving both merchants and the payment ecosystem vulnerable to repeat offenders.