Resources / Benchmarks

Benchmark

Chargeback Win Rates by Reason Code

Representment win-rate benchmarks by Stripe dispute reason code, with notes on what conditions move outcomes within each band.

·1 min read·Dispute Predator Research

[Body content to be written.]

Methodology

[Body content to be written. State sample size, time window, what reason-code mix is included, what's excluded, and what counts as a "win" vs. "lost" for benchmark purposes.]

High-recoverability codes

[Body content to be written.]

Reason code Typical win rate Decisive evidence
product_not_received [data] [data]
product_unacceptable [data] [data]
duplicate [data] [data]
credit_not_processed [data] [data]

Mixed-recoverability codes

[Body content to be written.]

Reason code Typical win rate Decisive evidence
subscription_canceled [data] [data]
unrecognized [data] [data]
incorrect_account_details [data] [data]

Low-recoverability codes

[Body content to be written.]

Reason code Typical win rate Decisive evidence
fraudulent [data] [data]
general [data] [data]
check_returned [data] [data]

What changes outcomes within a code

[Body content to be written. Explain that the bands above are mid-points; actual outcomes for any specific merchant are dominated by their evidence quality. A merchant with strong logistics integration and clean refund records wins consistently above the band; a merchant with sparse evidence wins below.]

Caveats

[Body content to be written. Reason: even within "fraudulent," subcodes vary — a real-card-stolen-card scenario has a different baseline than a friendly-fraud "I don't recognize this" filed by a customer who actually purchased. Aggregate benchmarks hide that signal.]