Error Codes and suggested resolution
This table lists the error codes that you may experience when working with 3DS APIs. For unresolvable errors, contact Elavon support atemail#SEDevPortalSupport@elavon.com
Error code | Error Text | Error Description | Suggested resolution |
---|---|---|---|
101 | Message Invalid | Reasons could be one of the following:
| Validate the request for the error highlighted in the error detail. If you made the required updates, but still get this error, contact Elavon support. |
102 | Message version is not supported | Message version received is not valid for the receiving component. | Validate the messageVersion field in the request. Valid values are 2.1.0 or 2.2.0 . |
103 | Sent Messages Limit Exceeded | Exceeded maximum number of messages. | Send the request after some time. If you still get this error, contact Elavon support. |
201 | Missing required data element | A required 3D Secure Data Message element is missing. For example, if acctNumber , a required field, is missing in the /3ds2/authenticate request | Validate the request and include the required data elements that are listed in the error detail. See the API reference table for an authenticate request parameters description. If you made the required updates, but still get this error, contact Elavon support. |
202 | Critical Message Extension Not Recognized | ID of critical Message Extension(s) that was not recognized; if more than one extension is detected, this is a comma-delimited list of message identifiers that were not recognized. | The EMVCo 3DS 2.1/2.2 specifications do not define any critical extension. This error code might be returned if the criticalityIndicator field in the /3ds2/authenticate request is set to true . If you get this error, contact Elavon support. |
203 | Format of one or more Data Elements is Invalid according to the EMV Specification | Could be returned for one of the following reasons:
| Validate the request and correct the value format for data elements listed in the error detail. See the API reference table for an authenticate request parameters description. If you made the required updates, but still get this error, contact Elavon support. |
204 | Duplicate Data Element | Valid data element is present more than once in the message. | Validate the request and delete the duplicate instance of the data elements listed in the error detail. If you made the required updates, but still get this error, contact Elavon support. |
301 | Unknown transaction ID | Transaction ID received is not valid for the receiving component. Invalid could mean that the Transaction ID is not recognised, or is recognised as a duplicate. | Validate that the threeDSServerTransID field value in the request matches the threeDSServerTransID field value you received in the corresponding authenticate response. |
302 | Data Decryption Failure | Data could not be decrypted by the receiving system due to technical or other reasons. | Verify that the field mentioned in the error details is encrypted according to 3DS specifications. In mobile SDK, the sdkEncData field is encrypted by SDK for the DS to decrypt. In case of a challenge, the mobile SDK encrypts the cReq and sends it as a JWE encrypted string to the ACS. |
303 | Access Denied, Invalid Endpoint | Access denied, invalid endpoint. | To resolve this error, verify the following conditions and send the request again.
|
304 | ISO Code Invalid | ISO code not valid for either open_in_newcountryLink opens new window or open_in_newcurrencyLink opens new window. | Validate the ISO code. If the ISO code is valid, ensure that you are sending all required and conditional data elements in the request. See the API reference table for an authenticate request parameters description. If you still get this error, contact Elavon support. |
305 | Transaction data not valid | If in response to an authentication request message:
If in response to a challenge request, and a challenge request message was incorrectly sent, the reason could also be one of the following:
| You might get this error when the card is not supported or there is an error processing the challenge. Suggest the user use a different card for the transaction. |
306 | Merchant Category Code (MCC) Not Valid for Payment System | Merchant Category Code (MCC) not valid for Payment System. For example, invalid MCC received in the authenticate request. | Check the MCC is correct. If you still get this error, then it could be an account configuration issue. Contact Elavon support. |
402 | Transaction Timed Out | Transaction timed-out | This error is generally returned if there is a system issue. Try again later and if the issue persists, contact Elavon support. |
403 | Transient System Failure | Transient system failure. For example, a slow processing backend system. | This error is generally returned if there is a system issue. Try again later and if the issue persists, contact Elavon support. |
404 | Permanent System Failure | Permanent system failure. For example, a critical database is inaccessible. | This error is generally returned if there is a system issue. Try again later and if the issue persists, contact Elavon support. |
405 | System Connection Failure | System connection failure. For example, the sending component is unable to establish a connection with the receiving component. | This error is generally returned if there is a system issue. Try again later and if the issue persists, contact Elavon support. |