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

**0060 (Unique Device ID)**
 - Description: Identifies the source lane or terminal through which a transaction is processed, so that a compromised device or fraudulent transaction can be easily identified. The last two numbers *must* be unique to each register within a location (01-99 as the base line for compatibility for all TPP’s). This field should be presented in all transaction types supported by a POS/PMS application. Ex.: 0060,51563621
 - Length: 2-8
 - Data type: numeric

**0400 (Product Code)**
 - Description: An international numeric code describing the type of purchase. A list of valid codes should be provided to the merchant by the acquiring bank or processor. Used in European countries. 
 - Length: 2-4
 - Data type: numeric 

**0401 (Invoice Number/ROC)** 
 - Description: Contains the invoice number or record of charge (ROC). Ex.: 0401,123456 
 - Length: 1-10
 - Data type: numeric

**0406 (Item 1 Text)**
 - Description: Required. Description of purchased item. This field is required along with API Field 0412. Ex.: 0406,BRUSH 
 - Length: 40 max
 - Data type: alphanumeric

**0407 (Item 2 Text)**
 - Description: Description of purchased item. Required if there is an Item Code 2 (API Field 0413). Ex.: 0407,SOAP 
 - Length: 40 max
 - Data type: alphanumeric

**0408 (Item 3 Text)**
 - Description: Description of purchased item. Required if there is an Item Code 3 (API Field 0414). Ex.: 0408,SHAMPOO
 - Length: 40 max
 - Data type: alphanumeric

**0409 (Item 4 Text)**
 - Description: Description of purchased item. Required if there is an Item Code 4 (API Field 0415). Ex.: 0409,TOOTHPASTE
 - Length: 40 max
 - Data type: alphanaumeric

**0410 (Item 5 Text)**
 - Description: Description of purchased item. Required if there is an Item Code 5 (API Field 0416). Ex.: 0410,TOOTHBRSH
 - Length: 40 max
 - Data type: alphanumeric

**0411 (Retail Terms)**
 - Description: Identifies special terms or payment options. Ex.: 0411,1234 
 - Length: 4 
 - Data type: numeric

**0412 (Item Code/Details 1)**
 - Description: Item Code describing type of product purchased.
Examples:
 - 0412,23;1;13.42 (This example includes all subfields, item code, quantity, amt) 
 - 0412,;2;2.35 (This example is quantity + amt only) 
 - 0412,453 (This example is item code only. This is an example of Legacy use).

 - Length: 4-35 
 - Data type: alphanumeric 

**0413 (Item Code/Details 2)** 
 - Description: Item Code describing type of product purchased. Required if there is an Item 2 text.  Refer to description for field 0412. 
 - Length: 4-35 
 - Data type: alphanumeric 

**0414 (Item Code/Details 3)**
 - Description: Item Code describing type of product purchased. Required if there is an Item 3 text. Refer to description for field 0412. 
 - Length: 4-35 
 - Data type: alphanumeric 

**0415 (Item Code/Details 4)**
 - Description: Item Code describing type of product purchased. Required if there is an Item 4 text. Refer to description for field 0412.
 - Length: 4-35 
 - Data type: alphanumeric 

**0416 (Item Code/Details 5)**
 - Description: Item Code describing type of product purchased. Required if there is an Item 5 text. Refer to description for Field 0412. 
 - Length: 4-35 
 - Data type: alphanumeric 

**0723 (Recurring Payments Status)**
 - Description: Flag indicating status of recurring payment (Card on file transaction).
- Valid values: 
 - F - First Payment
 - S – Subsequent scheduled recurring payment (i.e., regular payment)
 - U – Unscheduled recurring payment/purchase - Ex.: 0723,F 
 - Length: 1 
 - Data type: alphanumeric 

**0738 (Recurring Compliance Data)**
 - Description: Contains compliance data that merchants should retain and then return unaltered in the next recurring/card on file transaction. Ex.: 0738,12345. Not required in first requests to establish credential on file. Must retain this field value from response to initiate subsequent COF transactions. 
 - Length: 1-50 
 - Data type: alphanumeric 

**0739 (Credential on File - Initiation and Purpose Indicator)**
Description: This field indicates if the cardholder or merchant initiated the COF transaction and for what purpose.
See :magic-link[Data Fields]{id="data-fields#direct-marketing-fields"} for more details.

**Note:** This field is required for all COF transactions. For existing integrations that do not use this field yet, Fusebox TPP interfaces will continue to make assumptions based on the fields that the POS/PMS is currently sending.

Length: 4
Data type: alphanumeric

**5020 (Token Account Status)**
- Description: Identifies the account range as regulated or non-regulated and is received from the Card Brand. It will contain one of the below values to indicate the status of the account range and should be included in capture if present in the authorization response.
- Valid values:
 - R - Regulated
 - N - Non-regulated 
- Length: 1 
- Data type: alphanumeric

**5021 (Token Assurance Level)** 
 - Description: Defined by the token service provider, this Visa or MasterCard value indicates the assigned confidence level of the token-to-PAN/cardholder binding. It will be returned back to merchants in authorization response when it’s available from association. 
 - Length: 2 
 - Data type: numeric
 
**5022 (Token Requestor ID)**
 - Description: Contains the value that uniquely identifies the pairing of token requestor with the token domain. This value is sent in capture to identify the requestor to the card brand. For payment token transactions, merchant should send in token requestor id when it’s available. It’s a required field for MasterCard card-on-file token transactions. 
 - Length: 11 
 - Data type: numeric

**5023 (Token Cryptogram)**
 - Description: EMV tag contactless chip cryptogram is uniquely generated by the token requestor to validate authorized use of the token. 
 - Length: 40 
 - Data type: alphanumeric

**5024 (Token Cryptogram)** 
 - Description: Last 4 digits of actual account number will be returned back in authorization response when it’s available from association, merchant can use it for receipt-printing purposes instead of using payment token number. 
 - Length: 4 
 - Data type: numeric

**5025 (Card Brand Token Status)**
 - Description: Contains the status of the token.
 - Valid values:
 - 0 = Non-token transaction
 - 1 = Active
 - 2 = Suspended
 - 3 = Deactivated
 - 4 = Expired
 - 5 = Unknown
 - Length: 1 
 - Data type: numeric

## Tabulated Data

Tabulated Data is an API field type that supports multiple values in a single API field. It was developed to better address data that can be grouped together. This field allows API expansion to an area of the API (Retail, Direct Marketing, etc.) where available API fields are otherwise limited. The data separator in a tabulated field is a semi-colon (**;**).

The tabulated data are described as follows:

- Retail tabulated data fields: 0412, 0413, 0414, 0415, and 0416 
- SubField 1: Item code describing the type of product purchased \[max size 16, type N\] 
- SubField 2: Item quantity \[max size 3, type N\] 
- SubField 3: Item amount \[max size 13, type C\] 
- Format: NNNN;NNN;NNNNNNNNNN.NN

Overall total size = 4 + ; 16 + ; 3 + ; 10 + 2 = 35 total

In this example, API Field 0412 includes all subfields, item code, quantity and amount.

      0412,23;1;13.42

In this example, API Field 0412 is being used to pass only the Item Quantity and Amount and the Item Code field has been left blank.

0412,;2;2.35

In this example, API Field 0412 is being used as the item code only. It’s an example of Legacy use.

0412,453

AMEX Level III increased subfield 1 from 4 to 16 to accommodate SKUs as well as item codes.

Retail API fields

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