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

Prior to performing 3DS authentication or authorization, you can receive a risk score and transaction recommendation using fraud scoring.

:::notice{important}
There is an additional charge to implement fraud scoring. Reach out to your sales consultant to find out more information.
:::

You will need credentials to test in the sandbox environment. If you do not have credentials, fill in the information requested in the [3D Secure 2 test credentials request form](https://usbank.az1.qualtrics.com/jfe/form/SV_8dkBSYX47JzhPTw?class=track_link). For all the calls listed below, you must include your test credentials. For more details on authentication mechanisms supported, see :magic-link[Authentication]{id="authentication"}.

## Fraud scoring with a direct integration

**Step 1. Create transaction and generate a score**

Send the transaction type and data in the /transactions request.

| Transaction type | Description |
|-------------------|----------------------------------|
| Authorization (`auth`) | An auth is used to reserve funds on the customer's card without yet deducting it. This must be followed up with a subsequent 'capture' in the update transaction call. |
| Authorization Capture (`authCapture`) | A simultaneous combination of auth and capture in one, for when there is no need to separately auth then capture. |
| Refund (`refund`) | A refund credits a customer's payment method. Note that a refund should be a separate transaction, not an update to a transaction. The original transactionId may be known which can be supplied to the parentTransactionId field. You cannot score refunds. |

The score recommendations can be any of the following:

- `REVIEW`, in which case it is recommended to review the transaction by performing 3DS authentication.
- `ALLOW`, in which case the transaction can go directly to authorization and skip 3DS authentication.
- `PREVENT`, in which case it recommended the transaction should not go through on a high suspicion of fraud.

By default, `ALLOW` is the standard recommendation response in non-prod. You may force a specific response by using a shopper.email with the following email domains:

- `REVIEW` @qa-force-review.com
- `PREVENT` @qa-force-prevent.com

Save the `transactionId` generated to send updates later on.

**Example**

```
{
    "transaction": {
        "type": "authCapture",
        "amount": {
            "value": "1.00",
            "currencyCode": "USD"
        }
    },
    "card": {
        "number": "{{card}}",
        "expirationMonth": 12,
        "expirationYear": 2024
    },
    "shopper": {
        "shopperId": "merchant-generated-shopper-id-01",
        "email": "jdoe@qa-force-review.com",
        "telephone": "+18665181262"
    }
}
```

**Step 2. Update transaction**

Once a recommendation is given, send an update about what happened after scoring to help train the machine learning engine to better identify fraud and give accurate predictions. These updates can happen asynchronously after a transaction to optimize transaction time.

Send the transaction type and data in the /transactions/{transactionId} request.

| Transaction type | Description |
|--------------------|------------------------------|
| Authorization (`auth`) | It’s possible that the amount authorized will change. This should be sent as another update to the transaction. Note this is not the initial authorization step so you should set `isInitialAuthorization` to false and `isPartialCaptureOrIncrementalAuth` to true. Supply the new amount that was authorized. |
| Capture (`capture`) |	Capture is an update that is done after an auth. The amount does not need to match what’s been authorized. Note this is not the first authorization step so you should set `isInitialAuthorization` to false. The captured amount can also be updated using auth. |
| Authorization Capture (`authCapture`) | A simultaneous combination of auth and capture in one, for when there is no need to separately auth then capture. |
| Void (`void`) | In some circumstances, transactions are voided. There must be a preceding `auth`, `authCapture`, or `capture` to send a void update to a transaction. The void data should be sent as an update to the transaction. |

## Fraud scoring with all-in-one WebSDK

**Step 1. Select fraud scoring and 3DS flow**

| Description| Value |
|--------------|----------------------|
| Fraud scoring only | `threeDSPreferenceIndicator = 03` |
| 3DS flow only | `threeDSPreferenceIndicator = 04` |
| Fraud scoring + always force 3DS flow after scoring |	`threeDSPreferenceIndicator = 05` |
| Fraud scoring + 3DS fraud score if recommended | `threeDSPreferenceIndicator = 01` |

**Step 2. Submit flow option in the WebSDK**

Send the `threeDSPreferenceIndicator` in the sdk.web3dsflow.

**Example**

```
sdk.web3dsFlow({
    "threeDSPreferenceIndicator": "01",
    "purchaseAmount": "200",		
    "purchaseCurrency": "840",		 
    "purchaseExponent": "2",			
    "purchaseDate": "20170316141312",      
    "acctNumber": "4017730000000005",	     
    "cardExpiryDate": "YYMM",		   
    "messageCategory": "01",			
    "transType": "01",			
    "threeDSRequestorAuthenticationInd": "01",     
    "acquirerBin": "761018452",    
    "acquirerMerchantID": "445842",   
    "threeDSRequestorID": "1002475300000000080340007",    
    "threeDSRequestorName": "Test007",   
    "meta":
        {
            "challengeIframeElement": document.getElementById('iframe-container')       
        }
})  
```

Integration guide

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

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