3DS SDK error codes
Last updated: December 5, 2025
If the 3D Secure (3DS) SDK for Android or iOS encounters an issue, it returns an error code. You can use the error codes to troubleshoot issues, and implement robust error handling in your application.
Error codes are grouped based on the stage of the authentication process in which they occurred:
1XXXcodes - Authentication process errors2XXXcodes - Connectivity errors3XXXcodes - 3DS2 protocol errors4XXXcodes - Internal errors5XXXcodes - 3DS1 protocol errors
Authentication process errors occur when authentication could not be completed due to user action or the app's configuration.
| Error code | Description |
|---|---|
| The session ID provided is invalid. Typically, this corresponds to a |
| The authentication credentials used to request a resource from the Sessions API are invalid. For example, due to an invalid session secret. |
| The user explicitly canceled the authentication process. |
| The authentication process timed out while waiting for the user to complete the challenge. |
| The authentication process completed but was unsuccessful. The Sessions API returned a value other than |
| The 3DS protocol version is not supported by the 3DS server. |
| The session ID used for the authentication request was already used by another authentication request currently in progress. |
| An authentication request was already requested with another session ID and is currently in progress. |
| The 3DS SDK's configuration file, For security reasons, the SDK does not operate with a modified configuration. |
| The Checkout.com domains have been overridden in the application's |
| SDK initialization was requested while another initialization request is already in progress. |
| The SDK was not initialized. |
Connectivity errors occur when there are issues communicating between the SDK and the remote server.
Retrying the authentication may resolve the error.
| Error code | Description |
|---|---|
| An internet connection could not be established. |
| The connection failed. |
| The network connection timed out. |
| A client or server connection was interrupted while loading. |
| The connection attempt requires activating a data context while roaming, but international roaming is disabled. |
| The URL Loading System encountered an error that it cannot interpret, or the error code received from |
| A critical certificate transparency check failed and a secure connection could not be established. |
3DS2 protocol errors occur when a component of the 3DS2 process reports an issue. For example, due to invalid or corrupt data received from the issuer's access control server (ACS), or the 3DS Server.
| Error code | Description |
|---|---|
| The issuer's response could not be validated. For example, due to a counter mismatch. |
| The challenge limit of 255 was exceeded. |
| The card issuer reported an error. |
| The issuer's response could not be validated. |
| The issuer's response could not be validated. |
| The SDK identified a decryption failure in the 3DS process. |
| The issuer's response could not be validated. |
| The 3DS transaction timed out. |
| The issuer reported that authentication could not be performed due to a technical issue, or other problem. |
| The 3DS Server reported an issue. For example, due to receiving an HTTP response other than a |
| The issuer's response could not be validated. |
| The SDK identified an error in the 3DS process. |
| The issuer's response could not be validated. |
| The SDK identified an error in the 3DS process. |
| The issuer's response could not be validated. For example, due to the response body being empty or |
| The SDK identified an error in the 3DS process. |
| The issuer's response could not be validated. |
| The SDK identified an error in the challenge data provided by the card issuer. |
| Authentication completed with a non-recoverable error. For example, the issuer rejected the verification and requested that authorization not be attempted. |
| The SDK identified an error in the 3DS process. |
Internal errors occur when there is an issue with the 3DS SDK.
If you encounter persistent errors, request support.
| Error code | Description |
|---|---|
| The SDK encountered an internal error. |
| The standalone 3DS service was not initialized. |
3DS1 protocol errors occur when a component of the 3DS1 process reports an issue.
| Error code | Description |
|---|---|
| The issuer's ACS response could not be validated, resulting in a response processing error. |
| The issuer reported a server-side error during the 3DS1 authentication process. |
| The SDK identified an error in the 3DS process. |
| The SDK identified an error in the 3DS process. |