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

3D Secure 2 (3DS 2) is the new authentication protocol for eCommerce card payments. Whether you are an existing Elavon customer or not, you can still add Elavon's 3D Secure (3DS) solution to your transaction authentication process. Merchants can use Elavon's 3DS 2 solution either as a standalone service or as a feature within an existing Elavon product. The best integration option for your business may depend on items such as your technical implementation, business model, and strategies for managing fraud.

## Option 1 - 3DS 2 as a standalone service 
To use the 3DS 2 solution as a standalone service, use one or a combination of these options:

- Integrate directly with Elavon's 3DS Server 
- Integrate using Elavon's 3DS Web SDK
- Integrate using Elavon's Mobile SDKs (iOS/Android) 

The 3DS 2 as a standalone service option is suitable for the following merchants:

- Any merchant that processes their payments with Elavon or a certified third-party processor. 
- Merchants that use external or third-Party eCommerce solutions but process via Elavon. 
- Merchants that have multiple processors. 

### High-level features of the standalone integration options

#### Direct to 3DS Server

- Direct communication between the merchant's server (backend) and the 3DS Server.
- Merchant has more control over each part of the integration process. 

 For example, you can control how to handle the challenge flow when the issuer returns the challenge response, you can set the preference to challenge the user or not, you can control where the authentication request should be called in the payment flow, and you can do an inventory check-in between a payment flow.
- Requires extra development effort as compared to the other integration options. 

 The development effort required for each merchant varies and depends on factors such as the technical expertise of the development team, understanding of the payment industry, and usage of similar products. However, Elavon's developer documentation guides you step-by-step in the deployment process with sample codes, requests, and responses. 

:magic-link[Integration steps for direct integration to the 3DS Server]{id="server-to-server-steps"}

#### 3DS Web SDK 

- A JavaScript library built on the Elavon 3DS Server API for an easy integration option to handle different 3DS authentication flows.
- Ideal for merchants who want to add 3DS 2 support to their existing web-based checkout solution. 
- Minimal development effort required if using the all-in-one workflow of the Web SDK.
 
The all-in-one workflow is prepackaged with all features and is ready to use once integrated with the merchant's payment page. It runs all steps in the 3DS payment processing with one function call.
- For granular control over the 3DS flow, the Web SDK also provides individual 3DS steps as a "toolkit" of functions that merchants can call as required. 
- Once integrated into a merchant's website or checkout page, the Web SDK handles the communication with the 3DS server to complete the 3DS flow on behalf of the merchant.
- Supports browsers on both mobile and desktop devices. Also, supports the use of the Web SDK (JavaScript) in a native mobile app through the use of a WebView.
- Web SDK demo app available to understand the capabilities offered by the all-in-one and toolkit workflows of the Web SDK before actually integrating it into the payment page. You can :magic-link[try the Web SDK demo application]{id="websdk-demo-app"} to understand more about these flows.
 - Read more about :magic-link[Integration steps for the Web SDK]{id="websdk-overview"}.


#### Mobile SDKs 

- Ideal for merchants who have all or most transactions via their shopping app.
- Built over the 3DS API for easy integration into a merchant's mobile app.
- Initiates and handles the complete 3DS transaction flow on behalf of the merchant.
- Sample apps available to understand the capabilities offered by the mobile SDKs before actually integrating them into the merchant's app.


## Option 2 - 3DS 2 for Elavon merchants using Converge 


### Converge for merchants in European Union (EU)

Converge supports the following 3 integration options:

- **Direct API** - To use the 3DS 2 feature, you need to either integrate the 3DS Web SDK to your website or set a direct integration to the 3DS Server. 

- **Hosted Payments Page** - To configure a hosted payments form, you can use one of the following options. 

 - **Lightbox** - To use the 3DS 2 feature, when you create a payment session through the Converge API (`POST /payment-sessions`), set the `doThreeDSecure` field value to `true`. 

 - **Redirect** - To use the 3DS 2 feature, when you create a payment session through the Converge API (`POST /payment-sessions`), set the `doThreeDSecure` field value to `true`.

 - **Payment Link** - When you send a payment link via the Converge UI, the 3DS 2 authentication check is enabled by default.

- **Shopping cart plugins** - The shopping cart plugins built by Elavon support 3D Secure 2.0. 

### Converge for merchants in North America (NA) 

:::::notice{note}

 At present, the 3D Secure 2 Service through Converge is available for merchants in the US. Merchants in Canada can use the benefits of 3D Secure 2 by using one of the direct integration options.
:::::


#### Prerequisite

To enable the 3D Secure 2 feature as part of Converge,

- new merchants should request the sales consultant to include 3DS 2 as part of their Converge integration

- existing merchants should call Elavon support

#### Integration options

- **Hosted payments page (HPP)** - automatically uses 3D Secure 2 for all transactions made using a terminal that meets the general requirements for using 3D Secure 2 with Converge. 

- **Lightbox** - automatically uses 3D Secure 2 for all transactions made using a terminal that meets the general requirements for using 3D Secure 2 with Converge. 

- **Buy button / Payment link** - automatically uses 3D Secure 2 for all transactions made using a terminal that meets the general requirements for using 3D Secure 2 with Converge. 

- **Billing & Invoicing** - automatically uses 3D Secure 2 for all transactions made using a terminal that meets the general requirements for using 3D Secure 2 with Converge. 

- **Checkout.js** - merchants can either embed the Web SDK in the checkout page or for granular control, manually implement a Checkout.js page with 3D Secure 2 flow. For more details about how to use this option, see this .

- **XML API** - Use one of the standalone options to use the 3D Secure 2 service. 

## Sample use cases for different integration options 

These sample use cases in the following table are some examples of integrations that you can use. You can invent your own integration type that meets your requirement.


| Integration type | Features | Sample use cases |
| ---------------- | -------- | ---------------- |
| Web SDK (JavaScript) | <ul><li>Easiest integration option to handle the 3DS 2 flow in browsers with minimal programming effort.</li> <li>The all-in-one workflow handles the complete 3DS flow and challenge (if required) with one function call.</li> <li>Supports browsers on both mobile and desktop devices.</li> <li>Supports hybrid integrations (see the last row in this table for example use cases).</li></ul> | <ul><li>You want an easy and quick way to integrate the 3DS 2 service.</li><li>Your platform is web-based or the processing is typically performed on the front-end (i.e., in the web browser).</li><li> You want to embed the JavaScript library directly in your payment page (website) and your app (via WebView).</li><li>You are a FuseBox or a viaConex customer and you want to use 3DS 2.</li></ul> |
| Direct integration (API) | <ul><li>Direct communication between the merchant's server (backend) and the 3DS Server.</li><li>More control over each part of the integration process.</li><li>Only integration option that supports 3RI i.e., merchant-initiated transactions. For example, calls for a recurring subscription payment every month can only be initiated by the merchant's server which communicates directly to the 3DS Server.</li></ul> | <ul><li>You want to have more control over the 3DS Secure authentication check process.</li><li>Your business is unable to use a website or an application-based integration.</li><li>You are capturing cardholder data on your website without any encryption and then passing the cardholder data to your server for authentication with the processor.</li><li>You are a FuseBox or a viaConex customer and you want to use 3DS 2.</li></ul> |
| Native Mobile App SDK (iOS / Android) (Releasing soon) | <ul><li>Easy integration into a merchant's mobile app by importing the SDK within your application codebase.</li><li>Mobile SDKs initiate and handle the complete 3DS transaction flow.</li><li>All the features of 3D Secure 2 check optimized for native Android & iOS app, instead of the website.</li></ul> | <ul><li>You have a major share of the customer base who uses your native mobile app for Android and iOS.</li><li>You want to integrate the 3DS 2 features into your mobile app.</li></ul> |
| Converge for merchants in NA (US) | <ul><li>No extra development work is required for these integration options: Hosted payments page (HPP), lightbox, buy button or payment link, and billing & invoicing. </li><li>Minimal development effort if using the checkout.js option.</li><li>For customers using the converge API, integrate using either the direct integration to the 3DS Server or the Web SDK.</li></ul> | <ul><li>You are a merchant in NA (US) and you are already using Converge as your payment processing system.</li><li> You want all the features of 3D Secure 2 without the complexity of manual programming or integration.</li></ul> |
| Converge for merchants in EU | <ul><li>3DS Web SDK is now embedded in Converge EU and no extra integration effort is required.</li><li>All integrations options support 3DS: lightbox, redirect, or payment links.</li></ul> | <ul><li>You are a merchant in the EU and you are already using Converge as your payment processing system. </li><li>You want all the features of 3D Secure 2 without the complexity of manual programming or integration.</li></ul> |
| Hybrid integration | A combination of one or more integration options. See the sample use case column for examples. | **Direct API + Web SDK (all-in-one workflow) example** You capture the cardholder data on your website (Web SDK integration), store the tokenized card details on your server, and then use the card-on-file details for subsequent subscription-based transactions (send a merchant-initiated request also called 3RI via Direct API). In a reverse scenario, if the results of a 3RI transaction return that the card is no longer valid, you can direct the cardholder to authenticate a new card through your website (Web SDK integration). **Web SDK + Mobile SDK example** Your customer base equally uses your website and mobile app for shopping. In this scenario, you can integrate the Web SDK JavaScript file on your payment page and the Mobile SDKs into your native apps. **Web SDK + Converge (Checkout.js) example** For a simpler integration, you can embed the Web SDK into your checkout.js page. In this case, the Web SDK handles the complete 3D Secure 2 check for you. Optionally, you can use the Web SDK to perform 3DS 2 authentication and then pass the authentication values into checkout.js for payment authorization. Your native app (mobile) users can use the same Web SDK integration in their mobile apps by using WebView components. This integration mode gives you more control over authentication errors. |

Integration options overview

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

Product Security and Best Practices

UI Mockups

3D Secure 2 Concepts

3D Secure 2 Glossary