Makes Payment Evaluation signal scores nullable
Makes the score property nullable for all signals in Payment Evaluations. Radar Standard users receive null for score. Other eligible Radar plans continue to return rounded numeric scores. Integrations that expect score to always contain a number can fail when it returns null. Previously, an unavailable score returned -1. After upgrading, it returns null instead.
docs.stripe.comquote checked- parameter change
- Your codeby hand
Nemotron fixes
In its own wordsmatches the page ✓
| [Makes Payment Evaluation signal scores nullable](https://docs.stripe.com/changelog/endive/2026-09-30/payment-evaluations-nullable-score.md) | Radar | Breaking | api |
Also readmatches the page ✓
Integrations that expect `score` to always contain a number can fail when it returns `null`. Previously, an unavailable score returned `-1`. After upgrading, it returns `null` instead.
- Before upgrading, update your integration to handle null signal scores and replace checks for -1 with checks for null. When a score isn’t available, use the corresponding signal’s risk_level property, such as fraudulent_payment.risk_level. Risk levels remain available to Radar Standard users.
What Teire looks for in your code
nothing to search for: checked by hand
Does it reach your code?