- Breaking changes
- Public preview
Makes the radar session property optional in the Payment Evaluations API Breaking changes Public preview
What’s new
The radar_session property within the client_device_metadata response object of the Payment Evaluations API is now nullable. Previously, this property was required in the response object.
Why is this a breaking change?
This is a breaking change because the radar_session property can now return null values in API responses, but previously it always contained a value. If your code assumes this property is always present and attempts to access its properties without null checking, you might encounter runtime errors when processing payment evaluations where the radar session is null.
To avoid errors, update your integration to check if radar_session is null before accessing its properties or performing operations that depend on radar session data.
Impact
If your integration creates payment evaluations and relies on the radar_session property always being present, you must update your code to handle cases where this property might be null. Check for null values before accessing radar session data to prevent errors in your application.
If you pass in radar_session when creating the payment evaluation, it still populates.
Changes
| Field | Change | From → to |
|---|---|---|
| Radar. PaymentEvaluation. client_device_metadata_details. radar_session | Changed | string → nullable(string) |
Upgrade
- View your current API version in Workbench.
- If you use an SDK, upgrade to the corresponding SDK version for this API version.
- If you don’t use an SDK, update your API requests to include Stripe-Version: 2026-04-22. preview
- Upgrade the API version used for webhook endpoints .
- Test your integration against the new version.
- If you use Connect, test your Connect integration .
- In Workbench, perform the upgrade . You can roll back the version for 72 hours.
Learn more about Stripe API upgrades.