Restructured Payment Evaluation Object

Stripe Radar has significantly enhanced its fraud detection capabilities by restructuring the Payment Evaluation object. The change moves risk assessment information from the insights hash to a new extensible signals hash, while promoting the recommended_action property to the top level of the object. This modernization provides more detailed and actionable fraud prevention data.

New Risk Signals

The signals hash now contains three distinct risk evaluations:

• fraudulent_payment: Likelihood that a payment results in a dispute with fraudulent reason code or an early fraud warning (available by default)
• fraudulent_dispute: Likelihood of a fraudulent dispute claim (public preview)
• early_fraud_warning: Likelihood of an early fraud warning (public preview)

Each signal includes three properties: evaluated_at (timestamp), risk_level (normal, elevated, or highest), and score (now a float with 2 decimal precision, up from integer values).

Required Migration Steps

Breaking Change: The insights hash has been completely removed. Integrations must update immediately:

• Replace insights.fraudulent_dispute.risk_score references with signals.fraudulent_payment.score
• Replace insights.fraudulent_dispute.recommended_action with recommended_action at the top level
• Test thoroughly against the new API version (2026-03-25.dahlia) before upgrading production environments

Developers have a 72-hour rollback window if issues arise during the upgrade process.