N-Z

This field contains the amount of national tax included in the transaction amount.

This field contains an indicator used to indicate the presence of national tax information. 0 indicates not subject to tax and a 1 indicates subject to tax.

Includes all items contained in the billing file and is equal to the total debit amount minus the total credit amount processed in the batch. This is a signed field. For more information about a signed field refer to section I.

This field is populated with the net fuel price, less any taxes exempted or discounts, for the transaction.

This field contains a value indicating if tax was included. Y is entered if the extended item amount includes the tax amount and N is entered if the extended item amount does not include the tax amount.

This field will contain the net non-fuel price, less any taxes exempted or discounts.

Discover transactions only – This field contains a unique ID assigned by Discover Network at the time of the authorisation response.

This field indicates if there was a no show for the reservation.

Valid values:

• 0 = not applicable

• 1 = No show

This field contains the product code for non-fuel items purchased. This file format supports up to 8 different non fuel product codes. Refer to the Fleet Card Implementation Guides from the associations for valid values.

Installment transaction field – this field contains the number of installments applicable to the transaction.

This field is used to identify the number of payment forms relating to split tender transactions (a split tender transaction is when more than one form of payment was used for a purchase).

This field contains the odometer reading for the vehicle. (An odometer is a mechanism within a vehicle that provided information on the mileage the vehicle travels.)

This field contains the date the order was taken. The format for the date should be YYMMDD. YY denotes the year, MM denotes the month, and DD denotes the day.

This field is optional and used to indicate other charges for commercial cards uses at lodging locations. Other charges indicated in this field would be for services not outlined in any other types of charges. Two decimals are implied for this field. Default value is zeroes.

This field is used for Visa Line Item Detail and would contain the amount of any other tax for the transaction.

This field supports a tokenised transaction. It contains the first nine digits of the cardholders account number.

Carries a unique reference number assigned to a cardholder’s card PAN. This value remains constant across tokenised and non-tokenised transactions.

Cruise line transactions only - indicates the number of adults traveling.

Cruise line transactions only -indicates the number of children traveling.

Last name (surname) of the passenger followed by a slash and the first initial of the passengers’ first name as indicated on the auditor’s coupon. If the transaction type is “REF”, the name is taken from the refunded flight coupon. This field is required to qualify for Visa/MasterCard incentive rates.

This field consists of the city name (up to thirteen characters) followed by two character state abbreviation which is in the last two positions of this field. The last two positions of this field will be used to determine the country code. If the values in the last two positions are a valid state the country code will be populated with USA. If the values in the last two positions are a valid Canadian province, the country code will be populated with CAN. If the values in the last two positions are not a valid state or province they will be used to populate the country code field.

If the activity is exclusive to EU activity, Spaces are allowed...

This field contains the name of the travel agent or ticketing location where the transaction took place. The point of sale name is used in airline transactions and is optional for other transactions. This field can be left blank if not applicable.

This field is required to qualify for Visa/MasterCard/Diners/Discover incentive rates. It occupies positions 1-2 of field 22 on the Visa authorisation system. Refer to the below table for various valid values.

This field indicates the capability of the terminal.

Valid values:

• 0 - unknown

• 1 - No terminal

• 2 - Magnetic stripe read

• 3 - Bar code reader

• 4 - OCR reader

• 5 - Integrated Circuit Card reader

• 6 - Hybrid/Dual Terminal – US Only

• 7 - Contactless Solution Only

• 8 - Proximity Read Capability

• 9 - Key entry, no magnetic stripe capability

This field contains the building number for the processing center.

This field contains the city for the processing center.

This field contains the country for the processing center.

This field contains the fax number for the processing center.

Contains the identifier for the processor (users can populate this field with their company details).

This field contains the name for the merchant’s processor.

This field contains the phone number for the processing center.

This field contains the street name for the processing center.

This field contains the zip code for the processing center.

Applicable to Visa transactions only - the product id is a value assigned to U.S. and Canada regions identifying the type of card being used (the product). This value is passed in the authorisation response message in field 62.23 Card Level Results if authorised through an MDEX. If transaction is authorised through another means, check with the authorisation vendor to understand where the product id will be passed. The value received in this field must be passed in the settlement record, unchanged. This field is required to qualify for Visa incentive rates.

This field contains a code read from a card magnetic stripe that indicates prompts that occur at the point of interaction.

Valid values:

• 1 = Prompts for ID number and odometer reading

• 2 = Prompts for vehicle number and odometer reading

• 3 = Prompts for driver number and odometer reading

• 4 = Prompts for odometer reading only

• 5 = No prompts issued

This field allows acquirers to identify which 3-D Secure authentication protocol was used for e-commerce transactions.

Valid values:

• 1 = 3D Secure Version 1.0

• 2 = EMV 3D Secure

The purchase ID format indicates the format of additional identifying information for purchases, such as order number or invoice number, etc.

Valid values:

• 1 = order number

• 3 = rental agreement number

• 4 = hotel folio number

• 5 = invoice number

The purchase identifier is used to send information identifying the purchase to the issuer and cardholder. It indicates the type of identifying information (order number, invoice number, hotel folio number, car rental agreement number, text description, etc.).

This field contains the time of day the purchase was made. The format of this field should be hhmm where hh denotes the hour within the hours range of 00-23 and mm denotes the minutes in the 00-59 range.

Record locator is the PNR (passenger name record) data. If a ticket number is not sent and a record locator is sent the record locator will be passed to the associations in place of the ticket number.

Nine numeric characters, right justified, are assigned for records to monitor the integrity and continuity of data. Each record is sequentially numbered by the merchant from 000000001 and increased by one for each additional record in the file.

This field is used to describe the type of record. This field is essential in processing the remainder of the record. The following Record Type Identifiers have been defined:

• File Header Record — TFH

• Batch Header Record — TBH

• Transaction Header Record — THR

• Transaction Advice Basic Record — TAB

• Transaction Auxiliary Record — TAR

• Transaction Airline Addendum Record — TAA

• Transaction Car Rental Addendum Record — TCR

• Transaction Hotel/Lodging Addendum Record — THL

• Transaction Chip Card Addendum Record — TCC

• Transaction Installment Addendum Record — TIL

• Merchant Address Addendum Record — TMA

• Transaction Visa Fleet Card Addendum Record — TVF

• Transaction MasterCard Fleet Card Addendum Record — TMF

• Transaction Visa Line Item Detail Addendum Record — TVL

• Transaction MasterCard Line Item Detail Addendum Record — TML

• Batch Trailer Record — TBT

• File Summary Record — TFS

This field is populated by the merchant for their use to assist with finding original documents, and for chargebacks. Elavon will include the reference code data on copy retrieval requests or chargeback forms.

This field contains the return city for the auto rental.

This field contains the return country code for the auto rental.

This field contains the return state for the auto rental.

This field contains the renter name for the auto rental.

This field indicates if there are restrictions on the ticket.

Valid values:

• 0 = no restriction

• 1 = restricted (non-refundable)

This field will be used for online PIN Debit transactions and will contain an alphanumeric value used with other key data elements to identify and track all messages related to a given cardholder transaction. This field must be populated with the value contained in field 37 of the authorisation message.

Stopover code(s) and official city airport code(s) for up to a maximum of four flight segments per addendum record to denote passenger itinerary. Valid values for stopover codes are “O” (destination city), “X” (connecting city) or space. If there is only one leg of travel, stopover codes and city airport codes for the Origination and Destination One should be entered. If there are two legs of travel, information for Origination, Destination One and Destination Two should be entered. If there are three legs of travel, then the stopover code for Destination Three should be entered in addition to the other three segments. If there are four legs of travel, the cities and stopover codes should be entered in all five segments of the routing field. If there are more than four legs of travel, a second addendum record should not be created and the information for the first four segments only should be entered.

This field contains the amount of sales tax on the transaction. This field is required for certain interchange incentive rates.

This field contains a sales tax indicator relating to the transaction. This field is required for certain interchange incentive rates.

Valid values:

• 0 = tax not included

• 1 = tax included

• 2 = tax exempt

Mastercard Identity Check a.k.a. (Mastercard Secure Code) Transactions only - This field indicates the presence and type of security protocol present in the authorisation process.

Valid values:

• 2 Channel

• 9 None (no security protocol)

This field contains the Service Establishment Number assigned to the merchant for either Discover or American Express (i.e. Discover SE, AMEX SE) transactions. This format does not support AMEX transactions from T&E merchants, for example airlines, hotels, and car rentals.

The settlement amount is the total debit amount less total credit amount.

This field contains the merchant settlement currency code.

Reserved for future use, zero fill.

This field supports Visa Line Item Detail and contains the zip code for the location the item is shipped from.

Contains the SITA telex number.

This field contains the merchant Summary of Charge (SOC) text. SOC text is a 30 byte batch reference field that is populated by the merchant and used to facilitate the investigation of a merchant payment inquiry and assists the merchant in reconciliation. It is returned to the merchant in the EPA file.

Summary of Charge (SOC) number is a batch identifier that is created by the merchant and creates an association to the currency of the transactions contained within each transaction currency header record batch in the file. This is used for management information and financial reporting. The SOC number must be unique for each merchant id and can only be used once within a 12 month period. This number provides the information required by the Elavon processing system to product reporting and reconciliation data. SOC information is at a batch level and is returned to the merchant in the EPA file.

The suggested formula for the creation of the 8-digit SOC number is as follows:

• 3 digit Julian date of the file creation + 1 digit for the year

• 4 digit sequential number, incremented by 1 per THR record

Example for January 15, 1999 = 01590001

Visa only – This field contains a value which identifies if a transaction meets Visa’s spend requirement defined by the Visa region. This field should be populated as a straight pass thru from authorisation to clearing/settlement. The Spend Qualified Indicator is located in field 62.25 of the authorisation response record.

This field contains the name of the railway start station.

Contains the two digit abbreviation for the state (if US) or province (if Canada) for the transaction.

The stored credential indicator is a value which indicates the transaction is one where the merchant is initiating the first transaction in a series on behalf of the cardholder using credentials stored on file.

VISA and MASTERCARD – valid values

• C – Unscheduled Credential on File - (Visa Only)

• S – Storing Credential indicates credential stored for the first time for later use. (V and MC)

• R – Recurring Transaction using Stored Credentials (V and MC)

• I – Instalment Transaction using Stored Credentials (V and MC)

Installment transaction field – this field contains the amount for all subsequent installments.

This field supports Visa Line Item detail and would contain the national standard coding structure value for the description of goods.

This field must contain the amount of surcharge assessed on the transaction.

Discover and Union Pay transactions only – This value is assigned by the Merchant to assist in identifying a specific card transaction. The STAN remains unchanged for the life of the card transaction. The STAN in the settlement record should match what was submitted in the Authorization Request.

The tax amount field contains the amount of tax applied to the transaction.

This field supports MasterCard Fleet card addendum and contains the tax amount for tax exempt fleets.

This field supports MasterCard Fleet card addendum and contains the tax amount for tax exempt fleets when more than one tax amount applies.

This field supports MasterCard Line Item Detail and contains a value indicating the detailed tax rate applied in relationship to a specific tax amount.

This field supports MasterCard Line Item Detail and contains an indicator that is used to further define tax categories applied to specific domestic processing arrangements in certain locations (type of tax being applied to this line item).

Chip transaction field – this field contains the EMV Version of the Terminal.

Chip transaction field – Tag 9F33 – this field indicates the card input data, the Cardholder Verification Method and the security capabilities that are supported by the terminal.

Chip transaction field – Tag 9F1A – this field contains the country code of the country where the terminal is located.

This field contains the terminal serial number or means of identifying the terminal for merchant locations with multiple terminals.

Chip transaction field – Tag 9A – this field contains the terminal transmission date from the Chip reader, format YYMMDD where YY indicates the year, MM indicates the month, and DD indicates the day.

Chip transaction field – Tag 9F35 – this field contains the terminal type which indicates the environment of the terminal, its communications capability, and its operational control.

Chip transaction field – Tag 95 – this field contains a series of indicators from the terminal perspective. The terminal records the results of offline and online processing by setting a series of indicators in this field.

Airline transaction field – This field will contain either a space or a code to indicate why a ticket was changed.

Valid values:

• C – Change to existing ticket

• N – New ticket

• Space – not used

If the transaction type code is TKT or REF, the field will usually contain the three-digit carrier code followed by the ten-digit form serial number and one-digit check digit for the ticket number. The field must be left justified. The PNR (Passenger Name Record) can also be used. The ticket number is used to achieve incentive interchange rates and is passed to the associations. If the merchant is unable to provide a ticket number in the billing record, contact your Elavon representative.

For information purposes:

1. Elavon will pass the first 13 positions of the ticket number received from the carrier to Visa per their requirements. The check digit will not be passed to Visa, if it is received from the carrier. Visa cardholder statements will reflect a 13 alpha / numeric ticket number in the merchant name field.

2. Elavon will pass up to 14 positions of the ticket number, including the check digit to MasterCard per their requirements.

If the Transaction Type is “TKT”, the ticket/document amount field in the first Transaction Advice Addendum (TAA) record will contain the total sale amount of the ticket referenced in the preceding Transaction Advice Basic (TAB) record.

The ticketing carrier is the official three digit code of the ticketing carrier as assigned by the International Air Transport Association (IATA). If a carrier code has not been assigned, contact your Elavon representative. This field is required for association incentive interchange rates. If you have yet to be assigned a 3-digit Carrier code, contact your Elavon Account Manager.

This field will be populated in tokenised transactions. The token assurance level is a value that allows the token service provider to indicate the confidence level of the payment token to PAN/Cardholder binding. The token assurance level is located in the authorisation field 123, usage 2, dataset ID 68, tag 2 and must be passed in the clearing, unchanged.

This field will be populated in tokenised transactions. The token requestor id is a value that uniquely identifies the pairing of token requestor with the token domain. The token requestor id is located in the authorisation field 123, usage 2, dataset ID 68, tag 3 and must be passed in clearing, unchanged.

This field contains the total authorised amount for the transaction.

Total of all credit amounts in the batch. This is a signed field. For more information about a signed field, refer to section I.

Total number of all credit items in the batch.

This field contains the total of all debit amounts in the batch. This is a signed field. For more information about a signed field, refer to section I.

Total number of all debit items (i.e., debit TAB records) in the batch.

Installment transaction field – this field contains the total installment amount.

Total number of debit or credit items (i.e., number of TAB records) in the batch.

This field contains the total amount of all the non-room charges. It is an optional field with two decimals implied. It is used for commercial cards used for lodging transactions only.

Contains the total number of records in the file (all records including header and trailer records).

Discover transactions only – The Transaction Data Condition Code field identifies the condition of the Track Data submitted in the authorisation request. This field is required for association incentive interchange rates.

If the merchant is utilising Dynamic Currency Conversion (DCC), the transaction amount field contains the amount of the transaction in the transaction currency before DCC is applied.

For all other types of transactions (i.e., all transactions except DCC), the transaction amount field contains the amount of the transaction in the local currency. This is the transaction amount that will be processed by Elavon to the Card associations.

The transaction amount is a required field. 2 decimals are implied for US and Canadian transactions.

The transaction amount must include the surcharge amount if one is assessed.

Chip transaction field – Tag 9F53 – this field indicates the type of transaction being performed.

This field contains the numeric value for the currency code for the transaction.

The transaction date is the date of sale or refund in the format YYMMDD where YY denotes the year, MM denotes the month, and DD denotes the day.

Visa and Amex transactions – this field must include an identifier provided in the authorisation message to facilitate linking of authorisation and settlement records. This field is required for Visa incentive interchange rates.

Union Pay transactions – this field should be populated with the Union Pay date (MMDD) and time (HHMMSS) followed by the Union Pay settlement date in Julian format. Sample layout would be 1123111722327 (MMDDHHMMSSJJJ).

All other card brands – this field should be space filled.

Mastercard Transactions only – U.S.REGION – This field contains a value from the authorisation response message that indicates the fundamental safety and security of a transaction and will include the assessment of both validity of the card and cardholder. The value must be passed unaltered from the authorisation to settlement. Effective April 2019 this field will be mandatory for incentive interchange.

The transaction record count indicates if the transaction will contain a TAB only or a TAB and TAA.

Valid values:

• 01 = if there exists only a Transaction Advice Basic (TAB) record for this transaction

• 02 = if a TAA record follows

This field contains the merchant transaction reference information. This information is also referred to as the Record of Charge (ROC). The information in this field will be used to investigate any transaction level inquiries. This field is a user defined optional field. ROC information is at a transaction level and is returned to the merchant in the EPA file.

Chip transaction field – Tag 9F41 – this field contains the sequence number assigned to the transaction. The transaction sequence counter is a counter maintained by the terminal that is incremented by one for each transaction.

Contains the local transaction time in the format HHMMSS where H indicates the hour, M indicates the minute, and S indicates the seconds. The local transaction time is in the time zone the merchant is located in.

Used to describe the transaction type as indicated below:

• TKT = Sale Transaction (Not electronically billed)

• REF= Refund

• MSC = Miscellaneous Charge

Used to differentiate between debit (sale) and credit (refund) transactions as follows:

• 05 = Sale

• 06 = Refund

Installment transaction field – this field contains a value indicating the type of installment, issuer or acquirer. ISS is used for issuer installment and ACQ is used for acquirer installment.

Installment transaction field – this field is used when a promotion was offered on the installment sale.

This field supports Visa Fleet Card addendum and contains a value which indicates the type of purchase.

Valid values:

• 1 = Fuel

• 2 = Non-fuel

• 3 = Both (fuel and non-fuel)

MasterCard transactions only – the UCAF Collection Indicator is present on Secure Code e-commerce transactions only indicating the type of participation.

Valid values:

• 0 – UCAF data collection is not supported

• 1 – Merchant UCAF (only the merchant is participating)

• 2 – Full UCAF (all parties are participating)

• 3 – MasterPass; Maestro Basic Checkout

• 4 – Reserved for future use

• 5 – Issuer Risk Based Decisioning

• 6 – Merchant Risk Based Decisioning

• 7 – Partial Shipment or Recurring Payment

This field supports Visa Line Item Detail addendum and contains the value added tax invoice reference number.

This field supports both Visa Fleet card addendum in addition to Visa Line Item Detail addendum. The field is populated with the cost of fuel per unit of measure (for example dollars per gallon) and has 4 decimals implied. For example if the price per gallon is $2.749 per unit this field would be populated with 0000000027490

This field supports Visa Line Item Detail and contains a code indicating the unit of measure for the line item.

This field is created by the Elavon host during authorisation and returned in the authorisation response to the client. This field is important in linking authorisations and financial transactions in Elavon systems to facilitate customer reporting. Any client building an EGSF submission file that receives this field in the authorisation response from the Elavon host should populate that data without alteration in this field on the TAB record. If not authorising through Elavon the field should be left blank.

Chip transaction field – Tag 9F37 – this field contains the number used in the generation of the cryptogram for chip transactions. It provides variability and uniqueness to the cryptogram.

Visa transactions only – validation code is a unique value that Visa includes as part of the authorisation response for CPS transactions to ensure that key authorisation fields are preserved in the clearing record.

This field contains the VAT (Value Added Tax) or applicable tax amount.

This field contains the VAT (Value Added Tax) tax rate or applicable tax rate for the item.

This field supports MasterCard Fleet Card addendum and contains the vehicle number.

This field provides a unique identifier of what EGSF specification layout was used to develop the credit card billing file being delivered to Elavon. Previous versions can be left blank.

Currently used for MasterCard transactions only. The Wallet Identifier provides information about transactions initiated through MasterCard systems indicating the type of wallet used.

Valid examples could be:

• 0101 - MasterPass Remote

• 0102 – MasterPass Remote NFC Payment

• 0103 – Apple Pay

• 0216 – Android Pay

• 0217 – Samsung Pay 

Weekly rental rate contains the weekly rental rate for the vehicle rented.