SCA migration guide for plugins and developer libraries

Plugins and third-party libraries should include identifying information so we can contact you about future changes or critical updates to the API. Use the setAppInfo function to provide those details in your Stripe integration.

We encourage you to join the Stripe Partner Program, which includes free registration and more resources for developers building plugins. Learn more about suggested best practices.

For developers of plugins or libraries:

• Choose Stripe Checkout when possible. Checkout is a low-code integration that lets you collect payments using a customizable form. You can embed the payment form on your website or host it on Stripe. To learn more about this payment integration option, see Stripe Checkout.
• For more control over your checkout flow, use the Payment Intents and Setup Intents APIs. These APIs work with Elements, Stripe’s customizable UI components for payment flows, and other Stripe APIs like PaymentMethods, Customers, and Connect. The Payment Intents and Setup Intents APIs display authentication flows like 3D Secure 2, save cards to use later, and support SCA.
• For recurring payments, use Stripe Billing. Billing is a tool for managing subscriptions and invoicing. To learn how to update your Billing implementation to support SCA requirements, see SCA migration guide for Billing.
• Programmatically subscribe your user to webhooks: You can register a webhook endpoint for your account or connected accounts and manage them with the Webhooks API, simplifying setup for your users.

If none of these options work for your integration, let us know.

After you have finished implementing the new integration path, configure your Dynamic 3D Secure Radar rules to test your integration using 3D Secure test cards. Make sure to test both successful and unsuccessful authentication cases.

We recommend releasing an update for your users to let them know your payments solution is SCA-ready. You can share the guide to Strong Customer Authentication with your users to help them understand these regulatory changes. When you’ve released an SCA-ready update, please let us know as well.