Breaking changes
Updates to 3D Secure details in Charge object Breaking changes
What’s new
Updates the payment_method_details.card.three_d_secure fields on the Charge object, and removes the succeeded and authenticated booleans. Use the result enum instead.
Impact
Lets you more accurately determine the 3D Secure status of a payment by using the new result enum in the payment_method_details.card.three_d_secure fields of the Charge object. The previous succeeded and authenticated booleans have been removed, providing a more granular and comprehensive way to understand the 3D Secure authentication process for a given payment.
Changes
| Parameters | Change | Resources or endpoints |
|---|---|---|
| authenticated succeeded | Removed | Charge. payment_method_details. card. three_d_secure SetupAttempt. payment_method_details. card. three_d_secure |
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: 2020-08-27
- Upgrade the API version used for webhook endpoints .
- Test your integration against the new version.
- If you use Connect, test your Connect integration .
- In Workbench, perform the upgrade . You can roll back the version for 72 hours.
Learn more about Stripe API upgrades.