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.

These are cookies that support site functionality that is visible or advantageous to you or your experience of the site, they enable websites to remember choices and provide a more personalized experience.   Functional cookies help to provide services that you request, such as language preference or layout.

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

U.S. Bank Europe DAC. Registered in Ireland – Number 418442..  Registered Office: Block F1, Cherrywood Business Park, Dublin 18, D18 W2X7, Ireland.
U.S. Bank Europe DAC, trading as Elavon Merchant Services, is regulated by the Central Bank of Ireland.
 
U.S. Bank Europe 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.
U.S. Bank Europe 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.

Most popular solutions

Additional solutions

Fusebox integration & options

Optional platform features

Documentation

North America

Europe

Regions

## September, 2024

Added information about our :magic-link[eCommerce Merchant Fraud Detection]{id="integration-guide"} solution, which can be used alone or in partnership with 3D Secure. 

## October, 2022

This release adds support of EMV 3-D Secure 2.2 features

### Authentication request sent for information only (`transStatus = I`)
Information only is a new transaction status value (`transStatus = I`) added in 3D Secure 2.2. If you want to send the data only for information purposes and do not need authentication, send a value of `05, 06, or 07` in the `threeDSRequestorChallengeInd` field in the authentication request. 

All integration options support this new transaction status request field. 

### Support of message category 02 (NPA) for merchant-initiated transactions
The message category (`messageCategory`) field helps the merchant and the issuer to identify data elements that should be included in a message based on the type of transaction. When sending a merchant-initiated (3RI) authentication request (`deviceChannel = 03`), you can now send the request for non-payment authentication by specifying `messageCategory = 02`. Use this message category when you want to send a request for identity verification and account confirmation. 

### ACS Information Indicator
The `acsInfoInd` field value in the `/lookup` response indicates the 3DS support available for the account number. For example, if the `acsInfoInd` field value is `03`, it means that the issuer will support decoupled authentication for this card number. You could then indicate support for decoupled authentication in the authentication request. 

:::::notice{note}
This release does not support the decoupled authentication feature that is supported in the EMVco 3DS 2.2 specification. 
:::::

### Support of MOTO transactions
Merchant-initiated (3RI) transactions (`deviceChannel = 03`) now support Mail order Telephone order (MOTO) transactions. In the case of decoupled authentication for a MOTO transaction, the merchant’s customer service representative can convey the Cardholder Information Text (`cardholderInfo`) verbally for transactions conducted via a landline or mobile phone.

### Support of card schemes for 3DS 2.2
Our 3DS 2 solution supports following card schemes for the 3DS 2.2 specification: Visa, Mastercard, American Express, and Discover/Diners. 

### 3D Secure 2.2 to 3D Secure 2.1 fallback
The 3D Server supports fallback to 3DS 2.1 if the issuer or the account number does not support 3D Secure 2.2. To learn more about the conditions for 3DS Server's fallback strategy, visit the following links:

### 3DS 1.0 support discontinued
Beginning mid-October 2022, most card brands will stop support for 3DS 1.0 . Therefore, with the 3DS 2.0 release, we have also discontinued the support for 3DS 1.0. We strongly recommend that you upgrade your environment to use to 3D Secure 2.

The 3DS server will return an error for the following scenarios:

- The customer attempts to make a transaction using a card (`account`) that does not support 3DS 2.1 or later. 
- You have set the `clientEndProtocolVersion = 1.0.2` in the `/lookup` or `/authenticate` request.


## August 2021

This release supports the following features.

### 3D Secure 2 now available also for merchants who do not process their payment with Elavon

Even merchants who do not process their payment with Elavon can also use the 3D Secure 2 solution by Elavon now. Such merchants will be registered as service provider merchants. After the registration is complete, they can use the 3D Secure solution just like merchants who process their payments with Elavon.

### Message extension elements for the travel industry

Partners and merchants who operate in the travel industry can send travel-related data such as air, car rental, hotel, and travelers to the issuer (ACS) in the `/authenticate` request. The issuer uses this data in risk-decisioning and determining the appropriate authentication response that it will send to the merchant.

### Token expiry timestamp

The `/token` response returns a new field: `validTo`. This field value indicates the exact time of token expiry in the UTC format. Review the authentication page for more details.


### Web SDK updates

#### New features in the Web SDK version 1.0.5
- Supports the 'service provider fields' in the `/authenticate` request for merchants who do not process their payment with Elavon. For details on these fields, see the 3D Secure 2 authenticate sample request in either the all-in-one workflow or the toolkit workflow
- Supports travel industry data in the `messageExtension` element of the `/authenticate` request.
- Error messages return all fields that were wrong in the corresponding request message.
- Accepts `acctInfo` object and its fields in the authenticate request

#### Bug fixes in the Web SDK
- `threeDSServerTransID` is now an optional field to send an authenticate request.

Install the latest version of Web SDK.

#### Web SDK demo application
The Web SDK demo application helps you to test all the functionalities that the Web SDK supports. You can now download the Web SDK demo application from the developer portal. Use the demo credentials to send requests and responses in a test environment.


## June 2021 (Documentation update only)

To receive authentication credentials that you would need to test the different integration options in the sandbox environment, fill in the information requested in this form.

[3D Secure 2 test credentials request form](https://usbank.az1.qualtrics.com/jfe/form/SV_8dkBSYX47JzhPTw)

We will send you the credentials by the next business day. We will also send contact details to whom you can reach out for any help required during the integration and testing process.

## February 2021

The first release of the 3D Secure 2.0 solution by Elavon. This release supports the following features:

### Available integration options

Two integration options are supported in this release: integrate directly to the 3DS Server or use the :magic-link[Web SDK ]{id="server-to-server-steps"} for integration to the 3DS Server.

### Fallback to 3D Secure 1

When the issuer or the card used for the transaction does not support 3D Secure 2, the transaction falls back to 3D Secure 1.

### Test environment to test different authentication scenarios

Use the test environment to test the authentication scenarios supported by 3D Secure 2. Use the test card numbers to test these scenarios. To test the Web SDK, you can also download the Web SDK demo app and use these test card numbers to generate different authentication scenarios.

Elavon's 3D Secure 2 solution supports 3D Secure 2.1 authentication for Mastercard, Visa, American Express, and Diners card schemes. Review the Getting started page for a brief overview of 3D Secure 2.1 and the different authentication flows supported.


Release notes

Alliance Offers

Data as a Service

Invitation to Apply

Accounts

Bank Holidays

Card Activation

Card Controls

Challenge-Widget

Commercial Credit Cards

Commercial Statements

Credit Card Account Details

Credit Card Accounts Overview

Credit Card Alerts

Credit Card Application Status

Credit Card APRs

Credit Card Balance Transfers

Credit Card Disputes

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: Dashboard

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

Elavon Payment Gateway

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

Card as a Service API

Core Banking API

Money Movement API

Reference API

Access Online Transactions

Account Transfers

Account Validation

ACH Originations

Bank Information

Card as a Service

Check Payables

Corporate Account Information

Corporate Account Information 3LO

Corporate Credit Cards

Corporate Onboarding

Corporate Statements

Custody

Data Toolbox

Data Toolbox - Accounts

Data Toolbox - Documents

Data Toolbox - Transactions

Debit Card Phone Number Lookup

Disbursements via Zelle®

U.S. Bank Flexible Capital Platform

Freight Payment Customer Profiles

Freight Payment Transactions

Incoming Webhooks

Instant Payments

Investment Accounting

PaySmart

Payee Choice

Payee Token+

Personal Loans

Positive Pay

Push to Card

Receivables

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

Fraud scoring

Integration guide

API reference

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

Error Codes and suggested resolution

Common Error Scenarios

HTTP response status codes

Appendices

Product Security and Best Practices

UI Mockups

3D Secure 2 Concepts

3D Secure 2 Glossary