{"title":"Error handling","category":"default","creationDate":1776961627,"content":"

The Adyen payments platform performs regular checks to make sure that the mobile device that is used in a Mobile solution is secure.<\/p>\n

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.<\/p>\n

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.<\/p>\n

Error messages for the Android SDK<\/h2>\n

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<\/strong> to learn if your integration needs internet connectivity to resolve the error.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Error code<\/th>\nDescription<\/th>\nInternet needed to resolve<\/th>\nRequired action<\/th>\n<\/tr>\n<\/thead>\n
ANDROID_NOT_UPDATED<\/td>\nTransaction canceled.<\/td>\n\"-white_check_mark-\"<\/td>\nUpdate the SDK to the latest software version and try again.<\/td>\n<\/tr>\n
DEBUG_ENABLED_APK<\/td>\nTransaction canceled.<\/td>\n\"-x-\"<\/td>\nOn the device, go to Settings<\/strong> > System<\/strong> > Developer Options<\/strong> and turn off Developer Options<\/strong>.<\/td>\n<\/tr>\n
DEVELOPER_OPTIONS_ON<\/td>\nTransaction canceled.<\/td>\n\"-white_check_mark-\"<\/td>\nOn the device, got to Settings<\/strong> > System<\/strong> > Developer Options<\/strong> and turn off Developer Options<\/strong>.
In your Test integration this error only occurs for PIN transactions.<\/div><\/div><\/td>\n<\/tr>\n
INVALID_NYC1_FIRMWARE_VERSION<\/td>\nCard reader firmware version is invalid.<\/td>\n\"-white_check_mark-\"<\/td>\nUpdate the card reader to the latest software version and try again.<\/td>\n<\/tr>\n
LOCAL_TIME_TAMPERING<\/td>\nTransaction canceled. Unable to check the security requirements.<\/td>\n\"-white_check_mark-\"<\/td>\nOn the device, go to Settings<\/strong> > System<\/strong> > Date and Time<\/strong> and turn on Automatic date and time<\/strong>.<\/td>\n<\/tr>\n
NON_SELF_RESOLVABLE<\/td>\nTransaction canceled. Unable to check the security requirements.<\/td>\n\"-white_check_mark-\"<\/td>\nContact our Support Team<\/a> to resolve the issue.<\/td>\n<\/tr>\n
NO_TOKEN<\/td>\nCannot transact.<\/td>\n\"-white_check_mark-\"<\/td>\nConnect the device to a network so that the SDK can check the security requirements.<\/td>\n<\/tr>\n
SECURITY_PATCH_LEVEL_OUTDATED<\/td>\nTransaction canceled.<\/td>\n\"-white_check_mark-\"<\/td>\nUpdate the SDK to the latest software version and try again.<\/td>\n<\/tr>\n
SYSTEM_CHANGE<\/td>\nTransaction canceled. Cannot transact due to system change.<\/td>\n\"-x-\"<\/td>\nConnect 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. <\/div><\/div><\/td>\n<\/tr>\n
TOKEN_EXPIRED_S&F<\/td>\nOffline transaction window has expired.<\/td>\n\"-white_check_mark-\"<\/td>\nConnect the device to a network so that the SDK can check the security requirements.<\/td>\n<\/tr>\n
USB_DEBUGGING_ON<\/td>\nTransaction canceled.<\/td>\n\"-x-\"<\/td>\nOn the device, go to Settings<\/strong> > System<\/strong> > Developer Options<\/strong> and turn off Developer Options<\/strong>.<\/td>\n<\/tr>\n
WIFI_DEBUGGING_ON<\/td>\nTransaction canceled.<\/td>\n\"-x-\"<\/td>\nOn the device, go to Settings<\/strong> > System<\/strong> > Developer Options<\/strong> and turn off Developer Options<\/strong>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Error messages for the Android Payments app<\/h2>\n

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.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Error code<\/div><\/th>\n
Error name<\/div><\/th>\n
Error shown<\/div><\/th>\n
Description<\/th>\n<\/tr>\n<\/thead>\n
01_001
02_001
03_001<\/td>\n		No return URL
No return URL found
No return URL found<\/td>\n		UI<\/td>\nThe return URL field is empty or missing. Check and fix the return URL. This error can occur during the onboarding check<\/strong> (01_001), during the boarding<\/strong> (02_001), or before the payment<\/strong> (03_001).<\/td>\n<\/tr>\n
01_002
02_002
03_002<\/td>\n		Return URL encoding error
Invalid return URL
Invalid return URL<\/td>\n		UI<\/td>\nThe 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<\/strong> (01_002), during the boarding<\/strong> (02_002), or before the payment<\/strong> (03_002).<\/td>\n<\/tr>\n
01_003<\/td>\nNative library error<\/td>\nApp Link<\/td>\nPossibly the boarding request token is incorrect. Restart the onboarding process.<\/td>\n<\/tr>\n
01_004
02_018<\/td>\n		Installation ID error
Installation ID error<\/td>\n		App Link<\/td>\nPossibly the SDK requirements are not matched. Make sure to check the SDK requirements. This error can occur during the onboarding check<\/strong> (01_004) or during the boarding<\/strong> (02_018).<\/td>\n<\/tr>\n
01_105
02_020
03_019
05_005
05_006<\/td>\n		Invalid return URL
Error
Invalid return URL
Error
Error<\/td>\n		UI<\/td>\nThe return URL is incorrect. Check and fix the return URL. This error can occur during the onboarding check<\/strong> (01_005), during the boarding<\/strong> (02_020), before the payment<\/strong> (03_019), or after the payment<\/strong> (05_005 and 05_006).<\/td>\n<\/tr>\n
02_003<\/td>\nBackend error<\/td>\nApp Link<\/td>\nThis error occurs from the backend. Make sure you have the right Payments app role or that your encryption passphrase is set correctly.<\/td>\n<\/tr>\n
02_004<\/td>\nBoarding token error<\/td>\nApp Link<\/td>\nPossibly the boarding request token is incorrect when sending the boarding token in your App Link. Check and fix the boarding request token.<\/td>\n<\/tr>\n
02_005<\/td>\nBoarding token error<\/td>\nApp Link<\/td>\nThe boarding token that was used is either encoded incorrectly or not encoded at all. Make sure that the boarding token is encoded correctly.<\/td>\n<\/tr>\n
02_006<\/td>\nBoarding token error<\/td>\nApp Link<\/td>\nThis error occurs when our system receives a boarding token but is unable to properly deserialize it.<\/td>\n<\/tr>\n
02_007<\/td>\nBoarding token error<\/td>\nApp Link<\/td>\nPossibly, during the onboarding process, the signature validation of the boarding token failed. Restart the onboarding process.<\/td>\n<\/tr>\n
02_008<\/td>\nBoarding token error<\/td>\nApp Link<\/td>\nPossibly the boarding token is expired. Restart the onboarding process.<\/td>\n<\/tr>\n
02_009
03_009<\/td>\n		General error
General error<\/td>\n		App Link<\/td>\nThis error can occur when our system encounters a network communication problem either during boarding<\/strong> (02_009) or before the payment<\/strong> (03_009). Check your network connection.<\/td>\n<\/tr>\n
02_010<\/td>\nInstallation ID mismatch<\/td>\nApp Link<\/td>\nThe 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.<\/td>\n<\/tr>\n
02_011
02_012
02_013
02_014
02_016<\/td>\n		Invalid signature
Invalid signature
Local error
Error
Error<\/td>\n		App Link<\/td>\nThese errors can occur during the boarding flow<\/strong>. Restart the onboarding process.<\/td>\n<\/tr>\n
02_015<\/td>\nError<\/td>\nApp Link<\/td>\nThis error occurs during the getInstallationToken<\/code> API call. Restart the onboarding process.<\/td>\n<\/tr>\n
02_017<\/td>\nApp is already boarded<\/td>\nApp Link<\/td>\nThis error occurs if you send another boarding request when the app is already boarded.<\/td>\n<\/tr>\n
02_019<\/td>\nInstallation Token error<\/td>\nApp Link<\/td>\nThe host URL cannot be extracted from the installation token to construct the correct URL for the request.<\/td>\n<\/tr>\n
03_003<\/td>\nDecoding error<\/td>\nApp Link<\/td>\nThe Terminal API request is either encoded incorrectly or not encoded at all.<\/td>\n<\/tr>\n
03_004<\/td>\nEmpty request object<\/td>\nApp Link<\/td>\nThe request object cannot be empty. Make sure that your Terminal API request includes all required parameters and send it again.<\/td>\n<\/tr>\n
03_005<\/td>\nOnboarding data not found<\/td>\nApp Link<\/td>\nThis error can occur if you try to make a payment without onboarding. Restart the onboarding process first, then make the payment again.<\/td>\n<\/tr>\n
03_006<\/td>\nAPI error<\/td>\nApp Link<\/td>\nThis error can occur when you make a call to the Payments app API<\/a>. Check the path and request parameters and the destination URL.<\/td>\n<\/tr>\n
03_007
03_008<\/td>\n		Configuration not found
Configuration not found<\/td>\n		App Link<\/td>\nThese errors can occur before the payment<\/strong> if there is no configuration object found.<\/td>\n<\/tr>\n
03_010<\/td>\nInstallation token not found<\/td>\nApp Link<\/td>\nYour request to the Payments app API<\/a> is missing the installation token.<\/td>\n<\/tr>\n
03_012<\/td>\nError<\/td>\nApp Link<\/td>\nThis error can occur when our system cannot verify your request. Restart the onboarding process.<\/td>\n<\/tr>\n
03_013<\/td>\nNexo request error<\/td>\nApp Link<\/td>\nA 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.<\/td>\n<\/tr>\n
03_014
03_015<\/td>\n		Decryption error
Decryption failed<\/td>\n		App Link<\/td>\nThese 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.<\/td>\n<\/tr>\n
03_016<\/td>\nLoad key error<\/td>\nApp Link<\/td>\nThis error can occur before the payment<\/strong> when our system is unable to retrieve or generate the necessary encryption key.<\/td>\n<\/tr>\n
03_017<\/td>\nMalformed transaction request<\/td>\nApp Link<\/td>\nPossibly a required parameter is missing from your Terminal API request. Make sure that your Terminal API request is correct and includes all required parameters.<\/td>\n<\/tr>\n
03_018<\/td>\nNFC error<\/td>\nApp Link<\/td>\nThe NFC reader is disabled, or not supported on the mobile device. Make sure to use a mobile device with an integrated NFC reader<\/a> and enable the NFC reader.<\/td>\n<\/tr>\n
03_020
05_007
05_010<\/td>\n		Local data error
Local data error
Error<\/td>\n		App Link<\/td>\nThese errors can occur when our system tries to retrieve essential security credentials during boarding<\/strong> (03_020), both before and after the payment<\/strong> (05_007), or after the payment<\/strong> (05_010). Restart the onboarding process. If this does not help, contact the Adyen Support team.<\/td>\n<\/tr>\n
03_021
05_008<\/td>\n		Shared key not found
Shared key not found<\/td>\n		App Link
UI<\/td>\n		These errors can occur when our system tries to retrieve essential security credentials during boarding<\/strong> (03_020) or both before and after the payment<\/strong> (05_008). Restart the onboarding process. If this does not help, contact the Adyen Support team.<\/td>\n<\/tr>\n
05_003<\/td>\nDecoding response object error<\/td>\nApp Link<\/td>\nThere was a problem with decoding the Base 64-encoded Terminal API response.<\/td>\n<\/tr>\n
05_004<\/td>\nEncryption error<\/td>\nApp Link<\/td>\nThere was a problem with the encryption of the Terminal API response. Try again. If this does not help, contact the Adyen Support team.<\/td>\n<\/tr>\n
05_009<\/td>\nError<\/td>\nApp Link<\/td>\nThis error can occur after the payment<\/strong> 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.<\/td>\n<\/tr>\n
05_016
05_017<\/td>\n		Error
Error<\/td>\n		App Link<\/td>\nThese errors can occur after the payment<\/strong> 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.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

See also<\/h2>\n