Breaking changes

Sources now provide a recommended value when the issuer advises using 3D Secure Breaking changes

What’s new

Adds recommended as a possible value for a Source object’s card[three_d_secure] property. Previously, the only valid values were not supported, optional, and required.

Impact

Adding a recommended value to the card[three_d_secure] property of the Source object provides more nuanced information about 3D Secure availability. You can now identify cases where 3D Secure is suggested but not mandatory, allowing for more informed decision-making in payment processing.

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: 2018-02-06

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.