Skip to content
Create account
or
Sign in
The Stripe Docs logo
/
Ask AI
Create account
Sign in
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
Developer tools
Get started
Payments
Finance automation
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
Overview
About Stripe payments
    Overview
    Currencies
    Declines
    Payouts
    Recurring payments
    3D Secure authentication
    Refund and cancel payments
    Balances and settlement time
    Receipts
    Handle webhook events
    SCA readiness
      Plugins
      Previous authorisation agreements
      SCA enforcement
Upgrade your integration
Payments analytics
Online payments
OverviewFind your use caseManaged Payments
Use Payment Links
Build a checkout page
Build an advanced integration
Build an in-app integration
Payment Methods
Add payment methods
Manage payment methods
Faster checkout with Link
Payment interfaces
Payment Links
Checkout
Web Elements
In-app Elements
Payment scenarios
Custom payment flows
Flexible acquiring
Orchestration
In-person payments
Terminal
Other Stripe products
Financial Connections
Crypto
Climate
HomePaymentsAbout Stripe paymentsSCA readiness

Previous authorisation agreements

Learn which payments previous authorisation agreements can be used for (sometimes referred to as grandfathering).

Copy page

Warning

If you’re affected by SCA, update your Stripe integration now, even if some of your payments can use previous authorisation agreements.

Eligibility

Strong Customer Authentication requires an additional step of customer authentication, but sometimes you collect payments when your customer isn’t actively using your application. Even if they authenticated in the past, SCA may require your customer to come back online and re-authenticate. To reduce friction in these off-session payments, Stripe APIs enable upfront authentication – so you can authenticate your customer on-session once and reuse the card off-session repeatedly. As of 14 September 2019, you need to use these APIs to reduce the chance of failed payments when reusing cards or creating subscriptions and invoices.

However, you can use previous authorisation agreements for off-session payments that meet the following criteria:

  • Cards from EU customers saved before December 31, 2020
  • Cards from UK customers saved before September 14, 2021

This means you don’t have to use Stripe’s new APIs to set up saved cards again, and your off-session payments can proceed normally—without re-authentication from customers.

How it works

You can use previous authorisation agreements for all off-session payments that meet both of these conditions, regardless of payment amount and frequency:

  • You saved the card details before the eligibility cutoff
  • You explicitly tell Stripe the transaction is off-session

Stripe automatically looks for a transaction made with the card prior to the eligibility cutoff. If found, Stripe uses the previous authorisation agreement for the current transaction. If the bank accepts the previous authorisation agreement, the transaction is categorised as out of scope for SCA and can proceed without additional authentication.

If the bank declines the previous authorisation agreement, it’s like any other PaymentIntent failing the confirmation step. The PaymentIntent’s status changes to requires_payment_method, and you have to notify your customer to complete the payment.

Saving cards after the eligibility period

Now that SCA has taken effect, save and reuse cards with the Payment Intents and Setup Intents APIs to qualify for off-session exemptions. You can also save cards using Stripe Checkout.

Preparing your saved cards for SCA

For Stripe to re-use authorisation agreements, you need to use PaymentIntents and tell Stripe the payment is off-session.

How you saved the card before the eligibility cutoffWhat to do after the eligibility period
By passing a token, source, or payment method to the CustomerCreate a PaymentIntent with off-session flag
By creating a SetupIntent or using setup_future_usage in a PaymentIntentCreate a PaymentIntent with off-session flag

For subscriptions and invoices managed with Stripe Billing, refer to the Billing SCA guide.

See also

  • Payment Intents Overview
  • Payment Intents Migration Guide
Was this page helpful?
YesNo
Need help? Contact Support.
Join our early access programme.
Check out our changelog.
Questions? Contact Sales.
LLM? Read llms.txt.
Powered by Markdoc