Driftwatch

Stripe / Stripe API /

Breakingdirection flip: their tools call this safe

Response field score is no longer guaranteed

What changed

Producer-side tools call this non-breaking. For a consumer it is a null dereference on an unknown future date.

Affects score on insights_resources_payment_evaluation_signal_v2 reachable from 1 operation. Nothing fails at the call; it fails wherever the value is finally used, which is usually somewhere else entirely.

no longer guaranteed present; can now be null

Who is affected

Code that reads Stripe's insights_resources_payment_evaluation_signal_v2 objects, used by 1 Stripe operation.

Before and after

WhereBeforeAfter
insights_resources_payment_evaluation_signal_v2.scorealways presentmay be missingno longer guaranteed present
insights_resources_payment_evaluation_signal_v2.scorenumbernull|numbercan now be null

Code that breaks

// response.score may now be absent or null
const score = response.score ?? fallback;

Based on Stripe’s published API specification. How severity is decided.