Disputes in needs_response or warning_needs_response, clock is ticking on evidence.
At a glance
Real-time count of Stripe disputes that require merchant action. Specifically status IN ('needs_response', 'warning_needs_response'), both states have a hard 7-day evidence-submission deadline (10 days for early-warning chargebacks). A missed deadline equals an automatic loss; the funds are debited from the merchant’s Stripe balance plus a $15 dispute fee. The card answers “how many evidence packs are due right now”.
Calculation
Calculated automatically from your Stripe data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A US DTC apparel brand on Shopify + Stripe, monthly volume ~$420,000 across ~3,200 charges. Reading at 14:00 UTC on 12 Apr 26.
What’s interesting:
- The card alerts at
>0, so 11 is a 5-alarm operational fire. Each open dispute is a deadline. The 8 formal chargebacks have a median 4 days remaining; missing those deadlines means losing 15 = 1,960 at stake. - The 3 early-warning disputes are the highest-leverage subset. Visa RDR and Mastercom Collaboration disputes are pre-chargeback, the merchant can refund the customer pre-emptively (full or partial) and the chargeback never files. The cost is the refund itself; the avoided cost is the chargeback (which counts against the merchant’s chargeback rate threshold of 0.9% / 1.5% with card networks). For low-value cases, refunding is almost always cheaper than fighting.
fraudulentis the dominant reason (6 of 11). This signals true fraud (stolen card used at checkout) where chargeback win rate is structurally low (<10% even with strong evidence). The right action is usually to document the case for Stripe Radar tuning rather than fight; pair this card with Radar Score Distribution to identify whether Radar is letting through cards it should be blocking.product_not_receivedandunrecognizedare winnable. These have higher win rates (40 to 70%) with strong evidence: shipping carrier delivery confirmation, customer email correspondence, IP-address-at-purchase logs. Each takes 30 to 60 minutes of evidence-pack assembly; at 230/hour effective time-saved if won.- **The total at-risk is 165 in dispute fees = 420,000/month merchant, this is 0.6% of monthly revenue tied up in disputes. The chargeback-rate threshold is 0.9% (Visa) / 1.5% (Mastercard) of total transactions; at 11 open disputes against ~3,200 charges this merchant is at 0.34% chargeback rate, well below threshold but worth monitoring.
product_not_received, unrecognized), refund the early-warning cases pre-emptively, and accept losses on most fraudulent cases unless evidence is unusually strong.
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in Stripe Dashboard: Payments → Disputes for the full per-dispute list with status, reason, deadline, and evidence-submission state. Filter toStatus = Needs response for the formal chargebacks that match this card’s primary count. Filter to Status = Warning needs response for the early-warning subset.
The Disputes overview view provides aggregate trend data; useful for the rate-and-trend cards but not for the live count.
Why our number may legitimately differ from Stripe Dashboard:
Cross-connector reconciliation:
The most useful reconciliation rule: open disputes count + closed disputes (last 30 days) ÷ total successful charges (last 30 days) should be < 0.9% to stay below Visa’s threshold; < 1.5% for Mastercard. Above either, Stripe will start applying their own monitoring program (additional fees, mandated chargeback prevention requirements).
Known limitations / merchant FAQs
The card alerts at>0. That seems aggressive. Should I change it?
The threshold is deliberately tight because every open dispute has a hard deadline. A missed deadline equals an automatic loss; the funds plus dispute fee are debited from your Stripe balance with no recourse. The right operational pattern is daily triage, not weekly. If your dispute volume is so high that the binary alert produces noise, the right fix is reducing dispute volume (Radar tuning, payment-method updates, fulfilment improvements), not raising the threshold.
Should I always submit evidence, or refund pre-emptively?
Depends on the dispute reason and value. (a) fraudulent: refund pre-emptively if early-warning, accept loss if formal chargeback unless evidence is unusually strong (e.g. delivered to verified billing address, customer email confirming receipt). Win rate <10% on fraudulent even with strong evidence. (b) product_not_received: fight if you have shipping carrier delivery confirmation; win rate 60 to 80%. (c) unrecognized or customer_initiated: fight if you have customer email correspondence or IP-address-at-purchase logs; win rate 40 to 60%. (d) duplicate: refund the duplicate immediately and submit evidence of the legitimate charge; win rate 70 to 85%. (e) subscription_canceled or subscription_disagreement: review the subscription cancellation flow; refund if the cancellation was attempted but the system kept charging.
What is “early warning” / warning_needs_response?
Visa Rapid Dispute Resolution (RDR) and Mastercom Collaboration are pre-chargeback notification services. The card network notifies the merchant before the formal chargeback files; the merchant has ~10 days to refund the customer pre-emptively. If refunded, no chargeback files. If not, the chargeback proceeds. Refunding pre-emptively is almost always cheaper than fighting the formal chargeback because: (a) you avoid the $15 dispute fee, (b) you avoid the chargeback-rate impact (which counts against your account threshold), (c) the customer gets the refund faster and is less likely to escalate further.
My chargeback rate is approaching 0.9%. What happens at 0.9%?
Visa’s Chargeback Monitoring Program (VCMP) and Mastercard’s Excessive Chargeback Program (MECP) flag merchants above 0.9% (Visa) / 1.5% (Mastercard) chargeback rate. Stripe is required to enrol you in their internal monitoring program at these thresholds; expect mandatory chargeback-prevention measures (3DS for high-risk transactions, additional Radar rules, reduced authorisation limits) and an additional ~$30/month per program. If the rate stays elevated for 4 to 12 consecutive months, your Stripe account can be terminated. The threshold is the prevention line; below 0.5% is healthy.
A single high-value dispute could move my chargeback rate from 0.4% to 0.9%. Is that possible?
Yes for low-volume merchants. Chargeback rate is chargebacks ÷ transactions; on a 200-transaction merchant a single chargeback is 0.5%. The threshold-management pattern: low-volume merchants need to fight every dispute aggressively because the rate impact is large; high-volume merchants can afford to refund-pre-emptively because the rate impact of any single dispute is small.
Why is fraudulent reason so hard to win even with evidence?
Card networks have a structural bias toward the cardholder for fraud claims because the alternative (forcing cardholders to prove they didn’t make the charge) is operationally impossible. The merchant must prove (a) the charge was authorised by the actual cardholder, AND (b) the goods / service was delivered to the cardholder. Strong evidence (signature on delivery, IP address matching billing address geographic region, customer-email confirming receipt) increases win rate but doesn’t typically exceed 30%. The right view: fight to deter, not to win; documented dispute defence reduces serial fraudster attacks even when the individual case loses.
Stripe Radar already blocks fraud. Why am I getting fraud disputes?
Radar’s job is to maximise legitimate-charge throughput while minimising fraud; it tunes to your merchant’s risk tolerance. Even at the most conservative setting, Radar lets through some fraud, the alternative would be blocking too many legitimate charges. The dispute card surfaces the fraud Radar didn’t catch; review it monthly with Radar Score Distribution to identify whether Radar tuning needs to shift toward stricter (raise the block threshold from “high” to “elevated”) at the cost of higher false-positive rate.
What’s the average evidence-submission deadline?
~7 days for formal chargebacks (needs_response); ~10 days for early warnings (warning_needs_response). The exact deadline is in the dispute’s evidence_details.due_by field; the card surfaces days-remaining for triage. Never wait until day 6, evidence packs commonly need 30 to 60 minutes of work and any system issue (Stripe portal slowness, missing carrier data) can lose hours.
Can I auto-submit evidence?
Yes for the structured cases. Stripe’s Sigma platform and several third-party tools (Chargeflow, Disputifier, Sift) automate evidence assembly using shipping data, customer correspondence, and IP-address logs. ROI is positive on merchants with >$500 monthly disputed value; below that the manual cost is lower.