A-M

This data element helps the issuer to trust the transaction by validating this key component of the Mastercard SecureCode/Mastercard Identity Check authentication process

This field contains the credit card account number or Elavon Token which identifies the customer. The account number is left justified with trailing spaces. Visa’s authorisation network record returns the cardholder account number in field 2. The cardholder account number must contain 13, 16 or 19 digits with the last digit being a mod-10 check digit.

The Account Status value is a value which will indicate if a transaction is on a Regulated or Non-Regulated BIN. This field is populated in tokenised transactions and must contain the value received back in the authorisation request unchanged. This field will be used in qualification. The Account Status is located in field 62.26 on the Visa authorisation system record. If the transaction is authorised through another means other than an MDEX, check with the authorisation vendor to understand where this field will be passed.

ACI is applicable to Visa transactions only. ACI is a code assigned by the Visa authorisation system to reflect the authorisation characteristics. This field was formerly known as the Payment Service Indicator.

Valid values:

• A = Card present

• B = Tokenised E-commerce with mobile device

• C = Card Present (cardholder activated, self-service terminal)

• E = Card Present with merchant name and location data

• F = Account Funding transaction (card not present)

• J = Card Not Present – Recurring Bill Payment

• K = Card Present with Key Entry (card is key-entered, address verification requested with exact match on zip code)

• N = Not a Custom Payment Service (CPS) transaction

• P = Card Not Present (preferred customer participation requested)

• R = Card Not Present (address verification not required)

• S = Electronic Commerce 3D Secure Attempts

• T = A CPS Program was not available when authorised

• U = Card Not Present 3D Secure Electronic Commerce

• V = Card Not Present (address verification requested)

• W = Card Not present – Non 3D Secure Electronic Commerce

• X = Disqualified Custom Payment Service transaction (inserted by BASE II)

This field is required to qualify the transactions for Visa Custom Payment Services rates. The Authorization Characteristics Indicator is located in field 62.1 on the Visa authorisation system record. If transaction is authorised through another means other than an MDEX, check with the authorisation vendor to understand where this field will be passed.

If the merchant is participating in Verified by Visa (V by V) the following combinations of elements are required:

• When ECI equals 05, then ACI must equal U

• When ECI equals 06, then ACI must equal S

• When ECI equals 07, then ACI must equal W or P

A number used by the merchant to designate a specific ticketing location. Spaces are acceptable if no value is entered by the merchant.

This field is populated in support of line item detail for a MasterCard transaction. It will contain the alternate tax identifier for the line item.

MasterCard Only - This field contains the fee amount for the airline ancillary service provided.

Visa Only - This field contains the fee description for the airline ancillary service provided. This description will be passed to Visa in place of the ticket number.

Visa defines this as Ancillary Service Category. MasterCard refers to the same data as Ancillary Fee Code

This field will contain the airline ancillary service/fee category code for the sole or primary type of service that has been provided. Up to four ancillary service /fee category codes per ancillary transaction can be submitted. This field should be left justified reflecting the two position applicable value. Below is a list of valid values.

• BF = Bundled Service

• BG = Baggage Fee

• CF = Change Fee

• CG = Cargo

• CO = Carbon Offset

• FF = Frequent Flyer

• GF = Gift Card

• GT = Ground Transport

• IE = In-Flight Entertainment

• LG = Lounge

• MD = Medical

• ML = Meal/Beverage

• OT = Other

• PA = Passenger Assist Fee

• PT = Pets

• SA = Seat Fees

• SB = Standby

• SF = Service Fee

• ST = Store

• TS = Travel Service

• UN = Unaccompanied Travel

• UP = Upgrades

• WI = WiFi

Visa only – This field will contain a value which specifies the airline ancillary service sub category code applicable to the service at the coupon level as defined by ATPCO. Up to four ancillary service sub category codes per ancillary transaction can be submitted. Valid ancillary service sub category codes can be obtained from ATPCO.

Visa only – The ticket number assigned to the airline ancillary transaction.

Chip transaction field – Tag 5F24 – this field captures the expiration date which is imbedded within the chip.

Chip transaction field – Tag 82 – this field provides a series of indicators that reflect the specific functions supported by the chip card account.

Chip transaction field – Tag 9F26 – this field contains chip information passed from the chip to the terminal to validate the chip. This information must be captured and passed in the settlement.

Chip transaction field – Tag 9F36 – this field contains the count (the counter increments by 1 each time a transaction is initiated) of the transactions performed within the application.

The approval code is a series of alpha/numeric characters assigned by the credit card company to validate approval of a transaction. This field is also known as the authorisation code. If no value is entered, zeroes or spaces are accepted; however, to qualify for Association incentive rates, the authorisation code from the authorisation response record must be moved to this field.

Chip transaction field – Tag 5F2A – this field contains the currency code the transaction was authorised in.

Chip transaction field – contains the date transaction was authorised on.

Applicable to Visa transactions only – authorisation response code is a code that is returned by Visa in the authorisation response message (usually 00) indicating approval of a transaction. This field may be spaces if a value is not transferred from the Visa authorisation response record field 39.

This field contains the source of the authorisation.

Valid values:

• 00 = Off-line by terminal

• 01 = On-line to acquirer

• 02 = Voice (referral)

• 10 = EMV compliant, offline by terminal

• 11 = EMV compliant, online to acquirer

• 12 = EMV compliant, voice

If Multi-Currency or DCC transaction, the authorised amount field should contain the amount which was authorised and must equal the cardholder amount.

If NOT Multi-Currency or DCC transaction, the authorised amount should contain the amount which was authorised and must equal transaction amount keeping in mind the below scenario for U.S. processing.

The authorised amount field must contain the total amount authorised for all transactions approved simultaneously with a single approval code.

If the merchant participates in surcharging, the authorised amount will also include the surcharge amount if one is assessed.

Example for the airline industry: If four tickets for $400 each are authorised simultaneously, the authorised amount for all four transactions will be $1,600.

When a credit card company’s Address Verification Service (AVS) is utilised, this field will contain the code used by the credit card company to respond to the address verification request. This field may be spaces if a value is not transferred from the authorisation response record.

Valid values:

• A – Address matches, but zip code does not match

• B – Street address match for Int’l transaction

• C – Street address & Postal Code not verified for Int’l address

• D – Street address & Postal Code match, Int’l address

• E – Error response for merchant category code

• G – Address information is unavailable, non AVS participant

• I – Address information not verified for Int’l address

• M – Street address & Postal Code match for Int’l transaction

• N – Address & ZIP code do not match

• P – Postal Code matches for Int’l transaction

• R – Retry, system unavailable or timed out

• S – Issuer does not support AVS

• U – Address information is unavailable, domestic transaction

• W – Nine digit ZIP code match

• X – Exact match, address and nine digit ZIP code match

• Y – Address & 5 digit ZIP code match

• Z – Five-digit ZIP code match

MasterCard transactions only – the Banknet date is the date the transaction was authorised through Banknet. The format of this field is MMDD. This field is required to qualify for MasterCard incentive rates.

MasterCard transactions only – the Banknet Reference Number is assigned by MasterCard to each authorisation message. The Banknet Reference Number contains the financial network code, a unique identifying number and the identification for the MIP that generated it. This field is required to qualify for MasterCard incentive rates.

This field contains the total number of batches in this file, must be numeric and greater than zero.

Installment transaction field – this field would contain the boarding fee amount fees associated with the installment transaction.

The business center charges are charges incurred at the business center of a hotel. Optional information passed for commercial card lodging/hotel transactions.

The business code indicates the type of market.

Valid business codes are below:

• LG = Lodging

• CA = Car Rental

• FL = Fleet

• Space = none (not applicable)

Indicates the date the car was checked out (rented). Format must be YYMMDD where YY denotes the year, MM denotes the month, and DD denotes the day.

The car class code contains the classification of the vehicle rented, such as midsize, luxury, etc.

This field contains the Customer Service telephone number for the car rental company.

This field contains the phone number for the physical car rental property.

This field contains the agency code, phone number, or address abbreviation used to identify the rental location.

Indicates the date the car will be returned. Format must be YYMMDD where YY denotes the year, MM denotes the month, and DD denotes the day.

Chip transaction field – this field contains the number assigned to a specific card when two or more cards are associated with a single account number.

This field contains and identifier which indicates the type of card used.

Valid values:

• AX = American Express

• DB = Debit Card (PIN based)

• DC = Diners Club/Carte Blanche

• DI = Discover

• EB = Electronic Benefits Transfer (EBT)

• JB = JCB

• VI = Visa

• MC = MasterCard

• UP = Union pay

• P1 = Private Label 1

• P2 = Private Label 2

• P3 = Private Label 3

The cardholder activated terminal level indicator indicates the transaction took place at a self-service terminal used for transactions in an unattended POS situation. Values in this field will vary depending on association and environment.

Valid values:

Visa:

• ' ' - Not Applicable

• 1 - Limited Amount Terminal

• 2 - Automated Dispensing Machine

• 3 - Self Service Terminal (For AFD/CAT)

MasterCard:

• ' ' - Not Applicable

• 1 - Automated Dispensing Machine

• 2 - Self Service Terminal (For AFD/CAT)

• 3 - Limited Amount Terminal

• 4 - In-flight Commerce

• 6 - Electronic Commerce

• 7 – Transponder

• 9 – Mobile Acceptance Solution

The cardholder amount contains the amount the cardholder will be billed for this transaction. This is a required field.

Mastercard Identity Check (a.k.a. MasterCard Secure Code) Transactions only - This field indicates the type of authentication used in the 3D Secure transaction.

Valid values:

• Cardholder certificate not used

• Processed through MasterPass

• Digital Secure Remote Payment transaction

The cardholder currency code is the ISO numeric currency code of the cardholder. This is a required field.

The cardholder ID method indicates how the cardholder was identified.

Valid values:

• 1 = signature obtained on sales slip

• 2 = PIN (debit card transactions)

• 3 = unattended terminal, no PIN pad

• 4 = mail/phone order or ecommerce

• Spaces = not specific

Chip transaction field – Tag 9F34 – this field contains the result of the cardholder verification procedure.

The Carrier Code consists of two alpha characters denoting official carrier designator for each of up to four flight segments.

Carrier Code One:

Positions 72-73 – Two-digit carrier code corresponding to the leg of travel between the Origination and City One.

Carrier Code Two:

Positions 74-75 – Two-digit carrier code corresponding to the leg of travel between City One and City Two.

Carrier Code Three:

Positions 76-77 – Two-digit carrier code corresponding to the leg of travel between City Two and City Three.

Carrier Code Four:

Positions 78-79 – Two-digit carrier code corresponding to the leg of travel between City Three and City Four.

The cash back amount field contains the amount of cash back given to the cardholder at the time of the transaction.

If chip transaction (TCC record), TAG 9F03

Chip transaction field, Visa only – this field contains a value indicating what the condition the transaction occurred in. In certain situations the transaction failed chip validation and falls back to magnetic stripe processing. This field must contain one of the valid values below:

• 0 = not applicable

• 1 = transaction was initiated from a magnetic stripe with a service code beginning with 2 or 6 and the last read at VSDC terminal was a successful chip read or was not a chip transaction.

• 2 = transaction was initiated at a chip capable terminal from a magnetic stripe that contains service code 2 or 6, and the previous transaction initiated by that terminal was an unsuccessful chip read. 

A designator as per IATA Resolution 728 reflecting class of service reserved or requested for up to four legs of travel. To qualify for association incentive rates, the class of service must be present for at least the first leg of travel.

Class of Service Coupon One

Position 188 – One character code corresponding to the class of service for the first leg of travel

Class of Service Coupon Two

Position 189 – One character code corresponding to the class of service for the second leg of travel

Class of Service Coupon Three

Position 190 – One character code corresponding to the class of service for the third leg of travel

Class of Service Coupon Four

Position 191 – One character code corresponding to the class of service for the fourth leg of travel

Reserved for future use.

DCC (dynamic currency conversion) transactions only - conversion rate field contains the exchange rate from the local currency to the cardholder’s currency. This field has no implicit decimal point. The exchange rate must express the value of 1 major unit of the transaction currency in terms of the cardholder currency. If the transaction is not DCC, the field should be zero filled.

This field is populated for Fleet Cards and contains the amount of the discount given based on the coupon presented at the time of purchase.

This field is used for transaction level processing (MPS2 & 3 international platforms) and contains the country code where the transaction originated from. The value in this field is NOT used for batch level processing (MPS1 US and Canadian platform).

The date and time the file was created in the format YYMMDDHHNN where YY is the last two digit of the year, MM is the month, DD is the day of the month, HH is the local hour of the day in twenty-four hour notation, and NN is the minute of the hour.

Airline transaction field – The credit reason indicator is used for an airline transaction and is a code to indicate the reason for a credit to the cardholder.

Valid values:

• A = Passenger transport ancillary purchase cancellation

• B = Airline ticket and passenger transport ancillary purchase cancellation

• C = Airline ticket cancellation

• O = Other

• P = Partial refund of airline ticket

• Space = not used

Total number of credit (refund) records in the file.

Chip transaction field – Tag 9F27 – this field indicates the type of cryptogram and the actions to be performed by the authorisation system.

Chip transaction field – Tag 9C – this field indicates the type of financial transaction.

A three-character code which indicates the currency represented in the transaction. This field may be zeros however, is required to match the authorised response record to qualify for Visa Customer Payment Services (CPS) incentive rates. The Visa authorisation system places this information in field 49.

This field contains up to a 17-alphanumeric-value the client and purchaser can use to identify a transaction. The customer code is determined by the client and should be informative to both the client and the purchaser. It will be used as an identifier that will appear on the credit card billing statement to allow the cardholder or business to track purchases made with the commercial/corporate/business card. This is useful for commercial/corporate/business card activity where more than one employee or department has access to the same card. A business can correctly allocate the expense to the proper department, project, or individual using this value.

A special identifier output as part of a transaction record and included by credit card companies on cardholders’ account statements and/or reconciliation reports. The values for this data element are agreed upon by one of more of the following parties: the cardholder, the cardholder’s travel agency, and the credit card company.

This field contains the customer service phone number for the client. It is an optional field however is required for certain association incentive rates for Card Not Present transactions.

This field contains the cardholder or company VAT registration number. A VAT Registration Number is an alphanumeric identifier consisting of up to 15 characters and is unique to any corporate entity doing business in a European Union country that implements the Value Added Tax system.

CVV2 applicable to Visa transactions only - the CVV2 (Card Verification Value 2) results code is a value returned in the authorisation response indicating the result of CVV2 participation. CVV2 participation indicates the merchant is participating in the Card Verification Value 2 Program which is a program that enables issuers to validate the card.

Valid values:

• M = CVV2 Match – indicates that Visa or the issuer was able to verify the CVV2 value provided by the merchant

• N = CVV2 No Match – indicates that Visa or the issuer was not able to verify the CVV2 value provided by the merchant

• P = Not Processed – indicates that Visa or the issuer was unable to verify the CVV2 value provided by the merchant because their verification system was not functioning or not all the information needed to verify the CVV2 value was included in the request.

• S = CVV2 should be on the card – indicates that Visa or the issuer was not able to perform CVV2 verification, and notifies the merchant that the card should contain a CVV2 value.

• U = Issuer does not participate in CVV2 service – indicates that the issuer is not participating in the CVV2 service. 

Daily rental rate contains the daily rental rate for the vehicle rented.

This field indicates the sequence number for the record. The file should start at 1 and increment by 1 per record.

Contains the number of days the vehicle will be rented.

This field contains information from the point of sale and is primarily used for MasterCard transactions. For All other card brand transactions this field should be space filled.

MasterCard transactions only – DE22 Point of Service Data Code is a series of codes that identify terminal capability, terminal environment and point of interaction security data. It identifies special conditions that are present at the time a transaction occurred at the point of interaction. The information in DE22 must be passed unchanged from auth to clearing. DE22 contains 12 sub fields as described below.

Sub Field One – Terminal Data: Card Data Input Capability

• 0 – Unknown; data not available

• 1 – Manual; no terminal

• 2 – Magnetic stripe reader capability

• 4 – Optical character reader (OCR) capability

• 5 – Integrated circuit card (ICC) capability

• 6 – Key entry-only capability

• A – PAN auto-entry via contactless magnetic stripe

• B – Magnetic stripe reader and key entry capability

• C – Magnetic stripe reader, ICC, and key entry capability

• D – Magnetic stripe reader and ICC capability

• E – ICC and key entry capability

• M – PAN auto-entry via contactless M/Chip and contactless magnetic stripe

• V – Other capability

Sub Field Two – Terminal Data: Cardholder Authentication Capability

• 0 – No electronic authentication capability

• 1 – PIN entry capability

• 2 – Electronic signature analysis capability

• 3 – Software based online mPOS with PIN supported

• 5 – Electronic authentication capability is inoperative

• 6 – Other

• 9 – Unknown; data unavailable

Sub Field Three – Terminal Data: Card Capture Capability

• 0 – No capture capability

• 1 – Card capture capability

• 9 – Unknown, data unavailable

Sub Field Four – Terminal Operating Environment

• 0 – No terminal used

• 1 – On card acceptor premises; attended terminal

• 2 – On card acceptor premises; unattended terminal

• 3 – Off card acceptor premises; attended

• 4 – Off card acceptor premises; unattended

• 5 – On cardholder premises; unattended

• 6 – Off cardholder premises; unattended

• 7 – Private use (Future use)

• 9 – Unknown; data unavailable

Sub Field Five – Cardholder Present Data

• 0 – Cardholder present

• 1 – Cardholder not present (unspecified)

• 2 – Cardholder not present (mail/facsimile transaction)

• 3 – Cardholder not present (phone order or from automated response unit [ARU])

• 4 – Cardholder not present (standing order/recurring transactions)

• 5 – Cardholder not present (electronic order [PC, Internet, mobile phone, or PDA])

• 9 – Unknown, data unavailable

Sub Field Six – Card Present Data

• 0 – Card not present

• 1 – Card present

• 9 – Unknown, data unavailable

Sub Field Seven – Card Data: Input Mode

• 0 – Unspecified; data unavailable

• 1 – Manual input; no terminal

• 2 – Magnetic stripe reader input

• 6 – Key entered input

• A – PAN auto-entry via contactless magnetic stripe

• B – Magnetic stripe reader input; track data captured and passed unaltered

• C – Online Chip

• F – Offline chip

• M – PAN auto-entry via contactless M/Chip

• R – PAN entry via electronic commerce, including remote chip

• S – Electronic Commerce

• T – PAN auto entry via server

Sub Field Eight – Cardholder Authentication Method

• 0 – Not authenticated

• 1 – PIN

• 2 – Electronic signature analysis

• 5 – Manual signature verification

• 6 – Other manual verification (such as a driver’s license number)

• 9 – Unknown; data unavailable

• S – Other systematic verification

Sub Field Nine – Cardholder Authentication Entity

• 0 – Not authenticated

• 1 – ICC – Offline PIN

• 2 – Card acceptance device (CAD)

• 3 – Authorizing agent – Online PIN

• 4 – Merchant/card acceptor – signature

• 5 – Other

• 9 – Unknown; data unavailable

Sub Field Ten – Card Data Output Capability

• 0 – Unknown; data unavailable

• 1 – None

• 2 – Magnetic stripe write

• 3 – ICC

• S – Other

Sub Field Eleven – Terminal Data Output Capability

• 0 – Unknown; data unavailable

• 1 – None

• 2 – Printing capability only

• 3 – Display capability only

• 4 – Printing and display capability

Sub Field Twelve – PIN Capture Capability

• 0 – No PIN capture capability

• 1 – Unknown; data unavailable

• 2 – Reserved

• 3 – Reserved

• 4 – PIN capture capability 4 characters maximum

• 5 – PIN capture capability 5 characters maximum

• 6 – PIN capture capability 6 characters maximum

• 7 – PIN capture capability 7 characters maximum

• 8 – PIN capture capability 8 characters maximum

• 9 – PIN capture capability 9 characters maximum

• A – PIN capture capability 10 characters maximum

• B – PIN capture capability 11 characters maximum

• C – PIN capture capability 12 characters maximum

This field is populated with a value indicating if the extended item amount is a debit or credit. Valid values are D for debit and C for credit.

The debit interchange indicator is used to indicate a special interchange rate was used in the processing of the transaction.

Valid values:

• 0 = Does not participate

• 1 = Pulse

• A = All Star

• B = INLK/PAVD Business

• C = INLK/PAVD Consumer Prepaid

• D = Durbin Qualified

• F = Durbin Qualified (Additional Fraud Review)

• P = NYCE Premier

• R = INLK/PAVD Small Ticket Prepaid

• S = INLK/PAVD Small Ticket

• V = VPP related INLK

• X = INLK/PAVD Commercial Prepaid

• Y = International

This field contains the network identifier for PIN based Debit cards.

Valid values:

• AF = AFFN

• AO = Alaska Option

• CU = Credit Union 24

• EX = Accel

• IL = Interlink

• MR = Maestro

• NT = Nets

• NY = NYCE

• PS = Pulse

• ST = Star

• SZ = Shazam

Total number of debit (sale) records in the file.

This field contains the switch settlement date for PIN based Debit cards in MMDD format.

Visa debt repayment is a limited-acceptance opportunity for qualified merchants. Merchants may accept Visa consumer Debit, Visa commercial Debit, and Visa Prepaid cards (exceptions apply) 1 for debt repayment transactions. There are special acceptance requirements and procedures to identify the permitted debt transaction types. This indicator informs Elavon if the merchant is participating in this program and allows Elavon to add the required data to the clearing transaction sent to Visa

Values:

• Y = Debt Repayment Transaction

• “_” = Not participating

Chip transaction field – Tag 84 – contains the card application identification code for the card application from ISO 7816-5, selected by the terminal.

• Airline transactions should contain the date of departure of first flight.

• Cruise line or tour operator transactions should contain the completion date.

• Format of this field must be YYMMDD where YY denotes the year, MM denotes the month, and DD denotes the day. This field must be numeric and greater than zero.

This field is populated for Visa line item detail information containing the destination country code.

This field is populated for Visa line item detail information containing the destination ZIP code.

Cruise Line transactions only – contains the name of the railway destination station

Chip transaction field –this field contains information indicating the type of the device used at the terminal for contactless transactions and is primarily used for MasterCard transactions. For all other card brand transactions this field should be space filled.

This field contains a value which identifies the entity the transaction occurred in. The field is currently supported by Visa only. The value placed in this field at settlement must match the value from the authorisation. Visa introduced this field to support Visa Checkout and contains a value of VCIND when applicable.

The Directory Server Transaction ID is generated by the Mastercard Directory Server during the authentication transaction and passed back to the merchant with the authentication results.

This field contains the discount amount applied to the item.

Two characters denoting the type of document:

• 05 – Sale (debit)

• 06 – Refund (credit)

Installment transaction field – this field contains the amount a customer put down as a deposit on a transaction.

This field relates to Fleet card transactions and contains the driver’s license number of the person making the purchase.

This field contains the amount of duty taxes. Duty taxes are taxes levied on certain goods, services or transactions.

DCC (dynamic currency conversion) transactions only – This field contains the number of digits in Foreign Exchange Rate Exponent in a DCC transaction otherwise zero fill. This value expresses the implicit decimal point in the conversion rate. For example if the conversion rate equals ‘00000812’ and the conversion exponent equals 6 then the exchange rate equals 00.000812.

Space reserved for future use.

This field provides a place for the client to dynamically change the MCC at a transaction level and is usually populated in instances where a domestic MCC is required for the region vs a card association MCC or if the transaction is for a PSP (Payment Service Provider) in which case this field would contain the MCC for the sub-merchant. The dynamic merchant category code field is used to specify the dynamic or natural MCC and would contain the MCC specific to the transaction.

This field provides a place for the client to dynamically change the merchant city at a transaction level. This field could contain the merchant city, customer service phone number, URL or WEB address depending on the type of transaction. Card not present transactions should populate this field with either a customer service phone number, URL or WEB address. If a customer service phone number is being populated it should be left justified, 3 digits followed by a hyphen then the remaining seven digits and space filled to the right. An example would be 999-9999999ss. The Dynamic Merchant City field would contain the merchant relevant information (either merchant city, customer service phone number, URL or WEB address) for the transaction.

This field provides a place for the client to dynamically change the merchant country code at a transaction level. The dynamic merchant country code field would be populated with the merchant country code applicable for the transaction.

This field provides a place for the client to dynamically change the merchant doing business as (DBA) name at a transaction level. Listed below are a few reasons/purposes for this field:

1. This field could be used for clients which want to use a soft descriptor to identify something specific relating to this transaction that would remind them about the purchase. Such as a city where an ecommerce transaction took place or a particular product line (such as sales, consulting, etc.).

2. This field is also used for Payment Facilitator transactions where sub-merchant information is required.

The dynamic merchant DBA Name field should be populated with the appropriate merchant information for the type of transaction based on the desired/required result.

This field provides a place for the client to dynamically change the merchant email address at a transaction level. The dynamic merchant email address field would contain the merchant email address specifically for the transaction.

This field provides a place for the client to dynamically change the merchant phone number at a transaction level. The dynamic merchant phone number field would contain the merchants’ phone number specifically for the transaction.

This field provides a place for the client to dynamically change the merchant state at a transaction level. The dynamic merchant state name field should contain the merchant state specifically for the transaction.

This field provides a place for the client to dynamically change the merchant street address at a transaction level. The dynamic merchant street address field should contain the merchant street address specifically for the transaction.

This field provides a place for the client to dynamically change the merchant zip code at a transaction level. The dynamic merchant zip code field should contain the merchant street zip code specifically for the transaction. The zip code entered here should also match the appropriate valid zip code for the state entered in the dynamic merchant state field.

This field provides a place for the client to dynamically enter the sub-merchant ID associated with the transaction. The dynamic sub-merchant ID field should contain the sub-merchant ID specifically for the transaction.

This field provides a place for the client to dynamically enter the sub-merchant TAX ID. The dynamic sub-merchant TAX ID field should contain the sub-merchant TAX ID specifically for the transaction.

Electronic Commerce Indicator (ECI) = A VisaNet code that identifies a transaction that is conducted over the Internet or other network using a cardholder access device.

Mail Order Telephone Order (MOTO) = The purchase of goods or services where the cardholder is not present at the point of sale; the purchase is a result of a mail order, telephone order, fax order and so forth.

Valid values:

• 01 = Single Transaction for a mail/telephone order

• 02 = Recurring transaction

• 03 = Installment payment

• 04 = Unknown classification/other mail order

• 05 = Secure E-Commerce transaction

• 06 = Non-authenticated security transactions without complete cardholder authentication

• 07 = Non authenticated security transactions, channel-encrypted

• 08 = Electronic commerce not secure transaction

• 09 = Non authenticated security transaction at a SET capable merchant

• 20 = AMEX only – Payment token data present only

• Blank = not applicable

If the merchant is participating in Verified by Visa (V by V) the following combinations of elements are required:

• When ECI equals 05, then ACI must equal U

• When ECI equals 06, then ACI must equal S

• When ECI equals 07, then ACI must equal W or P

This field will carry the value returned in the Authorization Response. It indicates how the transaction was tokenised so Elavon knows how to detokenise the data. If the transaction is not tokenised via Elavon’s authorisation system, SPACE Fill

The presence of an “E” in this field means the ticket was electronic and no flight coupons were provided to the customer.

This field contains email address to be used for communication. Multiple addresses should be separated using ‘,’

This field contains the month and year (MMYY) after which the credit card account number is no longer valid. If the expiration date is not available, this field may be zero filled.

This field contains the individual item amount that is normally calculated as price multiplied by quantity.

This field indicates if there were extra charges for the transaction.

Valid values:

• 0 or Blank = no extra charges

• 2 = extra mileage or restaurant

• 3 = late return or gift shop

• 4 = one way service fee or mini bar

• 5 = parking violation or telephone

• 6 = other (used for hotel transactions only)

• 7 = laundry (used for hotel transaction only)

Comprised of prime code (service class), followed by the secondary and/or discount code(s) to indicate the class of service and fare level to which the passenger is entitled. Six characters are passed for each of up to four flight segments.

Fare Basis One:

Positions 80 - 85 – Prime code for the first leg of travel belongs in position 80. Discount codes must be placed in the remaining five positions.

Fare Basis Two:

Positions 86 - 91 – Prime code for the second leg of travel belongs in position 86. Discount codes must be placed in the remaining five positions.

Fare Basis Three:

Positions 92 - 97 – Prime code for the third leg of travel belongs in position 92. Discount codes must be placed in the remaining five positions.

Fare Basis Four:

Positions 98 - 103 – Prime code for the last leg of travel belongs in position 98. Discount codes must be placed in the remaining five positions.

This field contains an identification code assigned by Elavon. The identification code can be up to 6 positions in length. If less than six positions are assigned, the remaining positions in this field should be space filled.

This field is allocated by Elavon, always ELAVON with two training spaces.

Contains the date the file is transmission. Format of this field is YYMMDD where YY denotes the year, MM denotes the month, and DD denotes the day.

Undefined reserved space and can be either blank or zero filled.

Installment transaction field – this field is used when an installment payment is being deferred and indicates when the first payment date will occur. The format of this date must be YYMMDD.

This field contains the scheduled date of departure for the specified segment of travel (up to four legs). This field is required for certain association incentive interchange rates. Format of this field must be YYMMDD where YY denotes the year, MM denotes the month, and DD denotes the day. This field must be numeric and greater than zero.

The local flight departure time for up to four legs of travel; as published in the carrier’s current schedule based on the twenty-four hour clock or expressed as “A”, “P”, “N”, “M”, for a.m., p.m., noon, and midnight, respectively. Possible examples include: “0000”,“0715” or “715A”, “1015” or “1015A”, “1200” or “12N”, “1915” or “715P”, “2400” or “12M”. This field will be blank if the corresponding flight number is equal to blank or “OPEN”. This field is required for some association incentive interchange rates.

The flight number applicable to the space reserved or requested for up to four legs of travel. This field may be blank or contain the word “OPEN”. This field is required for some association incentive interchange rates.

Chip transaction field – Tag 9F6E – the form factor indicator defines the type of consumer device used to conduct the transaction. The field is conditional, however if information is passed it must be carried throughout the transaction (auth and settle).

This field supports Visa line item detail and contains the amount for the freight/shipping for the item.

This field contains the quantity (number of gallons) of fuel dispensed and has 4 decimals implied. For example if 10.75 gallons were dispensed this field would be populated with 0000000107500

This field contains a value which indicates the type of fuel (regular, unleaded, diesel, etc.) purchased. Each association has a different value associated with type of purchase. Refer to the association for valid values.

The gift shop purchase field contains charges incurred at the gift shop of a hotel. Optional information passed for commercial card lodging/hotel transactions.

This field is only populated for transactions that are fuel purchase only transaction and will contain the total price for the fuel purchase.

Total HASH value of credit (refund) transactions in the file (sum of all credits).

Total HASH value of debit (sale) transactions in the file (sum of all debits).

Total HASH net value of all transactions in the file (i.e. DEBITS minus CREDITS).

The health club charges field contains charges incurred at the health club of a hotel. Optional information passed for commercial card lodging/hotel transactions.

Reference number provided in DCC Inquiry Response message for Host DCC transactions. Zero-fill if not applicable.

Indicates the date the guest is checking into the hotel. Format must be YYMMDD where YY denotes the year, MM denotes the month, and DD denotes the day.

Indicates the date the guest is checking out of the hotel. Format must be YYMMDD where YY denotes the year, MM denotes the month, and DD denotes the day.

This field contains the customer service telephone number for the hotel and cannot be zero filled.

This field contains the phone number for the physical hotel property and cannot be zero filled.

This field contains an indicator for In-App transactions.

Valid values:

• Y = In-App Ecommerce Transaction

• N = Non In-App transaction

• Space/blank = not an applicable Account

This field contains a value indicating the number of incremental authorisations submitted for this transaction.

Installment transaction field – this field contains the key of the promotion under which the sale was done.

Installment transaction field – this field is used to indicate when an installment payment is being deferred. It contains the number of months the payment is being deferred.

Chip transaction field – this field contains the unique and permanent serial number assigned to the IFD by the manufacture.

Year, month, and day (YYMMDD) denoting the date the invoice is prepared.

The merchant determines the invoice number for reconciliation purposes. Elavon will print whatever information is sent in the invoice number field (up to 14 characters) onto their merchant statement. If only six are available, six should be sent followed by eight spaces.

Airline transactions field – This field contains the ticket number of the associated purchase. (If this purchase has a connection or relationship to another purchase, such as a baggage fee for a passenger transport ticket, this field will contain the ticket document number for the other purchase. If this is a standalone purchase this field must contain the same value as in the Ancillary Ticket document Number field.)

Chip transaction field – Tag 9F10 – this field contains information the issuer wants to pass to the chip. The field is conditional, however if information is passed it must be carried throughout the transaction (auth and settle).

Chip transaction field – Tag 71 – this field contains the results of the Issuer Script Execution, part one. This field is conditional, unless transaction is a reversal in which case this field is then required.

Chip transaction field – Tag 72 – this field contains the results of the Issuer Script Execution, part two. This field is conditional, unless transaction is a reversal in which case this field is then required.

The item commodity code is a code identifying the standard classification code for products and services used to detail where money is spent within a company.

This field contains a description of the individual item purchased.

This field is to support Visa Line Item Detail and would contain the product code for the item purchased.

This field contains the quantity of the item purchased.

This field contains the line item unit of measure. Examples would be EAC for each, PKG for package, FOT for foot, GRO for gross, GLI for gallon, etc.

This field supports Visa line item detail and contains the total amount of all line items for the transaction.

The market specific authorisation data indicator indicates the industry (market) for the transaction.

Valid values:

• A = valid auto rental authorization data received

• B = valid bill payment data received

• H = valid hotel authorization data received

• E = valid electronic commerce transaction aggregation data received

• J = Valid B2B invoice payment received

• M = valid healthcare market specific authorization data received

• N = invalid hotel or auto rental auth data received

• T = valid transit market specific authorization data received

• Blank or space = no market specific authorization data received

This field supports MasterCard Fleet Card detail and contains a four digit code that indicates the card acceptor oil company brand name.

The MasterCard Assigned ID is a value assigned by MasterCard for interchange and transaction data integrity purposes. If the client has been assigned a MasterCard Assigned ID it should be populated in this field for passing along to MasterCard in the outgoing record.

The Associations have assigned specific Merchant Category Codes (MCC) for merchants according to the operating regulations. If this field is not filled by the merchant, Elavon will insert the appropriate Merchant Category Code from its accounting system.

U.S. Bank/Elavon will assign a specific merchant number to your account to identify the source of transactions. This field is entered at the left for a length of ten characters followed by five spaces (left justified).

This field contains the merchant name for the batch.

This field supports Visa Line Item Detail and contains either the merchant VAT registration number or the Single Business Reference Number (SBRN) used for tax purposes.

This field contains the monetary or percentage tax rate on a gallon of fuel included in the pump price.

This field contains a value to indicate whether transaction miscellaneous fuel tax is exempted or not. Y for exempt and N for not exempt.

This field contains the monetary or percentage tax rate on saleable goods (non-fuel).

This field contains a value indicating whether the transaction miscellaneous non fuel tax is exempted or not. This field is only populated for non-fuel fleet card activity. A Y indicates tax exempt and an N indicates not tax exempt.

This field contains the three digit motor fuel product code for the transaction.

This field contains the quantity of motor fuel dispensed.

This field contains the amount for the fuel sale.

This field contains a value indicating the type of service received at the card acceptor site.

Valid values:

• 0 or space indicates undefined

• 1 indicates self service

• 2 indicates full service

• 3 indicates only non-fuel products being purchased

This field contains a value describing the unit of measure for the motor fuel dispensed.

Valid values:

• 1 = Gallons

• 2 = Liters

• 3 = Pounds

• 4 = Kilos

• 5 = Imperial gallons

• Space = not applicable

This field contains the unit price for the motor fuel.

This field is used by Mastercard to differentiate between software and hardware-based mPOS terminals and PIN entry support.

Valid values:

• 0 = Dedicated MPOS Terminal with PCI compliant dongle

• 1 = Off the shelf terminal

The movie charges field contains charges incurred for movie rentals at the hotel. Optional information passed for commercial card lodging/hotel transactions.

VISA only field – Multiple Clearing Sequence Number and Count field (formally known as Document Composition) is used for transactions where one authorisation is obtained and multiple clearing records are submitted. This field indicates the clearing sequence and count for each settled transaction. For example if you had one authorisation and used it for four settlement transactions, in the first settlement transaction you would enter 0104, in the second 0204, in the third 0304 and in the fourth 0404. This indicates to Visa there are four settled transactions for the one authorisation. Airline transactions populate this field in the TAA record and transactions from a Card Not Present environment, non-airline, will populate this field in the TAB record.

If the transaction is an airline transaction, the TAA record is used and a default of 0101 should be used.