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

EMV is a payment method primarily designed to prevent counterfeit cards and card skimming through use of dynamic data and cryptography. The cryptogram that is generated provides the dynamic data used to validate that the transaction is unchanged and that it originated from a genuine card.

This section provides an introduction to EMV and its impact on applications directly integrated with the Elavon Fusebox transaction processing gateway.


::page-heading-list{min-level=2 max-level=2 }


## Transaction Types

The transaction types below are for card-present transactions.

**Transaction Type Authorization Only (Type 01)** 
  - Credit, full EMV. The transaction qualifier (API Field 0115) must equal 010. EMV supports the Forced/Voice Auth Only 
    feature of this transaction type as a partial EMV.

**Transaction Type Sale (Type 02)** 
  - Credit, full EMV. The transaction qualifier (API Field 0115) must equal 010. EMV supports the Forced/Voice Auth Only feature of this transaction type as a partial EMV.

**Transaction Type Sale (Type 02)** 
  -  Credit/Debit, full EMV. Recommended authorization transaction type for both credit and debit. 

**Prior Authorization (Type 07)** 
  -  Credit-only. Changes an existing Auth Only (Type 01) to a Prior-Auth (Type 07) for settlement. Prior authorizations can also be performed on Forced / Voice Auth Only (Type 01) transactions. This is considered a partial EMV transaction type if the cardholder is present, otherwise use the token from the preceding Auth Only. 

**Return (Type 09)** 
  -  Credit/Debit, partial EMV for credit, full EMV for debit. Debit transactions should follow the standard online PIN process.

**Void Sale (Type 11)** 
  -  Credit/Debit, partial EMV when the cardholder is present. Changes an existing Sale (Type 02) or Prior-Auth (Type 07) to a voided transaction. Usually it is not settled, but it may be included in a batch.

**Void Return (Type 17)** 
  -  Credit/Debit, partial EMV when the cardholder is present. It nullifies an existing Return (Type 09) transaction and changes the status61 of the return transaction to a voided transaction.

**Full Reversals (Type 61)** 
-  Credit/Debit, partial EMV. Reverses the Authorization (Type 01) or Sale (Type 02) for the full amount. Attempted automatically with a Void Sale (11). 

## Benefits of EMV

**Transport Layer Security**

In compliance with industry standards, all applications are required to support TLS 1.2 protocol as well as SHA-2 certificates in all transmissions to our host.

**Counterfeit and Skimmed Cards**

EMV provides offline and online mechanisms to protect against counterfeit and skimmed cards.

- Offline - EMV uses either Static Data Authentication (SDA) or Dynamic Data Authentication (DDA).
- DDA allows the EMV Kernel to authenticate that the chip is genuine. It uses unique data for every transaction, therefore, even if it is copied, it cannot be used offline.
- SDA allows the EMV Kernel to authenticate that the chip is genuine. It can only be used to conduct an offline transaction, which is not allowed in the U.S.
- Online - EMV provides authentication of the chip and the issuer.
- The chip is authenticated with the Application Request Cryptogram (ARQC). This provides a dynamic online digital signature allowing the issuer to authenticate both the chip and the transaction data.
- The Authorization Response Cryptogram (ARPC) provides a dynamic online digital signature that allows the chip to authenticate the response code returned by the issuer.

**Man-in-the-Middle Attack**

A man-in-the-middle attack intercepts the transaction data between the chip and the EMV kernel (offline), or between the various components in the transaction process (online).

- Offline - Protection via Combined Data Authentication and Generate AC (CDA) process. This adds to the security of DDA with a cryptogram generated to secure the transaction data integrity between the chip and acceptance.

- Online - Man-in-the-middle protection is provided by the combined ARQC/ARPC request and response cryptograms, protecting the integrity of both the response and request data.

**Lost and Stolen Cards**

EMV provides lost and stolen card protection via offline and online PIN for both credit and debit cards, based on the issuer card setup. Since the chip is the issuer’s representative in the card, it knows the PIN and can authenticate it offline. In the U.S., all debit cards require an online PIN as the cardholder verification method (CVM).

**Delinquency**

The chip conducts offline risk management by limiting the offline risk to an accumulated amount for a number of transactions. Once the threshold is met, the next transaction is forced to go online.


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

Fusebox overview

Getting started

Transaction flow

Transaction sequencing

API message format

Reconciliation

Settlements

Transaction types

Authorization Only (01)

Sale Transaction (02)

Prior-Authorized Sale (07)

Return (09)

Void Sale (11)

Batch Close (13)

Batch Create and Inquiry (14)

Void Return (17)

Transaction Inquiry (22)

Token Request (37)

Full Authorization Reversal (61)

Heartbeat (73)

Incremental Authorization (75)

Partial Authorization Reversal (76)

Concepts

Tokenization

Tokenization introduction

Tokenization API fields

Tokenization scenarios

Example transactions

Error scenarios

Retail

Retail scenarios

Retail API fields

Retail examples

Lodging

Lodging transactions

Lodging API fields

Lodging examples

Credential on file transactions

Best practices

Software conversions

Restaurant

Restaurant transactions

Restaurant API fields

Restaurant examples

Restaurant credential on file transactions

Restaurant receipts

MOTO and eCommerce

eCommerce transactions

MOTO and eCommerce API fields

Ecommerce examples

Direct marketing examples

eCommerce credential on file transactions

EMV transactions

Implementation considerations

Certification

EMV API fields

EMV Public Cap Keys, parameters, and reports

Sample files

EMV receipts

EMV integration samples

API-based settlement

Settlement transactions

API-based settlement fields

API-based settlement examples

Check payment

Check transactions

Check API fields

Check payment examples

DCC transactions

DCC transaction flows

DCC API fields

DCC examples

DCC receipt requirements

DCC certification process

Gift and stored value cards

Gift and stored value card transactions

Gift and stored value card API fields