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

The 3D Secure 2 transaction authentication process involves the transfer of PII information to the issuer and then authentication values back from the issuer to the merchant. Therefore, you must review the security features and follow the recommended best practices on this page.

## Security features in the 3DS Server and the Web SDK

- All API requests and responses use one `threeDSServerTransID` field value (unique to each session) during the transaction authentication life cycle. This unique ID will be generated in response to the `/lookup` or the `/authenticate` request, and it will remain the same until the transaction authentication is complete. If this field value is different at any stage, the server will return an error response. However, if you send a wrong ID in the `/authenticate` request, the server ignores the wrong ID and returns a new ID that will be used until the transaction is complete.

- If the 3DS Server/ Web SDK doesn't receive a response from any component within X minutes, it returns an error response with a 'session timeout' error message. Note that the timeout time differs for different scenarios and the state of the transaction. For example, the authentication token expires after every 10 minutes approximately. The integrator can request a new token to prevent a session timeout.

- The 3DS Server/ Web SDK uses a device fingerprinting mechanism to collect extra information about the device (browser/client) from which the request has originated. The data is included as part of the `aReq` sent to the Issuer, who uses it to validate the authenticity of the transaction. The device fingerprinting data elements include any browser-specific properties and native device-specific properties when using the mobile SDKs. 

- Elavon's 3DS Server is certified by EMVco and by the following card brands:
    - 3D Secure 2.1: Visa, Discover, Mastercard, and American Express
    - 3D Secure 2.2: Visa, Discover, and Mastercard

- All inbound and outbound communication from the 3DS Server and the SDKs (Web and Mobile) uses TLS v1.2. It is a mandatory requirement for all communication within the solution.

- All inter-server communication and processing use an encrypted form of the cardholder PAN. The decryption of the PAN only occurs at the outbound step of sending the aReq to the network Directory Server.

## Best practices recommended for merchants

- You can authenticate to the 3DS Server using either the HTTP basic authentication method (Base-64 encoded username and password) over secure HTTP or using the OAuth 2.0 (token-based). Elavon suggests that if you are integrating directly with the 3DS Server, use the Basic Auth method. However, if you  are using the Web SDK, use token-based authentication. For details on these two methods, see :magic-link[Authentication]{id="authentication"}.

- You must also treat the following values that you receive in the `/authenticate` response as secure data: `threeDSServerTransID`, `authenticationValue`, and `eci`.

    
:::::notice{note}

As part of the 3D Secure 2 flow, the integrator/merchant should never collect any data from the cardholder that's required to satisfy the challenge request. The challenge happens directly between the cardholder and the issuer, and the 3DS Server/ SDKs will communicate the challenge result  to the merchant. An example of one such request is the one-time passcode sent by the issuer for extra identification during the challenge result.
    
:::::


- If you get an authentication-related error such as an invalid or expired API Key, contact the Elavon support team. Note that you might need to give your MID and other details.

- For both speed and security, ZIP and password-protect (with the Advanced Encryption Standard (AES) encryption option) any files that you will send to the Elavon support team.


Product Security and Best Practices

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

Release notes

Appendices

UI Mockups

3D Secure 2 Concepts

3D Secure 2 Glossary