apiwatch

All changes / Stripe

Breaking rest

Radar Standard users must now call Payment Evaluations with Stripe API version 2026-09-30.endive or later, and on that version an unavailable signal score is null instead of -1

Took effect · Stripe Radar Payment Evaluations API — signal score nullable on 2026-09-30.endive; Radar Standard requires 2026-09-30.endive or later

Reviewed against the vendor source on Oct 2, 2026 (AI-assisted review). Key facts are re-checked against the source daily.

What changes

On API versions before 2026-09-30.endive, Radar Standard users' Payment Evaluation requests now fail with HTTP 403 and error code payment_evaluation_on_api_version_not_supported; previously they succeeded. After upgrading, Radar Standard users receive null for every signal's score (other eligible Radar plans still get rounded numeric scores), and an unavailable score is null rather than -1, while risk_level stays available.

Breaking: Calls fail after this date.

What to do

If you're on Radar Standard, call Payment Evaluations with API version 2026-09-30.endive or later. Before upgrading, handle null signal scores (replace checks for -1 with checks for null) and fall back to each signal's risk_level, such as fraudulent_payment.risk_level.

Strings to search for

payment_evaluationspaymentEvaluationsPaymentEvaluationPaymentEvaluationServiceV1RadarPaymentEvaluationsradar/paymentevaluation

Counts only in files that mention stripe + radar.

Source

https://docs.stripe.com/changelog/endive/2026-09-30/payment-evaluations-nullable-score.md