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.

Below are the API fields specific to the lodging industry.

**0054 (POS Entry Mode)** 
- Description: ISO lodging-specific values:
 - 01 = Manual/Key Entry 
 - 05 = Integrated circuit card read 
 - 07 = Contactless Chip Card 
 - 80 = EMV fall back to swipe 
 - 90 = Magnetic Stripe 
 - 91 = Contactless magnetic stripe read
- Length: 2 
- Data Type: numeric

**0060 (Unique Device ID)** 
- Description: Data in this field identifies the source lane or terminal through which a transaction is processed to identify a compromised device or fraudulent transaction can be easily identified.
Some third party processors support a maximum of 2 digits numeric, while others support a maximum of 4 or 8 digits to be passed in this field. This means that 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.
- Length: 2 - 8 
- Data Type: numeric 

**0300 (Charge Description)**
Valid values:
 - 0 = Health Spa
 - 1 = Lodging
 - 2 = Food/Beverage
 - 3 = Gift Shop
 - 4 = Beauty Salon
 - 5 = Convention Fees
 - 6 = Tennis/Pro Shop
 - 7 = Golf/Pro Shop
 - 9 = unassigned
 - 8 = unassigned Defaults to 1. 
- Length: 1
- Data Type: numeric

**0301 (Folio Number)**
- Description: Folio number where the transaction was charged. Ex.: 0301,123456
- Length: 1 - 8 
- Data Type: numeric

**0302 (Room Rate)**
- Description: Per-day charge for the room.
Valid Values: 0.00 - 99999.99 ($99,999.99 max)
Ex.: 0302,50.00
- Length: 2
- Data Type: cents

**0303 (Arrival Date)**
- Description: Date when the customer checks in to the property. Format is MMDDYY. Ex.: 0303,061025 
- Length: 6
- Data Type: date

**0304 (Departure Date)**
- Description: Actual or anticipated guest departure date. Typically, this field coincides with the transaction date (or the date the transaction was settled). If the transaction is a partial payment, occurring prior to the departure, the departure date should be set to the current date, not the actual departure date. Format: MMDDYY Ex.: 0304,061525 
- Length: 6
- Data Type: date 
 
**0305 (Program Code)**
Valid values: 
 - 1 = Lodging 
 - 2 = Assured Reservation (no show) 
 - 3 = Advanced Deposit 
 - 4 = Delayed Charge 
 - 5 = Express Service 
 - 6 = Assured Reservation. Defaults to 1.
- Length: 1
- Data Type: numeric

**0307 (Duration of Stay)**
- Description: The number of days for the charge. Minimum one day. Ex.: 0307,5
- Length: 2 
- Data Type: numeric

**0308 (Ticket Number/ROC)**
- Description: Record of Charge (ROC) or reference number assigned to the charge. Ex.: 0308,12345678 
- Length: 8
- Data Type: numeric
 
**0309 (Employee Number)**
- Description: Identifies the person who checked the guest out. Ex.: 0309,22 
- Length: 1 - 6
- Data Type: numeric

**0310 (Room Number)**
- Description: Identifies the room number for primary charges. Ex.: 0310,211 
- Length: 1 - 4
- Data Type: alphanumeric

 **0311 (Extra Charges Amount)**
- Description: Dollar amount for any extra charges incurred by the guest. Ex.: 0311,125.00 
- Length: 1 - 14
- Data Type: cents
 
**0312 (Extra Charges Reason Codes)**
- Description: This field should only contain a value if the Extra Charges Amount (API field 0311) contains a valid amount. Enter multiple reasons back to back.
Reason(s) codes:
 - 2 = Restaurant
 - 5 = Telephone 
 - 3 = Gift Shop 
 - 6 = Other 
 - 4 = Minibar 
 - 7 = Laundry Ex.: 0312,23 (for Restaurant and Gift Shop charges) 
- Length: 6
- Data Type: numeric 

**0313 Guest Name**
- Description: Name of the guest. If Track I is present and this field is blank, the name encoded in Track I will be used.
Ex.: 0313,Claire Bell 
- Length: 26
- 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. 
- Length: 1 - 50
- 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.
Code Description: 
 - 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. A required field for MasterCard card-on-file token transactions.
- Length: 11
- Data Type: numeric

**5024 (Last 4 Digits of Primary PAN)**
- 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

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

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