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

The Gateway API response message returned from Fusebox contains most of the required data elements for receipt printing. There are some elements obtained by the payment application during the 2nd Generate AC completion process that need
to be retained by the POS and printed on the receipt. It is the responsibility of the payment application to ensure that all required 
data, especially any data returned from the 2nd Generate that *does not* contain cardholder-sensitive data, is sent to the POS for retention and/or receipt printing. 

There are two fields to identify EMV elements required to be printed on approvals or declines:

- 1378 - EMV Approved Receipt Field List

- 1379 - EMV Declined Receipt Field List

These fields will be populated by the Fusebox TPP interface layer based on the TPP specifications.

Some TPPs require static text to preface this data on the receipt. The Fusebox TPP Interface layer will add any static text after a pipe delimiter 
(“|”) in fields 1378 and 1379 to accommodate this requirement.

:::::notice{note }
The labels are provided for the receipts as a static requirement from the TPP. Fields not present in the API response need not be printed. The POS/PMS will need to accommodate the presence or absence of those fields presented in 1378/1379. 
:::::

The following is an example of fields returned for an approved transaction for a TPP that does not require static text:

1378,1326|;1300|;1307|;1325|;

1300,2A29435BF19ACEC13030

1307,0000008000

1325,A0000000041010

1326,Mastercard

1380,C


The following is an example of fields returned for an approved transaction for a TPP that does require static text:

1378,1326|Application Label: ;1300|ARPC: ;1307|TVR: ;1325|AID: ;

1300, 2A29435BF19ACEC13345

1307, 0000008000

1325, A0000000041010

1326, Mastercard

1380,Chip

If the first Generate AC action returns an “AAC” cryptogram instead of the expected online “ARQC” cryptogram, the payment application will not send the transaction to Fusebox, and no TPP-specific API Field 1379 is returned. In that event, we’ve created a generic declined list for field 1379.

**Example**
1379,1319|Tag 82: ;1307|Tag 95: ;1313|Tag 5F34: ;0017|Tag 9F03: ;1312|Tag 9F1A: ;1300|Tag 9F26: ;1321|Tag 9F27: ;1303|Tag 9F34: ;1320|Tag 9F36: ;1323|Tag 9F37: ;1305|Tag 9F10: ;1335|TAC: ;1336|TACd: ;1337|TACo: ;1329|Tag 9F0D: ;1330|Tag 9F0E: ;1331|Tag 9F0F: ;1358|Tag 9C: ;


If the first Generate AC action returns an “AAC” cryptogram instead of the expected online “ARQC” cryptogram, the default value for 1380 is based on field 0054 and identified below. 

**Entry Method (Swiped)**
 - Field 54 (90)
 - Field 1380 (SWIPED)

**Entry Method (Manual/Key Entry)**
 - Field 54 (01)
 - Field 1380 (MANUAL KEYED) 

**Entry Method (CHIP)**
 - Field 54 (05)
 - Field 1380 (CHIP) 

**Entry Method (Contactless)**
 - Field 54 (07)
 - Field 1380 (Contactless) 

**Entry Method (Fallback to Swipe)**
 - Field 54 (80)
 - Field 1380 (CHIP/MAG)  

## Decoding ICC Application Preferred Name
EMV Tag 9F12 (API Field 1326), ICC Application Preferred Name, has permitted characters that are non-control as defined in the ISO/IEC 8859 that may need translation depending upon the configuration of your terminal. In order to translate non-standard character sets, the payment application will need to refer to the EMV Tag 9F11.

The following list represents what is in Tag 9F11, the Issuer Code Table Index, a value to indicate the code table according to ISO/IEC 8859 for displaying the Application Preferred Name.

- Value: 01 - Part 1 of ISO/IEC 8859
- Value: 02  - Part 2 of ISO/IEC 8859 
 - Value: 03  - Part 3 of ISO/IEC 8859   
 - Value: 04  - Part 4 of ISO/IEC 8859 
 - Value: 05  - Part 5 of ISO/IEC 8859   
 - Value: 06  - Part 6 of ISO/IEC 8859   
 - Value: 07  - Part 7 of ISO/IEC 8859   
 - Value: 08  - Part 8 of ISO/IEC 8859   
 - Value: 09  - Part 9 of ISO/IEC 8859   
 - Value: 10  - Part 10 of ISO/IEC 8859  

## EMV data retention by the POS

Any EMV transaction data obtained after Fusebox returns the response data to the payment application, including any data available after the 2nd Generate AC and risk analysis processing, will not be in Fusebox. This information should be retained by the POS system for receipts, subsequent transactions in the life cycle, chargebacks, cardholder issuer diagnosing, etc.

Check the :magic-link[EMV API fields]{id="emv-api-fields"} for identification of what EMV fields should be retained.



EMV receipts

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 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