SCA Migration Guide for Plugins and Developer Libraries

    Learn how to update your Stripe plugin or developer library to support Strong Customer Authentication (SCA).

    Do I need to support SCA for my users?

    Businesses in the European Economic Area (EEA) accepting online payments from customers in the EEA require a different user experience, namely 3D Secure. Transactions that don’t follow the new authentication guidelines may be declined by a customer’s bank, as of September 14th, 2019. This additional layer of authentication requires migrating to SCA-ready solutions like the new version of Checkout or the Payment Intents API, described in Step 2.

    Step 1: Identify your plugin on our platform

    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 and libraries. You can learn more about our suggested best practices in our documentation.

    Step 2: Determine your integration path

    Refer to our SCA migration guide to review the integration paths for the new version of Checkout, the Payment Intents API, Stripe Billing, and iOS or Android. For developers of plugins or libraries:

    • Choose Checkout when possible. Stripe’s new version of Checkout is a fully hosted payment page that can be branded by businesses, supports recurring subscriptions, and is the easiest way to provide SCA support to your users.
    • If you need control over your checkout experience, use the Payment Intents API. It works with Elements, our customizable UI components for payment flows, and other Stripe APIs like PaymentMethods, Customers, and Connect. The Payment Intents API automatically displays authentication flows like 3D Secure 2 and ensure your integration is SCA-ready. You can also choose between an asynchronous API that requires the use of webhooks, and a synchronous API that is simpler for card-only integrations.
    • Programmatically subscribe your user to webhooks. You can register a webhook endpoint for your account or connected accounts and manage them via the Webhooks API, simplifying setup for your users.

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

    Step 3: Test dynamic authentication

    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.

    Step 4: Notify your users and Stripe

    We recommend releasing an update for your users to let them know your payments solution is SCA-ready. You can share our 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.

    Next steps

    Was this page helpful?

    Thank you for helping improve Stripe's documentation. If you need help or have any questions, please consider contacting support.

    Questions?

    We're always happy to help with code or other questions you might have. Search our documentation, contact support, or connect with our sales team. You can also chat live with other developers in #stripe on freenode.

    On this page