Skip to main content
When a payment requires 3D Secure (3DS) authentication and the process fails, the payment is declined with one of the following codes in the decline_code field.

​
three_d_secure_failed

The customer failed 3D Secure authentication. This may happen if the customer entered an incorrect SMS code or rejected the authentication request in their banking app. What to do: Ask the customer to retry the payment. If the issue persists, suggest they contact their card issuer.

​
three_d_secure_timeout

The customer did not complete 3D Secure authentication within the allowed time window. What to do: Create a new payment and ask the customer to complete authentication promptly.

​
three_d_secure_not_supported

The card does not support 3D Secure authentication. This is uncommon for cards issued in the EEA (where 3DS is mandated by PSD2/SCA), but may occur with some non-European cards. What to do: The customer may need to use a different card that supports 3DS.

​
three_d_secure_error

An error occurred during the 3D Secure verification process. This is typically a temporary issue with the card issuer’s 3DS infrastructure. What to do: Retry the payment. If the issue persists, the customer should contact their card issuer.