The following are common reasons why payments that go through 3D Secure authentication might fail.<\/p>\n
When 3D Secure authentication fails, you will likely receive a feedback from your cardholder that they are unable to use their card. You do not receive a relayed authorisation or a webhook, and you do not see the payment in the Payments<\/strong> list in your Customer Area<\/a>. This is because the payment is already blocked after the authentication, and the authorisation is not sent to Adyen.<\/p>\n To resolve this issue, make sure that the card is enrolled in 3D Secure with one of the methods listed above before retrying the payment. If the issue persists, contact our Support Team<\/a>.<\/p>\n When 3D Secure authentication fails multiple times, you will likely receive a feedback from your cardholder that they are unable to use their card. As required by PSD2 regulations, Adyen temporarily blocks a card from performing 3D Secure authentication after five consecutive failed authentication attempts<\/em>.<\/p>\n To resolve this issue:<\/p>\n Following PSD2 requirements, by default, Adyen declines a payment if a merchant skips 3D Secure authentication for a payment that requires SCA.<\/p>\n Alternatively, you can choose to enable soft declines for the cards that you issue. When enabled, Adyen sends a soft decline and informs the merchant to retry the payment with a 3D Secure flow. It is up to the merchant to retry the payment. To enable soft declines, reach out to your Adyen contact.<\/p>\n When a payment is soft declined, Adyen sends a balancePlatform.payment.created<\/a> webhook for the failed authorisation. In the validationResult<\/a> array, you will find the You can also see the payment attempt in the Transfers<\/strong> list in your Customer Area<\/a>.<\/p>\nThe card has been blocked<\/h2>\n
\n
The payment requires SCA but the processing merchant skipped 3D Secure<\/h2>\n
type<\/code> PSD2SoftDeclineCheck<\/strong><\/span> with an invalid<\/strong><\/span> result<\/code>.<\/p>\nSee also<\/h2>\n