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

It is suggested that customers changing to a different transaction processor at the time of conversion work with their integration analyst to determine how the information stored in their database corresponds to the information required below.

Prior to processing these conversion records, the software must be configured as if it were running front desk transactions in a production mode. When these transactions are processed, they are edited and validated as if they were regular transactions. However, the process stops short of actually sending the transaction to Fusebox and the processor. The conversion occurs by populating the fields in the database based on the information provided for those fields and on how the system is configured.

:::::notice{note}
If the user is changing to a different transaction processor, the conversion program should not try to carry over the CPS fields.
:::::


**0001 (Transaction Type)**
- Required
- Description: Must be 01 (Auth Only)

**0002 (Transaction Amount)**
- Required
- Description: Transaction amount (total amount authorized). Minimum of four digits, decimal point included.

**0003 (Account Number)**
- Required
- Description: Contains either the unformatted track swipe or the manually-entered account number. 
 
**0004 (Expiration Date)**
- Required
- Description: Required only if full magnetic stripe data is not provided in API Field 0003.

**0007 (Reference Number)**
- Required
- Description: Unique number supplied by the POS to identify the transaction.

**0012 (Force Flag)**
- Required
- Description: Must be 1.

**0015 (PS2000 Data)**
- Required
- Description: Most third party processor interface sets do not return this field. The information once contained in this field is now returned in API fields 0034, 0035, and 0036.

**0016 (PS2000 Amount)**
- Not Required
- Description: Most third party processor interface sets do not return this field.

**0032 (Original Auth Date)**
- Required
- Description: Date the original transaction took place.

**0033 (Original Auth Date)**
- Required
- Description: Date the original transaction took place. 
 
**0034 (Authorization Characteristics Indicator)**
- Conditional
- Description: Code representing the Card Association authorizing the transaction. Information received as part of the original authorization response.

**0035 (CPS Validation Code)**
- Conditional
- Description: Computed value assigned by the card association (Visa/MasterCard) and returned as part of the original authorization response.

**0035 (CPS Transaction Identifier)**
- Conditional
- Description: Unique tracking number assigned by the card issuing bank and returned as part of the original authorization response. 

**0037 (Authorizer)**
- Conditional
- Description: Code that identifies the authorizing agency. 

**0038 (Merit Reason Code)**
- Conditional
- Description: Code assigned by processor to track rating.  

**0039 (Merit POS Entry Mode)**
- Conditional
- Description: Code assigned by processor to identify how data was entered. 

**0040 (Merit CVC Error Indicator)**
- Conditional
- Description: Code returned by issuing bank to indicate the result of the CVC check.  

**0041 (Merit Mag Stripe Qualifier)**
- Conditional
- Description: Code returned by issuing bank to indicate the quality of the track data received.   

**0042 (Merit Authentication Code)**
- Conditional
- Description: Code assigned by issuing bank to transaction.  

**0109 (Terminal ID)**
- Required
- Description: References a terminal defined in the PBUI configuration file.
  - **Note** - If using dial backup, PBUI uses the eighth position when creating the backup terminal ID, so the terminal ID size is limited to 7 characters. 

**0110 (Cashier ID)**
- Not Required
- Description:  Can contain any code or name up to 7 characters to identify the person creating the transaction.

**0115 (Transaction Qualifier)**
- Required
- Description: Must be 010 for credit.

**0125 (CPS Retrieval Reference No.)**
- Conditional 
- Description: Assigned for chargeback retrieval purposes.
 
**0126 (CPS Acquiring ICA)**
- Conditional 
- Description: Acquiring bank or third party processor ID.

**0127 (CPS Miscellaneous Data (Requested Payment Service)**
- Conditional 
- Description: Any additional, non-standard, data that the processor.

**0128 (CPS Original Auth Amount)**
- Conditional 
- Description: Original authorization. The only dollar amount associated with this transaction.
 
**0129 (CPS Preferred Customer Indicator)**
- Conditional 
- Description: Indicates if this customer qualifies for the preferred plan. 
 
**0130 (CPS Total Authorized Amount)**
- Conditional 
- Description: Total amount authorized up to this point in the lifecycle of this transaction. Includes decimal point. 

**0131 (Total Number of Incremental Auths Sent)**
- Conditional 
- Description: Total number of incremental authorizations up to this point in the lifecycle of this transaction.

**0131 (Total Number of Incremental Auths Sent)**
- Conditional 
- Description: Total number of incremental authorizations up to this point in the lifecycle of this transaction.

**0300 (Charge Description)**
- Required
- Description: Default is 001 = Lodging 

**0301 (Folio Number)**
- Required
- Description: Folio number.  

**0302 (Room Rate)**
- Required
- Description: Per day charge for room. Include decimal. If room rate $1,000 or more, enter 999.99. 

**0303 (Arrival Date)**
- Required
- Description: Date when customer checks in to the property. 

**0304 (Departure Date)**
- Required
- Description: Date when guest expects to checkout. 

**0305 (Program Code)**
- Required
- Description: 
  - 01 = default  
  - 02 = No Show  
  - 03 = Advanced Deposit   
  - 04 =  Charge 
  - 05 = Express Service 
  - 06 = Assured Reservation 

**0307 (Duration of Stay)**
- Required
- Description: The number of days for the charge.   

**0308 (Ticket / ROC Number)**
- Required
- Description: Record of charge, reference number assigned to the charge. Usually the same as API field 0007.

**0309 (Employee Number)**
- Required
- Description: Identifies the person who checked in or out of the property.

**0310 (Room Number)**
- Required
- Description: Identification of the room incurring primary charges.

**0311 (Extra Charges Amount)**
- Required
- Description: Dollar amount (including decimal point) for any extra charges incurred by the guest.

**0312 (Lodging Extra Charges Reason Codes)**
- Required
- Description: Dollar amount (including decimal point) for any extra charges incurred by the guest.
Reason(s) for extra charges. Enter multiple reasons back to back. This field should only contain a value if the Extra Charges Amount (Field 311) contains a valid amount.  
  - 0 = N/A  
  - 2 = restaurant  
  - 3 = gift shop  
  - 4 = mini bar  
  - 5 = telephone  
  - 6 = other  
  - 7 = laundry                                    

**0313 (Guest Name)**
- Required
- Description:  Name of guest.

**0723 (Recurring Payments Status)**
- Conditional
- Description: Flag indicating status of recurring payment (Card on File transaction). 
- Valid values are: 
  - F - First Payment  
  - S – Subsequent scheduled recurring payment (i.e., regular payment) 
  - U – Unscheduled recurring payment/purchase

**0738 (Recurring Compliance Data)**
- Conditional
- Description: Contains compliance data that merchants should retain and then return unaltered in the next card on file transaction. 

**0738 (Recurring Compliance Data)**
- Conditional
- Description: Contains compliance data that merchants should retain and then return unaltered in the next card on file transaction. 

**1002 (Cardholder Name)**
- Not Required
- Description: Cardholder name parsed from Track I, if provided in API request.

**1008 (Unique ID Request)**
- Required
- Description: Requests Unique ID in API request. Masked Account Number In response.  

**1011 (Host Reference Number)**
- Not Required
- Description: Reference number assigned by the host processor to track this transaction. Only required if the processor provided one.

**1015 (AVS Result Code)**
- Not Required
- Description: Code indicating level of success of address verification portion of authorization.

**8002 (Location Name)**
- Required
- Description: Gateway UI based reporting, settlement and other database functions.

**8006  (Chain Code)**
- Required
- Description: A six position code assigned at the chain level used for key management.


Software conversions

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

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