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.

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

Elavon Financial Services DAC. Registered in Ireland – Number 418442.
Registered Office: Block F1, Cherrywood Business Park, Dublin 18, D18 W2X7, Ireland.
Elavon Financial Services DAC, trading as Elavon Merchant Services, is regulated by the Central Bank of Ireland.
 
Elavon Financial Services 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.
Elavon Financial Services 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.

**0001 (Transaction Type)**
- Description: Electronic Check Conversion/Verification/Guarantee 
 - Length: 2 
 - Void: 11 
- Data Type: N
 
**0002 (Transaction Amount)** 
- Description: Total amount of the transaction, using currency mask 0.00. 
- Length: 1 - 14
- Number: C

**0003 (Account Number)**
- Description: 254
A/N	Account number is not required for check, but a masked account number will be returned for reference. Check transactions do not support Tokenization. 
- Length: 1 - 254
- Number: A/N

**0006 (Authorization Code)** 
- Description: Approval code. 
- Length: 6
- Number: A/N

**0007 (Reference Number)**
- Description: Unique reference number to transaction. 
- Length: 1 - 8
- Number: N

:::::notice{important}
Elavon does not recommend padding the Reference Number field (Field 0007) with leading zeros. Should you choose to do so, be sure to store the value in your system as a String instead of an Integer. This will eliminate any potential discrepancies in how this field is presented in two-part transactions, and the chance of downgrades or fees is greatly reduced. 
:::::

**0009 (Batch Number)**
- Description: Current open batch number at host.
- Length: 1 - 8 
- Number: N

**0030 (Online Indicator)**
- Description: Code returned by the Elavon Gateway Applications indicating the transaction was processed online. This value must be returned with any subsequent adjustments or capture requests. 
 - 0 = Offline 
 - 1 = Online 
- Length: 1 
- Number: N
 
**0033 (Authorization Transaction Time)**
- Description: Time of the original transaction (HHMMSS).
- Length: 6 
- Number: T

**0036 (Transaction Identifier)**
- Description: Unique tracking number assigned to the transaction by the TPP.
- Length: 1 - 15 
- Number: A/N

**0037 (Authorizer)**
- Description: Code which identifies the authorizing agency.
- Length: 1 
- Number: A/N 

**0043 (System Trace Audit Number)**
- Description: The STAN is a unique number generated by Third Party Processor Interface and used by the processor to track a transaction through its system.
- Length: 25 
- Number: N 

**0054 (POS Entry Mode)**
- Description: ISO POS entry mode values: 
 - 01-Manual/Key Entry
 - 10-MICR Entry
- Length: 2 
- Number: N 

**0060 (Unique Device ID)**
- Description: The data in this field identifies the source lane or terminal through which a transaction is processed, so that a compromised device or fraudulent transaction can be easily identified. Some third-party processors only support a maximum of four digits being passed in this field, so the last four numbers must be unique to each register within a location. This field should be presented in all transaction types supported by a POS/PMS application.
- Length: 8 
- Number: N 

**0109 (Terminal)**
- Description: Terminal passed in the incoming message.
- Length: 8 
- Number: A/N 

**0110 (Cashier ID)** 
- Description: Can contain any code or name up to 8 uppercase characters to identify the person logged into the POS. 
- Length: 1 - 8 
- Number: N 
 
**0112 (Processor ID)**
- Description: Responds with the Third Party Processor Interface number used to process this transaction 
- Length: 3 
- Number: N

**0115 (Transaction Qualifier)**
- Description: Fusebox Conversion – 020.
- Length: 3 
- Number: N
 
**0125 (Retrieval Reference Number)** 
- Description: Assigned for chargeback retrieval purposes.
- Length: 1 - 15 
- Number: A/N

**0126 (Track Indicator)** 
- Description: Indicator showing how card was presented on original authorization: 
 - 0=Manual 
 - 1= MICR swiped
- Length: 1 
- Number: N

**0130 (Total Authorized Amount)**
- Description: Total amount authorized. 
- Length: 1 - 14 
- Number: C

**0140 (Merchant Currency Trigraph)** 
- Description: ISO Alpha Currency Code of the merchant.
- Length: 3
- Number: A

**0651 (Auxiliary TPP Reversal Data)** 
- Description: Some TPPs require special data to be retained from the original request and return with future transactions like a void. 
 - **Note** - This value does not have to be stored or retained. 
- Length: 256
- Number: A/N

**0900 (Account Number/MICR)** 
- Description: MICR information to be sent to processor. 
 - May be manual account number (up to 15 characters) or swiped data that includes the all the information from the bottom of the check. 
 - **Note** Output is masked in the response. 
- Length: 1 - 40
- Number: A/N

**0901 (Driver's License)**
- Description: Driver’s license information. May be manually entered or swiped. \*Optional. 
- Length: 1 - 127
- Number: A/N

**0902 (Check Number)**
- Description: Sequential check number of check presented. 
- Length: 10
- Number: N

**0903 (State ID)**
- Description: State code where check or driver’s license issued. 
- Length: 2
- Number: A 

**0904 (State Code)**
- Description: Numeric state code where check or driver’s license was issued. \*Optional. 
- Length: 2
- Number: N

**0905 (Date of Birth)** 
- Description: Date of Birth. The format is MMDDYY. \*Optional. 
- Length: 6
- Number: N

**0906 (Check Type)**
- Description: Type of check presented:
 - 000 = personal check (default) 
 - 001 = personal savings 
 - 003 = corporate 
 - 004 = payroll 
 - 005 = government
- Length: 3
- Number: N

**0907 (MICR Entry Mode)**
- Description: Indicates how MICR Field 900 was entered: 
 - 0 = manual 
 - 1 = MICR reader 
- Length: 3
- Number: N

**0908 (Driver License Entry Mode)**
- Description: Indicates how Field 901 was entered: 0 = manual 1 = swiped **Note** Confirm Federal, State and local regulations regarding the use of a Driver’s License Optional.
- Length: 1
- Number: N

**0910 (Zip)**
- Description: Zip Code from address listed on check presented. \*Optional.
- Length: 9
- Number: A/N

**0911 (Phone Number)**
- Description: Phone number of primary account holder listed on check. \*Optional.
- Length: 10
- Number: N

**0912 (ABA Number)**
- Description: ABA (transit) number from the bottom of the check.
Required for manually entered account numbers. 
- Length: 9
- Number: N

**0913 (Alternate Identification Indicator)**
- Description: Indicator that identifies the type of alternate identification presented. Optional. Confirm Federal, State and local regulations regarding the use of alternate identification.
 - 0 = Other
 - 1 = SSN
 - 2 = Courtesy Card
 - 3 = Military ID
 - 4 = Debit Card
 - 5 = Credit Card
 - 6 = Address
- Length: 1
- Number: N
 


**0914 (Alternate Identification)**
- Description: Alternate Identification. This field contains the appropriate data relating to the type of identification noted in field 913. Should be Masked in the response. \*Optional. 
- Length: 80
- Number: A/N

**0916 (Check Status)**
- Description: 
 - 0 = Verification Only 
 - 1 = Accept Check Conversion 
 - 2 = Decline Check Conversion 
 - 4 = Validation 
 - 5 = Guarantee 
- Length: 1
- Number: A/N

**0917 (ACH Reference Number)**
- Description: Host Reference for approved ACH transactions. 
- Length: 1 - 25
- Number: A/N

**0918 (Returned Check Note)**
- Description: To accommodate additional state specific return check fee information. 
- Length: 1 - 100
- Number: A/N 
 
**0920 (ACH Check Format Code)**
- Description: The format code required for ACH ECS transactions.
Valid Values: 
 - 001 = ECS 
 - Data = Format B 
- Length: 3 
- Number: N

**Field 0921**
- Field Name: ACH Check Format Code
- Description: Indicates the ECS Product method used for the ACH transaction.
Valid Values: 
 - WEB = Web Initiated-Entry 
 - TEL = Telephone Initiated-Entry 
 - CCD = Corporate Cash Disbursement 
 - PPD = Pre-Arranged Payment and Deposit 
- Length: 3 
- Number: N

**0934 (ACH Check Product Code)**
- Description: This field contains the Name of the Consumer making the check transaction. 
- Field may also contain an Opt-Out Number 
- No Special Characters Allowed. 
- Length: 25 
- Number: A/N

**1000 (Card Type)**
- Description: CK – Fusebox Electronic Check Conversion. 
- Length: 2 
- Number: A/N

**1001 (Card Name)** 
- Description: CHECK – Fusebox Electronic Check Conversion. 
- Length: 1 - 26 
- Number: A/N

**1003 (Elavon Response Code)**
- Description: Code generated by the Elavon Gateway Applications to indicate the status of the transaction. 
- Length: 1 - 4 
- Number: N

**1004 (Host Response Message)**
- Description: Host response message, either verbatim or evaluated. May contain Elavon Gateway messages. 
- Length: 1 - 80 
- Number: A/N
 
**1005 (Merchant Number)** 
- Description: Merchant number from the merchant information configured the Fusebox site ID. 
- Length: 1 - 30 
- Number: A/N

**1008 (Masked Account Number)**
- Description: Masked Account Number (last 4 preserved). 
**Note**: Fusebox does not support Tokenization 1008,ID: on check transactions). 
- Length: 21 
- Number: A/N

**1009 (Host Response Code)**
- Description: Host response code indicating condition of the transaction. 
- Length: 1 - 10
- Number: A/N

**1010 (Elavon Response Message)**
- Description: Elavon verbose response message corresponding to error code returned in field 1003.
- Length: 1 - 80
- Number: A/N

**1012 (Elavon Batch Number)**
- Description: Elavon batch number assigned to this transaction.
- Length: 1 - 8 
- Number: N
 
:::::notice{note}
The actual fields returned in the Output Response are dependent on the module being used. If the interface requires the data, and the processor returns the information, it is returned in the format required by the processor.
:::::

Check API Fields

Alliance Offers

Data as a Service

Invitation to Apply

Accounts

Bank Holidays

Card Activation

Card Controls

Commercial Credit Cards

Credit Card Account Details

Credit Card Accounts Overview

Credit Card Alerts

Credit Card Application Status

Credit Card APRs

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 Redemption Coming Soon

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

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

Access Online Transactions

Account Transfers

Account Validation

ACH Originations

Bank Information

Card as a Service

Card as a Service API

Check Payables

Core Banking API

Corporate Account Information

Corporate Credit Cards

Corporate Onboarding

Corporate Statements

Custody

Data Toolbox

Data Toolbox - Accounts

Data Toolbox - Documents

Data Toolbox - Transactions

Disbursements via Zelle

U.S. Bank Flexible Capital Platform

Freight Payment Customer Profiles

Freight Payment Transactions

Instant payments

Investment Accounting

Money Movement API

PaySmart

Payee Choice

Payee Token+

Personal Loans

Positive Pay

Push to Card

Receivables

Reference API

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

Settlements

Reconciliation

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)

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

API-Based Settlement Examples

Check Payment

Check Transactions

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

Gift and Stored Value Card Examples

Online Debit Transactions

Online Debit API Fields

Online Debit Examples

Private Label Cards

Private Label Transactions

Private Label API Fields

Private Label Examples

Health Savings Account Cards

HSA Support

Fusebox and Simplify HSA Card Support

HSA Card API Fields

Puerto Rico

E4 Support

API Fields

EBT Transactions

IVU Transactions

Receipt Example