On this page
- Integration overview
- Sample use cases
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) (Releasing soon)
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.
3DS Web SDK
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.
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.
Mobile SDKs (Releasing soon)
- 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 three integration methods:open_in_newLink opens new window
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
doThreeDSecurefield value to
true. For details on the API call, see the Converge API Reference documentationopen_in_newLink opens new window.
Redirect - To use the 3DS 2 feature, when you create a payment session through the Converge API (
POST /payment-sessions), set the
doThreeDSecurefield value to
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. For details, see the documentation for the supported pluginsopen_in_newLink opens new window.
Converge for merchants in North America (NA)
At present, the 3D Secure 2 Service through Converge is available only for merchants in the United States (US).
To enable the 3D Secure 2 feature as part of Converge; existing merchants should call Elavon support
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 checkout.js example HTML formopen_in_newLink opens new window.
XML API - use one of the standalone options to use the 3D Secure 2 service. If you want to use the 3D Secure 2 Web SDK for an XML API integration, see this example codeopen_in_newLink opens new window.
For more details about these integration options for Converge NA, see 3D Secure 2 Integration optionsopen_in_newLink opens new window.
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|
|Direct integration (API)|
|Native Mobile App SDK (iOS / Android) (Releasing soon)|
|Converge for merchants in NA (US)|
|Converge for merchants in EU|
|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|