Handle a Stripe authentication_required decline on a saved card and implement a compliant retry flow prompting the cardholder for step-up authentication

Steps

1. When a PaymentIntent confirm attempt returns an error with code 'authentication_required', the issuer requires SCA for this transaction even though the card was previously used off-session
2. Do not retry the same PaymentIntent with off_session=true — instead, create a new PaymentIntent with on_session=true (or surface the existing PaymentIntent's client_secret to the customer) and use Stripe.js to present the 3DS challenge
3. Send the customer an email or push notification with a link to a secure payment page where they can complete the step-up authentication
4. On the payment page, use Stripe.js handleNextAction() or confirmCardPayment() with the PaymentIntent's client_secret to trigger the challenge flow
5. After the customer completes authentication, the PaymentIntent status transitions to 'succeeded' or 'requires_capture'; fulfill the order accordingly
6. Log the number of authentication_required declines and successful retries to measure the impact and tune your retry email timing and copy