Breaking changes
Adds expired status for Issuing Authorisations Breaking changes
What’s new
Issuing authorisations expired by Stripe now transition to the expired status instead of the reversed status.
Why is this a breaking change?
This change introduces a new enum value, expired, on the status field of Issuing authorisation objects. Some authorisations with a reversed status now have an expired status to indicate that Stripe expired the authorisation.
Impact
The status of an authorisation that is either reversed by the acquiring business or expired by Stripe used to have the status field set to reversed. Users need to be able to distinguish between the two states to determine when they can release the funds held by the authorisation. Authorisations that have been reversed can’t be captured and the funds associated with the authorisation can be released. Authorisations that have been expired by Stripe can be captured later.
Users were unable to distinguish whether they can release funds by relying on this status field alone. This change adds an expired status for authorisations expired by Stripe to allow users to distinguish what state the authorisation is in.
Changes
| Value | Change | Enums |
|---|---|---|
| expired | Added | Issuing. Authorization#list. status Issuing. Authorization. status |
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-03-31. basil
- 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.