Adds expired status for Issuing Authorizations
Issuing authorizations expired by Stripe now transition to the expired status instead of the reversed status. 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.
docs.stripe.comquote checked- behaviour change
- Your codeby hand
Nemotron fixes
In its own wordsmatches the page ✓
| [Adds expired status for Issuing Authorizations](https://docs.stripe.com/changelog/basil/2025-03-31/issuing-authorizations-expired.md) | Issuing | Breaking | api |
Also readmatches the page ✓
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.
- 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.
What Teire looks for in your code
nothing to search for: checked by hand
Does it reach your code?