Breaking changes

Adds expired status for Issuing Authorizations Breaking changes

What’s new

Issuing authorizations 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 authorization objects. Some authorizations with a reversed status now have an expired status to indicate that Stripe expired the authorization.

Impact

The status of an authorization 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 authorization. Authorizations that have been reversed can’t be captured and the funds associated with the authorization can be released. Authorizations 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 authorizations expired by Stripe to allow users to distinguish what state the authorization is in.

Changes

Upgrade

1. View your current API version in Workbench.
2. 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

3. Upgrade the API version used for webhook endpoints .
4. Test your integration against the new version.
5. If you use Connect, test your Connect integration .
6. In Workbench, perform the upgrade . You can roll back the version for 72 hours.

Learn more about Stripe API upgrades.

Related changes

• Adds reason code for Issuing authorizations created while Stripe is unavailable
• HTTP Accept headers for webhooks now specify JSON during Issuing authorizations