Elavon downloads and stores cookies on your device when you visit our website. We use these cookies to better understand and improve your browsing experience by identifying most visited pages, personalising content, and measuring site performance.

Essential cookies enable core functionality such as page navigation and access to secure areas. The website cannot function properly without these cookies; they can only be disabled by changing your browser preferences.

Performance cookies help us to improve our website by collecting and reporting information on its usage (for example, which of our pages are most frequently visited).

These cookies and similar technologies gather information about your browsing habits. They remember that you've visited a website and share this information with other organisations, such as advertisers and platforms on which we advertise.
They do this in order to provide you with ads that are more relevant to you and your interests. Although these cookies and similar technologies can track your visits to other websites, they don't usually know who you are.
Without these cookies, online advertisements you encounter will be less relevant to you and your interests.


Cookie Settings

Elavon Financial Services DAC. Registered in Ireland – Number 418442.
Registered Office: Block F1, Cherrywood Business Park, Dublin 18, D18 W2X7, Ireland.
Elavon Financial Services DAC, trading as Elavon Merchant Services, is regulated by the Central Bank of Ireland.
 
Elavon Financial Services DAC. Registered in Ireland with Companies Registration Office. The liability of the member is limited. United Kingdom branch registered in England and Wales under the number BR022122.
Elavon Financial Services DAC, trading as Elavon Merchant Services, is a credit institution authorised and regulated by the Central Bank of Ireland.  Authorised by the Prudential Regulation Authority.  Subject to regulation by the Financial Conduct Authority and limited regulation by the Prudential Regulation Authority.  Details about the extent of our regulation by the Prudential Regulation Authority are available from us on request.

This table lists the error codes that you may experience when working with 3DS APIs. For unresolvable errors, contact Elavon support at[#SEDevPortalSupport@elavon.com](mailto:#SEDevPortalSupport@elavon.com?class=track_link)

| Error code | Error Text | Error Description | Suggested resolution |
| ---------- | ---------- | ----------------- | -------------------- |
| 101 | Message Invalid | Reasons could be one of the following: <ul><li>Message not recognized</li> <li>Invalid message type</li> <li>Invalid message for the receiving component</li> <li>Invalid formatted message</li></ul> | 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 :magic-link[API reference table for an authenticate request parameters description]{id="api-reference"}. 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: <ul><li>Data element not in the required format or value is invalid</li><li>Message Version Number does not match the value set by the 3DS Server in the authentication request message.</li><li>Data element is present in a message where the conditional inclusion does not apply.</li><li> `acsUiTemplate = 05` is supported only for `acsInterface = 02`. </li></ul> | Validate the request and correct the value format for data elements listed in the error detail. See the :magic-link[API reference table for an authenticate request parameters description]{id="api-reference"}. 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. <ul> <li>The endpoint in the API request is valid.</li><li>The user credentials are correct.</li><li>The URI is valid.</li><li>The method used is correct. For example, if you used GET instead of POST.</li><li>The content type is 'application/json'</li><li>The authentication token has not expired for the session. Get a new :magic-link[authentication token]{id="authentication"}.</li></ul> |
| 304 | ISO Code Invalid | ISO code not valid for either [country](http://www.iso.org/iso/country_codes) or [currency](http://www.iso.org/iso/home/standards/currency_codes.htm). | 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 :magic-link[API reference table for an authenticate request parameters description]{id="api-reference"}. If you still get this error, contact Elavon support. |
| 305 | Transaction data not valid | If in response to an authentication request message: <ul><li>Cardholder Account Number is not in a range belonging to the Issuer</li></ul>If in response to a challenge request, and a challenge request message was incorrectly sent, the reason could also be one of the following:<ul><li>challenge request message was received by the wrong ACS</li><li>challenge request message was not sent, based on the values in the authentication response message</li><li>challenge request message with this ACS Transaction ID has already been received and processed</li></ul> | 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. |

Error Codes and suggested resolution

Alliance Offers

Data as a Service

Invitation to Apply

Accounts

Bank Holidays

Card Activation

Card Controls

Commercial Credit Cards

Credit Card Account Details

Credit Card Accounts Overview

Credit Card Alerts

Credit Card Application Status

Credit Card APRs

Credit Card Payments

Credit Card Qualified Offers

Credit Card Statements

Credit Card Transactions

Data Sharing for Marketing Purposes

Digital Wallets

Make a Payment - Coming Soon

Rewards Accelerator

Rewards Automatic Redemption

Rewards Balance Summary

Rewards Redemption Coming Soon

Rewards Redemption Accounts

Rewards Redemptions

Rewards Transactions Earned and Redeemed

Travel Notifications

User Profile

3DSecure2

Avvance

CheckoutJs

Commerce SDK

Converge

Disputes Management

Dynamic Currency Conversion

eBoarding

Elavon Cloud Payments Interface

Fusebox

Hosted Payment Page

In Person Payments on Opayo

Leads

Lightbox payment modal

Online Payments on Opayo

Opayo

Opayo Direct

Opayo Forms

Opayo Reporting API

Opayo Server

Opayo Shared API

Payment Method Gateway

Payments Core 365

Simplify

viaconex

XML API

Access Online Transactions

Account Transfers

Account Validation

ACH Originations

Bank Information

Card as a Service

Card as a Service API

Check Payables

Core Banking API

Corporate Account Information

Corporate Credit Cards

Corporate Onboarding

Corporate Statements

Custody

Data Toolbox

Data Toolbox - Accounts

Data Toolbox - Documents

Data Toolbox - Transactions

Disbursements via Zelle

U.S. Bank Flexible Capital Platform

Freight Payment Customer Profiles

Freight Payment Transactions

Instant payments

Investment Accounting

Money Movement API

PaySmart

Payee Choice

Payee Token+

Personal Loans

Positive Pay

Push to Card

Receivables

Reference API

RTP® - Real-Time Payments

Tokenized Payments

Treasury Builder

U.S. Bank FBO Account

Virtual Account Reporting

Virtual Card Payments

Voyager Accounts

Voyager Cards

Voyager Drivers

Voyager Transactions

Voyager Vehicles

Wire Transfers

EMV 3D Secure Overview

Getting Started

Authentication

Integration options

Integration options overivew

Direct integration to 3DS server

Direct integration - Sample Request and Response

Integrate using the Web SDK

Web SDK Overview

Using the All-in-one Workflow of the Web SDK

Using the Toolkit Workflow of the Web SDK

Web SDK Demo Application

Other Features

3D Secure 2 for merchants not processing with Elavon

Merchant-initiated (3RI) transactions 

Merchant-initiated (3RI) transactions overview

3RI - Sample Request and Response

Travel industry message extension

Test your integration

API Reference

Common Error Scenarios

HTTP response status codes

Release notes

Appendices

Product Security and Best Practices

UI Mockups

3D Secure 2 Concepts

3D Secure 2 Glossary