stripe dispute lost with radar risk_level normal: how to fix

TL;DR

Radar's risk_level predicts fraud at payment time; it does not decide chargeback outcomes. A lost dispute with a normal risk level is an evidence problem, not a Radar failure. Read the dispute reason code, rebuild the evidence around what that reason code requires, and get it in before the deadline.

stripe dispute lost with radar risk_level normal: how to fix

Use this when

• risk_level was normal or low and the dispute still went against you.
• You assumed a clean Radar score would protect the dispute.
• You are writing the post-mortem and need the real cause.

Not for this skill when

• Radar blocked a legitimate payment. That is a false-positive decline issue.
• Evidence was rejected as a duplicate or the dispute is closed.

Steps

1. Read the dispute's reason code and the network's reason text. Verify: you can state the reason in one sentence.
2. Pull the evidence pack you submitted and list what it contained. Verify: each item in the pack is named.
3. Compare your pack against what that reason code actually requires (proof of delivery for not-received, usage logs for subscription disputes, and so on). Verify: you can point at the missing piece.
4. Rebuild the pack around the reason code's requirements and submit before evidencedueby. Verify: the evidence object shows the new submission.
5. After the outcome, add a reason-code checklist to your dispute process so the next pack starts complete. Verify: a new dispute of the same reason triggers the checklist.

Variant phrasings

stripe radar normal but dispute lost

Common search order.

risk_level normal chargeback lost

Field-first wording.

radar low risk lost dispute why

Question-form search.

Compatibility: Stripe Radar and Stripe Disputes. risk_level is a fraud signal at authorization time; dispute outcomes are decided by the card network on evidence.

Why it happens

Two different systems answer two different questions. Radar asks whether the payment looks fraudulent. The dispute process asks whether the cardholder's claim holds up against your evidence. A legitimate-looking payment can still lose when the evidence does not address the specific claim.

Edge cases / pitfalls

• Do not tune Radar rules to fix dispute losses. You will trade chargebacks for declined good orders.
• Reason codes differ by network. Visa and Mastercard want different proof for similar-sounding claims.
• A normal risk_level is still worth attaching to the pack. It is weak evidence, but it is evidence.
• Track win rate by reason code. One bad reason code is a process fix; all of them is an evidence-quality problem.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstIJshwmiUv4vqIJMAQydrg