Breaking changes
Adds additional enum values for Radar manual reviews Breaking changes
What’s new
Adds the following values to the closed_reason enum:
- acknowledged : The review was acknowledged and then closed.
- payment _ never _ settled : The review was closed because the payment never settled.
Why is this a breaking change?
If your integration handles the closed_reason enum to expect only the previous set of values, this change might break it.
Impact
We added these enum values to support manual reviews for Radar on bank debits because the previous set of enum values didn’t account for all states that might occur in asynchronous bank debit flows. You can use the new values for states where:
- The review was acknowledged and then closed ( acknowledged ).
- The review was closed because the payment never settled ( payment _ never _ settled ).
Update your integration to make sure any code that handles the closed_reason response expects these new values.
Changes
| Values | Change | Enum |
|---|---|---|
| acknowledged payment_never_settled | Added | Review. closed_reason |
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: 2025-09-30. clover
- Upgrade the API version used for webhook endpoints .
- Test your integration against the new version.
- If you use Connect, test your Connect integration .
Learn more about Stripe API upgrades.