3D Secure authentication required: how to recover the payment
Quick answer
`authentication_required` means the issuer will approve the payment only after the cardholder completes a 3D Secure challenge, which an off-session subscription charge cannot do on its own.
Worth retrying? No — the credential or customer action must change first.
Why this decline happens
- European SCA rules require strong customer authentication for many transactions.
- The stored mandate or off-session exemption was not accepted by the issuer for this charge.
- The issuer's risk model escalated an otherwise routine renewal to a challenge.
Retry strategy that fits this code
- A silent retry cannot satisfy an authentication challenge; it will return the same code.
- The recovery path is an on-session payment link where the customer can complete the challenge in a browser.
- Once authenticated, save the resulting credential so future renewals can use the authenticated mandate.
- Check that your off-session exemptions and mandate setup are configured correctly — a high rate here is usually an integration issue, not a customer issue.
What to tell the customer
- Explain that the bank needs the customer to confirm the payment, and that it takes under a minute.
- Send a direct authenticated payment link rather than asking them to log in and hunt for billing settings.
- Set expectations that the confirmation is a bank security step, not a problem with their account.
Frequently asked
- Why do renewals need 3D Secure if the first payment did not?
- Exemptions are granted per transaction by the issuer. A renewal can lose an exemption when the issuer's risk assessment or the applicable regulation changes.
- Does completing 3D Secure once fix future renewals?
- Usually. An authenticated mandate gives later off-session charges a stronger basis for approval, though issuers may still challenge occasionally.
Handling this at scale, not one invoice at a time
A single decline code is easy to handle manually. A steady stream of them across different customers, invoice values, and failure reasons is a workflow problem. RRLabs classifies each failure, scores the recovery opportunity, and recommends the next best action — then attributes recovered revenue only once your billing provider confirms the payment succeeded.