gmcif global multi-currency input file (gmcif)

Global Multi-Currency Input File (GMCIF)

Version 2.68

Global Multi-Currency Settlement File (GMCIF)

Version 2.68 Confidential 2

Introduction ........................................................................................................................................... 4

Purpose of Document ..................................................................................................................................... 4

Supporting Documentation............................................................................................................................. 4

Support Services .............................................................................................................................................. 4

File Processing ...................................................................................................................................... 5

File Delivery ..................................................................................................................................................... 5

Processing Cycle .............................................................................................................................................. 5

Multiple Files ................................................................................................................................................... 5

Validation ....................................................................................................................................................... 5

Development Guidelines ...................................................................................................................... 6

Character Set .................................................................................................................................................. 6

File Structure ................................................................................................................................................... 6

File Record Length........................................................................................................................................... 6

Amount and Value Fields ................................................................................................................................ 7

File Format and Status Descriptions ............................................................................................................... 7

Key for Record Tables ..................................................................................................................................... 7

Special Field Requirements ................................................................................................................. 8

SE Number – Contained in Settlement Batch Record (SBR) ............................................................................ 8

SOC Number – Contained in Transaction Currency Header Record (THR) ...................................................... 8

Approval code – Contained in Transaction Detail Record (TDR) ..................................................................... 8

MOTO/ECI and CVV2 and Cash Back Fields .................................................................................................... 8

US and Canadian Transactions ....................................................................................................................... 8

Payment Facilitator ........................................................................................................................................ 8

File Header Record (FHR)..................................................................................................................... 9

Settlement Batch Record (SBR) ........................................................................................................ 10

TXN Header Record (THR).................................................................................................................. 11

TXN Detail Record (TDR) .................................................................................................................... 12

Transaction AUX Record (TAR) ......................................................................................................... 20

Airline AUX Record (AAR) .................................................................................................................. 29

Passenger Transport AUX Record (PTA) ......................................................................................... 32

Diners AUX Record (CRR) .................................................................................................................. 34

Hotel Addendum AUX Record (HAR) ................................................................................................ 34

Extended Data AUX Record (EXD) Private Use ............................................................................... 35

Purchase Card AUX Record (PAR) Private Use ............................................................................... 35

Purchase Card Info AUX Record (PIR) Private Use ......................................................................... 36

Alternative Payment AUX Record (APM) .......................................................................................... 37

TXN Trailer Record (TTR) ................................................................................................................... 38

File Trailer Record (FTR) .................................................................................................................... 39

Diagram of GMCIF File Construction ................................................................................................ 40



Ancillary Fee Codes ............................................................................................................................ 41

Multi-Currency Conversion ................................................................................................................ 42

Revision History .................................................................................................................................. 45

Copyright © 2018 Elavon Merchant Services. All rights reserved.

The information contained in this document is subject to change without notice.

This document contains information protected by copyright.

No part of this document may be photocopied or reproduced in any form without prior written consent from Elavon Merchant Services.

Elavon Financial Services DAC

Registered in Ireland with Companies Registration Office (Reg. No. 418442). Registered Office: Building 8 Cherrywood Business Park, Loughlinstown, Dublin, D18 W319, Ireland.

Registered in England and Wales under the number BR009373. The liability of the member is limited.

Elavon Financial Services DAC, trading as Elavon Merchant Services, is regulated by the Central Bank of Ireland. United Kingdom branch is authorised by Central Bank of Ireland and the Prudential Regulation Authority and subject to limited regulation by the Financial Conduct Authority and Prudential Regulation Authority. Details about the extent of our authorisation and regulation by the Prudential Regulation Authority, and regulation by the Financial Conduct Authority are available from us on request.



Introduction

Purpose of Document

The purpose of this document is to provide detailed information to enable Merchants, 3rd party processors and Suppliers of EFTPOS systems with the necessary information to produce GMCIF files of multi-currency transactions for acquisition by Elavon Merchant Services.

Supporting Documentation

Global Multi Currency Authorisation Specification (KAAI): This document provides information on the authorisation formats supported by Elavon and details format layouts and field descriptions for multi-currency authorisation requests and responses.

Global Multi-Currency Draft Capture Specification (GICC): This document provides information on the field layout and field descriptions for the ELAVON draft capture product. This allows the authorisation and settlement of a transaction simultaneously by the ELAVON system.

Support Services

Elavon provides full technical and implementation consultancy to merchants and their software providers, who wish to use the acquisition and processing services of the Europe Card Acceptance

Global Multi-Currency service. If you have any questions or queries concerning this document and its contents you should contact your Elavon Implementation Manager.



File Processing

File Delivery

The Elavon card acceptance processing systems are available to accept merchant file submissions 7 days a week, 24 hours per day.

Processing Cycle

The Elavon processing cycle commences at 22:15 GMT and runs every day. All files received by 22:15 GMT will be included in that days processing cycle. All files received after 22:15 GMT will be included in the next day’s processing cycle.

Multiple Files

The Elavon processing systems support the ability for multiple files to be delivered per processing day and depending on the time of delivery will include these files in the current processing cycle.

Validation

When a file is received by the Elavon processing system an initial file validation is carried out. This process will include duplicate file checking on approximately the first and last 40 bytes of the file. As well as duplicate file validation there is also validation carried out on a number of fields within the file.



Development Guidelines

Character Set

The GMCIF file should be constructed and delivered to the Elavon processing systems using the ASCII character set (and only CAPITAL LETTERS have to be used in alphanumeric fields).

File Structure

The GMCIF has been designed to be as flexible as possible; therefore there are many different ways of constructing the file for processing. The following table shows a typical GMCIF record structure sequence.

Record Name Abbreviation Comments

File Header Record FHR One per file.

Settlement Batch Record SBR

Transaction Currency Header Record

THR

Transaction Detail Record TDR One per transaction.

Auxiliary Record TAR One per TDR – T&E, Cashback Service and DCC Service.

Airline Auxiliary Record AAR One per TDR where required.

Auxiliary Record CRR One per TDR where required – Diners text fields and/or Diners Airline Invoice Number.

Auxiliary Record HAR One per TDR where required – additional hotel data.

Auxiliary Record EXD Max. 9999 per TDR where required.

Auxiliary Record PAR One per TDR where required.

Auxiliary Record PIR One, max ten per PAR where PAR is present.

Auxiliary Record APM One per TDR where required.

Transaction Currency Trailer Record

TTR One per Transaction Currency Header Record (THR).

File Trailer Record FTR One per file.

At the end of the document there is a diagram of a typical file structure

File Record Length

The GMCIF file supports a fixed record length of 450 bytes per record, terminated by the standard ASCII end of line and carriage return characters (hexadecimal characters codes 0D 0A).

Optional or Conditional Fields must be padded with spaces (if alphanumeric) or zeros (if numeric) where not populated (unless otherwise stated).

Since the file format is expected in ASCII characters, every line/record of the file has to be delimited from the other by the ASCII characters “Carriage return” (CR) and “Line feed” (LF). Hexadecimal representation is 0D0A.



Amount and Value Fields

It should be noted that the GMCIF format when processed by Elavon will set all amount and value fields contained in the file to 2 decimal places (unless otherwise stated), therefore any currencies that support more than 2 decimal places should be rounded.

NOTE: All the amount values should be presented as absolute values, without “+” or “-“signs.

Examples:

USD $1,170.45 should be represented as 117045 GBP 27 should be represented as 2700 JPY 1000 should be represented as 100000

File Format and Status Descriptions

Contained within each record there is a format and status indicator for each field, this indicates the validation criteria for the file as well as the format of each field, it is important that the status for each field is used as validation is carried out on these fields and will therefore reduce the chance of file rejections. The following key displays the format of the status and format fields.

Format Description Comments

N Numeric Field Right Justified, Leading Zeros.

A Alphanumeric Field Left Justified, Trailing Spaces.

M Mandatory Field Must be populated, validated by Elavon.

O Optional Field Optional field, not validated by Elavon.

C Conditional Field Must be populated by some merchants/processors.

Cx Conditional Field Must be populated in conjunction with other conditional fields.

Key for Record Tables

Column Heading Description

L Length

F Format (Numeric / Alphanumeric)

S Status (Mandatory / Optional / Conditional)



Special Field Requirements The GMCIF file has fields which contain information critical to the successful processing of the file. Detailed below is a list of these fields with a full explanation of their purpose and data requirements.

SE Number – Contained in Settlement Batch Record (SBR)

Service Establishment Number (Merchant ID Number). Assigned to a merchant by Elavon. Identifies the merchant’s profile and settlement currency requirement. Please note that for each settlement currency required there will be a unique SE Number assigned.

SOC Number – Contained in Transaction Currency Header Record (THR)

This is the Summary of Charge number which is created by the processor/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 produce reporting and reconciliation data.

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

- 3 digit Julian date of file creation + the last digit of the current year - 4 digit sequential number, Incremented by 1 per THR record, Example for January 15, 2009 = 01590001 Example for October 17, 2011 = 29010001

Approval code – Contained in Transaction Detail Record (TDR)

If the transaction was online approved, the authorisation code must be stored here. If the transaction is manually entered, without an authorisation requested, it must be space-filled. It is prohibited to store an approval code generated by the merchant. Only the authorization code received from the acquiring institution is allowed to be placed in this field.

MOTO/ECI and CVV2 and Cash Back Fields

These fields are available after special agreements.

US and Canadian Transactions

Each State or Province requires its own batch. The State or Province Code must be consistent for all records in a batch. For example:

Record Contents Record Cont. Contents Cont.

SBR SBR

THR THR

TDR with State = NY TDR with Province = QU

TAR TAR

AAR AAR

TDR with State = NY TDR with Province = QU

TAR TAR

AAR AAR

… …

TTR TTR

Payment Facilitator

A settlement batch must not combine Payment Facilitator and non-Payment Facilitator transactions. If the Host identifies an issue within a record in a Payment Facilitator batch the entire batch will be rejected.



File Header Record (FHR)

Field Name L Position F S Remarks

Record type 3 1-3 A M Always FHR

Data record sequence number

9 4-12 N M Start at 1 and increment by 1 per record

File creation date 8 13-20 N M YYYYMMDD

File transmission date

8 21-28 N M YYYYMMDD

File Receiver 8 29-36 A M Allocated by Elavon Always ‘ELAVON’ with two trailing spaces

Processor ID 9 37-45 A M

Processor Identifier allocated by Elavon.

Value Description

GMCA Test Environment

GMCP Production Environment

DCIP/DCSP Direct settlement with Diners.

Processor Name 20 46-65 A M Name of the merchant’s processor i.e. file submitter.

Building number 20 66-85 A O Building number of processing centre

Street name 20 86-105 A O Street name of processing centre

City 20 106-125 A O City or Town name of processing centre

Country 20 126-145 A O Country of processing centre, Country Name

ZIP Code 9 146-154 A O ZIP or Postal code of processing centre

Phone number 20 155-174 A O Contact telephone number of processing centre

FAX number 20 175-194 A O Facsimile telephone number of processing centre

SITA Telex number 10 195-204 A O SITA Telex number (AIRLINE USE ONLY)

E-Mail Address 160 205-364 A C For batch authorisation use. Multiple addresses should be separated using ‘,’.

File number 4 365-368 N O Unique file number for each submission file in the range 0001 to 9999

Filler 82 369-450 A M Space padded



Settlement Batch Record (SBR)


Record type 3 1-3 A M Always SBR


9 4-12 N M Increment by 1 per data record

SE Number 17 13-29 N M Service Establishment Number / Merchant ID Number (allocated by ELAVON)

Settlement currency

3 30-32 N M Merchant settlement currency code (ISO 4217) In a Multi-Currency Conversion (MCC) batch this value represents the chosen settlement currency.

Merchant name 20 33-52 A O Merchant name

Building number 20 53-72 A O Building number of processing centre

Street name 20 73-92 A O Street name of processing centre

City 20 93-112 A O City or Town name of processing centre

Country 20 113-132 A O Country of processing centre, Country Name

Zip code 9 133-141 A O ZIP or Postal code of processing centre

Phone number 20 142-161 A O Contact telephone number of processing centre

Fax number 20 162-181 A O Facsimile telephone number of processing centre

SITA Telex number 10 182-191 A O SITA Telex number (AIRLINE USE ONLY)

Merchant Group Identifier

2 192-193 N O Only valid if a partner is processing in Spain and other countries. Value will be allocated and provided by Elavon. Space-fill if not used.

Payment Facilitator Dynamic Merchant Indicator

1 194 A C

Payment Facilitator Processing Indicator

Value Description

Y Transaction processed as Payment Facilitator.

Space-Fill Not Applicable

If Y, Payment Facilitator Data must be submitted in Transaction AUX Record (TAR). PF values will echo authorisation values.

MasterPass - Digital Wallet Merchant Enabled Flag

1 195 A C

Flag to indicate that the digital wallet is enabled on merchant side. Must be sent regardless of whether the transaction had been processed using digital wallet.

Value Description

Y MasterPass Enabled



Note: We can only accept a maximum 999 Settlement Batch Records per file.



TXN Header Record (THR)


Record type 3 1-3 A M Always THR



SOC Number 8 13-20 N M The Summary of Charge number is a batch identifier created by the merchant/processor.

Currency of TDR records

3 21-23 N M Transaction Currency code for TDR records contained in the batch (ISO 4217)

SOC Merchant Reference

30 24-53 A O Merchant Summary Of Charge Reference. This value is passed to the Merchant Processing System.




TXN Detail Record (TDR) Field Name L Position F S Remarks

Record Type 3 1-3 A M Always TDR

Data Record Sequence Number


Card Number 19 13-31 A M

Transaction Type Value

ZAPP ZAPP BIN 888 + Consumer ID Elavon

All Other Transactions

Card account number (PAN) (*4)

Expiry Date 4 32-35 N M MMYY (Field 4 of Track 2 or Tag 5F24 without DD) (*5) ZAPP: populate as 0000

Transaction Amount

13 36-48 N M

Two implied decimal positions. Right justified and zero-padded.

27.00 EUR is represented as 0000000002700 100 JPY is represented as 0000000010000 100.000 KWD is represented as 0000000010000

Transaction Type

2 49-50 N M

Value Description

00 Purchase

01 Refund

04 Recurring Transaction – valid for Visa and MasterCard

05 Instalment Transaction – valid for Visa and MasterCard

06 Unscheduled Credential on File Transaction – valid for Visa only

07 Storing Credential on File – valid for Visa and MasterCard




Transaction Source

2 51-52 N M

Value Description

00 Swiped / Verified by signature

01 Keyed / Verified by signature

02 Keyed / Card Not Present MOTO/EC Indicator Mandatory

03 PAN Auto Entry via Server in contactless debt repayment transactions

04 Swiped Unattended / No verification

05 Swiped / PIN verified

06 Chip / PIN verified

07 Chip / Verified by signature

08 Swiped / PIN verified, Chip fallback

09 Swiped / Verified by signature, Chip fallback

10 Credential on File

11-14 Reserved For Future Use

15 Swiped / PIN verified, unattended

16 Chip / PIN verified, unattended

17 Chip / No verification, unattended

18 Swiped / PIN verified, unattended fallback

19 Swiped / No verification, unattended fallback

20 CTLS Mag Stripe / No verification

21 CTLS Mag Stripe Unattended / No verification

22 CTLS Mag Swipe / PIN verified

23 CTLS Mag Swipe Unattended / PIN verified

24 CTLS Chip / No verification

25 CTLS Chip Unattended / No verification

26 CTLS Chip / PIN verified

27 CTLS Chip Unattended / PIN verified

28 Alternative Payment Method (APM) e.g. Zapp

30 In-App Ecommerce - MOTO/ECI Indicator and AAV Collection Indicator for M/C are mandatory

Authorisation Code

10 53-62 A M If no authorisation code is obtained then field must be padded with spaces

Authorisation Source

2 63-64 N M

Value Description

00 Offline by terminal (no online auth)

01 Online to acquirer

02 Voice (referral)

03 Auth by Alternative Payment Method

10 EMV offline by terminal, chip approved

11 EMV online to acquirer

12 EMV voice (referral)




Transaction Currency

3 65-67 N M Transaction currency code (NUMERIC ISO 4217) (in accordance with the THR Currency settings)

Merchant Country Code

3 68-70 N M Country code where the Merchant is located (NUMERIC ISO 3166)

Transaction Date

8 71-78 N M YYYYMMDD Note: must be the same as the authorisation date.

Transaction Time

6 79-84 N M HHMMSS or file creation time

Transaction Reference

30 85-114 A O

Merchant transaction reference field (feeds to ROC text) / ROC-Text-1 (Diners Customer Reference 1)

ZAPP Transactions: Settlement Retrieval ID (sale transactions) RefundTRID (refund transactions)

State/Province Code (Merchant)

2 115-116 A C

Mandatory where Merchant Country code is US/CA. If Country-Code = 840 or 124 then ‘TAR’ is mandatory. Important: The State or Province code should be consistent for all transactions in the batch.

Application Cryptogram

16 117-132 A C Cryptogram returned from the ICC in response of the GENERATE AC command (EMV TAG 9F26)

Cryptogram Information Data

2 133-134 A C Indicates the type of cryptogram and the actions to be performed by the authorization system (EMV TAG 9F27)

Issuer Application Data (IAD)

64 135-198 A C Contains proprietary application data for transmission to the issuer in all transaction messages. (EMV TAG 9F10)

Unpredictable Number

8 199-206 A C Value provided by the terminal to provide variability and uniqueness to the generation of the application (EMV TAG 9F37)

Application Transaction counter (ATC)

4 207-210 A C

Counter maintained by the application in the ICC, indicates the number of transactions processed by the card application (EMV TAG 9F36)

Terminal Verification Results

10 211-220 A C Result of the different verification operations performed by the authorization system (EMV TAG 95)

Transaction Date

6 221-226 A C The local date that the transaction was authorized (EMV TAG 9A)

Transaction Type

2 227-228 A C Indicates the type of financial transaction, representing the first two digits of ISO 8583:1987 Processing code (EMV TAG 9C)

Transaction Amount

12 229-240 A C Authorization amount of the transaction as provided by the terminal to the card (EMV TAG 9F02)

Transaction Currency Code

4 241-244 A C Indicates the currency code of the transaction according to ISO 4217 (EMV TAG 5F2A)




Application Interchange Profile

4 245-248 A C Indicates microcircuit application-specific functions (information supplied by the card) (EMV TAG 82)

Terminal Country Code

4 249-252 A C Indicates the country of the terminal, represented according to ISO 3166 (EMV TAG 9F1A)

Amount, Other 12 253-264 A C Secondary Amount of the transaction (e.g. Cash Amount) as provided by the terminal to the card (EMV TAG 9F03)

Terminal Capabilities

6 265-270 A C

Indicates the card data input, CVM, and security capabilities of the terminal. Alphabetic characters must be presented in upper case (EMV TAG 9F33)

CVM results 6 271-276 A C Result of Cardholder Verification Procedure (EMV TAG 9F34)

Terminal Type 2 277-278 A C Indicates the environment of the terminal, its communications capability, and its operational control (EMV TAG 9F35)

Interface Device (IFD) Serial No

16 279-294 A C Unique and permanent serial number assigned to the IFD by the manufacturer (EMV TAG 9F1E)

Transaction category Code

2 295-269 A C Describes environment of the TX. Derived from MCC (EMV TAG 9F53)

Dedicated File (DF) Name

32 297-328 A C Identifies the name of the DF as described in ISO/IEC 7816-4. Mandatory for Diners transactions. (EMV TAG 84)

Terminal application version no.

4 329-332 A C EMV Version of the Terminal SW (EMV TAG 9F09)

Transaction Sequence Counter

8 333-340 A C Counter maintained by the terminal that is incremented by one for each transaction (EMV TAG 9F41)

Card Sequence Number

3 341-343 A C A number distinguishing between separate cards with the same PAN Otherwise space-fill (EMV TAG 5F34)

Issuer Script Results part I

24 344-367 A C Results of the Issuer Script Execution

Issuer Script Results part II

18 368-385 A C Results of the Issuer Script Execution

System Trace Audit Number

6 386-391 A C

Mandatory for Discover Processing in the US/CAN and Union Pay in all countries.

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.

If not present = Space-fill




Retrieval Reference Number

12 392-403 A O If not present = Space-fill

Form Factor Indicator

8 404-411 A C

VISA payWave / Diners Contactless: the Form Factor Indicator is transmitted from the card to the terminal in the response of GET PROCESSING OPTIONS command in order to be forwarded to the issuer. Mandatory for Visa and Diners.

MasterCard Contactless: Tag 9F6E is defined to hold Third Party Data.

(EMV TAG 9F6E)

Reserved For Future Use

14 412-425 A O Space-fill

MOTO/ Ecommerce Authentication Indicator

1 426-426 A C

If Transaction Source Field equals 02 (Card Not Present) or 30 (In-App Ecommerce)

Value Description

1 Mail Order / Telephone Order

5 Full Ecommerce Cardholder fully authenticated using 3D Secure issuer authentication.

6 Attempted Ecommerce Cardholder cannot or does not participate in 3D Secure.

7 SSL or Channel Encrypted Used to transmit Transaction Data (non-secure).

Space-Fill Not applicable

Cardholder Verification Value (CVV2)

1 427 A C

Required if Transaction Source Field = 02 (Keyed).

Value Description

M Match

N No Match

U Issuer Does Not Participate

P Unable to Verify

S Unable to Perform Verification


American Express Values

Value Description

Y Match

N No Match

U Unchecked





AVS Result 1 428 A O

Address Verification Service Result Code.

When a credit card company’s Address Verification Service (AVS) is utilized, this field will contain the code used by the credit card company to respond to the address verification request. This field may be space filled if a value is not transferred from the authorization response record. Returned in Authorisation Response Message as a result of an AVS Request

Dynamic CVV2 Result Code

1 429 A O Reserved for future use

Check-In Date 6 430-435 N O

YYMMDD Cruises Line: Check-in Date Car Rental: Check-in Date / returns Tour-Operator / Travel-Agent: Check-in Date Hotel: pls. use the HAR-Record Otherwise Space-fill

Check-Out Date 6 436-441 N O

YYMMDD Cruises Line: Check-out Date / returns Car Rental: Check-out Date Tour-Operator / Travel-Agent: Check-out Date Hotel: pls. use the HAR-Record Otherwise Space-fill

Mobile POS (MPOS) Indicator

1 442 A C

Indicating that the Point of Sale Device is e.g. a Mobile or a Tablet Computer.

Value Description

M Mobile device has been used as Point of Sale

Space-fill Not applicable

Dual Brand Override Indicator

2 443-444 A C

Field denotes card brand selected by the customer at the Point of Interaction. Only applies to dual branded cards. Only currently supported for Union Pay.

Only populate if a dual brand override is required. Otherwise space-fill.

Value Description

UP Union Pay





Spend Qualified Indicator

1 445 A O

Optional data field is used in conjunction with certain card products that have minimum annual spending limits, and is populated by Visa. Indicates whether an account is spend-qualified, based on the point-of-sale spend history of the account and the defined product-level spend requirement for country of issuance. It is forwarded to participating endpoints in authorisation and full financial messages.

Value Description

N Spend qualification threshold not met

Q Spend qualification threshold met

Space-fill Spend processing does not apply

Unattended Acceptance Terminal Indicator

1 446 N O

Indicates type of unattended terminal. Also known as Card Activated Terminal (CAT) Indicator.

Value Description

1 Automated dispensing machine with PIN, online authorised

2 Self-Service terminal

3 Limited amount terminal without PIN (No CVM), offline

POS Terminal Capability

1 447 N M

Indicates terminal card entry capabilities.

Value Description

0 Unknown

1 No Terminal Used

2 Magnetic Stripe Reader

3 ICC incl. Magnetic Stripe Reader and Key Entry

7 Contactless incl. ICC, Magnetic Stripe Reader and Key Entry

8 Contactless Only

9 Key Entry Only

Debt Repayment Indicator

1 448 A M

Indicates Debt Repayment Transactions.

Value Description

Y Debt Repayment Transaction

Space-Filled Not Applicable

Reserved for Future Use

2 449-450 A M Space-filled



Note: We can only accept a maximum of 9,999 Transaction Detail Records per Settlement Batch Record.

Fields from position 117 to 385 and 404 to 425 in the TDR relate to EMV transactions. As such, these should only be populated where appropriate. They are to be filled if the Transaction Source Field (position 51-52) is equal to one of the following values 06, 07, 16, 17, 24, 25, 26, 27.

If an EMV field is not present please space-fill if the field is alphanumeric or zero-fill if the field is numeric.



Transaction AUX Record (TAR)


Record Type 3 1-3 A M Always TAR



Product ID 2 13-14 A C

Only available in the VISA US region from the authorisation message. Otherwise space-fill.

Must be present in conjunction with Transaction Identifier and Validation Code Fields.

Reference: Visa Transaction Identifier DE 62.23 (Card Level Result)

Transaction Identifier

15 15-29 A C1

American Express: Field contains the Amex Transaction Identifier provided in the authorisation response message.

Visa: Field contains the Visa Transaction Identifier provided in the authorisation response message. Must be present in conjunction with the Validation Code and Authorisation Characteristics Indicator fields.

Please note: for tokenised Verified by Visa transactions this field will carry the TAVV (Token Authentication Verification Value).

Space-fill if not applicable.

Reference: Visa Transaction Identifier DE 62.2

Validation Code 4 30-33 A C1

Visa: information is be provided to the merchant as part of the authorisation message. Field may include a code to determine the accuracy of the authorisation date contained in the clearing record. Otherwise space-fill.


Authorisation Characteristics Indicator

1 34 A C1

Field is required to qualify transactions for Visa Custom Payment Services rates. Otherwise space-fill.


BankNet Reference Date

4 35-38 N C 2

For MasterCard transactions: MMDD

Otherwise space-fill.

Must be present in conjunction with the Financial Network Code and BankNet Reference fields.

Reference: MasterCard Financial Network Data DE15




Financial Network Code

3 39-41 A C2

For MasterCard transactions:


Reference: MasterCard Financial Network Data DE 63.1

BankNet Reference

8 42-49 A C2

For MasterCard transactions. Last two digits are space filled.


Reference: MasterCard Financial Network Data DE 63.2

Condition Code 4 50-53 A C Always space-filled

Cashback Amount

13 54-66 N O Not higher than the transaction-amount in the TDR. Same currency as in the TDR.

Cardholder Amount (DCC)

13 67-79 N C3

Dynamic Currency Conversion (DCC) transactions only.

Transaction Amount in Cardholder Currency.

Zero-fill if not applicable.

Must be in major currency unit with two implicit decimal places e.g.

1 Euro = 0000000000100 1 Cent = 0000000000010

Right justified, leading zeroes.

Must be present in conjunction with the Cardholder Currency Code, Conversion Rate and Conversion Exponent fields.

Cardholder Currency Code (DCC)

3 80-82 N C3


ISO Numeric Currency Code of Cardholder. Zero-fill if not applicable.

Conversion Rate (DCC)

8 83-90 N C3


Foreign Exchange Rate.


This field has no implicit decimal point e.g.

0.812 = 00000812

The exchange rate must express the value of 1 major unit of the transaction (and merchant's settlement) currency in terms of the cardholder currency, i.e. multiply the Transaction Amount by the Exchange Rate to get the Cardholder Amount.




Conversion Exponent (DCC)

1 91 N C3


Number of digits in Foreign Exchange Rate Exponent. Zero fill if not applicable.

This value expresses the implicit decimal point in the Conversion Rate e.g.

Conversion Rate = 00000812

Conversion Exponent = '6' Exchange rate = 00.000812

Payment Facilitator Dynamic Merchant DBA Name

25 92-116 A C

DBA name for the Dynamic Merchant of the transaction (if Payment Facilitator Processing).

Space filled for non-Dynamic Merchant Information submitters.

Payment Facilitator Dynamic Merchant City

13 117-129 A C

DBA City for the Dynamic Merchant of the transaction (if Payment Facilitator Processing).


Payment Facilitator Dynamic Merchant Street Address

25 130-154 A C

DBA Street address of the Dynamic Merchant of the transaction (if Payment Facilitator Processing).


Payment Facilitator Dynamic Merchant ZIP Code

9 155-163 A C

DBA ZIP code of the Dynamic Merchant of the transaction (if Payment Facilitator Processing).


Payment Facilitator Dynamic Merchant State/Province Code

2 164-165 A C

DBA State/Province Code of the Dynamic Merchant of the transaction (if Payment Facilitator Processing).

Space filled for non-Dynamic Merchant Information submitters

Payment Facilitator Dynamic Merchant Country Code

3 166-168 A C

DBA Country code of the Dynamic Merchant of the transaction (if Payment Facilitator Processing). Numeric ISO 3166





Payment Facilitator Dynamic Merchant Sub Merchant ID

14 169-182 A C

Sub Merchant ID allocated by the Payment Facilitator for the Dynamic Merchant of the transaction (if Payment Facilitator Processing).


Track Data Condition Code

2 183-184 N C

Only valid and conditional for Discover Processing in the US/CAN.

This field is required if the Card Transaction receives a positive Authorization Response. This field is required for association incentive interchange rates. Space-fill if not present.

Please see below Note *1

Network Reference Identification Number (NRID)

15 185-199 A C

Only valid and mandatory for Discover Processing in the US/CAN.

Unique ID assigned by Discover at the time of the Authorization Response. It is not repeated for a period of one (1) year and follows the life of the Card Transaction.

Space-fill If not present.

Card Scheme Data Date and Time

10 200-209 A C

Only valid for Union Pay. Value received from Union Pay in the authorization Response.

Format: MMDDHHMMSS


Card Scheme Data Settlement Date

3 210-212 A C

Only valid for Union Pay. Value received from Union Pay in the authorization Response.

Format: Julian Day


Digital Wallet Data

5 213-217 A C Digital Wallet Data provided in authorizations

Please see Note *2 – Description table




Accountholder Authentication Value (AAV) Collection Indicator

1 218 N C

MasterPass authentication indicator. Formerly called the UCAF Collection Indicator.

Value Description

0 MasterPass – Consumer Authentication not supported

1 MasterPass – Merchant only / Authentication attempt

2 MasterPass – Full Authentication

3 MasterPass – Maestro Basic Checkout

5 MasterPass – Risk Based Decision with Issuer. Not currently supported.

6 MasterPass – Merchant used own Risk Based Decision. Not currently supported.

MasterCard Assigned ID

6 219-224 A C

MasterPass only: This field contains the MasterCard assigned merchant ID. The value should be provided if the AAV Collection Indicator has a value of 3.

Payment Facilitator Dynamic Merchant MCC Code

4 225-228 N C

MCC Code for the Dynamic Merchant of the transaction (if Payment Facilitator Processing)


Payment Facilitator Dynamic Merchant Phone Number

20 229-248 A C

Phone Number for the Dynamic Merchant of the transaction (if Payment Facilitator Processing). Amex Only.


Payment Facilitator Dynamic Merchant Email Address

40 249-288 A C

Email Address for the Dynamic Merchant of the transaction (if Payment Facilitator Processing). Amex Only.


Payment Facilitator Dynamic Merchant Tax ID

14 289-302 N C

Tax ID for the Dynamic Merchant of the transaction (if Payment Facilitator Processing). Amex Only.





Unique Transaction Response Reference Number

11 303-313 A C

Contains the Elavon generated Unique Transaction Response Reference Number supplied during authorisation via the Elavon ISO Protocol (EISOP) format.

This value is not available via other authorisation protocols.

Space-fill if not applicable.

DCC Reference Number

14 314-327 N C

Reference number provided in DCC Enquiry Response message for Host DCC transactions.


Transit Transaction Type Indicator

2 328-329 N C

Transit Data provided as part of a Transit Transaction.

Value Description

01 Pre-Funded

02 Real-Time Authorised

03 Post-Authorised Aggregated

04 Authorised Aggregated Split Clearing

05 Other

06 Post-Authorised Aggregated Maestro

07 Debt Recovery




Transportation Mode Indicator

2 330-331 N C

Transit Data provided as part of a Transit Transaction.

Value Description

00 Unknown

01 Urban Bus

02 Interurban Bus

03 Light Train Mass Transit

04 Train

05 Commuter Train

06 Waterborne Vehicle

07 Toll

08 Parking

09 Taxi

10 High-Speed Train

11 Rural Bus

12 Express Commuter Train

13 Para Transit

14 Self-Drive Vehicle

15 Coach

16 Locomotive

17 Powered Motor Vehicle

18 Trailer

19 Regional Train

20 InterCity

21 Funicular Train

22 Cable Car

Transaction Integrity Class (TIC)

2 332-333 A C

Required for MasterCard transactions in the US Region Only.

Contains a value from the authorisation response message that indicates fundamental safety and security of a transaction. Includes an assessment of validity of the card and cardholder.

Value must be passed unaltered from authorisation to settlement.

Mandatory for incentive interchange.

Payment Account Reference (PAR) Number

35 334-368 AN C

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




3D Secure Version Number

1 369 N C

Indicates if the transaction has been processed under 3D Secure Version 1 or Version 2 rules. Mandatory for all 3D Secure transactions.

Value Description

1 3D Secure Version 1

2 3D Secure Version 2

Directory Server (DS) Server Transaction ID

36 370-405 AN C

Carries the Directory Server (DS) Transaction ID generated during 3D Secure Version 2 authentication. Must be present for all MasterCard 3D Secure Version 2 transactions.

Accountholder Authentication Value (AAV)

32 406-437 AN C Carries the MasterCard SecureCode AAV. Formerly called the Universal Cardholder Authentication Field (UCAF).

PIN Capability 1 438 N C

Indicates PIN entry capability.

Value Description

1 PIN supported

3 Software based MPOS with PIN supported

Mobile POS (MPOS) Acceptance Device Indicator

1 439 N C

Indicates if an MPOS device is Hardware or Software Based.

Value Description

0 Hardware Based MPOS – dedicated MPOS terminal with dongle (with or without keypad)

1 Software Based MPOS – off the shelf mobile device

Filler 11

440-450 A M Space-fill



*1 Track Data condition Code / Discover US/CAN only

Field Position 1

This position is the Track 1 Data Indicator.

Position Value Description

0 = No Track 1 data present

1 = Track 1 data present with CVV not provided

2 = Track 1 data present with non-zero and non-blank CVV

3 = Track 1 data present with CVV set to all zeros

4 = Track 1 data present with CVV containing some or all blanks

5 = Track 1 data present but CVV location not disclosed by Issuer

Field Position 2

This position is the Track 2 Data Indicator.

Position Value Description

0 = No Track 2 data present

1 = Track 2 data present with CVV not provided

2 = Track 2 data present with non-zero and non-blank CVV

3 = Track 2 data present with CVV set to all zeros

4 = Track 2 data present with CVV containing some or all blanks

5 = Track 2 data present but CVV location not disclosed by Issuer

Note: The value for this field may be found in positions 1-2 of the Transaction Qualifier (Field 124) in the Authorization Response

*2 Digital Wallet description table

Description Field Length

Digital Wallet Type Visa Checkout = V MasterPass = M

1 AN

Digital Wallet Data

Visa Checkout Data

Position 1 – 2 Additional Authorisation Method

Position 3 - 4 Additional Authorisation Reason Code

MasterCard MasterPass Data

Position 1 – 3 Wallet Identifier

Values are: 101 (MasterPass Remote Ecommerce) 102 (MasterPass Remote NFC)

Position 4 Spaces

4 AN



Airline AUX Record (AAR)


Record Type 3 1-3 A M Always AAR



Ticket Number

11 13-23 A M Airline ticket number (left justified with trailing spaces)

Filler 12 24-35 N M Zero-fill

Airline Code 3 36-38 N M Numeric airline code (IATA) e.g. ‘220’ for Lufthansa)

Filler 2 39-40 N M Zero-fill

Agent Code 8 41-48 N M Agency code (IATA)

Agent Name 26 49-74 A M Agency name

Restricted Ticket

1 75 N M

Value Description

0 No Restriction

1 Restricted (Non-Refundable)

Passenger Name

29 76-104 A M Passenger name

Originating Airport

3 105-107 A M Airport code (IATA)

Reservation System

4 108-111 A O RESERVED (space-fill)

Segment 1 3 112-114 A M Carrier code (IATA)

Class 3 115-117 A M Class of service

Stop-Over Code

1 118 N M

Value Description

0 Allowed

1 Not Allowed

Leg Departure Date

8 119-126 N M MMDDYYYY

Destination 3 127-129 A M Airport code (IATA)

Fare Basis 6 130-135 A O Fare basis code

Segment 2 3 136-138 A C Carrier code (IATA)

Class 3 139-141 A C Class of service

Stop-Over 1 142-142 N C

Value Description

0 Allowed

1 Not Allowed

Leg Departure Date

8 143-150 N C MMDDYYYY

Destination 3 151-153 A C Airport code (IATA)







Stop-Over 1 166 N

Value Description

0 Allowed

1 Not Allowed

Leg Departure Date






Stop-Over 1 190 N C

Value Description

0 Allowed

1 Not Allowed

Leg Departure Date




Old Segments 192 208-399 A O RESERVED (Space pad)

Customer Code

20 400-419 A O Airline Customer Code

Flight Number 6 420-425 A O Flights number of 1st segment

Credit Reason Indicator

1 426 A O

Only valid for Visa. This field will contain either a space or a code to indicate the reason for a credit to the cardholder.

Value Description

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





Ticket Change Indicator

1 427 A C

Only valid for Visa. This field will contain either a space or a code to indicate why a ticket was changed.

Value Description

C Change to existing ticket

N New ticket


Reserved 13 428-440 A M Space padded




Passenger Transport AUX Record (PTA)


Record Type 3 1-3 A M Always PTA



Ancillary Ticket Document Number

14 13-26 A C

This field must contain the form number assigned by the carrier for the transaction. The value of this field is comprised of the carrier code, form, and serial number, without check digit.

Ancillary Service Category 1

4 27-30 A C This field must contain the ancillary service category code for the sole or primary type of service provided.

Ancillary Service Sub-Category 1

4 31-34 A C This field must contain either a valid ancillary service sub-category code for the Ancillary Service Category 1 field, or all spaces.


4 35-38 A C This field must contain either an ancillary service category code for an additional second type of service that has been provided, or all spaces.




4 43-46 A C This field must contain either an ancillary service category code for an additional third type of service that has been provided, or all spaces.




4 51-54 A C This field must contain either an ancillary service category code for an additional fourth type of service that has been provided, or all spaces.



Ancillary Fee Description

13 59-71 A C 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.

Issued in Connection with Ticket Number

14 72-85 A C

If purchase has a connection or relationship to another purchase (e.g. baggage fee for passenger transport ticket) field must contain ticket document number for the other purchase. For a standalone purchase, this field must contain the same value as in the Ancillary Ticket Document Number Field.

Ancillary Service Fee Code 1

2 86-87 AN C

Applies to transportation merchants. Identifies the reason for a non-ticket related transaction.

See Ancillary Fee Code Appendix for values.

This and the related Ancillary Fee Amount field can be



repeated up to four times.

Ancillary Service Fee Amount 1

12 88-99 N C

Fee amount. Two implied decimal positions.

27.00 EUR = 000000002700 100 JPY = 000000010000 100.000 KWD = 000000010000

Right justified and zero-padded.


2 100-101 AN C Second fee code.


12 102-113 N C Second fee amount.


2 114-115 AN C Third fee code.


12 116-127 N C Third fee amount.


2 128-129 AN C Fourth fee code.


12 130-141 N C Fourth fee amount.

Filler 309

142-450 A M Space-fill



Diners AUX Record (CRR)


Record Type 3 1-3 A M Always CRR

Data Record Sequence Number 9 4-12 N M Increment by 1 per data record

ROC Text 2 15 13-27 A O Diners Customer Reference 2





Invoice Number 15 78-92 A O Diners Airline Invoice Number

Filler 358 93-450 A M Space-fill

Hotel Addendum AUX Record (HAR)


Record Type 3 1-3 A M Always HAR

Data Record Sequence Number 9 4-12 N M Increment by 1 per data record

Date of Check-In 6 13-18 N M YYMMDD

Date of Check-Out 6 19-24 N M YYMMDD

Number in Party 3 25-27 N M Acceptable Values are ‘001’ to ‘999’

Name of Guest 20 28-47 A M

Folio Reference Number 10 48-57 AN O Hotel Folio Number

Confirmed Reservation Indicator 1 58 A O Y or N

Daily Room Rate 15 59-73 AN O




Extended Data AUX Record (EXD) Private Use


Record Type 3 1-3 A M Always ‘EXD’


9 4-12 N M Increment by 1per data record

Current EXD Record Number

4 13-16 N M Identifies the current EXD record in the sequence from 0001 – 9999.

Total No of EXD Records

4 17-20 N M Total No of EXD recs associated with the current TDR (min 0001, max 9999)

EXD Format 4 21-24 A M The format of the Extended Data e.g. “VGIS”

EXD Data 426 25-450 A M Extended Data. For VGIS format, the XML Data.

Purchase Card AUX Record (PAR) Private Use Field Name L Position F S Remarks

Record Type 3 1-3 A M Always PAR



Card Acceptor Reference

17 13-29 A M Attribute contains the card acceptor/supplier reference number (e.g. order number or invoice number).

Order Date 8 30-37 N O YYYYMMDD

Number of Line Items 2 38-39 N M Indicates the number of PIR records that will follow the PAR record. Acceptable values are ‘001’ to ‘010’




Purchase Card Info AUX Record (PIR) Private Use Field Name L Position F S Remarks

Record Type 3 1-3 A M Always PIR



Line Sequence Number

3 13-15 N M Contains the line number for this item (001 to 010). Valid values are 001-010 only.

Product ID 15 16-30 A O Contains the Product Code of the item purchased.

Item Quantity 12 31-42 N O Indicates the quantity of the item purchased and the associated decimal point location. Four decimal places are implied.

Item Unit of Measure

12 43-54 A O Indicates which unit of measure is used to convey one item. Allowed values are Litre, Kilo, Gallon, Pound, Pieces.

Unit Price 12 55-66 N O Contains the price per unit. Four decimal places are implied (including tax).

Extended Item Amount

12 67-78 N O Amount is denoted in the transaction currency. Two decimal places are implied. The net-price multiplied by quantity.

Tax Amount 12 79-90 N C Contains amount of sales tax or value added tax (VAT) on the purchase amount. Amount is denoted in the transaction currency. Two decimal places are implied.

Tax Rate 6 91-96 N C Four decimal places are implied, e.g. 25% = 250000

Line Item Total Amount

12 97-108 N O Attribute contains the total gross amount with discount and inclusive of tax (VAT). Amount is denoted in the transaction currency. Two decimal places are implied.

Line Item Date 8 109-116 N O YYYYMMDD

Corporate Contract Number

40 117-156 A O Attribute contains the corporate contract number.

Transaction Type 2 157-158 N M

Value Description

00 Purchase (Debit)

01 Refund (credit)




Alternative Payment AUX Record (APM) Field Name L Position F S Remarks

Record Type 3 1-3 A M Always APM



Settlement Type

2 13-14 A C

Only applies to ZAPP

Value Description

FP Fasterpayments

ON ONUS

Space-fill Refund

Payment Reference

42 15-56 A C

Only applies to ZAPP sales transaction.

Either the FP (Fasterpayments) or ONUS (merchant and customer has account within same financial institute) reference.

Mandatory for Sale transactions. Space-fill for refunds.

Reconciliation ID

15 57-71 A C Only applies to ZAPP – Recon ID assigned uniquely on a daily basis. Space-fill if not available.

Consumer Financial Institution ID

6 72-77 N M ZAPP - CFI ID - not yet supported

CFI Account Number

34 78-111 N C Only applies to ZAPP - Mandatory for refund transactions. Space-fill for sale transactions.

CFI Account Sort Code

8 112-119 A C Only applies to ZAPP - Mandatory for refund transactions. Space-fill for sale transactions.

CFI RollNum 35 120-154 A O Only applies to ZAPP - Required for Building Society accounts. Optional for refund transactions. Otherwise space-fill.

Settlement Retrieval ID

18 155-172 N C Refund Transactions: field contains the Settlement Retrieval ID taken from the original sale being refunded and is mandatory. Space-fill for sale transactions.

Case Reference ID

14 173-186 A O Only applies to ZAPP - The value is related to the chargeback from portal file. Optional for refunds otherwise space-fill.

Transaction Plus Indicator

2 187-188 N O Indicates that transaction attracts an extra fee

Unique Reference ID

18 189-206 A C Zapp remittance information. Unique Reference ID is provided by the CFI in Refund API.

Filler 244 207-450 A M Filler



TXN Trailer Record (TTR)


Record Type 3 1-3 A M Always TTR



TDR Record Count 9 13-21 N M Number of TDR records in batch

AUX Record Count 9 22-30 N M Number of various auxiliary records in batch (TAR, AAR, CCR, HAR, AAR, PAR, PIR, EXD)

Total Record Count 9 31-39 N M Total number of records in batch (only TDR records and AUX records)

Credit Transactions Count

9 40-48 N M Number of credit (refund) transactions in batch

Value of Credit Transactions

13 49-61 N M Accumulated value for credit transactions in batch

Debit Transactions Count

9 62-70 N M Number of debit (sale) transactions in batch

Value of Debit Transactions

13 71-83 N M Accumulated value for debit transactions in batch

Net Value of Transactions

13 84-96 N M Net value of batch (debits minus credits) Should be an absolute value.




File Trailer Record (FTR)


Record Type 3 1-3 A M Always FTR



SBR Record Count 9 13-21 N M Total number of SBR records in file

THR Record Count 9 22-30 N M Total number of THR records in file

TTR Record Count 9 31-39 N M Total number of TTR records in file

TDR Record Count 9 40-48 N M Total number of TDR records in file

Auxiliary Record Count

9 49-57 N M Total number of various auxiliary records in file (TAR, AAR, CCR, HAR, AAR, PAR, PIR, EXD)

Credit Record Count 9 58-66 N M Total number of CREDIT (refund) records in file

Debit Record Count 9 67-75 N M Total number of DEBIT (sale) records in file

Hash Credit Value 15 76-90 N M Total HASH value of CREDIT (refund) transactions in file

Hash Debit Value 15 91-105 N M Total HASH value of DEBIT (sale) transactions in file

Hash Net Value 15 106-120 N M Total HASH net value of all transactions in file (i.e. DEBIT minus CREDIT)

Total Record Count 9 121-129 N M Total number of records in file ( all records including FHR and FTR)




Diagram of GMCIF File Construction

File Header Record

(FHR)


Settlement Batch

Record (SBR)


Transaction Currency Header

Record (THR)


Record (THR)


Record (THR)


Record (THR)

Transaction Detail Record (TDR)

Transaction Detail

Record (TDR)

Transaction Detail Record

(TDR)

Transaction Detail Record

(TDR)


Transaction Detail

Record (TDR)

Transaction Addendum

Record (TAR)


Record (TAR)


Transaction Detail

Record (TDR)

Airline AUX Record (AAR)


(CCR)


Transaction Detail

Record (TDR)


(HAR)

Transaction Currency Trailer Record (TTR)

Transaction

Currency Trailer Record (TTR)


Trailer Record (TTR)


Trailer Record (TTR)

File Trailer Record

(FTR)



Ancillary Fee Codes Used in conjunction with the Ancillary Fee Code fields in the Passenger Transport AUX Record (PTA).

Code Description Code Description

BF Bundled Service OT Other

BG Baggage Fee PA Passenger Assist Fee

CF Change Fee PT Pets

CG Cargo SA Seat Fee

CO Carbon Offset SB Standby

FF Frequent Flyer SF Service Fee

GF Gift Card ST Store

GT Ground Transport TS Travel Service

IE In-Flight Entertainment UN Unaccompanied Travel

LG Lounge UP Upgrades

MD Medical WI WiFi

ML Meal/Beverage



Multi-Currency Conversion The below table lists currencies available for Multi-Currency Conversion (MCC) processing. Currency names marked with an (S) indicate that Elavon accept and settle payments in that currency.

Heading Description

N Numeric Code

A Alphabetic Code

Currency Currency Name

MU Number of Minor Units / Decimal Places

N A Currency MU

N A Currency MU

12 DZD Algerian Dinar 2

404 KES Kenyan Shilling 2

973 AOA Angolan Kwanza 2

410 KRW Korean Won 0

32 ARS Argentine Peso 2

414 KWD Kuwaiti Dinar 3

51 AMD Armenian Dram 2

417 KGS Kyrgyzstani Som 2

533 AWG Aruban Guilder 2

422 LBP Lebanese Pound 2

36 AUD Australian Dollar (S) 2

434 LYD Libyan Dinar 3

944 AZN Azerbaijani Manat 2

446 MOP Macanese Pataca 2

44 BSD Bahamian Dollar 2

807 MKD Macedonian Denar 2

48 BHD Bahraini Dinar 3

969 MGA Malagasy Ariary 2

50 BDT Bangladeshi Taka 2

454 MWK Malawian Kwacha 2

52 BBD Barbadian Dollar 2

458 MYR Malaysian Ringgit 2

933 BYN Belarussian Ruble 2

480 MUR Mauritian Rupee 2

84 BZD Belize Dollar 2

484 MXN Mexican Peso 2

60 BMD Bermudian Dollar 2

498 MDL Moldovan Leu 2

68 BOB Bolivian Boliviano 2

496 MNT Mongolian Tugrik 2

977 BAM Bosnia Herzegovina Mark

2

504 MAD Moroccan Dirham 2

72 BWP Botswana Pula 2

104 MMK Myanmar Kyat 2

986 BRL Brazilian Real 2

516 NAD Namibia Dollar 2

826 GBP British Pound Sterling (S)

2

524 NPR Nepalese Rupee 2

96 BND Brunei Dollar 2

532 ANG Netherlands Antillean Guilder

2

975 BGN Bulgarian Lev 2

554 NZD New Zealand Dollar (S) 2

108 BIF Burundian Franc 0

558 NIO Nicaraguan Cordoba 2

132 CVE Cabo Verdean Escudo 2

566 NGN Nigerian Naira 2



N A Currency MU

N A Currency MU

116 KHR Cambodian Riel 2

578 NOK Norwegian Krone (S) 2

124 CAD Canadian Dollar (S) 2

512 OMR Omani Rial 3

136 KYD Cayman Islands Dollar 2

586 PKR Pakistani Rupee 2

152 CLP Chilean Peso 0

590 PAB Panamanian Balboa 2

156 CNY Chinese Yuan Renminbi 2

598 PGK Papua New Guinean Kina 2

170 COP Columbian Peso 2

600 PYG Paraguayan Guarani 0

976 CDF Congolese Franc 2

604 PEN Peruvian Sol 2

188 CRC Costa Rican Colon 2

608 PHP Philippine Peso 2

191 HRK Croatian Kuna 2

985 PLN Polish Zloty (S) 2

203 CZK Czech Koruna (S) 2

634 QAR Qatari Riyal 2

208 DKK Danish Krone (S) 2

946 RON Romanian New Leu 2

214 DOP Dominican Peso 2

643 RUB Russian Ruble 2

951 XCD East Caribbean Dollar 2

646 RWF Rwandan Franc 0

818 EGP Egyptian Pound 2

882 WST Samoan Tala 2

230 ETB Ethiopian Birr 2

682 SAR Saudi Riyal 2

978 EUR Euro (S) 2

941 RSD Serbian Dinar 2

242 FJD Fijian Dollar 2

690 SCR Seychellois Rupee 2

953 XPF French Polynesian Franc

0

702 SGD Singapore Dollar (S) 2

950 XAF Gabon Franc 0

710 ZAR South African Rand (S) 2

270 GMD Gambian Dalasi 2

144 LKR Sri Lankan Rupee 2

981 GEL Georgian Lari 2

752 SEK Swedish Krona (S) 2

936 GHS Ghanaian Cedi 2

756 CHF Swiss Franc (S) 2

320 GTQ Guatemalan Quetzal 2

760 SYP Syrian Pound 2

328 GYD Guyanese Dollar 2

901 TWD Taiwan New Dollar 2

332 HTG Haitian Gourde 2

834 TZS Tanzanian Shilling 2

340 HNL Honduran Lempira 2

764 THB Thai Baht 2

344 HKD Hong Kong Dollar (S) 2

780 TTD Trinidad and Tobago Dollar 2

348 HUF Hungarian Forint (S) 2

788 TND Tunisian Dinar 3

352 ISK Icelandic Krona 2

949 TRY Turkish New Lira 2

356 INR Indian Rupee 2

980 UAH Ukrainian Hryvnia 2

360 IDR Indonesian Rupiah 2

784 AED United Arab Emirates Dirham

2



N A Currency MU

N A Currency MU

376 ILS Israeli New Shekel 2

840 USD United States Dollar (S) 2

388 JMD Jamaican Dollar 2

858 UYU Uruguayan Peso 2

392 JPY Japanese Yen (S) 0

860 UZS Uzbekistani Soʻm 2

400 JOD Jordanian Dinar 3

704 VND Vietnamese Dong 0

398 KZT Kazakhstan Tenge 2

952 XOF West African CFA Franc 0

886 YER Yemeni Rial 2



Revision History

Date Author Version Description of Change

28th Oct 2008 AT 2.08 Insert Record-Type DCC and AME

1st Dec 2008 AT 2.09 Insert Check-Out-Date on TDR

16th Dec 2008 AT 2.10 Rename AME to TAR, some clarifications

7th Jan 2009 AT 2.11 Expand TAR with DCC

13th Jan 2009 AT 2.12 Separate Visa-CPS-data and BankNet-data in different fields. Clarify ACI

27th Jan 2009 AT 2.13 Add Check-In-Date, small corrections

27th Jan 2009 AT 2.14 Reduce Airline Addendum-data up to 4 Legs. Correct EMV-position

4th Feb 2009 AT 2.15 Correction Check-out + in-date

10th Mar 2009 AT

2.16 Reduce the Cardholder-Amount (DCC) from 3 to 2 implicit decimal places and sort the TAR after the AAR

20th Mar 2009 AT 2.17 Corr. Decimal points DCC

14th Apr 2009 AT 2.18 Small corrections EMV-fields

18th Jun 2009 PS 2.19 Added values on POS entry mode for contactless payments

23rdJun 2009 PS 2.20 Explanation ECI and Purchase-date

24th Feb 2010 SF 2.21 STAN and RRN added to TDR, PAR and PIR records added.

25th Feb 2010 SF 2.21 ‘Number of Line Items’ added to PAR

5th Mar 2010 AT 2.22 Corr. Filler PIR-Record

6th Apr 2010 AT 2.30 Refresh the document / Alpha-Ticket-No.

17th May 2010 AT PIR-Record: add Sign-field

31st Aug 2010 AT Creation SOC number

25th Jan 2011 AT 2.31 Correction SOC-No + FTR amounts

29th Mar 2011 AT 2.32 Clarifications (AAR: eliminate Check-Digit)

7th Jun 2011 AT 2.40 Insert HAR, CRR and EXD / Insert Diners Invoice No (AAR)I

24th Jun 2011 AT 2.41 Correction Lengths on HAR, CRR Change cut-off time from 22:45 to 22:15

11th Oct 2011 AT 2.42 Insert Transaction Source - Table

20th Oct 2011 AT 2.43 Move DC-Airline-Invoice-Number from AAR to CRR

21st Feb 2012 AT 2.44 TAR: clarifications some fields / KAAI references

27th Mar 2012 AT 2.45 Minor corrections

29th May 2012 AT 2.46 Transaction ID change to ‘N’




19th Jun 2012 AT 2.47 Small optical changes

21st Aug 2012 AT 2.49 EMV TAG corrections

23rd Oct 2012 AT 2.50 Insert amount examples in TDR, ‘Transaction amount’. Clarification Chip-fields / Transaction ID changed to AN

25th Jan 2013 PS 2.51 Change on TAR BankNet ref date description from zero filled into space filled

2nd Feb 2013 ME 2.52 - Fixed conflicting TAR-AAR record sequences, all to TDR->TAR->AAR Section 4.2 – File Structure – TAR and AAR sections swapped, other sections show correct record order Section 5.1 TDR record – description for State/Province-Code Position [115..116] corrected – reference to Section 4.6.6 updated to 4.6.5

9th Apr 2013 AT 2.53 Correction Lengths ‘BankNet-Reference’ and ‘Condition Code’ Clarification ‘Currency’ in THR and TDR

25th Apr 2013 ME 2.54 RECORD : TDR POSITION : [341..343] CHANGE: Field type changed from “N” to “A” after check with AXIS on field definition

28th Oct 2013 PS 2.55 Fields for Discover Processing added: Track Data Condition Code and Network Reference Identification Number (NRID)

29th Oct 2013 PS 2.56 SBR: Dynamic Merchant Indicator field added. Merchant Group Identifier field added TAR: Dynamic Merchant Detail fields added. TDR: M-POS Indicator added TDR: STAN description changed

15th Nov 2013 PS 2.57 Length of Dynamic Merchant Data changed on TAR Correction of BankNet Reference field length and description on TAR

10th Dec 2013 PS 2.58 Added Card Brand Override Indicator

4th Feb 2014 PS

2.59 Added ancillary data in AAR. Added a new record called PTA for passenger transport ancillary data for VISA only. TDR: Added field Spend Qualified Indicator Added file number within FHR

4th Apr 2014 PS 2.60 Added digital wallet data and MasterPass merchant enabled flag

25th Mar 2015 PS 2.61 TDR: Added Form Factor Indicator – EMV processing value; Added UCAF Collection Indicator field for MasterPass transactions Added MasterCard assigned ID TDR: Added Form Factor Indicator

13th Apr 2015 PS 2.62 draft

TDR: Added transaction source code for APM Added authorization source code for APM Added ZAPP transaction reference details Added 2 notes *4 on card-number field for ZAPP payments and *5 on Expiry Date field for ZAPP payments New Record created called APM. Added APM AUX Record




13th Oct 2015 P Hammerson 2.62a TDR: Transaction Reference Field: changed ‘APTRID’ to ‘Settlement Retrieval ID’ APM: CFI RollNum Field: changed ‘To’ Column value from ‘134’ to ‘154’ Changed all subsequent ‘To’ / ‘From’ values accordingly ‘Reference ID’ Field: changed name to ‘Settlement Retrieval ID’ ‘Settlement Retrieval ID’ Field: Updated Remarks Column Added new Field: ‘Unique Reference ID’ Filler Field: changed ‘Length’ value from ‘282’ to ‘244’ Filler Field: changed ‘From’ value from ‘169’ to ‘207’

15th Feb 2016 P Hammerson 2.62b Transaction AUX Record ‘TAR’ Removed ‘Not Supported’ comment from UCAF Collection Indicator value 3 and MasterCard Assigned ID Field

18th Apr 2016 P Hammerson 2.62c Transaction Detail Record (TDR) MOTO/Ecommerce Authentication Indicator Field: updated description of field contents. Removed notes relating to 3D Secure Indicators.

29th Jul 2016 P Hammerson 2.62d TXN Detail Record (TDR): Transaction Source Field – added value 10 Credential on File Transaction. Reformatted table. TXN Detail Record (TDR): Dedicated File (DF) Name Field – updated description. Transaction AUX Record (TAR): Transaction Identifier Field – updated description to support American Express Transaction ID.

4th Oct 2016 P Hammerson 2.62e TXN Header Record – SOC Number Field: updated description. TXN Header Record – SOC Merchant Reference Field: updated description. TXN Detail Record – State/Province Code (Merchant) Field: updated description. TXN Detail Record – Terminal Capabilities Field: updated description. Revision History: moved section to end of document and corrected references where required. TXN Detail Record – Transaction Source: Credential On File Transaction changed to Reserved For Future Use. Reformatted document.




1st Feb 2017 P Hammerson 2.63 Special Field Requirements, Payment Facilitator: added comment re: PF requirements. Settlement Batch Record (SBR), Payment Facilitator Dynamic Merchant Indicator Field: updated field name and description. Transaction AUX Record (TAR): updated field names and descriptions for existing Payment Facilitator Fields. Added new Fields: Payment Facilitator MCC Code; Phone Number; Email Address; Tax ID. Added new Field: Unique Transaction Reference Number. TXN Detail Record (TAR) – Transaction Source: added new value 30 (In-App Secure Ecommerce). TXN Detail Record (TAR) – MOTO/Ecommerce Authentication Indicator: updated description. File Header Record (FHR) – Processor ID: updated description. File Header Record (FHR) – Processor Name: updated description. Special Field Requirements – SE Number: updated description. Settlement Batch Record (SBR), SE Number: updated description. TXN Detail Record (TDR), Cardholder Verification Value (CVV2): updated description and added additional values. Alternative Payment AUX Record (APM) – Reconciliation ID Field: updated description and status to Conditional where ID is available.

25th Jul 2017 P Hammerson 2.64 Transaction Detail Record (TDR) – Transaction Source: added new value 3 (PAN Auto Entry) Transaction Detail Record (TDR): added new fields (Unattended Acceptance Terminal Indicator / Terminal Capability) Transaction AUX Record (TAR): added new fields (DCC Reference Number / Transit Type Indicator / Transportation Mode Indicator)

4th Oct 2017 P Hammerson 2.65 TXN Detail Record (TDR), POS Capability Field: new value added, 9 (Key Entry), updated description. TXN Detail Record (TDR), Authorisation Source Field: updated description. Appendices: added Multi-Currency Conversion appendix.

17th Apr 2018 P Hammerson 2.66 Transaction AUX Record (TAR) – Transaction Identifier Field: updated description to include TAVV. TXN Detail Record (TDR) – Transaction Type Field: added new values 05 (Instalment Transaction), 06 (Unscheduled Credential on File) and 07 (Storing Credential on File). TXN Detail Record (TDR) – Transaction Source Field: updated value 10 to indicate Credential on File. TXN Detail Record (TDR): added new field (Debt Repayment Indicator). Diagram of GMCIF File Construction: updated diagram. TXN Detail Record (TDR) – Form Factor Indicator Field: added support for Diners Form Factor Indicator. Transaction AUX Record (TAR): added new field (Transaction Integrity Class). Multi-Currency Conversion: removed Iranian Rial and Zambian Kwacha – no longer supported.




20th Jul 2018 P Hammerson 2.67 Transaction AUX Record (TAR) – Unique Transaction Response Reference Number Field: updated field name and description. TXN Detail Record (TDR) – Transaction Reference Field: updated description. TXN Detail Record (TDR) – Transaction Type Field: updated description of value 05 (Instalment Transaction and 07 (Storing Credential on File) to support MasterCard. TXN Detail Record (TDR) – Transaction Source Field: updated description of value 10 (Credential on File) to support MasterCard. Settlement Batch Record – Settlement Currency Field: updated description. Transaction AUX Record – Cardholder Amount (DCC) Field / Cardholder Currency Code (DCC) Field / Conversion Rate (DCC) Field / Conversion Exponent (DCC) Field: updated descriptions.

1st Oct 2018 P Hammerson 2.68 TXN Detail Record (TDR) – Card Number Field: changed format from Numeric to Alphanumeric. TXN Detail Record (TDR): new field added (Reserved for Future Use). TXN Detail Record (TDR) – Transaction Source Field: updated description, removed references to card schemes. TXN Detail Record (TDR) – Form Factor Indicator: updated description. Universal Cardholder Authentication Field (UCAF): updated name to Accountholder Authentication Value (AAV) across document. Transaction AUX Record (TAR) – Digital Wallet Description Table: updated V.Me to Visa Checkout. TXN Detail Record (TDR) – Cardholder Verification Value (CVV2) Field: added American Express values. Transaction Detail Record (TDR) – Mobile POS (MPOS) Indicator: updated name to differentiate it from new Mobile POS (MPOS) Acceptance Device Field. Transaction Detail Record (TDR) – Dedicated File (DF) Name: updated description to advise that field is mandatory for Diners transactions. Transaction AUX Record (TAR): added new fields Payment Account Reference (PAR) Number / 3D Secure Version Number / Directory Server (DS) Transaction ID / Accountholder Authentication Value (AAV) / PIN Capability / Mobile POS (MPOS) Acceptance Device Indicator. Passenger Transport AUX Record (PTA): added new fields Ancillary Service Fee Code (x4) and Ancillary Service Amount (x4). Appendices: added new Appendix Ancillary Fee Codes.

gmcif global multi-currency input file (gmcif)

Documents