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

:::::notice{note}
In the following EMV integration samples asterisks are used to identify:
- Generally unchanging for the duration of the terminal cert.
- Items can change on a per transaction basis.
:::::


## EMV ICC PIN on terminal with NFC mag capability (for API 0047 POS data code index)

When an EMV card is inserted in a terminal with a highest capability of Near Field Communication (NFC) with magnetic swipe, the card and cardholder are authenticated by PIN entry.

**47.1 (POS Device Capability Indicator)** 
-  Value  = H
- ICC contact and contactless capability*

**47.2 (Cardholder Authentication Capability)**
- Value = 1
- PIN authentication capability*

**47.3 (Terminal Card Capture Capability)**
- Value = 1
- Card capture capability*

**47.4 (Terminal Operating/Location Environment)**  
- Value = 1
- Terminal on merchant premises*

**47.5 (Cardholder Present Indicator)**
- Cardholder present**

**47.6 = Card Present Indicator** 
- Value = 1
- Card is present**

**47.7 (Card Data Input Mode Indicator)** 
- Value = 5
- ICC contact**

**47.8 (Card Data Authentication Mode)**  
- Value = 1
- PIN**

**47.9 (Cardholder Authentication Mode)**  
- Value = 3
- Card holder ICC/PIN authenticated online**

**47.10 (Card Data Output Capability Indicator)** 
- Value = 3
- Integrated Circuit Card update capability*

**47.11 = Terminal Data Output Capability** 
- Value = 3
- Terminal display ability*

**47.12 (PIN Capture Capability Indicator)**  
- Value = C
- Capable of 12 characters PINs* 

**47.13 (POS Device Attendance Indicator)** 
- Value = 0
- Attended terminal* 

**47.14 (POS Device Terminal Type)** 
- Value = 4
- Merchant register/terminal*

## Back office standing auth (Cred on file) - Non-EMV implementation

A key entered transaction is performed on a back office terminal with a highest capability of manual entry.

**47.1 (POS Device Capability Indicator)**  
- Value = 6
- Keyed entry only capability*

**47.2 (Cardholder Authentication Capability)** 
- Value = 0
- No electronic authentication capability*

**47.3 (Cardholder Authentication Capability)**
- Value = 1
- Card capture capability*

**47.4 (Terminal Operating/Location Environment)** 
- Value = 0
-  No terminal used*

**47.5 (Cardholder Present Indicator)**  
- Value = 1
-  Cardholder not present (reason not specified)**

**47.6 (POS Data Code Index)** 
- Value = 0
-  Card is not present** 

**47.7 (Card Data Input Mode Indicator)** 
- Value = 6
-  Key entry** 

**47.8 (Card Data Authentication Mode)** 
- Value = 0
-  Card Data not authenticated**

**47.9 (Cardholder Authentication Mode)** 
- Value = 0
-  Card holder not authenticated (Failed or PIN bypass)**

**47.10 (Card Data Output Capability Indicator)**  
- Value = 1
-  None*

**47.11 (Terminal Data Output Capability)** 
- Value = 1
-  No terminal printing or display ability*

**47.12 (PIN Capture Capability Indicator)** 
- Value = 0
-  No PIN capture capability*

**47.13 (POS Device Attendance Indicator)** 
- Value = 2
-  No terminal*

**47.14 (POS Device Terminal Type)** 
- Value = 4
-  Merchant register/terminal*

## EMV ICC signature

When an EMV card is inserted in a terminal with a highest capability of Integrated Chip Contact, the card and cardholder are authenticated by Signature.

**47.1 (POS Device Capability Indicator)** 
- Value = C
-  ICC contact magnetic stripe and keyed capability*
  
**47.2 (Cardholder Authentication Capability)** 
- Value = 1
-  PIN authentication capability*

**47.3 (Terminal Card Capture Capability)** 
- Value = 1
-  Card capture capability*

**47.4 (Terminal Operating/Location Environment)** 
- Value = 1
-  Terminal on merchant premises*

**47.5 (Cardholder Present Indicator)** 
- Value = 0
-  Cardholder present** 
 
**47.6 (Card Present Indicator)** 
- Value = 1
-  Card is present**

**47.7 (Card Data Input Mode Indicator)** 
- Value = 5
-  ICC contact**

**47.8 (Card Data Authentication Mode)** 
- Value = 5
-  Attendant verification of card signature** 

**47.9 (Cardholder Authentication Mode)** 
- Value = 4
-  Cardholder authenticated by merchant (signature)**

**47.10 (Card Data Output Capability Indicator)** 
- Value = 3
-  None*

**47.11 (Terminal Data Output Capability)** 
- Value = 3
-  Integrated Circuit Card update capability*

**47.12 (PIN Capture Capability Indicator)**  
- Value = C
-  Capable of 12 characters PINs* 

**47.13 (POS Device Attendance Indicator)** 
- Value = 0
- Attended terminal* 

**47.14 (POS Device Terminal Type)** 
- Value = 4
-  Merchant register/terminal*


EMV integration samples

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

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