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

Below are two configuration files the payment application (or support systems for the payment applications) needs to load into the EMV PIN pad terminal:

**EMV CAP keys:** the public EMV keys for each AID supported by the TPP and the terminal.

**EMV parameters:** the TPP settings the EMV kernel uses to determine the EMV processing rules.



## EMV key load process 

Every EMV chip is issued with public and private keys that enable it to support the EMV protocol. There are multiple keys for each of the schemes / brands for all of the applications they support (their AIDs). In order to support this, EMVCo distributes the keys in a single EMV CAP key file.

The Elavon Gateway provides EMV public key files at the beginning of an integration project and updates as needed (the public keys change about once a year). The file contains the RID associated with the key, the key index, length, modulus, exponent, expiration date and check sum. 

The keys should be loaded prior to testing and must be updated within a TPP-specified time period. Refer to your terminal manufacturers guide on instructions for loading EMV Keys.

## Reports

There are several reports that may be required for certification. If they are not available through PIN pad commands, the payment application should be able to produce similar reports as the POS system. Below are the report requirements.

## EMV key load report

The POS must be able to produce an EMV key load report if requested by the EMV card associations or the Elavon Gateway operations team. Below is the format of the key load report.

- **EMV key load report header**
 - Date of last successful key load
 - Time of last successful key load TID 
 - Terminal Identification unique terminal identifier at the TPP
 - MID - Merchant Identification unique merchant identifier at the TPP 
 - Title - EMV PUBLIC KEY LOAD REPORT

- **EMV key load report** 
Repeated fields per key (this will be repeated 6 times for 6 different EMV public keys as per card associations). 
 - RID - First 10 characters of the AID, Application Identifier (EMV Tag 9F06) Format is either ASCII or Hex, confirm with your TPP interface guide. 
 - Key Index - Identifies the Certificate Authority public key in conjunction with the RID (EMV Tag 9F22). Format is either ASCII or Hex, confirm with your TPP interface guide. 
 - Key Modulus - Value of the modulus part of the Certificate Authority public key. Format is either ASCII or Hex, confirm with your TPP interface guide. 
 - Key Exponent - Value of the exponent part of the Certificate Authority public key. Format is either ASCII or Hex, confirm with your TPP interface guide. 

- **EMV Key Load Report Footer** Footer - END OF REPORT 

## EMV parameter load process

EMV parameters tell the EMV kernel what rules the TPP wants to support in the EMV processing. Every TPP has the ability to customize the values in the file. The Elavon Gateway has a single format for the EMV parameter file.

The Elavon Gateway provides EMV parameter files at the beginning of an integration project and as they change going forward. The file contains the TPP parameters that define the EMV Kernel choices for items like supported cardholder verification methods, floor limits, terminal action codes, etc. Some of these values control whether the ICC chip will be allowed to perform offline validation or what the action rules are to require a transaction be declined or go online.

:::::notice{note}
The payment application may wish to support multiple versions / configurations of the EMV parameters. If they do, each version may either require an additional EMV certification or additional scripts to the EMV certification. Refer to your TPP to identify what configurations they will allow the payment application to support and the impacts of supporting multiple.
:::::


## EMV parameter report

- **EMV parameter report header** 
 - Title - EMV PARAMETERS REPORT 
 - TID - Terminal Identification – unique terminal identifier at the TPP Format ex. Term ID: 001 
 - MID - Merchant Identification – unique merchant identifier at the TPP Format ex. Merchant ID: 999999999999 
 - Time - Time of last successful parameter load. Format ex. MM/DD/YYYY : HH:MM:SS 

- **EMV parameter report** Repeated fields by brand 
 - Subtitle Payment brand parameters: Visa 
 - Application ID 1-6 Application ID 1: A0000000031010 Application ID 2: Application ID 3: Application ID 4: Application ID 5: Application ID 6: 
 - Floor Limit Chip offline floor limit: 0.00 
 - Fallback Ind. Fallback indicator: Y/N 
 - Terminal Action Codes Terminal action code denial: 0010000000 Terminal action code online: D84004F800 Terminal action code default: D84000A800 

:::::notice{note}
This example is missing several parameters (ex.: random selection, terminal type, terminal capabilities, additional terminal capabilities, TDOL, PDOL). Refer to the PIN pad terminal specification to identify what command(s) will generate the necessary report. 
:::::


## EMV statistic report

Some TPPs may require an EMV statistic report. Check with your TPP integration guide to identify if this report is required for certification.

The basic premise for this report is having the ability to view, search and print EMV statistics since the last batch close. The results should refresh with a successful settlement at the host. This aids in troubleshooting the POS acceptance device.

**EMV statistic report includes** 

- Number of chip cards read failures
- Number of PIN entry errors 
- Number of offline funds declined 
- Number of technical Fallbacks 

## EMV offline declined transaction report

Check your TPP integration guide to identify if this report is required for certification.

The terminal application parameters and the data from the last offline declined transaction must be available on request. This may include DE 55 (a block containing multiple EMV tags in TLV format), the Terminal and Issuer Action Codes, the truncated PAN as printed on the receipt, and Application PAN Sequence Number, if present.

The elements printed include:
 
- **Element - Example or description** 
 - Masked Pan PAN: XXXXXXXX4564 
 - Pan Sequence \# PAN SEQ: 01 
 - Issuer Action Codes >br> 
 - IAC Default: F040008800 IAC Denial: - - - 0010000000 IAC Online: F040009800 
 - Terminal Action Codes TAC Default: D84000A800 - TAC Denial: 0010000000 TAC Online: D84004F800 
 - DE055 
 DE055:PS01EM1749F020600000000 10009F26085FD51646457D5 20482025C009F360204179C 01009F100706010A03A00000 9F3303E0B8C89F1A0201249 A030709109F3501229505000 00080005F2A0201249F21031 342589F3704BE721EC0 

\*An alternative option to printing the DE055 block is to list each tag on separate lines. Refer to your TPP specification for details.

EMV CAP keys, parameters, and reports

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