Technical Specifications

Transcription

1 Technical Specifications Version 1.8 May 2015 Global Payments is a trading name of GPUK LLP. GPUK LLP. All rights reserved. No part of this document may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior permission of Global Payments.

2 AMENDMENT HISTORY Version Status Date Issued Comment Originator Reviewed By 1.0 New 04/02/2013 Issued for Global Payments Sharon Janet Beeson Milnes 1.1 Update 15/02/2013 Amendments to ICC Record Sharon Janet Beeson layout Milnes 1.2 Update 28/02/2013 Amendment to Empty / Null Sharon Philip Jones Files on Page 2 Milnes 1.3 Update 29/07/2013 APACS to The UK Cards Association. EMV Terminal Sharon Milnes Lesley Armitage Type. 1.4 Update 18/10/2013 Issued for Authorisation Sharon Paul Drabble Scheme Reference Data 1.5 Update 14/11/2013 No changes to Content Version issued to show Tracked Changes 1.6 Update 19/02/2014 The following tables have been updated: Record Types Diners added to Table 1 Customer Instruction Field Segment 2 (Type 20) Sub Record Format 26 First File Trailer Label EOF1. Auxiliary Data Records Example Construction Terminal Capabilities and Terminal Attributes Auxiliary Data Record Terminal Attribute Codes Response Or Referral Message In Response To An Authorisation Request Additional explanations added to Scheme Reference Data Record and Acquirer Reference Data Record descriptions. 1.7 Update 14/03/2014 The following tables have been updated: Message Format For Authorisation Request The following tables have been added: Transit sub record for authorization Scheme wallet sub records for authorization Form Factor Sub Record for authorization Payment Attributes Sub Record for authorization Transit Code Values For Authorisation Payment Attributes Codes for authorization Milnes Phil Jones Sharon Milnes Paul Drabble Chris Lomax Jozef Morawski Paul Drabble Sharon Milnes

3 AMENDMENT HISTORY (Continued) Version Status Date Issued Comment Originator Reviewed By 1.7 Paul Sharon Milnes (Cont) Drabble Update 14/03/2014 The following tables have been added:- Point Of Interaction subrecord for clearing (includes transit indicators) Digital scheme wallet sub records for clearing Contactless form factor sub record for clearing Update 05/12/2014 Clarification to DCC Mark UP Percentage in authorisation and settlement sub records 1.8 Update 07/05/2015 Addition of mpos indicator for settlement Addition of Instalment Payment indicator for settlement Indication of record types not currently supported by global payments Addition of details for processing reversals and partial reversals Correction to DCC auxiliary record for authorisation (addition of Opt out marker) Correction to size of form Factor field in authorisation and settlement records Review comments added Paul Drabble Paul Drabble Andy Cope Katina Campbell

4 Contents Page Introduction 1 Currency Transactions 1 File Structure 1 File Integrity Checking 2 Record Types 3 Transaction Codes 3 Abbreviations 3 Volume Header Label Format 4 First File Header Label Format 5 Second File Header Label Format 6 User Header Label Format 6 SEGMENT 1 7 Table 1 Customer Instruction Field 8 SEGMENT 2 (Type 20) 9 Purchase With Cashback Type 20 9 SEGMENT 2 (Type 50) ML/VGIS 10 Reference Number Or ML Layout Type Sub Record Format 25 Reference Number/ML 10 SEGMENT 2 (Type 80) 11 DCC - Type Sub Record Format 27 DCC Data 11 SEGMENT 4 12 ICC Record Layout 12 Table 2 POS Entry Mode 13 Sub Records 14 Sub Record Format 26 Authorisation Network Reference Data (Scheme Reference Date/Acquirer Reference Data) 14 Sub Record Format 01 General Sub Record 15 Scheme Digital Wallet Sub Records 18 Net Summary Record 20 Net Claim Record 21 First File Trailer Label EOF1 22 Second File Trailer Label EOF2 22 User Trailer Label UTL1 23 Appendix A ISO Country And Currency Codes 23 Authorisation 24 Authorisation Messages 24 Authorisation Request Message 24 Currency Transactions 24 Message Contents 24 Reversals 24 Partial Reversals 24 Message Format For Authorisation Request 25 Table 3 Terminal Type Codes 28 Table 4 Message Type 29 Table 5 Card Details 31 Table 6 Descriptive Data CSC And/Or Address Data 32 Auxiliary Data Records Example Construction 32 ECommerce Auxiliary Data Record Type Table 7 - Additional Transaction Security Data (ATSD) 34 Dynamic Currency Conversion (DCC) Auxiliary Data Record Scheme Reference Data Record, Sub-type Acquirer Reference Data Record, Sub-type Transit Program Data Record Type Scheme Digital Wallet Data Record Type Contactless Device Information Data Record Type Payment Attributes Data Record Type Terminal Capabilities And Terminal Attributes Auxiliary Data Record 06 (Contactless/Proximity Cards) 41

5 Terminal Attributes 42 Terminal Attribute Codes 42 Response Or Referral Message In Response To An Authorisation Request. 43 Table 8 Response Codes And Message Text 44 Table 9 Response Additional Data Codes 44 ICC Data 45

6 Introduction This document details the settlement format for Global Payments (GP) Card Processing Service using a 640 byte variable length file, which is based on The UK Cards Association standard specifications. Note: We also support backward compatibility for both 90 and 380 byte files. In addition to the information contained within this document, it is recommended that you obtain a copy of The UK Cards Association standard specifications by contacting: UK Payments Administration Ltd 2 Thomas More Square London E1W 1YN Tel: Fax: enquiries@ukpayments.org.uk If you use a payment service provider, bureau, or any other kind of third party to assist in the processing of your card transactions, they will act at all times as your agent and you will be responsible for any acts or omissions on their part. You must ensure that they comply at all times with the terms of our Card Processing Agreement and that you pass on to them promptly all communications or information which we provide to you which will have an impact on the processing services they provide to you. Furthermore you agree to indemnify us against any losses, damages or liability that we may suffer as a result of acting on your agent s instructions or any other action or omission of theirs. Whilst we may provide details of third party processors to you, you are responsible for making a selection appropriate to your requirements and negotiating contractual terms directly with the third party in question. You remain fully responsible for paying any fees charged by your agent and in no circumstances will we collect these for your agent or remit them to your agent before making payment to you. Currency Transactions This service covers the acceptance of MasterCard, Visa and International Maestro for sales and refunds transactions. File Structure VOL1 Volume Header Record HDR1 Header 1 HDR2 Header 2 UHL1 User Header Label n1 Sale n2 Refund E4/5/6 Summary Record E7/8 Claim Record n3 Cash Advance* E6 Summary Record E8* Claim Record n2 Refund n1 Sale E4/5/6 Claim Record E7/8 Claim Record EOF1 End of File 1 EOF2 End of File 2 UTL1 User Trailer Label *Cash Advances A batch containing Cash Advance transactions must not contain any Sales/Refunds. 1

7 Note: The Cash Advance transaction type is for Financial Institutions only, therefore prior written approval is required from Global Payments before submitting this transaction type. Although 90 byte file structures are supported for existing customers, new customers must submit files in 640 byte variable format. Empty/Null files We do not support the processing of completely empty files or zero value files (e.g. Files containing headers and trailers but no transactions). n4 records All fields set to zero except Record count should be set to 1. n8 records All fields set to zero except Debit summary count should be set to 1 and Record count which should be set to 2. UTL records All fields set to zero except Debit item count which should be set to 1 and Record count which should be set to 2. Files must be written in ASCII United Kingdom 7-bit data code. Merchant outlet must batch the settlement file. There is no batch limit for an incoming file to Global Payments - except for merchant submitting VGIS data. For merchants submitting VGIS data the limits are as follows:- 99,999 transactions per batch 9,999 batches per file 999 VGIS line items per invoice. There is a limit of 2320ML records per invoice. Each transaction must have the Global Payments 8 digit merchant number. File Integrity Checking There are two levels of integrity checking when you submit a file to our Card Processing Service, a financial one and a logical one. A failure of either integrity check invalidates a submission file. Financial Integrity is achieved by a hierarchical structure. Transactions from a single source are netted, both number and value, onto a single summary record, using transaction codes n4 or n5. n = prefix (e.g.e4) n4 is used when sales equal or exceed refunds. n5 is used when refunds exceed sales. One or more summary records from one or more sources are netted in both number and value into a single claim record, transaction codes n7 or n8. n7 is used when refund summaries (n5) exceed sales summaries (n4). n8 is used when sales summaries (n4) equal or exceed refund summaries (n5). One or more claim records are netted in both number and value into the audit fields of the User Trailer Label. All transaction records must be included on a summary record. All summary records must be included on a claim record. All claim records must be included on the User Trailer Label. If any of the levels of totalling do not reconcile then there is an integrity failure, thus invalidating the whole file. Logical integrity is achieved by the numbering of the records within the file starting at and incrementing in single units with each subsequent record. Additionally the audit fields on the User Trailer Label contain the total record count which must equal the highest sequence number used. Any break in the numbering or a failure to record the correct number of records on file causes an integrity failure, thus invalidating the whole file. 2

8 Record Types Transaction Code For File Format Record Length Segment Required Sub Record + Fixed Variable Type 3 4 Type E E 90 J J L L L N 346 P R R 429 R R Transaction Codes Position Value Description Digit 1 E Segment 1 Mag Stripe Read (MSR)/ J Segment 1 + Segment 2 PAN Key Entry (PKE) L Segment 1 + Segment 2 + Sub Record Digit 1 N Segment 1 + Segment 4 ICC Read P Segment 1 + Segment 2 + Segment 4 R Segment 1 + Segment 2 + Segment 4 + Sub Record Digit 2 1 Sale 2 Refund 3 Cash Advance D Instalment Transaction Abbreviations Abbreviation Meaning R Right justified. If numeric, leading zeros. If alphanumeric, leading characters are space filled. L Left justified A Alphanumeric N Numeric AB Binary b Blank space. E.g. byyddd = M Mandatory O Optional unless mandated by a Card Scheme requirement 3

9 Volume Header Label Format Num Name Pos Type Len Description 1 Label Identifier 1 A 3 VOL value 2 Label Number +3 A 1 1 value 3 Volume Serial +4 A 6 Zero fill Number 4 Volume Accessibility +10 A 1 Space fill 5 Reserved +11 A 26 Space fill 6.1 Owner Identification +37 A 10 Unique customer number supplied by GP (Zero fill from left) 6.2 File Currency +47 A 1 0 value (not used by acquirer) Indicator 6.3 Reserved for future +48 A 3 Space Fill use 7 Reserved for future +51 A 28 Space Fill use 8 Label Standards +79 A 1 3 value Version 9 Filler applicable to fixed format only +80 A V Space Fill 90 byte fixed or 380 byte fixed 4

10 First File Header Label Format Num Name Pos Type Len Description 1 Label Identifier 1 A 3 HDR value 2 Label Number +3 A 1 1 value 3.1 Source ID or As advised by GP originator 3.2 Record Type Identifier +14 A 1 E value (Fixed 90 byte records) J value (Fixed 380 byte records) Z value (Variable length records >90 <=636) +15 A 2 Space fill 3.3 Version Number of Standard 3.4 File Currency Indicator 3.5 Reserved +18 A 3 Space fill 4 File set identification +21 A 6 Zero fill 5 File section number +27 A value +17 A 1 0 value (not used by acquirer) 6 File sequence +31 A value number 7 Generation Number +35 A value 8 Generation Version +39 A 2 00 value Number 9 Creation date +41 A 6 byyddd Julian. Where b is blank, YY is the last 2 digits of the year and DDD ( ) is the day in the year. This field must be equal to the processing date of the UHL record 10 Expiration date +47 A 6 byyddd earliest date at which file may be overwritten. Calculate as 14 calendar days greater than Creation date 11 File accessibility +53 A 1 Space fill 12 Block count +54 N 6 Zero fill 13 System code +60 A 13 Space fill if not used 14 Reserved +73 A 7 Space fill 15 Filler applicable to fixed format only +80 A V Space Fill 90 byte fixed or 380 byte fixed 5

11 Second File Header Label Format Num Name Pos Type Len Description 1 Label Identifier 0 A 3 HDR value 2 Label Number +3 A 1 2 value 3 Record format +4 A 1 F value (Fixed length) D value (variable length) 4 Block length +5 N value (E Fixed records) value (J Fixed records) value (M Variable records) 5 Record length +10 N value (E Fixed records) value (J Fixed records) value (M Variable records) 6 Reserved +15 A 35 Space fill if not used 7 Offset length +50 N 2 Zero fill 8 Reserved +52 A 28 Space fill 9 Filler applicable to fixed format only +80 A V Space Fill 90 byte fixed or 380 byte fixed User Header Label Format Num Name Pos Type Len Description 1 Label Identifier 0 A 3 UHL value 2 Label Number +3 N 1 1 value 3 Processing date +4 A 6 byyddd Julian date 4.1 Identifying number of +10 A 4 Zero fill receiving party 4.2 Destination code +14 A value 4.3 Reserved +18 A 2 Zero fill 5 Currency Code +20 A 3 Spaces Or: ISO alpha CCY code 6 File Currency +23 N 1 Zero Fill Indicator 7 Reserved +24 A 4 Zero Fill 8 Work code +28 A 9 Space Fill 9 File generation number +37 N 3R increment by 1 from the last file sent. 10 Reserved +40 A 14 Space Fill 11 Reserved +54 A 26 Any Valid Characters 12 Filler applicable to fixed format only +80 A V Space Fill 90 byte fixed or 380 byte fixed 6

12 SEGMENT 1 Num Name Pos Type Len Description 1 Cardholder number 0 N 19 As defined by the card company. Padded with leading zeros 2 Transaction code +19 A 2 n0 = Unique Sale Transaction n1 = Sale n2 = Refund n3 = Cash Advance nd = Instalment Transaction Where n is Record Type (page 3 Transaction Codes) 3 Source number +21 N (R) 11 As provided by GP. Padded with leading zeros 4 Card expiry date +32 N 4 MMYY 5 Amount +36 N 11 AMOUNT In the minimum unit of the CCY (unsigned). No decimal places. Maximum amount is 999,999, Transaction date +47 A 6 byyddd Julian date. This must be the same date as appears on the Terminal receipt or other notification given to the cardholder 6.2 Transaction time +53 N (R) 6 TRANSACTION TIME - HHMMSS. If not used must be Zero filled. (24hr) Authorisation method +59 N 1 Space fill if not used Authorisation number +60 A 1 Reserved for future use Authorisation number +61 A 6 If not used, must be Space filled. (Right Justified) 6.4 Originators transaction reference 6.5 Card issue number (1) 6.6 Terminal type/currency indicator +67 A 12 This must contain sufficient details to enable the originator to identify the specific transaction so that a copy voucher or terminal receipt given to the cardholder can be produced +79 N 1 Zero fill +80 A 1 If not used must be Zero filled. 0 = Unspecified terminal capabilities 1 = ICC reader only 2 = Magnetic Stripe only 3 = ICC/Magnetic stripe 4 = No card reader If the Currency Code is indicated elsewhere on the File e.g. E4 or E5 Summary Records, the Sterling Values (0-4) will refer to the declared currency. +81 N 1 Zero fill. 6.7 Card issue number (2) 6.8 Customer instruction +82 A 1 See Table 1 7 Sequence number +83 N (R) 7 Sequence number of this record within the file. 7

13 Table 1 Customer Instruction Field MasterCard Credit, MasterCard Debit, Visa Credit, Visa Debit, Electron, International Maestro, VPay, Diners Signed voucher 0 Mail/telephone order 1 Continuous authority 2 PIN verified online 3 PIN verified locally 4 Signed voucher ICC read 5 Signed voucher magnetic stripe read 5 Signed voucher keyed at POS 6 Unattended device without PIN 7 verification PIN verified (card) transaction 8 recovered after sale Signed voucher recovered after sale 9 Unattended device with PIN verified A locally Downgraded ICC (track 2 information D only) ICC fallback to magnetic stripe read F E-Commerce secure transaction with G cardholder certificate E-Commerce non authenticated H security transaction with card acceptor certificate Instalment Payment I (Not currently supported by E-Commerce non authenticated transaction without card acceptor certificate using channel encryption (eg SSL) E-Commerce non authenticated security transaction with card acceptor certificate using channel encryption (eg SSL) ICC Contactless Full proximity EMV transaction format MSR Contactless Proximity transaction with only track 2 magstripe (or equivalent data) available Global Payments) J L M N 8

14 SEGMENT 2 (Type 20) Purchase With Cashback Type 20 Num Field Name Pos Type Len Description 8 Method of authorisation +90 N 1 0 = By terminal 1 = On line to Acquirer 2 = Voice to Acquirer 5 = Method of authorisation not known 9 Type of purchase transaction +91 N 1 0 = Purchase or refund 1= Purchase with cash back 10 Cash amount +92 N 6 For purchase with cash back in the currency of the transaction. If a Purchase, Refund or Not used, must be Zero filled 11 Filler +98 A 13 Space fill 12 Filler +111 A 56 Space fill 13 Sub-record count +167 N 4 Total number of sub records within the transaction = no sub records 14 Format type +171 N 2 Defines the format of Segment 2 and the presence and format of any subsequent Segment 3 Digit 1 Segment 2 format 2 Purchase with cash back Digit 2 Segment 3 format 0 No Segment 3 9

15 SEGMENT 2 (Type 50) Reference Number Or ML Layout Type 50 Num Field Name Pos Type Len Description 8 Establishment name +90 A 26 Establishment name 9 Establishment +116 A 26 Establishment address address 10 Reference number +142 A 25 The unique reference number assigned by the merchant to this transaction. This number must be unique throughout the file. ie every financial record and its associated sub record must have the same Reference number and these numbers must be unique per financial record within the file 11 Sub-record count +167 N 4 Total number of sub records within the transaction = no sub records 12 Format type +171 N 2 Defines the format of Segment 2 and the presence and format of any subsequent Segment 3 Digit 1 Segment 2 Format 5 Reference/ML Digit 2 Segment 3 Format 0 No Segment 3 Sub Record Format 25 Reference Number/ML/VGIS Num Field Name Pos Type Len Description 1 Sub record counter 0 N 4 The sequence number of the sub record in relation to all sub records submitted for this transaction starting at 0001 and up to the Sub Record Count sent in Segment 2 2 Reserved Space filled A 3 Transaction code +19 N 2 Value = 25 for this sub record 4 Length of sub +21 N 3 Minimum 90 bytes, maximum 636 bytes record 5 Card acceptor reference number +24 A 25 Reference number same as Segment 2 type 3 Reference number field 10 6 Reserved +49 A 34 Space filled 7 Record sequence number +83 N 7 Sequence number of this record within the file 8 ML data +90 A ML data (see Note below) Note: This is a flexible length sub-record between 90 and 636 bytes in length 10

16 SEGMENT 2 (Type 80) DCC Type 80 Num Field Name Pos Type Len Description 1 Sub Record Flag +90 A 1 Dynamic Currency Conversion Value = D 2 Filler +91 N 51 Space filled 3 Card Acceptor Reference Number 4 Total Number of Sub Records +142 A 25 This is the unique number assigned by the processor. This number must be unique throughout the file N 4 Total number of sub records within the transaction. No sub records Value = 0000 Dynamic Currency Conversion Value = Format type +171 N 2 Defines the format of Segment 2 and the presence and format of any subsequent Segment 3 Digit 1 Segment 2 Format 8 DCC Digit 2 Segment 3 Format 0 No Segment 3 Sub Record Format 27 DCC Data Num Field Name Pos Type Len Description 1 Sub record counter 0 N 4 The sequence number of the sub record in relation to all sub records submitted for this transaction starting at 0001 and up to the Sub Record Count sent in Segment 2 2 Reserved +4 A 15 Space filled 3 Transaction code +19 N 2 Value = 27 for this sub record 4 DCC card acceptor currency amount +21 N 11 Transaction amount prior to DCC. In the card acceptor currency denomination 5 DCC card acceptor +32 N 3 Transaction currency code prior to DCC currency code 6 DCC commission +35 N 11 Commission fee on the DCC transaction. In fee 7 DCC conversion rate applied the cardholder currency denomination +46 N 11 Conversion rate used in the DCC transaction, as printed on the DCC receipt (minus decimal point). See Note 1 8 DCC mark up fee +57 N 11 The Mark Up percentage applied to the DCC transaction to 2 decimal places 9 Reserved +68 A 15 Space filled 10 Record sequence number +83 N 7 Sequence number of this record within the file 90 byte record Note 1: The format of the DCC conversion rate applied shall be as follows: xnnnnnnnnnn, where x is the number of decimal places to be used. For example, indicates an exchange rate of

17 SEGMENT 4 ICC Record Layout Num Name Pos Type Len Description Tag 1 Application PAN 0 A 2 Populate with the Value in Tag 5F34 sequence number 5F34 from the card. If Tag 5F34 is 2 Authorisation response code 3 Cryptogram transaction amount 4 Cryptogram transaction type 5 Terminal transaction date 6 Transaction currency 7 Terminal country code 8 Transaction cryptogram (TC) 9 Application interchange profile (AIP) 10 Application transaction counter (ATC) 11 Unpredictable number 12 Terminal verification results (TVR) 13 Issuer application data (IAD) 14 Application usage control not present on the card, zero fill +2 A 2 The response code sent back by the acquirer in answer to an authorisation request, or the code generated by the terminal for transactions completed locally when real-time authorisation could not be achieved. +4 N 11 Authorised amount of the 9F02 transaction excluding adjustments +15 N 2 Cryptogram transaction type 9C +17 N 6 YYMMDD - This must be the date supplied to the card during the generation of the Transaction Cryptogram +23 N 3 ISO currency code of the transaction. See Appendix A +26 N 3 ISO country code indicating the country where the terminal is located See Appendix A +29 AB 16 Transaction Certificate (TC), Authorisation Request Cryptogram (ARQC) or Application Authentication Cryptogram (AAC). The preferred cryptogram is a TC for successful transactions. However an ARQC is acceptable if the TC is not available +45 AB 4 Indicates the application functions that are supported by the application in the IC +49 AB 4 Counter maintained by the application in the card for monitoring card usage. +53 AB 8 Value to provide variability and uniqueness to the generation of the application cryptogram +61 AB 10 Code recording the results of the tests carried out by the terminal during the EMV process +71 AB 64 Additional, undefined data, sent by the card issuer to enable authentication of the card. For file data element right justify and FF hex fill +135 AB 4 The ICC equivalent of the service code found on track 2 of the magnetic stripe. 8A 9A 5F2A 9F1A 9F F36 9F F10 9F07 12

18 Num Name Pos Type Len Description Tag Right justified and padded with FF s Indicates restrictions limiting the application geographically or to certain types of transactions 15 Cryptogram +139 AB 2 Indicates the type of cryptogram ie 9F27 information data TC, AAC, ARPC 16 CVM results +141 AB 6 The results of the cardholder verification method performed in the transaction 9F34 17 Application Identifier (AID) +147 AB 32 The Application identifier from the ICC. Shall be the DF name if this is longer 18 Application version +179 AB 4 Version number of ICC application 9F08 number 19 Transactions status +183 AB 4 9B information 20 Terminal Type +187 AB 2 The terminal type as defined in the 9F35 EMV specifications 21 Terminal +189 AB 6 The terminal capabilities as defined 9F33 capabilities in the EMV specifications 22 POS entry mode +195 A 2 Code that identifies how a transaction was completed and what cardholder verification was used see Table 2 9F39 23 FILLER +197 N 59 Space filled 4F Table 2 POS Entry Mode Position Value Description Digit 1 1 Swipe Card transaction information 2 Keyed 3 ICC 4 Recovered data, keyed 5 Recovered data, electronic 7 Downgrade ICC transaction 8 Swipe ICC failure 9 Proximity Digit 2 1 Customer present, signature Cardholder verification if any 2 Customer present, PIN 4 Customer present, UPT no CVM 5 Customer present, UPT, PIN 7 Customer not present 8 No verification Note: In the event of ICC card fallback to keyed input, the first digit of POS entry mode shall be set to 2. 13

19 Sub Records Sub-records are a way of capturing additional transaction data beyond that required to settle a transaction, e.g. purchasing line item details. Sub-records shall not be used in a Fixed Format file. If a transaction has sub-records attached: The transaction must use a File Format that includes sub-records L, R. The transaction must include a Segment 2 layout to count the sub-records. If the transaction has no specific Segment 2 requirements e.g. there is no cashback or purchasing etc, then a default Segment 2 shall be created which shall be in Reference Number or ML Layout (see Segment 2 (Type 50). All fields will be space-filled, except for the sub-record count, which shall reflect the number of sub-records following the transaction. The File Format must reflect the requirement for Segment 2 to be included. for example: An IC transaction is a File Format N (Segments 1 and 4 only). Adding Segment 2 changes the File Format to P (Segments 1, 2 and 4). Adding sub-records changes the File Format to R. Sub Records must be added in ascending Transaction Code order, failure to do so will in transactions being rejected Sub Record Format 26 Authorisation Network Reference Data (Scheme Reference Data/Acquirer Reference Data) Num Name Pos Type Len Description 1 Sub record counter 0 N 4 The sequence number of the sub record in relation to all sub records submitted for this transaction starting at 0001 and up to the Sub Record Count sent in Segment 2 2 Reserved for The UK Cards +4 A 12 Space filled Association 3 Authorisation reference type +16 N 3 Value = 001 Acquirer Reference Data Value = 002 Scheme Reference Data See Note 1 4 Transaction code +19 N 2 Value = 26 for this sub record 5 Authorisation network reference date 6 Authorisation network reference data 7 Record sequence number +21 N 6 Date of authorisation in YYMMDD format +27 A 56 Unique reference number returned by the authorisation network in the authorisation response message. Data must be left justified, space filled: MasterCard Trace ID 15 characters. Data should be supplied as: +27 Trace ID Visa Transaction ID 15 characters + Validation Code 4 characters. Data should be supplied as: +27 Transaction ID +42 Validation Code +83 N 7 Sequence number of this record within the file. 90 byte record Note 1: Acquirer Reference Data to be supplied only in the event of a Reversal Transaction. Scheme Reference Data to be supplied for all transactions authorised online. 14

20 Sub Record Format 01 General Sub Record Note: This record type is not currently supported by Global Payments Num Name Pos Type Len Description 1 Sub record counter 0 N 4 The sequence number of the sub record in relation to all sub records submitted for this transaction starting at 0001 and up to the 2 Reserved for The UK Cards Association Sub Record Count sent in Segment 2 +4 A 15 Space filled 3 Transaction code +19 A 2 Value = 01 for this sub record 4 Transit +21 A 2 See Table 1 below Transaction type 5 Transportation +23 A 2 See table 2 below mode 6 POI Capabilities +25 A 24 See Table 3 below 7 Payment +49 A 24 Attributes 8 Reserved +73 Reserved for UK Cards Association 9 Record Sequence Number +83 N 7 Sequence number of this record within the file 90 byte record Table 1 Transit Transaction type Identifier Codes Code Description 01 Prefunded 02 Real-time authorised 03 Post-Authorised Aggregated 04 Authorised Aggregated Split Clearing 05 Other 06 Reserved For Future Use 07 Debt Recovery Reserved For Future Use Table 2 Transportation Mode Indicator Codes Code Description 00 Unknown 01 Urban Bus 02 Interurban Bus 03 Light Train Mass Transit (Underground, Metro, LTR) 04 Train 05 Commuter Train 06 Water Borne 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 15

21 18 Trailer 19 Regional Train 20 Inter City 21 Funicular Train Table 3 POI Capabilities Note: This record type is not currently supported by Global Payments The POI Capabilities is a set of single character indicators as shown below. Posn. Capability Value Meaning 1 Cardholder Present P Cardholder Present N No Cardholder Present B Cardholder Present & not present capable 2 Cardholder Activated A Cardholder Activated N Not Cardholder Activated 3 Device Control A Card Acceptor Attended Device U Card Acceptor Unattended Device S Card Acceptor Semi-attended Device C Cardholder Controlled Device 4 Device Location P On Merchant Premises F Off Merchant Premises 5 Swipe M Mag Stripe Read Capable N No Mag Stripe read Capability 6 Contact ICC C Contact IC Device N No contact ICC 7 Contactless ICC F Full Contactless Capabilities M Mag stripe Contactless Only E EMV Contactless Only N No Contactless Capability 8 Keyed K Key Entry Possible N Key Entry Not Possible 9 On File A Account On File N Account from Another Source 10 Card Capture P Card Can Be Captured N Card Cannot Be Captured 11 PIN Capabilities B Full PIN capabilities (online and offline) F Offline PIN Only O Online PIN Only N No PIN capabilities 12 CDCVM H High Value Payments And CDCVM Supported L Low Value payments and No SDCVM Supported 13 Signature S Signature Capture Supported N Signature Cannot Be Captured 14 No CVM V No CVM Supported N No CVM Not Supported 15 mpos I mpos device with integrated card reader N Not an mpos device S mpos device with separate card reader 16 Reserved for UK Cards Association 0 17 Reserved for UK Cards Association 0 18 Reserved for UK Cards Association 0 19 Reserved for UK Cards Association 0 20 Reserved for UK Cards Association 0 21 Reserved for UK Cards Association 0 22 Reserved for UK Cards Association 0 23 Reserved for UK Cards Association 0 24 Reserved for UK Cards Association 0 16

22 Table 4 Payment Attributes Note: This record type is not currently supported by Global Payments The Payment attributes indicators in Error! Reference source not found. allow for the transaction to be identified with specific criteria to define further the nature of the payment. Posn. Attribute Value Meaning 1 Card Acceptor/Cardholder Agreement (see Note 1) I Instalment Payment N Not Applicable 2 Cardholder Not Present Condition (see Note 2) 3 Reserved for The UK Cards Association 4 Reserved for The UK Cards Association 5 Reserved for The UK Cards Association 6 Reserved for The UK Cards Association 7 Reserved for The UK Cards Association 8 Reserved for The UK Cards Association 9 Reserved for The UK Cards Association 10 Reserved for The UK Cards Association 11 Reserved for The UK Cards Association 12 Reserved for The UK Cards Association 13 Reserved for The UK Cards Association 14 Reserved for The UK Cards Association 15 Reserved for The UK Cards Association 16 Reserved for The UK Cards Association 17 Reserved for The UK Cards Association 18 Reserved for The UK Cards Association 19 Reserved for The UK Cards Association 20 Reserved for The UK Cards Association 21 Reserved for The UK Cards Association 22 Reserved for The UK Cards Association 23 Reserved for The UK Cards Association 24 Reserved for The UK Cards Association R C M N T E Recurring Payment Cardholder Not Present (unspecified) Mail Order Not Applicable (i.e. cardholder present) Telephone Order Electronic Commerce Note 1: Values other than N only to be used with cardholder present, cardholder not present, continuous authority or electronic commerce sale message types. Note 2: Values other than N only to be used with cardholder not present or electronic commerce message types 17

23 Scheme Digital Wallet Sub Records Note: These record types are not currently supported by Global Payments Sub Record Format 28 - V.Me by VISA Num Name Pos Type Len Description 1 Sub record counter 0 N 4 The sequence number of the sub record in relation to all sub records submitted for this transaction starting at 0001 and up to the 2 Reserved for The UK Cards Association Sub Record Count sent in Segment 2 +4 A 15 Space filled 3 Transaction code +19 A 2 Value = 28 for this sub record 4 Digital Wallet +21 N 5 Unique ID 5 Additional authentication Method +26 A 2 6 Additional Authentication Reason Code +28 A 2 7 Reserved +30 A 53 Reserved for UK Cards Association 8 Record Sequence Number +83 N 7 Sequence number of this record within the file 90 Byte Record Sub Record Format 30 MasterPass Online Num Name Pos Type Len Description 1 Sub record counter 0 N 4 The sequence number of the sub record in relation to all sub records submitted for this transaction starting at 0001 and up to the 2 Reserved for The UK Cards Association Sub Record Count sent in Segment 2 +4 A 15 Space filled 3 Transaction code +19 A 2 Value = 30 for this sub record 4 Wallet Transaction Origin +21 A 3 5 Reserved +24 A 59 Reserved for UK Cards Association 6 Record Sequence Number +83 N 7 Sequence number of this record within the file 90 Byte Record 18

24 Sub Record Format 39 Contactless Sub Record Num Name Pos Type Len Description 1 Sub record counter 0 N 4 The sequence number of the sub record in relation to all sub records submitted for this transaction starting at 0001 and up to the 2 Reserved for The UK Cards Association Sub Record Count sent in Segment 2 +4 A 15 Space filled 3 Transaction code +19 A 2 Value = 39 for this sub record 4 Reserved +21 A 62 Reserved for UK Cards Association 5 Record Sequence Number +83 N 7 Sequence number of this record within the file 6 Contactless Form +90 AB 70 Factor 7 Contactless +160 AB 70 Discretionary Data 8 Reserved +230 A 70 Reserved for UK Cards Association 300 Byte Record Contactless Form Factor The contents of this data element will vary by card scheme; for VISA and MasterCard it is Tag 9F6E, for American Express it is Tag 9F67.The definition of these data elements can be found in the appropriate scheme s contactless specifications. The card acceptor will provide the whole data element in BER-TLV format as described in EMV as the Tag will vary from card scheme to card scheme. When the data is converted to hexadecimal, the value of the length component shall still represent the length of the binary data. For example TTTTLLdddddd would be interpreted as: TTTT is the EMV Tag LL is the length of the data dddddd is the contactless form factor with the length as defined by LL Data should be left justified and space filled Contactless Discretionary Data The contents of this data will vary by card scheme and will be as agreed by interchange parties. For VISA the discretionary data will be the content of Tag 9F7C. The definitions for these data elements can be found in the appropriate card scheme s contactless specifications. The card acceptor will provide the whole data element in BER-TLV format as described in EMV as the Tag will vary from card scheme to card scheme. When the data is converted to hexadecimal, the value of the length component shall still represent the length of the binary data. 19

25 Net Summary Record Num Name Pos Type Len Description 1 Reserved 0 N 19 Zero fill 2 Transaction code +19 A 2 n4, n5, n6 Note: Fixed file n is either E or J Variable file n = E 3 Source number +21 N 11 As defined by GP, zero filled from the left 4.1 Net summary currency code +32 A 3 Currency codes applicable for GP. Country Numeric value United Kingdom 826 European Euro 978 Hong Kong Dollars 344 Japanese Yen 392 US Dollars 840 Australian Dollars 036 New Zealand Dollars 554 Canadian Dollars 124 Singapore Dollars 702 Norwegian Dollars 578 Danish Krona 208 Swedish Krona 752 Swiss Franc 756 If Zero filled then currency is as defined within transaction. Note: Currency processing via GP is not available to all customers. It must first be agreed by GP. If valid ISO currency code then all attached transactions in the batch conform to the reported currency on the summary record. 4.2 Reserved for APACS +35 A 1 Space filled 5 Net amount +36 N 11 Net amount of fields 6.1 and 6.2 in the lowest denomination (unsigned) of the currency being used or that which is specified in Totals 6.1 Value of debit items +47 N 11 n4 n5 n6 Totals Totals Totals n1 n1 n3 6.2 Value of credit items +58 N 11 n4 n5 n6 Totals Totals Totals n2 n2 zeros 6.3 Count of debit items +69 N 7 n4 n5 n6 Totals Totals Totals n1 n1 n3 6.4 Count of credit items +76 N 7 n4 n5 n6 Totals Totals Totals n2 n2 zeros 7 Record sequence +83 N 7 Sequence number of this record within the number 8 Filler applicable to fixed format only file +80 A V Space Fill 90 byte fixed or 380 byte fixed 20

26 Net Claim Record Num Name Pos Type Len Description 1 Claimants bank 0 A 19 Zero fill not used by GP account detail or reference number 2 Transaction code +19 A 2 n7 payment by retailer (Refunds exceed sales total of n5> total of n4 + n6) n8 Claim by retailer (Sales exceed refunds total of n4 + n6 >= total of n5) Note: Fixed file format n is either E or J Variable file format n = E 3 Accounting unit +21 N 11 Zero fill not used by GP number 4.1 Currency code +32 N 3 If zero filled, then default currency is GBP. If ISO currency code then all transactions in the batch conform to the reported currency on the summary/claim record 4.2 Reserved +35 A 1 Space fill 5 Net claim amount +36 N 11 Net value of the claim in the lowest denomination, unsigned, of the currency being used or that specified in Value of debit summary items +47 N 11 Value of all debit summary items (n4 and /or n6) since last claim record, in the lowest denomination, unsigned, of the currency 6.2 Value of credit summary items 6.3 Count of debit summary items 6.4 Count of credit summary items 7 Record sequence number 8 Filler applicable to fixed format only being used or that specified in N 11 Value of all credit summary items (n5) since last claim record, in the lowest denomination, unsigned, of the currency being used or that specified in N 7 Count of all debit summary items (n4 and /or n6) since last claim record. +76 N 7 Count of all credit summary items (n5) since last claim record. +83 N 7 Sequence number of this record within the file +80 A V Space Fill 90 byte fixed or 380 byte fixed 21

27 First File Trailer Label EOF1 Num Name Pos Type Len Description 1 Label identifier 0 A 3 EOF 2 Label number +3 A Source identifier or originator +4 A 10 Head office ID as advised by GP, as VOL1 record 3.2 Record type identifier +14 A 1 E value (Fixed 90 byte records) J value (Fixed 380 byte records) Z value (Variable length records >90 <=636) 3.3 Reserved +15 A 2 Space fill 3.4 File currency indicator +17 A 1 0 Not used by acquirer 3.5 Reserved +18 A 3 Space fill 4 File set identification +21 A 6 Zero fill 5 File section number +27 A File sequence number +31 A Generation number +35 A Generation version +39 A 2 00 number 9 Creation date +41 N 6 Date file produced, in the form byyddd, where b is blank space. YY is the last two digits of the year and DDD ( ) is the day of the year. Field must be equal to the processing date of the UHL label 10 Expiration date +47 N 6 Earliest date at which file may be overwritten, in the form byyddd. Calculate as 14 days greater than creation date. 11 Accessibility +53 A 1 Space fill 12 Block count +54 N 6 Zero fill 13 System code +60 A 13 Space fill 14 Reserved +73 N 7 Space fill 15 Filler applicable to fixed format only +80 A V Space Fill 90 byte fixed or 380 byte fixed Second File Trailer Label EOF2 Num Name Pos Type Len Description 1 Label identifier 0 A 3 EOF 2 Label number +3 A Record format +4 A 1 F value (Fixed length) D value (variable length) 4 Block length +5 N value (E Fixed records) value (J Fixed records) value (M Variable records) 5 Record length +10 N value (E Fixed records) value (J Fixed records) value (M Variable records) 6 Reserved +15 A 35 Space fill if not used 7 Offset length +50 N 2 Zero fill 8 Reserved +52 A 28 Space fill 9 Filler applicable to fixed format only +80 A V Space Fill 90 byte fixed or 380 byte fixed 22

28 User Trailer Label UTL1 Num Name Pos Type Len Description 1 Label Identifier 1 A 3 UTL 2 Label Number +3 N Value of debit items +4 N 13 Monetary total of all debit (net claim) records (n8) since preceding HDR Label Group. This is a hash total 3.2 Value of credits +17 N 13 Monetary total of all credit (net claim) records (n7) since preceding HDR Label Group. This is a hash total 3.3 Count of debits +30 N 7 Count of all debit (net claim) records (n8) since preceding HDR Label Group 3.4 Count of credits +37 N 7 Count of all credit (net claim) records (n7) since preceding HDR Label Group 3.5 Record count +44 N 10 Total number of records since the preceding HDR Label Group. 3.6 Filler Space fill 4 Filler applicable to fixed format only +80 A V Space Fill 90 byte fixed or 380 byte fixed Appendix A ISO Country And Currency Codes ISO Code Currency Description ISO Number EUR Euro 978 STG Sterling 826 USD US Dollar 840 JPY Japanese Yen 392 AUD Australian Dollar 036 HKD Hong Kong Dollar 344 CHF Swiss Franc 756 CAD Canadian Dollar 124 NZD New Zealand Dollar 554 SEK Swedish Krona 752 NOK Norwegian Krone 578 DKK Danish Krone 208 SGD Singapore Dollar

29 Authorisation Authorisation Messages The information in this section is valid for all transactions sent to the Global Payments authorising host individually. Authorisation Request Message An authorisation request message is a standard message sent to Global Payments by a merchant when a transaction amount is above its floor limit. For Account Verification, the transaction amount value must always be set to Zero and the transaction type is applicable to MasterCard and Visa transactions. Currency Transactions For currency transactions, the currency code must be included in the authorisation message, otherwise the transaction will be processed as the default currency ie 826 (GBP). Message Contents Key A Alphanumeric characters ASCII characters in the range 0 to 9, A to Z, a to z,, $, % etc (ie HE 20 to 7E F Fixed H Hexadecimal (ASCII representation of characters 0-9, A-F) M Mandatory N Numeric (ASCII representation of characters 0-9) O Optional V Variable FS Field separator (ASCII code 1C ) US Unit separator (ASCII code 1F ) RS Record separator (ASCII code 1E ) GS Group separator (ASCII code 1D ) B24 BASE 64 Encoding/Decoding (refer APACS 70 for more detailed information) Reversals In order to reverse a transaction, the reversal message must be sent on the same day as the original authorisation message in order to prevent transactions where the authorisation has been reversed being inadvertently settled. Whilst reversal messages do not need to follow immediately after the original sale transaction, the scheme reference data and acquirer reference data from the original authorisation response must be provided in the reversal request message. Where there is a need to reverse a transaction after close of business on the day of the original this should be done as a refund. Global Payments will not accept responsibility for any scheme fees or charges resulting from authorisation messages being reversed after they have been settled or, when the necessary scheme and acquirer reference data have not been provided in the reversal request message. Partial Reversals The transaction amount in the reversal should contain the amount to be reversed. For a partial reversal, this amount must be less than the amount originally authorised. The Global Payments authorisation host does not require the originally authorised amount to be sent in the Auxiliary data record type 09 Approval Amount (record layout not show in this document as it is not needed). 24

30 Message Format For Authorisation Request No Size F/V M/O/C Range Name Comment 0 1 F M N Dial Indicator This number is incremented for each dial attempt: 1 = 1 st dial 2 = 2 nd dial 3 = 3 rd dial (2 nd NUA if available) 4 = Non dial (Host link) 1 8 F M N Terminal Identity The first 4 digits are the Merchants APACS Retailer ID (RID). The last 4 digits are used by the merchant to uniquely identify the terminal 2 4 F M N Message Number This number is allocated sequentially by the merchant. Message numbers should not be reset at the start or end of day for a given Terminal ID 3 4 F M H Terminal Type/Capabilities Code indicating terminal capabilities. See Table F M A Message Type Code indicating transaction type and category See Table V M N Merchant Number Merchant number issued by GP 6 1 F M FS Field Separator Hex 1C 7 40 V M A Card Details The contents of this field vary according to the mode of entry. See Table F M FS Field Separator 9 11 V M N Transaction Amount Amount of the transaction in the currency minor denomination, including cash element if applicable. Minimum 2 digits shall be sent (for example 1 penny is sent as 01) maximum 11 digits 10 1 F M FS Field Separator V O A Descriptive Data Additional data specific to the transaction for example CSC and/or address data. See Table F C7 FS Field Separator Reserved Not used 14 1 F C7 FS Field Separator 25

31 No Size F/V M/O/C Range Name Comment 15 1 F C11 A Authorisation Status 16 1 F C7 FS Field Separator V C5 N Cash back Amount Cash amount (amount 2 PWCB) in minor denomination of currency. Minimum 2 digits shall be sent (for example 1 penny is sent as 01) maximum 11 digits 18 1 F C7 FS Field Separator F C1 N Transaction Date and Time (YYMMDDhhmm) This indicates the time the transaction was generated 20 1 F C7 FS Field Separator 21 2 F C4 N EMV terminal type EMV Terminal Type values for chip and PIN refer EMVco 22 1 F C7 FS Field Separator 23 3 F C1 N Terminal country code 24 1 F C7 FS Field Separator 25 3 F C1 N Transaction currency code 26 1 F C1 FS Field Separator 27 2 F C9 N Reason on-line Code 28 1 F C7 FS Field Separator V C2 H,US ICC Authorisation Request data (Prohibited for non- ICC transactions) F C2 H ICC authorisation request cryptogram (ARQC) C2 H Application Interchange Profile (AIP) C2 H Application Transaction Counter (ATC) C2 H Terminal Random Number (TRN) C2 H Terminal Verification Results (TVR) C2 N Cryptogram Transaction Type 29.7 up to 64 V C2 H Issuer Application Data (IAD) Country where the terminal is located The currency in which the transaction is conducted A code which indicates the reason the terminal connected real time to the acquirer, or did not connect real time to the acquirer A cryptogram generated by the card requesting on-line authorisation Specifies the application functions that are supported by the application in the ICC A device for monitoring card usage Coded values recording the results of the tests the terminal carried out during the EMV processing Specifies the types of transactions the IC shall perform Additional, undefined data sent by the card to the issuer to enable authentication of the card 26

32 O M C1 C2 C3 C4 C5 No Size F/V M/O/C Range Name Comment C8 US Unit Separator 29.9 up to 32 C3 HB Application Identifier Data (AID) C8 US Unit Separator C3 H Application Version Number C3 US Unit Separator C3 H Cryptogram Information Data C8 US Unit Separator C2 H Card Verification Method (CVM) results C7 FS Field Separator 31 up to 480 C10 A Auxiliary data Record(s) C7 FS Field Separator C6 - C7 C8 C9 C10 C11 The application ID from the ICC card. Indicates the type of cryptogram. eg TC The following auxiliary data types are supported: E Commerce Dynamic Currency Conversion (DCC) Extended Terminal Capabilities Scheme Reference Data It is anticipated that a maximum of 2 auxiliary data records will be present as E Commerce and Contactless are mutually exclusive. Optional Mandatory Mandatory for ICC transactions, Optional for non-icc transactions Mandatory for ICC transactions (if present) including reversals, prohibited for non-icc transactions Optional for ICC transactions, prohibited for non-icc transactions Mandatory for ICC transactions and E Commerce transactions, Optional for other transactions Mandatory for Purchase with Cash back transactions, including reversals, prohibited for other transactions Mandatory if subsequent fields are present Mandatory if subsequent sub fields are present in the field Mandatory for ICC and ICC fallback transactions including reversals, optional for non-icc transactions Mandatory if terminal supports response Auxiliary Data The authorisation status is currently mandatory for MasterCard Transactions but is optional for other card schemes. For MasterCard transactions, the authorisation status shall be set to E where the final amount of the transaction is not known and may differ from the amount sent in the amount sent in the authorisation request message and shall be set to A if the final amount of the transaction is known i.e. The amount to be settled will be the same as the amount authorised 27

33 Table 3 Terminal Type Codes It is essential that the following data is as accurate as possible. If the terminal s true capabilities are not accurately described by this data, then the Global Payments authorising host or the card issuer may not approve the transaction. For example, MasterCard have strict rules concerning the acceptance of cards at Unattended/Cardholder Activated Terminals which are triggered if the fourth position indicates Unattended device support. First position Terminal Capabilities Second position Number of 16 lines which can be displayed or printed (0) indicates display or printer not available Third position Response message capabilities Fourth position Additional features and capabilities (0) indicates no additional capabilities supported Feature ICC Reader Magnetic Stripe Reader (MSR) Manual Card Reader Extended Terminal Capabilities (see Note 1) Lines of display available Down line loading Referral tel. no. Hold capability Down line loading floor limits/data Response additional data support Unattended device PINPAD available Terminal or operator able to capture cards Cardholders device (for example, may be a PC, mobile phone, PDA, digital TV or similar device for E or M commerce Note 1: If this bit is set then the data supplied is the extended terminal capabilities and attributes auxiliary data messages takes priority. See Terminal Attribute Codes'. 28

34 Table 4 Message Type Type Description Message Class Direction Category Notes 03 Purchase with Authorisation Request Card 1 st try Swipe cash back 04 Purchase with Authorisation Request Keyed 1 st try cash back 05 Purchase with Authorisation Request Card Re-try Swipe cash back 06 Purchase with Authorisation Request Keyed Re-try cash back 09 Purchase Authorisation Request No 1 st try Keyed cardholder present cardholder 10 Purchase Authorisation Request Card 1 st try Swipe 16 Purchase Authorisation Request Card Re-try Swipe 20 Purchase Authorisation Request Keyed 1 st try Customer Present 25 Debit reversal Authorisation Request - 1 st try Cancel at signature 26 Purchase Authorisation Request Keyed Re-try Customer Present 28 Debit reversal Authorisation Request - Re-try 30 Cash Authorisation Request Card 1 st try Swipe 31 Cash Authorisation Request Keyed 1 st try 36 Cash Authorisation Request Card Re-try Swipe 37 Cash Authorisation Request Keyed Re-try 45 Purchase cardholder not present Authorisation Request No cardholder Re-try 47 Refund cardholder not present 49 Refund cardholder not present Authorisation Request No cardholder Authorisation Request No cardholder 1 st try Re-try Keyed 58 Refund Authorisation Request Card 1 st try Swipe 61 Refund Authorisation Request Keyed 1 st try 63 Refund Authorisation Request Card Re-try 67 Refund Authorisation Request Keyed Re-try A0 Purchase continuous authority A1 Purchase continuous authority A8 A9 AA Purchase electronic commerce Purchase electronic commerce Refund electronic commerce Authorisation Request No cardholder Authorisation Request No cardholder 1 st try Re-try Authorisation Request Card 1 st try Authorisation Request Card Re-try Authorisation Request Card 1 st try 29

35 Type Description Message Class Direction Category Notes AB Refund Authorisation Request Card Re-try electronic commerce B2 Purchase Authorisation Request Keyed 1 st try electronic commerce B3 Purchase Authorisation Request Keyed Re-try electronic commerce B4 Refund Authorisation Request Keyed 1 st try electronic commerce B5 Refund Authorisation Request Keyed Re-try electronic commerce E6 Account Authorisation Request Card 1 st try See Note 1 Verification E7 Account Authorisation Request Card 2 nd try See Note 1 Verification E8 Account Authorisation Request Keyed 1 st try See Note 1 Verification E9 Account Authorisation Request Keyed 2 nd try See Note 1 Verification EA Account Authorisation Request CNP 1 st try See Note 1 Verification EB Account Authorisation Request CNP 2 nd try See Note 1 Verification EC Ecommerce/ Authorisation Request Keyed 1 st try See Note 1 Account Verification ED Ecommerce/ Account Verification Authorisation Request Keyed 2 nd try See Note 1 Note 1: For Account Verification, the transaction amount must always be ZERO and is applicable to MasterCard and Visa transactions. 30

36 Table 5 Card Details Magnetic Stripe Read (MSR) - Track 2 Data No Size F/V M/O/C Range Note A 40 V M A Unaltered contents of Magnetic Stripe Read track 2 including the SS, ES and LRC Manual Key Entered (PKE) No Size F/V M/O/C Range Note a 1 F M US Unit Separator b 25 V M N PAN c 1 F O US Unit Separator d 4 F O N Expiry date (entered as MMYY but sent as YYMM) - see Note 1 e 1 F O US Unit Separator f 2 V C N Issue number if required by Card Scheme ICC Supplied Equivalent Track 2 Data see Note 2 No Size F/V M/O/C Range Note a 37 V M A ICC track 2 data (TAG 57 ) b 1 F M US Unit Separator c 2 F O N ICC Application PAN sequence number ICC (Tag 5F34 ) IC Constructed Track 2 Equivalent Data Field see Note 3 No Size F/V M/O/C Range Note a 19 V M N ICC PAN (tag 5A ) b 1 F M US Unit Separator c 4 F M N Leftmost 4 characters (YYMM) of ICC expiry date (ICC (Tag 5F24 )) d 1 F O US Unit Separator e 2 F O N ICC PAN sequence number (ICC (Tag 5F34 )) Note 1: If there is no issue number on a card that has been key entered, the expiry date must be followed immediately by field 8 (Field separator) and not a Unit separator. When a start date has been entered as part of the key entered transaction, the start date must not be transmitted with the authorisation message request. Note 2: Each 4 bit nibble of data in sub-field a will be prefixed with binary 011 with even parity inserted on bit 8. If rightmost (least significant) 4 bit nibble of data element a is hex value F this should be discarded. Sub field c is missing if the Application PAN sequence number data object Tag 5F34 is not present on the card. Sub field b is mandatory if sub field c is present. Note 3: Sub field d and e are missing if Application PAN sequence number data object Tag 5F34 is not present on the card. Sub field e is mandatory is sub field e is present. The terminal shall always check for the presence of Track 2 Equivalent Data object Tag 57 and if it is present use this in the authorisation message from the terminal. 31

37 Table 6 Descriptive Data CSC And/Or Address Data Field Data 1 The 3 (in the case of Amex 4) digit CSC data 2 US Unit Separator 3 The first 5 numeric from the Postcode (In the UK this will be 2 or 3 digits only) 4 US Unit Separator 5 Numerics from address, truncated if required (These are the leading numerics from each line of the address up to maximum 5 digits Note 1: The validation of the CSC depends on the correct expiry date being submitted in addition to the CSC value. All address data shall relate to the customer s statement/billing address. Note 2: If this format is used, the two US characters are mandatory even if one or more of the sub elements are not populated. Auxiliary Data Records Example Construction Format 1 to be used in Authorisation Request Messages No Size F/V M/O/C Range Name Comment F M FS Field Separator F M N Auxiliary data message terminal capabilities F M N Auxiliary data message size limit 31.n.n V O Auxiliary data Variable length based on record 1 st 31.n.n V O Auxiliary data record 2 nd (if applicable) 31.n.n V O Auxiliary data record 3 rd (if applicable) 31.n.n V O Auxiliary data record 4 th (if applicable) 31.n.n 1 F M FS Field Separator Format 2 to be used in Authorisation Response Messages Auxiliary data message size limit Variable length based on Auxiliary data message size limit Variable length based on Auxiliary data message size limit Variable length based on Auxiliary data message size limit No Size F/V M/O/C Range Name Comment F M FS Field Separator F M N Residual auxiliary message count 32.n.n V O A 1st Auxiliary data record Variable length based on Auxiliary data message size limit 32.n.n V O A 2nd Auxiliary data record Variable length based on Auxiliary data message size limit 32.n.n V O A 3rd Auxiliary data record Variable length based on Auxiliary data message size limit 32.n.n V O A 4th Auxiliary data record Variable length based on Auxiliary data message size limit 32.n.n V O A nth Auxiliary data record Variable length based on Auxiliary data message size limit 32.n.n 1 F M FS Field Separator 32

38 E-Commerce Auxiliary Data Record Type 01 C1 No Size F M/O/C Range Name Comment / V O A Auxiliary Data Record M RS Record Separator M A Data Record type Value = 01 Electronic Commerce M N Data Record Subtype Value = M GS Group Separator M H Additional Transaction Security Data See table for See Table 7 breakdown C1 GS Group Separator O B64 Cardholder Authentication Value C1 GS Group Separator O B64 Cardholder Certificate Serial Number (SET only) C1 GS Group Separator O B64 Merchant Certificate Serial Number (SET only) C1 GS Group Separator O B64 Transaction ID / CAVV C1 GS Group Separator O B64 TransStain (SET only) C1 GS Group Separator O N Electronic Commerce Indicator C1 GS Group Separator Reserved for Future Use Up to 32 characters supplied by the merchant, are 32 characters for MasterCard UCAF, 28 characters for Visa 3D Secure CAVV 28 character Transaction ID issued as part of the authentication process This field must only be populated if the ECI is provided by the Merchant. It is provided directly by the authentication/verification system or as per the respective scheme guidelines. Otherwise it is omitted The ECI value takes precedent over any E Commerce setting of the EMV terminal type. Fields may be omitted. If any subsequent fields are present then the field delimiter GS for an omitted field must be included. 33

39 Table 7 - Additional Transaction Security Data (ATSD) Position 1 Value Security Capability MasterCard Securecode SET Verified by Visa Channel Encryption (SSL) Position 2 Certificates Card acceptor certificate Cardholder certificate ICC Cryptogram Reserved Position 3 Security Attempted MasterCard Securecode SET Verified by Visa Channel Encryption (SSL) Position 4 Security Results Authentication successful Evidence of attempted authentication System unable to verify Reserved Position 5 Reserved Position 6 Reserved The values of the first second and third positions are each cumulative in that they records all the features available or used in a transaction. Value settings for position 4 are mutually exclusive. 34

40 Dynamic Currency Conversion (DCC) Auxiliary Data Record 03 No Size F/V M/O/C Range Name Comment O A Auxiliary Data Record M RS Record Separator M A Data Record type Value = 03 Dynamic Currency Conversion (DCC) M N Data Record Sub-type Value = M GS Group Separator M N Currency Amount Transaction Amount prior to DCC, in the card acceptor currency minor denomination M GS Group Separator M N Currency Code Transaction currency code prior to DCC M N Conversion Rate Conversion rate used in the DCC transaction, as printed on the receipts. See Note M GS Group Separator M N Commission Fee Commission fee on the DCC transaction, in the cardholder currency minor denomination M GS Group Separator M N Mark Up Fee The Mark Up percentage applied to the DCC transaction to 4 decimal places O GS Group Separator O N Opt Out Marker Marker to indicate whether, or not, the cardholder was offered DCC but chose to pay in sterling (1 = DCC offered but not accepted, 0 = DCC offered and accepted) Note 1: As detailed in APACS Standard 70, Book 2, , the DCC exponent should contain up to 2 numeric characters and denote the number of positions the decimal separator shall be moved from the right in the DCC rate which may contain up to 21 numeric characters. For example, a value of 6<US> specifies a conversion rate of

41 Scheme Reference Data Record, Sub-type 01 This data is sent and received in the Auxiliary Data Field in the Authorisation Request/Response messages (see Page 27). This data is passed to the Global Payments authorising host by the Card Scheme and forwarded by the Global Payments authorising host if the terminal has indicated that it is capable of processing transaction identifiers. It should be captured and submitted as part of the Clearing Data (see Sub Record Format 26) for the original authorisation and any associated consequent authorisations, for example, on incremental authorisations or recurring payments. No Size F/V M/O/C Range Name Comment 1 1 F M RS Record Separator 2 2 F M N Data record type Transaction identifiers = F M N Data record sub-type = F M GS Group Separator 5 56 V M A Scheme Reference Data Comprising a string of up to 56 characters :- MasterCard Trace ID 15 characters Visa Transaction ID 15 characters Validation Code 4 characters Acquirer Reference Data Record, Sub-type 02 This data is sent and received in the Auxiliary Data Field in the Authorisation Request/Response messages (see Page 27). This data is generated by the Global Payments authorising host if the terminal indicates that it can support transaction identifiers (in Position 2 of the Terminal Attribute Codes in Auxiliary Data Record 6) and passed to the Point of Sale in the authorisation response message. The data must be included on any consequent reversal; otherwise the Global Payments authorising host will not send the reversal online to the card issuer. No Size F/V M/O/C Range Name Comment 1 1 F M RS Record Separator 2 2 F M N Data record type Transaction identifiers = F M N Data record sub-type = F M GS Group Separator 5 56 V M A Acquirer Reference Data Comprising a string of up to 56 characters. Note - Global Payments will return 16 characters in this field 36

42 Transit Program Data Record Type 11 Note: This record type is not currently supported by Global Payments This record is used in the authorisation request to supply detailed transit program information. No Size F/V M/O/C Range Name Comment 1 1 F M RS Record Separator 2 2 F M N Data record type Transit Program = F M N Data record sub-type = F M GS Group Separator 5 2 F M NA Transit Transaction Type Identifier See Table 1 below for acceptable values 6 2 F M N Transportation Mode Indicator Table 1 Transit Transaction Type Identifier Codes Code Description 01 Prefunded 02 Real-time authorised 03 Post-Authorised Aggregated 04 Authorised Aggregated Split Clearing 05 Other 06 Reserved For Future Use 07 Debt Recovery Reserved For Future Use Table 2 Transportation Mode Indicator Codes Code Description 00 Unknown 01 Urban Bus 02 Interurban Bus 03 Light Train Mass Transit (Underground, Metro, LTR) 04 Train 05 Commuter Train 06 Water Borne 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 Inter City 21 Funicular Train See Table 2 Below for acceptable value 37

43 Scheme Digital Wallet Data Record Type 13 Note: These record types are not currently supported by Global Payments This record is used to support electronic commerce transactions originating from a scheme digital wallet V.Me by VISA, Sub type 01 No Size F/V M/O/C Range Name Comment 1 1 F M RS Record Separator 2 2 F M N Data record type Scheme Digital Wallet = F M N Data record sub-type = V.Me by VISA F M GS Group Separator 5 5 F M A Digital Wallet Unique ID 6 1 F C1 GS Group Separator 7 2 F O A Additional Authentication Method 8 1 F C1 GS Group Separator 9 2 F O A Additional Authentication Reason Code C 1 Mandatory if subsequent fields are present MasterPass Online, Sub type 10 No Size F/V M/O/C Range Name Comment 1 1 F M RS Record Separator 2 F M N Data record type 2 Scheme Digital Wallet = 13 3 F M N Data record sub-type = MasterPass Online F M GS Group Separator 5 3 F M A Wallet Transaction Origin 38

44 Contactless Device Information Data Record Type 15 No Size F/V M/O/C Range Name Comment 1 1 F M RS Record Separator 2 2 F M N Data record type Contactless Device Information = F M N Data record sub-type = Version F M GS Group Separator 5 70 F M H Contactless Form Factor 6 1 F C1 GS Group Separator 7 70 O H Contactless Discretionary Data C 1 Mandatory if subsequent fields are present Contactless Form Factor The contents of this data element will vary by card scheme; for VISA and MasterCard it is Tag 9F6E, for American Express it is Tag 9F67.The definition of these data elements can be found in the appropriate scheme s contactless specifications. The card acceptor will provide the whole data element in BER-TLV format as described in EMV as the Tag will vary from card scheme to card scheme. When the data is converted to hexadecimal, the value of the length component shall still represent the length of the binary data. For example TTTTLLdddddd would be interpreted as: TTTT is the EMV Tag LL is the length of the data dddddd is the contactless form factor with the length as defined by LL Data should be left justified and space filled Contactless Discretionary Data The contents of this data will vary by card scheme and will be as agreed by interchange parties. For VISA the discretionary data will be the content of Tag 9F7C. The definitions for these data elements can be found in the appropriate card scheme s contactless specifications. The card acceptor will provide the whole data element in BER-TLV format as described in EMV as the Tag will vary from card scheme to card scheme. When the data is converted to hexadecimal, the value of the length component shall still represent the length of the binary data. 39

45 Payment Attributes Data Record Type 18 Note: This record type is not currently supported by Global Payments No Size F/V M/O/C Range Name Comment 1 1 F M RS Record Separator 2 2 F M N Data record type Payments Attributes = F M N Data record sub-type = Version F M GS Group Separator 5 24 F M A Payment Attributes Payment Attributes The Payment Attributes indicators allow for the transaction to be identified with specific criteria to define further the nature of the payment Pos Attribute Value Meaning No 1 Card Acceptor/Cardholder Agreement I Instalment Payment N Not Applicable 2 Reserved For The UK Cards Association 3 Reserved For The UK Cards Association 4 Reserved For The UK Cards Association 5 Reserved For The UK Cards Association 6 Reserved For The UK Cards Association 7 Reserved For The UK Cards Association 8 Reserved For The UK Cards Association 9 Reserved For The UK Cards Association 10 Reserved For The UK Cards Association 11 Reserved For The UK Cards Association 12 Reserved For The UK Cards Association 13 Reserved For The UK Cards Association 14 Reserved For The UK Cards Association 15 Reserved For The UK Cards Association 16 Reserved For The UK Cards Association 17 Reserved For The UK Cards Association 18 Reserved For The UK Cards Association 19 Reserved For The UK Cards Association 20 Reserved For The UK Cards Association 21 Reserved For The UK Cards Association 22 Reserved For The UK Cards Association 23 Reserved For The UK Cards Association 24 Reserved For The UK Cards Association 40

46 Terminal Capabilities And Terminal Attributes Auxiliary Data Record 06 (Contactless/Proximity Cards) No Size F/V M/O/C Range Name Comment O A Auxiliary Data Record M RS Record Separator M A Data Record type Value = 06 Extended terminal capabilities and attributes M N Data Record Sub-type Value = 01 Transaction details M GS Group Separator M H Terminal Attributes Code indicating the terminal attributes M GS Group Separator M H Terminal Attributes used Code indicating the terminal attributes used C1 GS Group Separator C2 H EMV Terminal Capabilities C1 GS Group Separator O H EMV Terminal Capabilities used C1 Mandatory if subsequent fields are present. C2 Mandatory for ICC transactions, Optional for non-icc transactions. The terminal capabilities as defined in EMV (ICC[Tag 9F33 ]) The terminal capabilities used values are mapped to the EMV terminal capabilities and indicate which capabilities were used in this transaction 41

47 Terminal Attributes The terminal codes in the table below lists the values used for both the terminal attributes data element and terminal attributes used data elements. The terminal attributes data element identifies the features supported by the terminal and the terminal attributes used data element identifies which of those features were used in the transaction being processed. For any terminal that supports these data elements, the terminal attributes data element shall be included in all authorisation and financial presentment messages regardless of the terminal attributes used for the transaction being processed. Terminal Attribute Codes Feature Position 1 Contactless reader magstripe format Read Capabilities Contactless reader EMV format Reserved for The UK Cards Association Reserved for The UK Cards Association Position 2 Response Message Partial/alternative amount approval responses supported Capabilities Transaction identifiers supported Alternate card number supported Reserved for The UK Cards Association Position 3 Contactless signature Contactless CVM Contactless CDCVM Reserved for The UK Cards Association Reserved for The UK Cards Association Position 4 MPoS with integrated card reader Mobile Point of Sale MPoS with separate card reader Reserved for The UK Cards Association Reserved for The UK Cards Association Position 5 Reserved for The UK Cards Association Reserved for The UK Cards Association Reserved for The UK Cards Association Reserved for The UK Cards Association Position 6 Reserved for The UK Cards Association Reserved for The UK Cards Association Reserved for The UK Cards Association Reserved for The UK Cards Association 42

48 Response Or Referral Message In Response To An Authorisation Request No Size F/V M/O/C Range Name Comment 0 1 F M N Terminal Dial Indicator Taken from authorisation request 1 8 F M N Terminal Identity Taken from authorisation request 2 4 F M N Message Number Taken from authorisation request 3 2 F M N Message Type Set to F M N Acquirer Response Code A code sent back by the acquirer to indicate a specific action is to be undertaken by the terminal - See Table F M N Confirmation Request Set to V O A Authorisation Code This field is not currently used by GP. The authorisation code is present in field F M FS Field Separator 8 11 V O N Amount This field is not used by GP 9 1 F M FS Field Separator V M A Message Text See Table F M FS Field Separator V O N, US Voice Referral Phone Number Not used by GP 13 1 FS O FS Field Separator 14 3 V O N Floor Limit Duality This field is not used by GP 15 1 F O FS Field Separator As now 16 4 F O N Date Format YYMM 17 1 F O FS Field Separator As now V O A ICC response data Include if ICC transaction 19 1 F O FS Field Separator Included (where field 20 is populated) 20 6 F O A Response additional data the results of the CV2 and AVS checks Included (where CV2/AVS data supplied in auth request) See Table 9. Where the terminal has indicated it is capable of processing Response Additional Data in the Third Position of the Terminal Type Codes see Table F O FS Included (where CV2/AVS data supplied in auth request) V O A Auxiliary Data See Auxiliary Data Records Tables 23 1 F O FS Field Separator Notes: The Return Code is contained in field 4 of the authorisation response message record (variable length layout). If a referral is received in the live environment then the transaction should not proceed until a manual Authorisation code has been obtained from Global Payments Voice Authorisation Centre. 43

49 Table 8 Response Codes And Message Text Response Code Message Text Reason 00 Auth code: nnnnnn Approve 02 Call Auth Centre Referral 02 Call Auth Centre Referral Usage 02 Call Auth Centre Referral Fraudulent Use 03 Invalid Merchant Merchant Unknown /Merchant number has not been set up on authorisation system 04 Decline & Pickup 05 Decline Decline (N/A reversals) 05 Cannot Authorise Terminal ID is unrecognised 05 Consent Revoked Cardholder has ended a Recurring Payment or Instalment 05 Invalid Tran 05 Unable to Auth 12 Request Invalid 13 Invalid Amount Request Invalid (Non numeric amount) 14 Invalid Card No Request Message has invalid amount 30 Bad Format Request message has invalid format 30 Bad Amount Amount Field is not numeric 30 Bad Expiry Date Expired card 30 Invalid Track2 54 Expired Card 58 Terminal ID Invalid Table 9 - Response Additional Data Codes Feature First position Not Checked CSC Matched Not Matched Reserved for APACS Second position Not Checked Post Code Matched Not Matched Partial Match Third Position Not Checked Address Numeric Matched Not Matched Partial Matched Fourth Position Not used by GP Authorising Entity Acquirer Not used by GP Not used by GP Fifth Position Reserved Reserved Reserved Reserved Reserved Sixth Position Reserved Reserved Reserved Reserved Reserved 44

50 Notes: Values other than 0, 1, 2, 4, or 8 are not valid in positions 1 to 3. A value of zero in any position indicates that no additional information is available. If the authorising entity is not known character 4 is set to zero and is assumed to be the issuer. ICC Data The Global Payments technical specifications to support ICC on our Card Processing Service, stipulates that certain data must be present in accordance with Card Scheme requirements. In order to complete the certification process with us, you must provide evidence that the data in these fields has been populated as required. In the case of ICC data the following information must be provided in addition to the test scripts, test file and receipts (where applicable):- Transaction Cryptogram (TC/ARQC or AAC) Application Interchange Profile (AIP) Application Transaction Counter (ATC) Terminal Verification Results (TVR) Unpredictable Number Issuer Application Data Application Usage Control CVM Results (CVMR) Application Identifier (AID) or FD Name, whichever is the longer Cryptogram Information Data Application Version Number Transaction Status Information (TSI) Terminal Type Terminal Capabilities Ideally the data should be produced as a separate log file or test file, collating the information in addition to the data required on the test file and authorisation request. e.g. ML log capturing the transaction data and authorisation data. 45

51 Global Payments 51 De Montfort Street Leicester LE1 7BB Tel Textphone Global Payments is HSBC Bank plc s preferred supplier for card processing in the UK. Global Payments is a trading name of GPUK LLP. GPUK LLP is authorised by the Financial Conduct Authority under the Payment Services Regulations 2009 (504290) for the provision of payment services. GPUK LLP is a limited liability partnership registered in England number OC Registered Office: 51, De Montfort Street, Leicester, LE1 7BB. The members are Global Payments U.K. Limited and Global Payments U.K. 2 Limited. Service of any documents relating to the business will be effective if served at the Registered Office. GPUK LLP. All rights reserved. TS 05/2015 GP066