Update your integration for SCA

For one-time payments, you can complete the full integration today.

Stripe Checkout

Get prebuilt, conversion-optimized checkout flows with minimal code. Choose this option if you prefer a low-maintenance integration. For this payment flow, you can complete the full integration, and handling exemptions doesn’t require any additional work.

• See how to integrate Stripe Checkout to learn more.

Payment Intents API

Build dynamic payment flows and custom checkout pages by migrating to the Payment Intents API with one of our client libraries:

• Stripe.js & Elements
• Stripe iOS SDK
• Stripe Android SDK

For this payment flow, you can complete the full integration, and handling exemptions requires no additional work.

• See how to use the Payment Intents API to learn more.

SCA requires customers to complete 3D Secure for some payments. When this step is required by the bank, the customer must be online to complete authentication. ​​This introduces complexity for businesses that save cards and charge them later when the customer is no longer on the website or application and can’t complete authentication. This is also known as off-session payments. Examples of this include fixed-amount subscriptions, metered-billing subscriptions, crowdfunding campaigns, and car rentals.

Stripe products and APIs now allow merchants to meet SCA requirements for off-session payments:

1. Mandate collection. A mandate represents the agreement you have with the customer on how you plan to use their card in the future. In your checkout flow, add some consent text. State that by completing checkout, the customer consents to your initiation of payment on their behalf. State the anticipated frequency of payments. Explain how the amount of the payments will be determined.

2. Strong authentication of the first transaction. Merchants are required to authenticate the customer when the mandate is set up. This can either be done by the first payment with the card or when saving the card to a customer without making an initial payment.

3. Flagging subsequent transactions. Any payment made with a saved card when a user is off-session must be marked accordingly, with reference to the first authenticated transaction. Stripe handles this for you.

By updating your payments integration to use these new APIs and flows, Stripe can request exemptions such as fixed-amount subscriptions and merchant-initiated transactions to process later payments made with a saved card. However, banks can decide to reject a request for exemption. Build a way to notify customers that they need to return to your application and complete authentication if required.

Stripe Billing with the new version of Checkout

Checkout is a prebuilt checkout page that lets you collect payments and manage simple subscriptions with a single integration.

• See how to build subscriptions to learn more.

Stripe Billing

Take advantage of automated tools to protect your revenue and scale your business. Build your own custom checkout experience.

1. Update your client-side integration to save and reuse cards.
2. Then, implement SCA-changes for Stripe Billing.

Off-Session Payments with the Payment Intents API

Build your own off-session payments logic and handle getting users back on-session to complete re-authentication as needed. While this approach takes more work than using Stripe Billing, it provides more flexibility.

There are three parts to building an off-session payment flow:

1. Save a card to a customer. You can save a card to a customer in a checkout flow (as the customer is making a payment) with the Payment Intents API, or outside of the checkout flow with the Setup Intents API. You can also use Stripe Checkout to save cards to a customer in a checkout flow or outside of the checkout flow.
2. Use a saved card to make a payment. Once you have cards saved to a customer, you can make both on-session or off-session payments.
3. Build a recovery flow. While Stripe requests exemptions to reduce the need for customer reauthentication, there is always a risk that the cardholder’s bank will reject the exemption request. You should always build a recovery flow to bring a customer back on-session in case they need to authenticate again.

For payments with separate authorize and capture, you can complete the full integration today.

The new version of Stripe Checkout

Get prebuilt, conversion-optimized checkout flows with minimal code. Choose this option if you prefer a low-maintenance integration. For this payment flow, you can complete the full integration today, and no additional work will be needed to handle exemptions.Use Stripe Checkout with separate auth and capture

Use Stripe Checkout with separate auth and capture

Payment Intents API

Build dynamic payment flows and custom checkout pages by migrating to the Payment Intents API with one of our client libraries:

• Stripe.js & Elements
• Stripe iOS SDK
• Stripe Android SDK

For this payment flow, you can complete the full integration, and handling exemptions requires no additional work.

• See how to use the Payment Intents API to learn more.

SCA requires customers to complete 3D Secure for some payments. When this step is required by the bank, the customer must be online to complete authentication. ​​This introduces complexity for businesses that save cards and charge them later when the customer is no longer on the website or application and can’t complete authentication. This is also known as off-session payments. Examples of this include fixed-amount subscriptions, metered-billing subscriptions, crowdfunding campaigns, and car rentals.

Stripe products and APIs now allow merchants to meet SCA requirements for off-session payments:

1. Mandate collection. A mandate represents the agreement you have with the customer on how you plan to use their card in the future. In your checkout flow, add some consent text. State that by completing checkout, the customer consents to your initiation of payment on their behalf. State the anticipated frequency of payments. Explain how the amount of the payments will be determined.

2. Strong authentication of the first transaction. Merchants are required to authenticate the customer when the mandate is set up. This can either be done by the first payment with the card or when saving the card to a customer without making an initial payment.

3. Flagging subsequent transactions. Any payment made with a saved card when a user is off-session must be marked accordingly, with reference to the first authenticated transaction. Stripe handles this for you.

By updating your payments integration to use these new APIs and flows, Stripe can request exemptions such as fixed-amount subscriptions and merchant-initiated transactions to process later payments made with a saved card. However, banks can decide to reject a request for exemption. Build a way to notify customers that they need to return to your application and complete authentication if required.

Off-Session Payments with the Payment Intents API

Build your own off-session payments logic and handle getting users back on-session to complete re-authentication as needed. While this approach takes more work than using Stripe Billing, it provides more flexibility.

There are three parts to building an off-session payment flow:

1. Save a card to a customer. You can save a card to a customer in a checkout flow (as the customer is making a payment) with the Payment Intents API, or outside of the checkout flow with the Setup Intents API. You can also use Stripe Checkout to save cards to a customer in a checkout flow or outside of the checkout flow.
2. Use a saved card to make a payment. Once you have cards saved to a customer, you can make both on-session or off-session payments.
3. Build a recovery flow. While Stripe requests exemptions to reduce the need for customer reauthentication, there is always a risk that the cardholder’s bank will reject the exemption request. You should always build a recovery flow to bring a customer back on-session in case they need to authenticate again.

SCA requires customers to complete 3D Secure for some payments. When this step is required by the bank, the customer must be online to complete authentication. ​​This introduces complexity for businesses that save cards and charge them later when the customer is no longer on the website or application and can’t complete authentication. This is also known as off-session payments. Examples of this include fixed-amount subscriptions, metered-billing subscriptions, crowdfunding campaigns, and car rentals.

Stripe products and APIs now allow merchants to meet SCA requirements for off-session payments:

1. Mandate collection. A mandate represents the agreement you have with the customer on how you plan to use their card in the future. In your checkout flow, add some consent text. State that by completing checkout, the customer consents to your initiation of payment on their behalf. State the anticipated frequency of payments. Explain how the amount of the payments will be determined.

2. Strong authentication of the first transaction. Merchants are required to authenticate the customer when the mandate is set up. This can either be done by the first payment with the card or when saving the card to a customer without making an initial payment.

3. Flagging subsequent transactions. Any payment made with a saved card when a user is off-session must be marked accordingly, with reference to the first authenticated transaction. Stripe handles this for you.

By updating your payments integration to use these new APIs and flows, Stripe can request exemptions such as fixed-amount subscriptions and merchant-initiated transactions to process later payments made with a saved card. However, banks can decide to reject a request for exemption. Build a way to notify customers that they need to return to your application and complete authentication if required.

Off-Session Payments with the Payment Intents API

Build your own off-session payments logic and handle getting users back on-session to complete re-authentication as needed. While this approach takes more work than using Stripe Billing, it provides more flexibility.

There are three parts to building an off-session payment flow:

1. Save a card to a customer. You can save a card to a customer in a checkout flow (as the customer is making a payment) with the Payment Intents API, or outside of the checkout flow with the Setup Intents API. You can also use Stripe Checkout to save cards to a customer in a checkout flow or outside of the checkout flow.
2. Use a saved card to make a payment. Once you have cards saved to a customer, you can make both on-session or off-session payments.
3. Build a recovery flow. While Stripe requests exemptions to reduce the need for customer reauthentication, there is always a risk that the cardholder’s bank will reject the exemption request. You should always build a recovery flow to bring a customer back on-session in case they need to authenticate again.