Driftwatch

Stripe / Stripe API /

Breakingdirection flip: their tools call this safe

risk_level can now return "low", "not_assessed", "unknown"

What changed

Producer-side tools call this additive. It breaks exhaustive switches, strict parsers and generated client enums.

Affects risk_level on insights_resources_payment_evaluation_signal_v2 reachable from 1 operation.

New values: low, not_assessed, unknown.

can now return "low", "not_assessed", "unknown"

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.risk_level"elevated", "highest", "normal""elevated", "highest", "low", "normal", "not_assessed", "unknown"

Code that breaks

switch (response.risk_level) {
  // existing branches …
  // no branch for "low"
  // no branch for "not_assessed"
  // no branch for "unknown"
  default:
    throw new Error("unexpected risk_level");
}

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