The Adyen payments platform performs regular checks to make sure that the mobile device that is used in a Mobile solution is secure.
If an issue is found during the security attestation process in an integration with the Android SDK, an error is shown on the mobile device. In many cases end users can resolve the issue themselves. The user needs to resolve the issue before trying to use the device again.
If an issue is found when using the Android Payments app, the error is shown on the mobile device or in the App link. The error usually needs to be fixed in the code.
Error messages for the Android SDK
The following tables show the most common errors and how to handle them. You need to resolve the issue before trying to use the device again. Refer to the column Internet needed to resolve to learn if your integration needs internet connectivity to resolve the error.
| Error code | Description | Internet needed to resolve | Required action |
|---|---|---|---|
| ANDROID_NOT_UPDATED | Transaction canceled. |  |
Update the SDK to the latest software version and try again. |
| DEBUG_ENABLED_APK | Transaction canceled. |  |
On the device, go to Settings > System > Developer Options and turn off Developer Options. |
| DEVELOPER_OPTIONS_ON | Transaction canceled. | |
On the device, got to Settings > System > Developer Options and turn off Developer Options. In your Test integration this error only occurs for PIN transactions. |
| INVALID_NYC1_FIRMWARE_VERSION | Card reader firmware version is invalid. | |
Update the card reader to the latest software version and try again. |
| LOCAL_TIME_TAMPERING | Transaction canceled. Unable to check the security requirements. | |
On the device, go to Settings > System > Date and Time and turn on Automatic date and time. |
| NON_SELF_RESOLVABLE | Transaction canceled. Unable to check the security requirements. | |
Contact our Support Team to resolve the issue. |
| NO_TOKEN | Cannot transact. | |
Connect the device to a network so that the SDK can check the security requirements. |
| SECURITY_PATCH_LEVEL_OUTDATED | Transaction canceled. | |
Update the SDK to the latest software version and try again. |
| SYSTEM_CHANGE | Transaction canceled. Cannot transact due to system change. | |
Connect the device to a network so that the SDK can check the security requirements. If the date/time of the device was changed, you must change it back to continue transacting. If the device was restarted, connect the device to a network so that the SDK can check the security requirements. |
| TOKEN_EXPIRED_S&F | Offline transaction window has expired. | |
Connect the device to a network so that the SDK can check the security requirements. |
| USB_DEBUGGING_ON | Transaction canceled. | |
On the device, go to Settings > System > Developer Options and turn off Developer Options. |
| WIFI_DEBUGGING_ON | Transaction canceled. | |
On the device, go to Settings > System > Developer Options and turn off Developer Options. |
Error messages for the Android Payments app
The following table shows errors, their potential causes, and how to handle them if you are using the Android Payments app for your Mobile solution. These issues are shown either in the UI or within the App Link.
Error code |
Error name |
Error shown |
Description |
|---|---|---|---|
| 01_001 02_001 03_001 |
No return URL No return URL found No return URL found |
UI | The return URL field is empty or missing. Check and fix the return URL. This error can occur during the onboarding check (01_001), during the boarding (02_001), or before the payment (03_001). |
| 01_002 02_002 03_002 |
Return URL encoding error Invalid return URL Invalid return URL |
UI | The return URL that was used is either encoded incorrectly or not encoded at all. Check and fix the return URL. This error can occur during the onboarding check (01_002), during the boarding (02_002), or before the payment (03_002). |
| 01_003 | Native library error | App Link | Possibly the boarding request token is incorrect. Restart the onboarding process. |
| 01_004 02_018 |
Installation ID error Installation ID error |
App Link | Possibly the SDK requirements are not matched. Make sure to check the SDK requirements. This error can occur during the onboarding check (01_004) or during the boarding (02_018). |
| 01_105 02_020 03_019 05_005 05_006 |
Invalid return URL Error Invalid return URL Error Error |
UI | The return URL is incorrect. Check and fix the return URL. This error can occur during the onboarding check (01_005), during the boarding (02_020), before the payment (03_019), or after the payment (05_005 and 05_006). |
| 02_003 | Backend error | App Link | This error occurs from the backend. Make sure you have the right Payments app role or that your encryption passphrase is set correctly. |
| 02_004 | Boarding token error | App Link | Possibly the boarding request token is incorrect when sending the boarding token in your App Link. Check and fix the boarding request token. |
| 02_005 | Boarding token error | App Link | The boarding token that was used is either encoded incorrectly or not encoded at all. Make sure that the boarding token is encoded correctly. |
| 02_006 | Boarding token error | App Link | This error occurs when our system receives a boarding token but is unable to properly deserialize it. |
| 02_007 | Boarding token error | App Link | Possibly, during the onboarding process, the signature validation of the boarding token failed. Restart the onboarding process. |
| 02_008 | Boarding token error | App Link | Possibly the boarding token is expired. Restart the onboarding process. |
| 02_009 03_009 |
General error General error |
App Link | This error can occur when our system encounters a network communication problem either during boarding (02_009) or before the payment (03_009). Check your network connection. |
| 02_010 | Installation ID mismatch | App Link | The boarding request token being used was issued for a different device than the device that is currently trying to use the token. Request a new boarding request token specifically for the current device. |
| 02_011 02_012 02_013 02_014 02_016 |
Invalid signature Invalid signature Local error Error Error |
App Link | These errors can occur during the boarding flow. Restart the onboarding process. |
| 02_015 | Error | App Link | This error occurs during the getInstallationToken API call. Restart the onboarding process. |
| 02_017 | App is already boarded | App Link | This error occurs if you send another boarding request when the app is already boarded. |
| 02_019 | Installation Token error | App Link | The host URL cannot be extracted from the installation token to construct the correct URL for the request. |
| 03_003 | Decoding error | App Link | The Terminal API request is either encoded incorrectly or not encoded at all. |
| 03_004 | Empty request object | App Link | The request object cannot be empty. Make sure that your Terminal API request includes all required parameters and send it again. |
| 03_005 | Onboarding data not found | App Link | This error can occur if you try to make a payment without onboarding. Restart the onboarding process first, then make the payment again. |
| 03_006 | API error | App Link | This error can occur when you make a call to the Payments app API. Check the path and request parameters and the destination URL. |
| 03_007 03_008 |
Configuration not found Configuration not found |
App Link | These errors can occur before the payment if there is no configuration object found. |
| 03_010 | Installation token not found | App Link | Your request to the Payments app API is missing the installation token. |
| 03_012 | Error | App Link | This error can occur when our system cannot verify your request. Restart the onboarding process. |
| 03_013 | Nexo request error | App Link | A security component of your Terminal API request could not be verified. Make sure that your encryption is correct and your Terminal API request includes all required parameters. |
| 03_014 03_015 |
Decryption error Decryption failed |
App Link | These errors can occur when our system receives an encrypted Terminal API request from your end, but is unable to decrypt it. Make sure that your encryption is correct and try again. |
| 03_016 | Load key error | App Link | This error can occur before the payment when our system is unable to retrieve or generate the necessary encryption key. |
| 03_017 | Malformed transaction request | App Link | Possibly a required parameter is missing from your Terminal API request. Make sure that your Terminal API request is correct and includes all required parameters. |
| 03_018 | NFC error | App Link | The NFC reader is disabled, or not supported on the mobile device. Make sure to use a mobile device with an integrated NFC reader and enable the NFC reader. |
| 03_020 05_007 05_010 |
Local data error Local data error Error |
App Link | These errors can occur when our system tries to retrieve essential security credentials during boarding (03_020), both before and after the payment (05_007), or after the payment (05_010). Restart the onboarding process. If this does not help, contact the Adyen Support team. |
| 03_021 05_008 |
Shared key not found Shared key not found |
App Link UI |
These errors can occur when our system tries to retrieve essential security credentials during boarding (03_020) or both before and after the payment (05_008). Restart the onboarding process. If this does not help, contact the Adyen Support team. |
| 05_003 | Decoding response object error | App Link | There was a problem with decoding the Base 64-encoded Terminal API response. |
| 05_004 | Encryption error | App Link | There was a problem with the encryption of the Terminal API response. Try again. If this does not help, contact the Adyen Support team. |
| 05_009 | Error | App Link | This error can occur after the payment when our system cannot extract the transaction ID. Possibly a required parameter is missing from the Terminal API response. Try again. If this does not help, contact the Adyen Support team. |
| 05_016 05_017 |
Error Error |
App Link | These errors can occur after the payment when our system cannot retrieve the installation token to create the payment URL. Restart the payment request process. If this does not help, contact the Adyen Support team. |