Skip to content
Create account or Sign in
The Stripe Docs logo
/
Create accountSign in

Adds support for 3D Secure versions 2.3.0 and 2.3.1

What’s new

You can now import 3D Secure authentication results that use versions 2.3.0 and 2.3.1 of the 3D Secure protocol. The version parameter in payment_method_options.card.three_d_secure now accepts "2.3.0" and "2.3.1" as valid values, in addition to the previously supported versions "1.0.2", "2.1.0", and "2.2.0".

This enhancement applies to Payment Intents and Setup Intents when you use the 3D Secure Import feature to import authentication results from external 3D Secure providers.

Impact

If you’re using 3D Secure Import and your 3D Secure provider returns authentication results using version 2.3.0 or 2.3.1, you can now successfully import these results into Stripe. Previously, attempting to import results from these newer protocol versions would fail validation. This change ensures compatibility with 3D Secure providers that have adopted the latest EMVCo specifications published in 2021 (v2.3.0) and 2023 (v2.3.1).

Changes

ValuesChangeEnums
2.3.02.3.1Added
PaymentIntent#confirm.payment_method_options.card.three_d_secureSetupAttempt.payment_method_details.card.three_d_secureSetupIntent#create.payment_method_options.card.three_d_secureSetupIntent#update.payment_method_options.card.three_d_secureSetupIntent#confirm.payment_method_options.card.three_d_secure

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: 2026-01-28.clover
  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