Free tools / Stripe decline codes / authentication_required
Stripe authentication_required: off-session 3DS and SaaS renewal recovery
authentication_required means the bank wants the cardholder to confirm the payment, usually through 3-D Secure or another strong customer authentication step. The payment cannot succeed until the customer completes it.
- Decline code
- authentication_required
- Type
- Authentication required
- Who can fix it
- The customer — needs to act
- Will a retry help?
- No: do not retry
What it means
The bank requires 3-D Secure / Strong Customer Authentication for this charge. Common in Europe on the first charge or after a card change.
The bank wants the cardholder to confirm the payment (3-D Secure / SCA). Stripe cannot retry headlessly; the customer must complete it from the hosted invoice.
Why it happens
- The issuer requires strong customer authentication (SCA), common in Europe and some other regions.
- An off-session recurring charge for which the bank asks the cardholder to take part.
- A card that was not set up properly for off-session use when first saved.
- The bank's own risk rules triggering a verification step.
What to do
- Send the customer a link to the hosted invoice or payment page so they can authenticate.
- Do not simply retry off-session: the same request will ask for authentication again.
- Explain briefly that their bank needs a quick confirmation.
- Save cards with a SetupIntent so future off-session payments have a better chance of going through.
- Check that the confirmation completed and the payment succeeded.
Should you retry?
A silent retry rarely helps. The customer has to complete the authentication step, after which the payment can succeed.
What to tell the customer
Short and neutral, ready for a checkout error, a billing page or a support reply. No placeholders — ready to paste.
Your bank needs you to confirm this payment. Please complete the verification, usually in your banking app, to finish paying.
Customer email template
Neutral wording for this situation. Replace {name}, {product}, {link} and {company}.
Hi {name},
Your bank asked for a quick confirmation before approving the payment for {product}. It takes a few seconds: {link}
Thanks,
{company}Handling many failed payments? See how FlowMRR helps you prioritize failed Stripe payments by revenue at risk. Want a ranked list from your own account? Try the free failed payment audit.
Try FlowMRR freeFrequently asked questions
What is the difference between authentication_required and a normal decline?
The bank has not refused the payment outright: it needs the cardholder to prove it is them. Once they authenticate, the payment can be approved.
Why does it happen on a renewal when the card worked before?
Issuers can require authentication on any charge, including renewals of a card that worked before. Whether a given charge is exempt is the bank's decision.
Other Stripe decline codes
- generic_decline
- do_not_honor
- insufficient_funds
- card_declined
- expired_card
- card_velocity_exceeded
- lost_card
- stolen_card
- fraudulent
- pickup_card
- incorrect_cvc
- incorrect_number
- processing_error
- try_again_later
- transaction_not_allowed
- restricted_card
- withdrawal_count_limit_exceeded
- card_not_supported
- currency_not_supported
- invalid_account
- stop_payment_order
- Look up any decline code
- The complete list of decline codes