80 Byte Population Guide

**To be used in conjunction with the latest 80 byte specification**

Version No: 15.93

2016
 OmniPay Innovation in Transaction Management

Contents
80 Byte Population Guide 1
1 Transaction Records for the 80 Byte File 11
1.1 Visa Transaction 11
1.2 MasterCard Transaction 12
1.3 Debit Card Addendum Record 12
1.4 VISA Transaction with PAN length >16 12
1.5 MasterCard Transaction with PAN length >16 13
1.6 International Maestro Transaction with PAN length >16 13
1.7 International Maestro Transaction with PAN length <=16 13
1.8 JCB Transaction 14
1.9 Diners/Discover Transaction 14
1.10 UPI Transaction 14
1.11 EPAL Transaction 14
1.12 iDeal Transaction 15
1.13 80 byte line terminators 15
1.14 Empty 80 byte file 15
1.15 Banknet Reference for MasterCard transactions 15

2 Merchant Address details 17

2.1 By Country 17
2.2 User defined regions 17
2.3 By Transaction 17
2.4 By Transaction Reject 17
2.5 Dynamic Descriptor 17
2.6 80byte Overrides 19

3 Merchant ID 20
3.1 OmniPay Authorisation MID 20
3.2 OmniPay Settlement MID 20

4 MasterCard Authorization to Clearing Mapping 21

5 OmniPay Authorization to Clearing Mapping 24
6 Card Not Present Environment 25
6.1 Non-secure Standard E-Commerce Transaction 25
6.2 Secure E-Commerce Transaction 27
6.3 Mail Order/Telephone Order (MOTO) Transaction 29
6.4 Recurring Transactions 31
6.5 Visa Instalment Transactions 34
6.6 Visa Multiple Clearing Records with Single Authorisation 35

80 Byte Population Guide Page 2

Version 15.93
 OmniPay Innovation in Transaction Management

6.7 MasterCard Multi Clearing Enhancement 37

6.8 MRPP Transactions 38
6.9 MUPP Transactions 40
6.10 MasterPass Transaction 47
6.11 MasterPass Enabled Merchant- non MasterPass transaction 50
6.12 Tokenised E-Wallet 52
6.13 MasterCard Digital Secure Remote Payments 52
6.14 Digital Wallet 58
6.15 Visa Checkout 59

7 Card Present Environment Attended 61

7.1 PAN Key Entry Signature Transaction 61
7.2 Voice Authorised transaction - Signature 63
7.3 Magnetic Stripe NO CVM Transaction 64
7.4 Magnetic Stripe (Not Reliable) NO CVM Transaction 66
7.5 Magnetic Stripe Signature Transaction 68
7.6 Magnetic Stripe (No Reliable) Signature Transaction 70
7.7 Magnetic Stripe - Online PIN Transaction 72
7.8 Magnetic Stripe (Not Reliable) - Online PIN Transaction 74
7.9 Chip read NO CVM Transaction 76
7.10 Chip read (Not Reliable) NO CVM Transaction 78
7.11 Chip read - Signature Transaction 79
7.12 Chip read (Not Reliable) Signature Transaction 81
7.13 Chip read - Online PIN Transaction 82
7.14 Chip read - Offline PIN Transaction 84
7.15 Chip read (Not Reliable) PIN Transaction 86
7.16 Acquirer Chip Transaction 87
7.17 Issuer Chip Transaction 89
7.18 EMV - Online PIN Transaction 91
7.19 Magnetic Stripe 'No CVM' Contactless Transactions 94
7.20 Magnetic Stripe Signature Contactless Transaction 96
7.21 Magnetic Stripe Online PIN Contactless Transaction 98
7.22 Chip read NO CVM Contactless Transaction 101
7.23 Chip read Signature Contactless Transaction 103
7.24 Chip read PIN Contactless Transaction 105
7.25 Purchase with Cash back 107

8 Card Present Environment Un-Attended 109

8.1 Magnetic Stripe No CVM LAT Transaction 109
8.2 Magnetic Stripe (Not Reliable) No CVM LAT Transaction 111
8.3 Magnetic Stripe NO CVMSST Transaction 113

80 Byte Population Guide Page 3

Version 15.93
 OmniPay Innovation in Transaction Management

8.4 Magnetic Stripe (Not Reliable) No CVM SST Transaction 116

8.5 Chip read NO CVMSST Transaction 118
8.6 Chip read (Not Reliable) No CVM SST Transaction 120
8.7 Magnetic Stripe Online PIN ADM Transaction 121
8.8 Magnetic Stripe (Not Reliable) Online PIN ADM Transaction 123
8.9 Chip read - Online PIN ADM Transaction 125
8.10 Chip read - Offline PIN ADM Transaction 127
8.11 Chip read (Not Reliable) Online PIN ADM Transaction 130

9 Credit/Money Transfer 131

9.1 OC/CFT Transactions 131
9.2 Payment Transaction /Payment of Winnings 133

10 MPOS transactions 135

11 ATM Automated Cash disbursements 136
12 Payment Facilitator Transactions 137
13 Manual Cash disbursements 138
14 Quasi-Cash Transactions 139
15 Dynamic Currency Conversion (DCC) 141
16 Airline with AID 143
17 Airline Without AID Data 146
18 Airline Ancillary Data 148
19 MasterCard Incentive Rates 150
19.1 Car Rental 150
19.2 Hotel/Cruise Liners 151
19.3 Commercial Cards (Other than Airline, Hotel/Cruise, Car Rental MCCs) 151
19.4 Commercial Cards (Airline MCCs) 153

20 Visa Car Rental Transactions 154

21 Visa Hotel Transactions 155
22 Visa Incentive Rates 156
22.1 Corporate LID Rates 156
22.2 Purchase VAT Rates 157

23 VISA CPS Rate Qualification 159

23.1 Visa CPS/Card Not Present MOTO 159
23.2 Visa CPS Recurring Transactions 161
23.3 Visa CPS Electronic Commerce (basic) 162
23.4 Visa CPS/E-Commerce Preferred 163
23.5 Visa CPS/Passenger Transport: Card Present 164
23.6 Visa CPS/Passenger Transport: Card Not Present 166
23.7 Visa CPS/E-Commerce Preferred: Passenger Transport 168
23.8 Visa CPS/Hotel and Car Rental: Card Present 170

80 Byte Population Guide Page 4

Version 15.93
 OmniPay Innovation in Transaction Management

23.9 Visa CPS/Hotel and Car Rental: Card Not Present 172
23.10 Visa CPS/E-Commerce Preferred: Hotel & Car Rental 173

24 JCB (Japan Credit Bureau) Transactions 176

25 Diners/Discover Transactions 183
26 ELV Transactions 194
27 UPI (CHINA UNION PAY) Transactions 196
28 Australian Debit Card Transactions 205
29 iDeal Transactions 207
30 Pre-Authorisation, Top-Ups & Clearing: 209
Multi-Currency Sample 80byte I 210
Multi-Currency Sample 80byte II 212
DCC Sample 80byte III 214
DCC Sample 80byte IV 215

80 Byte Population Guide Page 5

Version 15.93
 OmniPay Innovation in Transaction Management

Document History

Document History
Version Date Author Change Summary

Version 1.0 26-06-2007 R Verma First Draft version

Version 2.0 07-05-2008 R Verma Modified POS Terminal Capability & Cardholder ID fields for

Visa.

Version 3.0 09-06-2008 R Verma Added value S for Proof of attempt VbV i.e. for ECI =6

transactions

Version 4.0 10-07-2008 R Verma Updated value for Cardholder Present & Card Data input

mode for MasterCard.

Added Airline Fields

Version 5.0 29-07-2008 Vidhya Update E-Com section to remove ACI.

Chenniappan Add sections for EMV, Card present, Electronic, P-cards, Un-

attended terminal, Hotel and Car rental

Version 6.0 05-09-2008 Vidhya Add transaction record sequence for Visa and MasterCard.

Chenniappan Add OC/PT, ATM, Quasi cash transaction types, Banknet

reference details, Airline without AID. Added AVS, CVV2 fields

for CNP

Version 7.0 13-01-2009 Vidhya Update Section 4: Card Present Environment Un-Attended

Chenniappan to reflect the changes in the 80 byte spec.

Add qualification details for CPS rates

Update the Airline requirements without the trip leg data.

Version 8.0 23-03-2009 Vidhya Add new section for DCC

Chenniappan Add sample transactions for all

Update the doc with feedbacks from the doc review

Version 9.0 25-08-2009 Vidhya Add the doc with new scheme requirements

Chenniappan Add Section 15 for JCB transactions

Add Section 16 for ELV transactions

Add a new heading for Merchant Address details

 OmniPay Innovation in Transaction Management

Version 9.0 12-10-2009 Vidhya Update Merchant Address details

Chenniappan

Version 10.0 03-12-2009 Vidhya Minor updates to section 1.7, 4.1, 4,2, 7,9
Chenniappan Add new section 3 for Merchant ID
Add Contactless to section 4

Version 11.0 25-06-2010 Vidhya Update sections 5, 6 to include Auth Response code for
Chenniappan Visa

Add 2 new capture methods to sections 5.2, 5.3

(#67646)

Add 6 new CAPM for No CVM to section 5 (#80066)

Add section 15 for Visa Car Rental transactions

Add section 16 for Visa Hotel transactions

Add Visa CPS rates to section 18

Add Secure Telephone under section 4.4

Update section 4.5 for Recurring

Add section 20 for Diners/Discover transactions

Update section 7.1 for Visa OCs

Update section 5.15 for Visa EMV requirements

Update section 2 to include Dynamic Descriptor

Added Appendix A, Appendix B

Update all record names with the record type code for

easy look up.

Update to reflect the 80byte spec v3.1

Version 12.0 23-09-2010 Vidhya Update sections 4,5,6 for Data Integrity changes
Chenniappan (#85255)

Add section 5.17 for Purchase with Cashback

Version 12.0 14.12.2012 Karen Mc Donnell Add Update to Sect 6.6 Recurring Transactions
Version 12.0 12.03.2013 Karen Mc Donnell Update to CFT Section after suggestions from

Compliance Manager
Version 12.0 05.07.2013 Karen Mc Donnell Update to 6.7 MRPP First in series
Version 12.0 10.07.2013 Karen Mc Donnell Add Section 6.8 for MUPP Transactions
Version 12.0 10.07.2013 Karen Mc Donnell Update Entry Mode on Ecommerce transactions
Version 13.0 15.07.2013 Karen Mc Donnell Add UPI section
 OmniPay Innovation in Transaction Management

Version 13.0 06.07.2013 Linus Ingoldsby Add Ewallet (V.Me and MasterPass) sections, add ePAL

Australian Debit Card section

Version 13.0 04.09.2013 Linus Ingoldsby Update ePAL section, update OC's for 4.3 spec Update

Chip Read- Pin contactless transaction - Auth Code may

be present.
Version 13.0 13.11.2013 Linus Ingoldsby Update OC's- add unique business application IDs for

Money Transfer.
Version 13.0 21.11.2013 Linus Ingoldsby E-Wallet 'A' value for MasterPass enabled merchants

with a Non MasterPass transaction

Version 13.0 27.11.2013 Linus Ingoldsby Changed MC 'POS ENTRY MODE value =01 to 'Key

Entered' from 'Terminal Not Used.'

Version 13.1 09.05.2014 Linus Ingoldsby Replace MRRP in doc with MRPP (Typo amending)

Added CNP to UPI section.

Amending formatting of document.

Removing section 7.1 as is catered for elsewhere

Version 14 26.09.2014 Linus Ingoldsby Added MasterCard Airline Incentive Requirements

Updated elements to reflect new 4.5 80 Byte Spec

Revised CPS entries

Version 15 24.06.2015 Linus Ingoldsby General formatting Updates

Diners updates (NRID, Address)

Added MPOS to CAT cells in MasterCard Authorisation to

Clearing mapping.

Added iDeal configuration

Added mandate regarding Postal Code for Certain

Countries within MasterCard.

Added Airline Ancillary Data.

Tokenised Transactions

File Size Guideline

Sub merchant ID info

Amended Sample 80 bytes throughout.

Form Factor Indicator detail added

Multiple Clearing Sequence - Visa

Multiple Clearing Sequence - MasterCard

Instalment transactions - Visa

Updated '}1, }2,...' positioning to match 80 byte spec
 OmniPay Innovation in Transaction Management

Version 15.5 13.08.2015 Removed forced MCCs from MC MOTO requirements

Added Payment Facilitator clarification around

Submerchant ID

Added EMV relevant information to DCC transactions.

Changed Banknet Authorisation date on Banknet section

to Banknet Settlement Date.

Amended iDeal specification- Removed Visa POS

Terminal Capability, added values to <O record

requirements.

DSRP update to 4.9 specification -UCAF Indicators, Card

Data Input Mode & Electronic Commerce Indicator,

Recurring Transactions can now use Zero Value

Authentication as First in Series for Visa and MasterCard

Revised Airline Ancillary Data. - Must be unique

transaction, notincluded with airline ticket

Version 15.6 17.10.2015 Linus Ingoldsby Added Recurring DSRP section, based on feedback from

MC

#7 necessary for OCs. Updated OC section to reflect this.

Removed Union Pay Ecommerce, Secure Ecommerce,

and Moto. Will revisit when implemented by Compliance

Adding MOTO CP clarification to document.

Amended E-Wallet section to reflect new MasterCard

Requirements.

V.Me no longer supported, removing.

Version 15.7 10.12.2015 Linus Ingoldsby Various minor realignments.
Version 15.8 08.03.2016 Linus Ingoldsby Added Extended Service code to Contactless MC section

Changed typo in JCB Card Present Mag Stripe section

Added Extended Service Code requirement to MC Chip

Read transactions
Version 15.93x 04.05.2016 Linus Ingoldsby Added Diners Action Code Mandate

Removed Moto (>1) typo

Amended Manual transactions, added Voice Authorised

Manual transaction
 OmniPay Innovation in Transaction Management

Version 15.94 11.10.2016 Linus Ingoldsby Amended Applepay Visa transaction requirements. ECI -

7 now mandatory.

Amended Manual transactions, added Voice Authorised

Manual transaction

Changed Contactless terminal capability definition:

Contactless only Visa Terminals may perform PIN/Sig

transactions

Unattended Terminal Transaction Coverage amended.

Only Type 2 and Type 3 are supported by the Omnipay

Platform. Type 1 is not permitted.

 OmniPay Innovation in Transaction Management

1 Transaction Records for the 80 Byte File

The following are the transaction records that will be produced for Visa and MasterCard transactions.
All the transactions should be batched per merchant and then by transaction currency (Base currency for
DCC transactions) which is mandatory, see Appendix A for a sample 80byte file. For example, if there are 2
Visa and 2 MasterCard transactions submitted for a merchant with transaction currencies GBP and USD
each, then 2 batches are created one for the USD transactions containing both the Visa and MasterCard
transaction and another for GBP transactions for the same merchant.

Alternatively, transactions could be batched per merchant and then by transaction currency (Base
currency for DCC transactions) and further by card scheme such as Visa or MasterCard and this is optional.
See Appendix B for a sample 80byte file. For example, if there are 2 Visa transactions with currencies GBP
& USD and 1 MasterCard transaction with GBP currency submitted for a merchant, then Visa transaction
rd
with GBP is batched separately from MasterCard transaction with GBP for the same merchant plus a 3
batch for the Visa transaction with USD for the same merchant.

Sales vs. Refunds

Sales drafts (Purchases by a card user) are denoted by a '06' in the Tran Code field of each line of a
particular transaction.
Credit/Returns are denoted by a '07' in the Tran Code field of each line of a particular transaction.
It is not permissible to have a 06 value AND a 07 value in the Tran code field of a transaction. This will
cause the file to reject.
Refunds can contain the Authorisation information of the Sales transaction that it is funding. This will
allow that refund transaction to process at the same rate as the preceding Sale, assuming this is permitted
by scheme. A refund does not always have to be authorised, although there may be specific transaction
types (i.e. Payment Transactions which MUST be authorised, or that transaction will fail). If a transaction
does not contain the authorisation information of the preceding sale transaction AND processes without
authorising, a base interchange rate may be obtained, assuming that the transaction type is permitted by
scheme.

File Trailer Tran Code

If sum of the purchase amounts=sum of the refund amounts in a batch, then the batch summary
transaction code will be '70'. If sum of the purchase amounts > sum of the refund amounts in a batch,
then the batch summary transaction code will be '70'. If sum of the purchase amounts < sum of the refund
amounts in a batch, then the batch summary transaction code will be '71'. If sum of the batch totals with
transaction code '70' > sum of the batch totals with transaction code '71', then the file trailer transaction
code will be '80'. If sum of the batch totals with transaction code '70' < sum of the batch totals with
transaction code '71', then the file trailer transaction code will be '85'. If sum of the batch totals with
transaction code '70' =sum of the batch totals with transaction code '71', then the file trailer transaction
code will be '80'.

Number of records on a single 80 byte file should be Modulus of 1 million of count of all records in file.
Total records in file =12,345 File record count =012345
Total records in file =7,654,321 File record count =654321less than a million.

File Size recommendations:

Submitted files should not exceed 100,000 transactions in each 80 byte to ensure efficiency in processing.

1.1 Visa Transaction

The following records apply (either mandatory or optional) for Visa transactions:
File Header Record =Mandatory
 OmniPay Innovation in Transaction Management

Bankcard and T & E Detail record =Mandatory

Bankcard and T & E Detail Addendum Record 1 (<1) =Mandatory
Bankcard and T & E Detail Addendum Record A (<A ) =Mandatory
VISA Detail Addendum Record 1 (#1) =Mandatory
VISA Detail Addendum Record 2 (#3) =Mandatory
Summary Record =Mandatory
File Trailer Record =Mandatory

1.2 MasterCard Transaction

The following records apply (either mandatory or optional) for MasterCard transactions
File Header Record =Mandatory
Bankcard and T & E Detail record =Mandatory
Bankcard and T & E Detail Addendum Record 1 (<1) =Mandatory
Bankcard and T & E Detail Addendum Record A (<A) =Mandatory
MasterCard Interchange Compliance Detail Addendum Record 1 (=0) =Mandatory
MasterCard Interchange Compliance Detail Addendum Record 3 (=5) =Mandatory
Summary Record =Mandatory
File Trailer Record =Mandatory

1.3 Debit Card Addendum Record

Bankcard and T & E Detail Addendum Record E (<E) is used only when the PAN length of the card number
is >16. If the PAN length is >16, then the card number is populated in the Debit Card Cardholder Number
field in the Bankcard and T & E Detail Addendum Record E (<E). AVS, CVV2 and the Retailer Classification
Code RCC on this record should be space filled as they are only required for UK Domestic Maestro (UKDM)
cards. With RCMS migration to GCMS on 13th May 2011 all UKDM cards will be processed as International
Maestro and cleared through GCMS.

1.4 VISA Transaction with PAN length >16

For VISA transactions with PAN length >16, the Bankcard and T & E Detail Addendum Record E (<E) is
included. The card brand or the Card Type Code in the Bankcard and T & E Detail record is populated as
V. The following records apply (either mandatory or optional) for VISA transactions
File Header Record =Mandatory
Bankcard and T & E Detail record =Mandatory
Bankcard and T & E Detail Addendum Record 1 (<1) =Mandatory
Bankcard and T & E Detail Addendum Record A (<A) =Mandatory
Bankcard and T & E Detail Addendum Record E (<E) =Mandatory
VISA Detail Addendum Record 1 VISA Detail Addendum Record 1 (#1) =Mandatory
VISA Detail Addendum Record 2 VISA Detail Addendum Record 2 (#3) =Mandatory
Summary Record =Mandatory
File Trailer Record =Mandatory
Sample transaction:
06V mmdd 912869 2 600010080388314REALEX*TC27
06<1000000000000020400978 GBR LONDON NN
06<A 0401000000 0000000000000000000000000
06<E476142875000000000710010067 00000000000090000000000000000000000000
06#1594 00000002040097800 599901M 0
06#3 000000 0000000020400
 OmniPay Innovation in Transaction Management

1.5 MasterCard Transaction with PAN length >16

For MasterCard transactions with PAN length >16, the Bankcard and T & E Detail Addendum Record E (<E)
is included. The card brand or the Card Type Code in the Bankcard and T & E Detail record is populated as
M. The following records apply (either mandatory or optional) for VISA transactions
File Header Record =Mandatory
Bankcard and T & E Detail record =Mandatory
Bankcard and T & E Detail Addendum Record 1 (<1) =Mandatory
Bankcard and T & E Detail Addendum Record A (<A) =Mandatory
Bankcard and T & E Detail Addendum Record E (<E) =Mandatory
MasterCard Interchange Compliance Detail Addendum Record 1 (=0) =Mandatory
MasterCard Interchange Compliance Detail Addendum Record 3 (=5) =Mandatory
Summary Record =Mandatory
File Trailer Record =Mandatory
Sample transaction:
06M mmdd 531994 1 200010080367680REALEX*TC87
06<1000000000000034300344 GBR LONDON N
06<A mmdd000000 0000000000000000000000000
06<E526224000000000000110010064 00000000000090000000000000000000000000
06=0000000000000000034300MMDC123450330 599901 2F
06=51211000100010V09000

1.6 International Maestro Transaction with PAN length >16

For International Maestro transactions with PAN length >16, the Bankcard and T & E Detail Addendum
Record E (<E) is included. The card brand or the Card Type Code in the Bankcard and T& E Detail record is
populated as E. The following records apply (either mandatory or optional) for International Maestro
transactions
File Header Record =Mandatory
Bankcard and T & E Detail record =Mandatory
Bankcard and T & E Detail Addendum Record 1 (<1) =Mandatory
Bankcard and T & E Detail Addendum Record A (<A) =Mandatory
Bankcard and T & E Detail Addendum Record E (<E) =Mandatory
MasterCard Interchange Compliance Detail Addendum Record 1 (=0) =Mandatory
MasterCard Interchange Compliance Detail Addendum Record 3 (=5) =Mandatory
Summary Record =Mandatory
File Trailer Record =Mandatory
Sample transaction:
06E mmdd 169075 2 200010080388314REALEX*TC67
06<1000000000000032400344 GBR LONDON N
06<A mmdd000000 0000000000000000000000000
06<E606144000000000000410010067 00000000000090000000000000000000000000
06=0000000000000000032400MMDC123450330 599901 2F
06=51211000100010V09000

1.7 International Maestro Transaction with PAN length <=16

For International Maestro transactions with PAN length <=16, the Bankcard and T & E Detail Addendum
Record E (<E) is NOT included. The card brand or the Card Type Code in the Bankcard and T& E Detail
record is populated as E and the Cardholder Number is populated in the Bankcard and T & E Detail
record. The following records apply (either mandatory or optional) for International Maestro transactions
File Header Record =Mandatory
Bankcard and T & E Detail record =Mandatory
 OmniPay Innovation in Transaction Management

Bankcard and T & E Detail Addendum Record 1 (<1) =Mandatory

Bankcard and T & E Detail Addendum Record A (<A ) =Mandatory
Bankcard and T & E Detail Addendum Record E (<E) =Optional
MasterCard Interchange Compliance Detail Addendum Record 1 (=0) =Mandatory
MasterCard Interchange Compliance Detail Addendum Record 3 (=5) =Mandatory
Summary Record =Mandatory
File Trailer Record =Mandatory
Sample transaction:
06E6061440000000001 mmdd 169075 2 200010080388314REALEX*TC67
06<1000000000000032400344 GBR LONDON N
06<A mmdd000000 0000000000000000000000000
06=0000000000000000032400MMDC123450330 599901 2F
06=51211000100010V09000

1.8 JCB Transaction

The following records apply (either mandatory or optional) for JCB transactions
File Header Record =Mandatory
Bankcard and T & E Detail record =Mandatory
Bankcard and T & E Detail Addendum Record 1 (<1) =Mandatory
Bankcard and T & E Detail Addendum Record A (<A) =Mandatory
JCB Compliance Detail Record 1 (<K) =Mandatory
Summary Record =Mandatory
File Trailer Record =Mandatory

1.9 Diners/Discover Transaction

The following records apply (either mandatory or optional) for Diners transactions
File Header Record =Mandatory
Bankcard and T & E Detail record =Mandatory
Bankcard and T & E Detail Addendum Record 1 (<1) =Mandatory
Bankcard and T & E Detail Addendum Record A (<A) =Mandatory
Diners Club Addendum Record 1 (<D) =Mandatory
Summary Record =Mandatory
File Trailer Record =Mandatory

1.10 UPI Transaction

The following records apply (either mandatory or optional) for UPI transactions
File Header Record =Mandatory
Bankcard and T&E Detail Record (06H/07H) =Mandatory
Bankcard and T&E Detail Addendum Record 1 (<1) =Mandatory
Bankcard and T&E Detail Addendum Record A (<A) =Mandatory
Bankcard and T & E Detail Addendum Record E (<E) =Optional
UPI Addendum Record 1 (#C) =Mandatory
Summary Record =Mandatory
File Trailer Record =Mandatory

1.11 EPAL Transaction

The following records apply (either mandatory or optional) for EPAL transactions
File Header Record=Mandatory
Bankcard and T&E Detail Record (06H/07H) =Mandatory
 OmniPay Innovation in Transaction Management

Bankcard and T&E Detail Addendum Record 1 (<1) =Mandatory

Bankcard and T&E Detail Addendum Record A (<A) =Mandatory
Bankcard and T&E Detail Addendum Record E (<E) =Mandatory
VISA Detail Addendum Record 1 VISA Detail Addendum Record 1 (#1) =Mandatory
Bankcard and T & E Detail Record #Q (#Q) =Mandatory
Summary Record =Mandatory
File Trailer Record =Mandatory

1.12 iDeal Transaction

The following records apply (either mandatory or optional) for iDeal transactions (iDeal is an Online
Banking e-Payment solution currently utilised in the Netherlands, Please contact your Omnipay
Relationship Manager or a Project Manager to certify to support these transactions)
Bankcard and T & E Detail recordmandatory
Bankcard and T & E Detail record Addendum Record 1 (<1) =Mandatory
Bankcard and T & E Detail record Addendum Record A (<A) =Mandatory
Bankcard and T & E Detail record Addendum Record B (<B) =Mandatory
Bankcard and T & E Detail record Addendum Record C (<C) =Mandatory
Bankcard and T & E Detail record Addendum Record O (<O) =Mandatory
Summary Record =Mandatory
File Trailer Record =Mandatory

1.13 80 byte line terminators

Every 80 byte record should be terminated by a single line feed character (hexadecimal 0A this is the
UNIX line terminator convention).

A file is in UNIX format if every line ends with the single byte line feed (hexadecimal 0A, Ctrl-J, often
denoted as \n). A file is in DOS format if every line ends with the two bytes carriage return line feed
(hexadecimal 0D 0A, Ctrl-M Ctrl-J, often denoted as \r\n).

1.14 Empty 80 byte file

The following records apply (either mandatory or optional) for an empty 80 byte file:
File Header Record =Mandatory
File Trailer Record =Mandatory

1.15 Banknet Reference for MasterCard transactions

From October 2010 (Compliance 10.2) MasterCard introduced Account Level Management into Europe.

Please note that Banknet Reference Number and Banknet Settlement Date must be present for all US
acquired incentive interchange, and must be present wherever it is passed on the authorisation, for US
and other regions.

Failure for OmniPay not being able to utilize the Banknet Reference Number and Banknet Settlement Date
to determine the correct Interchange may result in MasterCard Scheme Rejects or settlement differences
due to interchange qualification. This is now being verified as part of the 80 byte certification in OmniPay.
Banknet reference number (Trace ID) is derived from positions 19 of DE 63 (Network Data) from the
MasterCard authorization response message. Banknet Settlement Date is derived from DE 15 (Date,
Settlement) of the MasterCard authorization response message.
 OmniPay Innovation in Transaction Management

OmniPay authorisation switch passes the banknet details back to the terminal in the following fields for
both APACS 70 and ISO 8583 formats:
Apacs70 response - F 22 Auxiliary data
ISO8583 response - BM 44.2 (Banknet ref no.), BM 15 (Banknet settlement date)

Clients should then populate these values on the OmniPay Settlement file. OmniPay auth switch is setup
to provide a dummy value of MDC123456 as the Banknet reference number for test purposes.

Where the transactions are authorised via FD Basildon switch using Standard 70-2 (former APACS 30) and
the 80 byte file is post boxed to OmniPay, if the auth process is turned on at Basildon then the banknet
details would be added to the 80 byte file as part of the auth matching process before it gets sent to
OmniPay.

Banknet Reference Number (MasterCard Interchange Compliance Detail Addendum Record 1 (=0),
Position 26, length 9): Must contain a valid Banknet Reference Number (DE 63 S2)

Banknet Settlement Date (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position
35, length 4): Banknet Date must contain a valid date in the format MMDD. This can also be the
MasterCard Settlement date from the Authorisation. (DE 63 S2)

Sample transaction:
06M5409640000000009 mmdd 724169 00010080378497
06<1000000000000010909826 GBR LONDON N
06<A mmdd000000 0000000000000000000000000
06<B
06=0000000000000000010909MDC1234560320 599901
06=51211000100000109000
 OmniPay Innovation in Transaction Management

2 Merchant Address details

Regions settings of a merchant dictates how the address details of a merchant (such as the State, Zip, City
and Country of the merchant) is sourced in order to be passed out to scheme either from the incoming 80
byte file or from the Merchant Master File (MMF). Following options are available for Merchant region
settings:
'By country'
User Defined Regions
'By transaction'
'By transaction reject'

2.1 By Country

System would take address data from the MMF regardless of the data submitted on the incoming
transaction.

2.2 User defined regions

Example of a user defined region is All to 1 USD, Like for Like. This is selected if pre-defined non-
geographical regions are configured within the institution and a merchant can be pointed to a given
region at set-up time. That is, where the system is not required to select the region based on the
merchants or transactions geographical location. This region setting would work the same way as 'By
Country' region setting.

2.3 By Transaction

System would attempt to take address data from incoming transaction on the 80byte file and if address
data on incoming transaction does not pass validation, it will revert to address data on MMF. Please refer
to section 2.5 below for how this works and the address fields on the 80byte file.

2.4 By Transaction Reject

System would take address data from the incoming transaction similar to section 2.1 but if this data does
not pass validation, system will front-end reject the transaction instead of reverting to the MMF. Please
refer to section 2.5 below for how this works and the address fields on the 80byte file.

2.5 Dynamic Descriptor

This is a requirement to allow the varying of merchant name and address details on the outgoing clearing
files sent to scheme for ultimate representation on to the cardholders statement through certain 80byte
fields. The system will attempt to take the address data from the incoming transaction on the 80byte
file when the merchant is setup to use By Transaction or By Transaction Rejects settings. If the
merchant country is U.S. or Canada the State field MUST be present and should have a valid value. There
 OmniPay Innovation in Transaction Management

is an additional validation in place for VISA whereby if the merchant country is U.S the postal code on the
80 byte should not be more than 5 digits long and if its more than 5 digits long, it will revert to MMF
instead or reject.

Bankcard and T & E Detail Addendum Record 1 (<1) contains the merchant address details that can be
changed dynamically for each transaction and they are as follows:
Charge Description/Merchant Name (Bankcard and T & E Detail Record, Position 56, length 25)
Merchant Category Code (VISA Detail Addendum Record 1 (#1), Position 50, Length 4) or
(MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 45, length 4)
Commercial Entity (Merchant) State/Province Code (Bankcard and T & E Detail Addendum
Record 1 (<1), Position 26, Length 3). This should contain a valid state code for US and Canada.
For all others, it can be populated with spaces or a province or region code or populated with the
country code as below.
Commercial Entity (Merchant) Country Code (Bankcard and T & E Detail Addendum Record 1
(<1), Position 29, Length 3). This should contain a valid 3 character alphabetic country code.
Commercial Entity (Merchant) Zip/Postal Code (Bankcard and T & E Detail Addendum Record 1
(<1), Position 32, Length 10)
Commercial Entity (Merchant) City (Bankcard and T & E Detail Addendum Record 1 (<1), Position
42, Length 13)
Bankcard and T & E Detail Addendum Record A (<A) also contains some merchant address details listed as
below typically used for varying within a single country only. When the Merchant City field is populated, it
will override the details from the MMF for all merchant region settings apart from By Transaction or By
Transaction Rejects when the detail will be taken from the <1 record instead. This is typically used to send
the Customer Service Telephone number for Visa CPS CNP transactions like MOTO or URL/email address
for Visa CPS ecommerce transactions in Domestic USA. This field can contain the city name in the local
spelling for MasterCard transactions in Europe. For example in Italy, the local name for Florence is Firenze
and if the MMF is setup as Florence then this city field can be used to override this value with the local
spelling Firenze as required by MasterCard. Please note that we dont validate the detail passed in this
field and would be forwarded to the schemes in the Merchant city field.
Merchant City (Bankcard and T & E Detail Addendum Record A (<A), Position 29, Length 13)
Merchant State (Bankcard and T & E Detail Addendum Record A (<A), Position 42, Length 3)
Bankcard and T & E Detail Addendum Record J (<J) also contains some merchant address details listed as
below typically used for domestic USA & Canada MasterCard transactions. Merchant URL field is only
applicable for MasterCard transactions and not for Visa. These fields are optional fields for passing on
additional details to the schemes.
 OmniPay Innovation in Transaction Management

Merchant URL/ Website address (Bankcard and T & E Detail Addendum Record J (<J), Position 5,
Length 60)
Merchant Phone Number (Bankcard and T & E Detail Addendum Record J (<J), Position 65,
Length 16)
MasterCard Interchange Compliance Detail Addendum Record 3 (=5)
Card Acceptor Street Address (Merchant Street Address) (MasterCard Interchange Compliance
Detail Addendum Record 3 (=5), Position 24, length 57)

2.6 80byte Overrides

Please note that the system will attempt to populate the following fields from the incoming transaction
on the 80byte over the values setup in the Merchant Master File REGARDLESS of the region settings of
the merchant. These Merchant details from the 80byte file will be passed on to the outgoing clearing files
sent to scheme for ultimate representation on to the cardholders statement instead of the details from
the Merchant Master File (MMF).
Interchange Program Qualification Flag (Bankcard and T & E Detail Addendum Record 1 (<1),
Position 58, length 1)
Recurring Transaction Flag (Bankcard and T & E Detail Addendum Record 1 (<1), Position 59,
length 1)
Merchant City (Bankcard and T & E Detail Addendum Record A (<A), Position 29, Length 13)
Charge Description/ Merchant Name (Bankcard and T & E Detail Record, Position 56, length 25)
Merchant Category Code (VISA Detail Addendum Record 1 (#1), Position 50, Length 4) or
(MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 45, length 4)
Merchant Tax ID or Corporation VAT Number (MasterCard Business/Purchase Card Addendum
Record 1 (}1), Position 26, length 15)
Merchant Phone Number (Bankcard and T & E Detail Addendum Record J (<J), Position 65,
Length 16)
 OmniPay Innovation in Transaction Management

3 Merchant ID
Merchant ID for the authorisations and the settlement are same for some of the new acquirers. For
others, Merchant ID (MID) or the merchant number used for authorizations on the OmniPay auth switch
and settlement 80 byte file differs as outlined below.

3.1 OmniPay Authorisation MID

Omnipay authorization Merchant number (MID) is composed of 15 digits of the format 0001XXXYYYYYYYY
where 0001 prefix is always present
XXX is the 3 digit institution number in the format 015
YYYYYYYY is the 8 digit Merchant number (MID).

For example, an auth MID would be 000109912345678.

3.2 OmniPay Settlement MID

Settlement 80 byte Merchant number (MID) could be of any length up to a maximum of 15 digits. The
MID used on the 80 byte file is the Our Reference Number from the Merchant Master File. There is
another 8 digit client number or merchant number setup on the Merchant Master File which is used as
part of the authorization MID YYYYYYYY as shown above.

In order to test merchants authorizing through OmniPay switch, we will be using MIDs where the last 8
digit of the Our Reference Number will match the 8 digit client number or merchant number.

For example, consider our reference number 540436503993735 where the last 8 digit will match the 8
digit client number 03993735. Here the auth MID 0001XXX03993735 will be used for authorizing the
transaction on the auth switch and the same transaction will be submitted on the settlement 80 byte file
using our reference number 540436503993735.
 OmniPay Innovation in Transaction Management

4 MasterCard Authorization to Clearing Mapping

The below section describes how authorization information should be mapped to clearing message in 80-byte
file. Please note that there are certain differences for the same data elements between the authorisation and
clearing message. It is because the authorization messages currently uses the ISO 8583-1987 message format,
and the IPM clearing message uses the ISO 8583-1993 message format, therefore mapping needs to be used
between the two.
Note: The below Mapping has been derived from MasterCard IPM Clearing Formats Manual *15 April 2011
Data Element: Authorization Clearing file (DE 22 string)

Card Data Input Capability: DE 61 S11 =0 0 =Unknown

Clearing File: DE 22S1 DE 61 S11 =1 1 =Manual, no terminal

DE 61 S11 =2 2 =Magnetic stripe only terminal

DE 61 S11 =9 5 =ICC Only

DE 61 S11 =6 6 =Key Entry Only

A =Contactless magnetic stripe

Note: May also contain Other transaction types

DE 61 S11 =4 (Chip/Mag Stripe/Key Entry)

DE 61 S11 =7 B =Magnetic stripe reader and key entry

DE 61 S11 =8 C =Magnetic stripe reader, ICC, key entry

DE 61 S11 =5 D =Magnetic stripe reader and ICC

No Equivalent to Auth DE 61 S11 E = ICC and key entry

M =Contactless M/Chip

Note: May also contain Other transaction types

DE 61 S11 =3 (Chip/Mag Stripe/Key Entry)

Cardholder Authentication

Capability: Auth DE 22 S2 =2 0 =No electronic authentication

Clearing File: DE22S2 Auth DE 22 S2 =1 1 =PIN

No Equivalent to Auth DE 61 S2 2 =Electronic signature analysis

5 =Electronic authentication capability is

Auth DE 22 S2 =8 inoperative

Auth DE S1 =4 6 =Other

Auth DE 22 S2 =0 9 =Unknown

Card Capture Capability: Auth DE 61 S6 =0 0 =None

Clearing File: DE22S3 Auth DE 61 S6 =1 1 =Capture

No Equivalent to Auth DE 61 S6 9 =Unknown

 OmniPay Innovation in Transaction Management

Auth DE 61 S3 =3 and

Operating Environment Auth DE 61 S1 =2 0 =No terminal used

Auth DE 61 S3 =0 and

Clearing File: DE22S4 Auth DE 61 S1 =0 1 =On premises of card acceptor, attended

Auth DE 61 S3 =0 and

Auth DE 61 S1 =1 2 = On premises of card acceptor, unattended

Auth DE 61 S3 =1 and

Auth DE 61 S1 =0 3 =Off premises of card acceptor, attended

Auth DE 61 S3 =1 and

Auth DE 61 S1 =1 4 =Off premises of card acceptor, unattended

Auth DE 61 S3 =2 and
Auth DE 61 S1 =1 5 =On premises of cardholder, unattended

No Equivalent to Auth DE 61 6 =Off premises of cardholder, unattended

Any other value of DE 61 S1 or S3 9 =Unknown

Cardholder Present Auth DE 61 S4 =0 0 =Cardholder present

Clearing File: DE22S5 Auth DE 61 S4 =1 1 = Cardholder not present, unspecified

Auth DE 61 S4 =2 2 =Cardholder not present, Mail order

Auth DE 61 S4 =3 3 =Cardholder not present, Telephone

Auth DE 61 S4 =4 4 =Cardholder not present, Recurring

5 =Electronic order (home PC, Internet, mobile

Auth DE 61 S4 =5 phone, PDA)

No Equivalent to Auth DE 61 S4

value 9 =Unknown

Card Present Auth DE 61 S5 =1 0 =Card not present

Clearing File: DE22S6 Auth DE 61 S5 =0 1 =Card present

No Equivalent on Auth DE 61 S5

value 9 =Unknown, Unavailable

Card Data Input Mode Auth DE 22 S1 in (00,03,04 ) 0 =Unspecified; Data Unavailable

Clearing File: DE22S7 Auth DE 22 S1 =01 1 =Manual, no terminal

2 =Magnetic stripe read, Track Data not required or

Auth DE 22 S1 =02 not captured

Auth DE 22 S1 =79 6 =Key entered

Auth DE 22 S1 =91 A =Contactless magnetic stripe

Auth DE 22 S1 in (90,80) B =Magnetic stripe read; track data captured and

OmniPay Innovation in Transaction Management

passed unaltered

Auth DE 22 S1 in (05) C =Online Authorized Chip

Auth DE 22 S1 =81 S =Electronic Commerce

Auth DE 22 S1 =07 M =PAN auto-entry via contactless M/Chip

S =CAT level 1 Automated Dispensing Machine,

Auth DE 61 S10 value 1 Unattended

Auth DE 61 S10 value 2 T =CAT level 2, Self Service Terminal, Unattended

CAT Level Indicator
U =CAT level 3, Limited Amount Terminal,

Clearing File: PDS 0023 Auth DE 61 S10 value 3 Unattended

Auth DE 61 S10 value 9 =MPOS Indicator

OmniPay Innovation in Transaction Management

5 OmniPay Authorization to Clearing Mapping

80 byte field Abbre. =5 DE61 field on the ISO 8583 IPM fields
record on authorisation for
the response from MC Clearing
80byte,
position
Card Data Input CDIC 12 DE61 S11 Req.BM22/BM60.53.3 DE22 S1
Capability
Cardholder CAC 13 DE61 S2 Req.BM22.2/BM60.53.3 DE22 S2
Authentication Capability
Card Capture Capability CCC 14 DE61 S6 Req.BM22/25 & / DE22 S3
BM60.53.2
Operating Environment TOE 15 DE61 S1, S3 Req BM25 DE22 S4
PIN Capture Capability PCC 23 - Req. BM22.2 DE22 S12
Cardholder Present CHP 16 DE61 S4 Req. BM25 DE22 S5
Card Present CP 17 DE61 S5 Req. BM22 DE22 S6
Card Data Input Mode CDIM 18 DE61 S1 Req.BM22/25 DE22 S7
Cardholder CAM 19 - Req.BM22/25 DE22 S8
Authentication Method
Cardholder CAE 20 - Req.BM22/25 DE22 S9
Authentication Entity
CAT Level indicator CAT 80 DE61 S10 PDS 0023

80 Byte Population Guide Page 24 of 216

Version 15.93
OmniPay Innovation in Transaction Management

6 Card Not Present Environment

All MOTO, E-Commerce and Recurring transactions have a capture method of Card Not Present. The card number is
captured by Manual entry. AVS and CVV2 are used as added security measures for card not present transactions.

Address Verification System (AVS) system will check the billing address of the credit card provided by the user with the
address on file at the credit card company. AVS verifies the numeric portions of a cardholder's billing address. At
present, only a few countries support AVS on Visa and MasterCard, notably the USA, Canada and the United Kingdom.
AVS verifies the numeric portions of a cardholder's billing address.

CVC2 (Card Validation Code) for MasterCard or the CVV2 (Card Verification Value) for Visa is a three or four digit value
printed on the back signature panel of the card. Supplying the CVV2 code in a transaction is intended to verify that the
customer has the card in their possession.

6.1 Non-secure Standard E-Commerce Transaction

These transactions are real time Authorised but not authenticated by VbV for Visa and Secure code for MasterCard.
For Visa, these transactions would have a capture method of eCommerce, Channel Encrypt and would qualify for a
non-secure Ecommerce rate if available or fall back to a standard rate. For MasterCard, these transactions would have
a capture method of eCommerce, Channel Encrypt and would fall back to a Base rate as non-secure Ecommerce rate
are not available.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response message. (TC50
TCR0 Pos 152-157)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) for Visa must equal 7. (TC05
TCR1 Pos 116)
7 =the cardholders payment card was protected with a form of internet security, such as SSL, but
authentication was not performed.

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) (TC50 TCR0 Pos 158)
9 =Key entered (no card reader available)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1). (TC05 TCR0 Pos 160)
4 =Mail/Telephone or Electronic Commerce

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2). (TC05 TCR0 Pos 162-163)
01 =Key Entered

AVS Response Code (VISA Detail Addendum Record 2 (#3), Position 32, Length 1) must be populated. (TC05 TCR1, Pos
127). The value is derived from the AVS field (BM44.2) in the authorization message for ISO8583 format.

CVV2 Result Code (VISA Detail Addendum Record 1 (#1), Position 56, Length 1) must be populated. (TC05 TCR5, Pos
127). The value is derived from the CVV2 field (BM44.10) in the authorization message for ISO8583 format.

Sample transaction: Capture Method - eCommerce, Channel Encrypt

06V4018440000000018 mmdd 142869 2 700010080388314
06<1543275000000020400978 GBR www.yahoo.ie
06<A mmdd000000 0000000000000000000000000
06#1594 00000003000082600 599901P 0
06#3 U000000 0000000030000

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

80 Byte Population Guide Page 25 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) for MasterCard must equal
J.
J =Channel encryption; cardholder certificate not used

UCAF (Universal Cardholder Authentication Field) Status Indicator (MasterCard Interchange Compliance Detail
Addendum Record 1 (=0), Position 53, length 1) must equal 0. (DE 48 S3)
0 = UCAF data collection is not supported at the merchants website. Does not qualify for UCAF Rates.

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) should be
81
81 =PAN Entry via electronic commerce, including chip.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) . (DE 22 S1)
1 =Manual, no terminal or unknown

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) (DE 22 S2)
0 =No electronic authentication or unknown

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1).
(DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1).
(DE 22 S4)
0 =No terminal used

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1)
(DE 22 S5)
5 =Electronic order (home PC, Internet, mobile phone, PDA)

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) (DE 22 S6)
0 =Card not present or unknown

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
(DE 22 S7)
S =Electronic Commerce

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) (DE 22 S8)
0 =Not authenticated or unknown

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1). (DE 22 S9)
0 =Not authenticated or unknown
9 =Unknown

Address Verification Code (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 54, length
1) must be populated. The value is derived from the AVS field (BM60.32) in the authorization message for ISO8583
format.

Sample transaction: Capture Method - eCommerce Channel Encrypt (UCAF-0)

06M5409640000000009 mmdd 060145 2 J00010080388314
06<1000000000000031900978 GBR LONDON
06<A mmdd000000 0000000000000000000000000
06=0000000000000000031900MMDC123450323 599981 0N

80 Byte Population Guide Page 26 of 216

Version 15.93
OmniPay Innovation in Transaction Management

06=51211000100050S00000

6.2 Secure E-Commerce Transaction

These transactions are real time authorised and authenticated by VbV for Visa and Secure code for MasterCard. Visa
transactions with ECI-6 would have a capture method of SET/3D-SET non-authenticated and would qualify for Secure
E-Commerce Merchant or E-Commerce (Secure) rates. Visa transactions with ECI-5 would have a capture method of
SET/3D-SET authenticated and would qualify for E-Commerce (Secure) rate. MasterCard transactions with UCAF-1
would have a capture method of eCommerce Channel Encrypt (1) and would qualify for Merchant UCAF rates.
MasterCard transactions with UCAF-2 would have a capture method of eCommerce Channel Encrypt (2) and would
qualify for Full UCAF rates. Issuing BINs need to be VbV or 3D enabled in order to achieve the secure ecommerce
rates. Refund transactions for secure ecommerce transactions will not be VbV or 3D authenticated; hence will only
qualify for the standard rate.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) (TC05 TCR1 Pos 116)
5 =the cardholder was authenticated using a Visa-approved authentication methodology. The
authorization message was successfully authenticated by Verified by Visa. ***Full VbV transaction****
6 =the merchant is capable of and attempted to authenticate the cardholder using Verified by Visa, but
the cardholder did not participate.

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) (TC50 TCR00 (L) Pos 103-114)
9 =Key entered (no card reader available)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) (TC05 TCR0 Pos 160)
4 =Mail/Telephone or Electronic Commerce

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2). (TC05 TCR0 Pos 162-163)
01 =Key Entered.

AVS Response Code (VISA Detail Addendum Record 2 (#3), Position 32, Length 1) must be populated. (TC05 TCR1, Pos
127). The value is derived from the AVS field (BM44.2) in the authorization message for ISO8583 format

CVV2 Result Code (VISA Detail Addendum Record 1 (#1), Position 56, Length 1) must be populated. (TC05 TCR5, Pos
127). The value is derived from the CVV2 field (BM44.10) in the authorization message for ISO8583 format.

Sample transaction: Capture Method - SET/3D-SET authenticated

06V4018440000000018 mmdd 142869 2 500010080388314
06<1000000000000030000826 GBR LONDON
06<A mmdd000000 0000000000000000000000000
06#1594 00000003000082600 599901P 0
06#3 U000000 0000000030000

Sample transaction: Capture Method - SET/3D-SET non-authenticated

06V4018440000000018 mmdd 142869 2 600010080388314
06<1543275000000020400978 GBR www.yahoo.ie
06<A mmdd000000 0000000000000000000000000
06#1594 00000003000082600 599901P 0
06#3 U000000 0000000030000

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1)

80 Byte Population Guide Page 27 of 216

Version 15.93
OmniPay Innovation in Transaction Management

J =Channel encryption; cardholder certificate not used

UCAF Status Indicator (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 53, length 1).
(DE 48 S3)
1 = UCAF data collection is supported by the merchant, and UCAF data must be present.
2 =Both merchant and issuer are UCAF enabled,as indicated in the Authorization Request/0100 message.
***Full secure Code transaction**** (Full UCAF)

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2
81 =PAN Entry via electronic commerce, including chip.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1)(DE 22 S1)
1 =Manual, no terminal or unknown

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1)(DE 22 S2)
0 =No electronic authentication or unknown

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length
1)(DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length
1)(DE 22 S4)
0 =No terminal used

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1 (DE 22
S5)
5 =Electronic order (home PC, Internet, mobile phone, PDA)

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1)(DE 22 S6)
0 =Card not present or unknown

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)(DE
22 S7)
S =Electronic Commerce

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1)(DE 22 S8)
0 =Not authenticated or unknown

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1)(DE 22 S9)
0 =Not authenticated or unknown
9 =Unknown

Address Verification Code (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 54, length
1) must be populated for optimal interchange. The value is derived from the AVS field (BM60.32) in the authorization
message for ISO8583 format

Sample transaction: Capture Method - eCommerce Channel Encrypt (Merchant UCAF)

06M5409640000000009 mmdd 060145 2 J00010080388314
06<1000000000000031900978 GBR LONDON
06<A mmdd000000 0000000000000000000000000
06=0000000000000000031900MMDC123450323 599981 1N
06=51211000100050S00000

80 Byte Population Guide Page 28 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Sample transaction: Capture Method - eCommerce Channel Encrypt (Full UCAF)

06M5409640000000009 mmdd 060145 2 J00010080388314
06<1000000000000031900978 GBR LONDON
06<A mmdd000000 0000000000000000000000000
06=0000000000000000031900MMDC123450323 599981 2N
06=51211000100050S00000

6.3 Mail Order/Telephone Order (MOTO) Transaction

These transactions include Telephone order or Mail Order. When MOTO is M transactions would have a capture
method of KE, Mail order and when it is T it would be KE, Telephone order. For Visa, these transactions would
qualify for Card Not Present or CVV CNP rates in certain regions. For MasterCard these transactions would qualify
for Base rates.

MOTO as part of Card Present testing. If Card Present testing is performed on the same terminal, we would expect the
Terminal Capability to be that of the terminal that is performing Card Present testing. Operating Environment in this
case should be (1) On Premises of Card Acceptor, unattended for MasterCard.

Scheme Restrictions for Maestro:

Mail Order transactions are not allowed for Maestro. Maestro only allow Telephone refunds, not sales, and only in a
narrow set of circumstances limited geographically.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag Bankcard and T & E Detail Record, Position 32,length 1)(TC05 TCR1 Pos 116)
M =Mail Order Transaction
T =Telephone Order Transaction

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1)(TC50 TCR00 (L) Pos 103-114)
9 =Key entered (no card reader available)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) (TC05 TCR0 Pos 160)
4 =Mail/Telephone or Electronic Commerce

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) (TC05 TCR0 Pos 162-163)
01 =Key entered.

AVS Response Code (VISA Detail Addendum Record 2(#3), Position 32, Length 1) must be populated. (TC05 TCR1, Pos
127). The value is derived from the AVS field (BM44.2) in the authorization message for ISO8583 format. Mandatory
for Visa MOTO transactions

CVV2 Result Code (VISA Detail Addendum Record 1 (#1), Position 56, Length 1) must be populated. (TC05 TCR5, Pos
127). The value is derived from the CVV2 field (BM44.10) in the authorization message for ISO8583 format

Sample transaction: Capture Method Mail Order

06V4018440000000018 mmdd 467041M5 00010080378498
06<1000000000000010101826 GBR LONDON
06<A mmdd000000 0000000000000000000000000
06<B
06#1594 00000001010182600 599901P 0
06#3 U000000 0000000010101
MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)
M =Mail Order Transaction

80 Byte Population Guide Page 29 of 216

Version 15.93
OmniPay Innovation in Transaction Management

T =Telephone Order Transaction

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2)
01 =Key entered.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1). (DE 22 S1)
1 =Manual, no terminal or unknown

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) (DE 22 S2)
0 =No electronic authentication or unknown

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
(DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
(DE 22 S4)
0 =No terminal used

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) (DE
22 S5)
2 =Cardholder not present, Mail order
3 =Cardholder not present, Telephone

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) (DE 22 S6)
0 =Card not present or unknown

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1).
(DE 22 S7)
1 =Manual, no terminal

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1)(DE 22 S8)
0 =Not authenticated or unknown

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) (DE 22 S9)
0 =Not authenticated or unknown
9 =Unknown

Address Verification Code (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 54, length
1) may be populated. Not mandated at present. The value is derived from the AVS field (BM60.32) in the authorization
message for ISO8583 format

Sample transaction: Capture Method KE, Telephone order

06M5409640000000009 mmdd 724169T7 00010080378497
06<1000000000000010909826 GBR LONDON
06<A mmdd000000 0000000000000000000000000
06<B
06=0000000000000000010909MMDC123450320 599901 U
06=51211000100030100000

Sample transaction: Capture Method KE, Mail order

06M5409640000000009 mmdd 724169M7 00010080378497
06<1000000000000010909826 GBR LONDON
06<A mmdd000000 0000000000000000000000000

80 Byte Population Guide Page 30 of 216

Version 15.93
OmniPay Innovation in Transaction Management

06<B
06=0000000000000000010909MMDC123450320 599901 U
06=51211000100020100000

6.4 Recurring Transactions

This section lists the information required to qualify for Recurring rates in addition to the setup for the various card
capture methods outlined in the previous sections based on how the initial transaction is captured either by Mail
order, Telephone order or e-Commerce. These transactions would have a capture method of KE, recurring

Recurring rates are available for Visa in certain regions and in order for a transaction to qualify at the Recurring rate,
the merchant and acquirer must be Visa Account Updater (VAU) certified in UK and EU. If a recurring rate is not
available then the transaction would qualify for a rate based on the Capture method. However if VAU is not enabled
or if its not VAU authenticated then Recurring rates cannot be attained.

For MasterCard, Recurring rates are available in Asia Pacific and only the Recurring Transaction Flag (Bankcard and T &
E Detail Record, Position 59, length 1) is required to qualify for these rates. Where the Recurring rates are not
available these transactions would qualify for a rate based on the Capture method. Recurring transactions are not
allowed for Maestro.

First transaction in Series

This is the first transaction in a series of recurring transactions and they should have the Capture method set correctly.
Recurring rate is available to online authorised, Consumer, Card Not Present transactions where the transaction is the
second or subsequent transaction in a series of Recurring transactions, and the first (initial) transaction in the series
was conducted using one of the following three authentication methods: CVV2, Verified by Visa (VbV) or Chip and PIN.

CVV2, (if the transaction is Card Not Present in nature, the transaction must be CVV2 checked).
Verified by Visa, (if the transaction is an E-Commerce transaction, the Acquiring Bin must be VbV certified
and an ECI of 5 or 6 must be present).
Chip and PIN, (if the transactions occurs in a Card Present environment, the card and terminal must be Chip
enabled, and the transaction must be verified via Pin
The VISA AND MASTERCARD First In Series transaction authorised through Omnipay requires an 'F' Flag to be present
in the Recurring Flag indicator field. This does not apply before Compliance 2014.

Zero Value Authentications can be used as first in series. As an example, a magazine subscription with the first issue
free may use this format. If this is case, we would not expect a 'First In Series' transaction on an 80 byte. This needs to
be agreed in advance with Omnipay.

Sample Transaction for the above example: VISA Chip & PIN transaction as first in series
06V4018440000000018 mmdd 111760 1 IPN09051400000
06<1 000000006026978 F
06<A mmdd000000 0000000000000000000000000110704
06<B OASE02
06#1 52N 00000000602697800000000000000000 554205
06#3 000000 0000000020400

Sample Transaction for the above example: VISA MOTO transaction with CVV2 as first in series
06V4018440000000018 mmdd 467041M5 00010080378498
06<1000000000000010101826 GBR LONDON F
06<A mmdd000000 0000000000000000000000000
06<B
06#1594 00000001010182600 599901P 0
06#3 U000000 0000000010101

Sample Transaction for the above example: VISA Secure eCom transaction as first in series
06V4018440000000018 mmdd 587523 2 500010080388314REALEX*TC92
06<1000000000000040000978 GBR LONDON F

80 Byte Population Guide Page 31 of 216

Version 15.93
OmniPay Innovation in Transaction Management

06<A mmdd000000 0000000000000000000000000

06<B
06#1594 00000004000097800 599901M 0
06#3 000000 0000000040000

Sample Transaction for the above example MasterCard Secure eCom transaction as first in series
06M5586900000000002 mmdd 657190 2 J00010080388314REALEX*TC104
06<1000000000000043000978 GBR LONDON F
06<A mmdd000000 0000000000000000000000000
06<B
06=0000000000000000043000MMDC123450402 599981 2
06=51211000100010V09000

Only those clients that authorize through Omnipay must flag first in series MC transactions with a value of F in the
Recurring Transaction Flag field. Other clients if authorizing transactions initiating the recurring series will need to consider
whether to include the value of F or space fill this field. This decision should be based on both the authorisation response
and clearing message.

Sample Transaction for the above example MasterCard Secure eCom transaction as first in series
Recurring Transaction Flag (Bankcard and T & E Detail Addendum Record 1 (<1), Position 59, length 1) must equal to
F(first in series of recurring).

06M5586900000000002 mmdd 657190 2 J00010080388314REALEX*TC104

06<1000000000000043000978 GBR LONDON F
06<A mmdd000000 0000000000000000000000000
06<B
06=0000000000000000043000MMDC123450402 599981 2
06=51211000100010V09000

Subsequent transactions in Series

These are the subsequent transactions in a series of recurring transactions. These transactions would have a capture
method of Card Not Present, Recurring for MasterCard and only if the IPQF flag is populated with a Y for Visa.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space filled.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space filled.

Interchange Program Qualification Flag (Bankcard and T & E Detail Addendum Record 1 (<1), Position 58, length 1).
This field is NOT required for MasterCard.
Y =Qualifies for RT rate Participation (VAU enabled or VAU authenticated)
N =Recurring rate is NOT sought.

Recurring Transaction Flag (Bankcard and T & E Detail Addendum Record 1 (<1), Position 59, length 1).
R =Recurring transaction, subsequent transactions in a series

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) (TC50 TCR00 (L) Pos 103-114)
0 =Unknown

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) (TC05 TCR0 Pos 160)
4 =Mail/Telephone or Electronic Commerce

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2). (TC05 TCR0 Pos 162-163)
01 =Key entered

CVV2 Result Code (VISA Detail Addendum Record 1 (#1), Position 56, Length 1) must be space filled.

80 Byte Population Guide Page 32 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Sample Transaction for the above example: VISA transaction as recurring in series (Recurring rates sought)
06V4018440000000018 mmdd 503314 2 00010080388314REALEX*TC93
06<1000000000000040000752 GBR LONDON YR
06<A mmdd000000 0000000000000000000000000
06<B
06#1504 00000004000075200 599901
06#3 000000 0000000040000

Sample Transaction for the above example: VISA transaction as recurring in series (Recurring rates are NOT sought)
06V4018440000000018 mmdd 503314 2 00010080388314REALEX*TC93
06<1000000000000040000752 GBR LONDON NR
06<A mmdd000000 0000000000000000000000000
06<B
06#1504 00000004000075200 599901
06#3 000000 0000000040000

MASTERCARD
Interchange Program Qualification Flag (Bankcard and T & E Detail Record 1, Position 58 (<1), length 1) must be space
filled.

Recurring Transaction Flag (Bankcard and T & E Detail Record 1, Position 59 (<1), length 1) must equal to R.
R =Recurring transaction, subsequent transactions in a series

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space filled.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space filled.

UCAF Status Indicator (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 53, length 1)
must be space filled.

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2)
01 =Key Entered.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1). (DE 22 S1)
1 =Manual, no terminal or unknown

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1). (DE 22 S2)
0 =No electronic authentication or unknown

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
(DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
(DE 22 S4)
0 =No terminal used

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1)(DE
22 S5)
4 =Cardholder not present, standing authorization

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) (DE 22 S6)
0 =Card not present or unknown

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1).
(DE 22 S7)

80 Byte Population Guide Page 33 of 216

Version 15.93
OmniPay Innovation in Transaction Management

1 =Manual, no terminal

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) (DE 22 S8)
0 =Not authenticated or unknown

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1). (DE 22 S9)
0 =Not authenticated or unknown
9 =Unknown

Address Verification Code (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 54, length
1) must be space filled.

Sample Transaction for the above example: MasterCard transaction as recurring in series
06M5409640000000009 mmdd 622472 2 00010080388314REALEX*TC101
06<1000000000000042000752 GBR LONDON R
06<A mmdd000000 0000000000000000000000000
06<B
06=0000000000000000042000MMDC123450402 599901
06=50000000100040100000

6.5 Visa Instalment Transactions

This section lists the information required to populate transactions that fall under the Visa definition of Instalment
Transactions. Visa mandates that any transactions which qualify as installment transactions be flagged as such.

Instalment transactions are a finite set of several transactions connected by a single Authorisation Code, and indicated
by an entry in the Recurring/Instalment Transaction Flag.

MCC of 6012 is reserved for Visa Debit Cards only. Other Card types may use other MCCs for instalment transactions.

First transaction in Series

This is the first transaction in a series of Instalment transactions and they should have the Capture method set
correctly as for a transaction of its type (i.e. eCom/Moto etc). First in series is not necessary but is catered for.

Recurring Transaction Flag (Bankcard and T & E Detail Addendum Record 1 (<1), Position 58, length 1)
X =Instalment Transaction (1st in Series Transaction)

Multiple Clearing Sequence Number ('#1' = VISA Detail Addendum Record 1, Position 72, length 2) First in series must
have Multiple Clearing Sequence number set to '01'.

Multiple Clearing Sequence Count ('#1' = VISA Detail Addendum Record 1, Position 74, length 2) Multiple clearing
sequence count reflects the total number of clearing transactions submitted for the same authorisation. If known, the
count may also be populated on the other clearing transactions associated with the authorization. If not known, the
count can be populated with all zeros or all spaces. In below examples '04' is used.

Sample Transaction for the above example: VISA Chip & PIN transaction as first in series
06V4018440000000018 mmdd 111760 1 IPN09051400000
06<1 000000006026978 X
06<A mmdd000000 0000000000000000000000000110704
06<B OASE02
06#1 52N 00000000602697800000000000000000 554205 0104
06#3 000000 0000000020400

Sample Transaction for the above example: VISA MOTO transaction with CVV2 as first in series
06V4018440000000018 mmdd 467041M5 00010080378498

80 Byte Population Guide Page 34 of 216

Version 15.93
OmniPay Innovation in Transaction Management

06<1000000000000010101826 GBR LONDON X

06<A mmdd000000 0000000000000000000000000
06<B
06#1594 00000001010182600 599901P 0 0104
06#3 U000000 0000000010101

Sample Transaction for the above example: VISA Secure eCom transaction as first in series
06V4018440000000018 mmdd 587523 2 500010080388314REALEX*TC92
06<1000000000000040000978 GBR LONDON X
06<A mmdd000000 0000000000000000000000000
06<B
06#1594 00000004000097800 599901M 0 0104
06#3 000000 0000000040000

Subsequent transactions in Series

These are the subsequent transactions in a series of Instalment transactions.

Recurring Transaction Flag (Bankcard and T & E Detail Addendum Record 1 (<1), Position 58, length 1)
I =Instalment Transaction (Subsequent Transaction)

Multiple Clearing Sequence Number ('#1' = VISA Detail Addendum Record 1, Position 74, length 2) Multiple Clearing
Sequence Number indicates what transaction number in the series this is. For example below, transaction '02' of '04'

Multiple Clearing Sequence Count ('#1' = VISA Detail Addendum Record 1, Position 74, length 2) Multiple clearing
sequence count reflects the total number of clearing transactions submitted for the same authorisation. If known, the
count may also be populated on the other clearing transactions associated with the authorization. If not known, the
count can be populated with all zeros or all spaces. In below examples '04' is used.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space filled.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space filled.

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) (TC50 TCR00 (L) Pos 103-114)
0 =Unknown

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1)(TC05 TCR0 Pos 160)
4 =Mail/Telephone or Electronic Commerce

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2). (TC05 TCR0 Pos 162-163)
01 =Key entered

CVV2 Result Code (VISA Detail Addendum Record 1 (#1), Position 56, Length 1) must be space filled.

AVS Response Code (VISA Detail Addendum Record 2 (#3), Position 32, Length 1) must be space filled.

Sample Transaction for the above example: VISA transaction as 2nd of 4 in series
06V4018440000000018 mmdd 503314 2 00010080388314REALEX*TC93
06<1000000000000040000752 GBR LONDON I
06<A mmdd000000 0000000000000000000000000
06<B
06#1504 00000004000075200 599901 0 0204
06#3 000000 0000000040000

6.6 Visa Multiple Clearing Records with Single Authorisation

80 Byte Population Guide Page 35 of 216

Version 15.93
OmniPay Innovation in Transaction Management

With these changes, merchants will now be able to submit a single authorization message for a card-not-present
transaction, and then submit separate clearing transactions as each part of the total order is fulfilled and shipped. This
practice is similar to that currently used for passenger transport transactions, especially for the airline industry, and
will provide merchants and acquirers with additional flexibility to process transactions.
These transactions are available in all regions except US.

First transaction in Series

This is the first transaction in a series of Multiple Clearing Record transactions and they should have the Capture
method set correctly as for a transaction of its type (i.e. eCom). The Authorisation code and Transaction ID should be
the same across all transactions, from First in series to Last in series.

VISA
Transaction ID ('#1' = VISA Detail Addendum Record 1, Position 31, length 15) Must match Transaction ID of second
and subsequent transactions.

Multiple Clearing Sequence Number ('#1' = VISA Detail Addendum Record 1, Position 72, length 2) First in series must
have Multiple Clearing Sequence number set to '01'.

Multiple Clearing Sequence Count ('#1' = VISA Detail Addendum Record 1, Position 76, length 2) Multiple clearing
sequence count reflects the total number of clearing transactions submitted for the same authorisation. If known, the
count may also be populated on the other clearing transactions associated with the authorization. If not known, the
count can be populated with all zeros or all spaces. In below examples '04' is used. '01' is not a viable option in this
field.

Sample Transaction for the above example: VISA Secure eCom transaction as first in series
06V4018440000000018 mmdd 587523 2 500010080388314REALEX*TC92
06<1000000000000040000978 GBR LONDON
06<A mmdd000000 0000000000000000000000000
06<B
06#1594 0000000400009780012345622456445 599901M 0 0104
06#3 000000 0000000040000

Subsequent transactions in Series

These are the subsequent transactions in a series of Multiple Clearing Sequence transactions.
Visa
Transaction ID ('#1' = VISA Detail Addendum Record 1, Position 31, length 15) Must match Transaction ID of initiating
Transaction.

Multiple Clearing Sequence Number ('#1' = VISA Detail Addendum Record 1, Position 72, length 2) Multiple Clearing
Sequence Number indicates what transaction number in the series this is. For example below, transaction '02' of '04'>
Number in this field for second and subsequent should start from '02'

Multiple Clearing Sequence Count ('#1' = VISA Detail Addendum Record 1, Position 74, length 2) Multiple clearing
sequence count reflects the total number of clearing transactions submitted for the same authorisation. The multiple
clearing sequence count in positions 4748 of each clearing transaction must be populated with the value that reflects
the total number of clearing transactions submitted for the same authorization. '01' is not a viable option in this field.

Sample Transaction for the above example: VISA transaction as 2nd of 4 in series
06V4018440000000018 mmdd 503314 2 500010080388314REALEX*TC93
06<1000000000000040000752 GBR LONDON
06<A mmdd000000 0000000000000000000000000
06<B
06#1504 0000000400007520012345622456445 599901 0 0204
06#3 000000 0000000040000

80 Byte Population Guide Page 36 of 216

Version 15.93
OmniPay Innovation in Transaction Management

6.7 MasterCard Multi Clearing Enhancement

This section lists the information required to populate transactions that fall under the MasterCard definition of
Multiple Clearing Enhancement. These are supported globally. This is not a mandatory population, but advised.
Brought on as part of Global 540Multi-Clearing Enhancements
For example, a merchant may find this solution useful when partial shipments, back orders, or multiple suppliers are
involved in a single purchase. This enables issuers to match multiple clearing events to an original authorization event
in order to accurately and sequentially manage a cardholders open-to-buy.

When a merchant obtains a single authorization approval representing multiple goods or services, the merchant may
clear the transaction through multiple presentments using the new Multi Clearing Enhancement system.

Authorisation Code, Banknet Date and Banknet Reference number must be populated from the initial Auth Response
in all related clearing transactions.

First to Penultimate transactions in Series

These the first to second last transactions in a series of Multiple Clearing Sequence transactions and they should have
the Capture method set correctly.

MASTERCARD
MasterCard Multi Clearing Sequence ID (MasterCard Interchange Compliance Detail Addendum Record 1 (=0),
Position 64, length 1):
M = Multi-Clearing Partial Amount, previously approved auth

Auth Code (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 64, length 1):
Mandatory field, Must match across all related clearing transactions

Banknet Reference Number (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 26, length
9):
Mandatory field, Must match across all related clearing transactions

Banknet Date (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 35, length 4):
Mandatory field, Must match across all related clearing transactions

Sample Transaction for the above example:

06M5409640000000009 mmdd 724169 00010080378497
06<1000000000000010909826 GBR LONDON N
06<A mmdd000000 0000000000000000000000000
06<B
06=0000000000000000010909MMDC123450320 599901 M
06=51211000600101600000

Last transaction in Series

This is the last transaction in a series of Multiple Clearing Sequence transactions.
MASTERCARD
MasterCard Multi Clearing Sequence ID (MasterCard Interchange Compliance Detail Addendum Record 1 (=0),
Position 64, length 1):
F = Final-Clearing Partial Amount, previously approved auth.

Auth Code (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 64, length 1):
Mandatory field, Must match across all related clearing transactions

Banknet Reference Number (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 26, length
9):
Mandatory field, Must match across all related clearing transactions

Banknet Date (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 35, length 4):
80 Byte Population Guide Page 37 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Mandatory field, Must match across all related clearing transactions

Sample Transaction for the above example:

06M5409640000000009 mmdd 724169 00010080378497
06<1000000000000010909826 GBR LONDON N
06<A mmdd000000 0000000000000000000000000
06<B
06=0000000000000000010909MMDC123450320 599901 F
06=51211000600101600000

6.8 MRPP Transactions

MasterCard have introduced MRPP (Maestro Recurring Payments Program) that will enable the Maestro brand to
accept recurring payments for e-commerce transactions that are acquired in Europe. This program enables Maestro
branded products to build on the existing Maestro Advance Registration Program by providing enhanced value to
members.

First in Series of MRPP transactions

First transaction in series must be full MasterCard Secure Code authenticated. Maestro transactions with UCAF-2
would have a capture method of eCommerce Channel Encrypt (2) and would qualify Ecommerce rates for Maestro.

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) for MasterCard must equal J
J =Channel encryption; cardholder certificate not used

Only those clients that authorize through Omnipay must flag first in series MC transactions with a value of F in the
Recurring Transaction Flag field. Other clients if authorizing transactions initiating the recurring series will need to consider
whether to include the value of F or space fill this field. This decision should be based on both the authorisation response
and clearing message.

Sample Transaction for the above example MasterCard Secure eCom transaction as first in series
Recurring Transaction Flag (Bankcard and T & E Detail Addendum Record 1 (<1), Position 59, length 1) must equal to
F(First In Series Of Recurring).

UCAF Status Indicator (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 53, length 1)
must be as follows. (DE 48 S3)
2 =Both merchant and issuer are UCAF enabled,as indicated in the Authorization Request/0100 message.
***Full secure Code transaction****(Full UCAF)

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2)
81 =PAN Entry via electronic commerce, including chip.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) (DE 22 S1)
1 =Manual, no terminal or unknown

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) (DE 22 S2)
0 =No electronic authentication or unknown

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1).
(DE 22 S3)
0 =None

80 Byte Population Guide Page 38 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
(DE 22 S4)
0 =No terminal used

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) (DE
22 S5)
5 =Electronic order (home PC, Internet, mobile phone, PDA)

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) (DE 22 S6)
0 =Card not present or unknown

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1).
(DE 22 S7)
S =Electronic Commerce

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1)(DE 22 S8)
0 =Not authenticated or unknown

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1)(DE 22 S9)
0 =Not authenticated or unknown
9 =Unknown

Sample transaction: Capture Method - eCommerce Channel Encrypt (Full UCAF)

06E mmdd 060145 2 J00010080388314
06<1000000000000032400344 GBR LONDON F
06<A mmdd000000 0000000000000000000000000
06<E606144000000000000410010067 00000000000090000000000000000000000000
06=0000000000000000031900MMDC123450323 599981 2N
06=51211000100050S00000

Subsequent in Series of MRPP transactions

These are the subsequent recurring MRPP transactions that are not secure authenticated as the first in series. These
transactions would have a capture method of KE, recurring and would qualify for Ecommerce rates for Maestro.

MASTERCARD
Interchange Program Qualification Flag (Bankcard and T & E Detail Record 1, Position 58 (<1), length 1)
A =MasterCard Assigned ID / Program Registration ID.

Recurring Transaction Flag (Bankcard and T & E Detail Addendum Record 1 (<1), Position 59, length 1)
R =Recurring transaction, subsequent transactions in a series

Interchange Program Value Field (Bankcard and T & E Detail Record 1, Position 60, length 10) must contain the
MasterCard Assigned ID/Program Registration ID. The MasterCard Assigned ID should be 6 digits in length. Program
Registration IDs should be 3 characters long and space-filled to the right. If Field contains a MasterCard Assigned ID,
this will populate PDS 0176; else it will populate PDS 0043 with the Program Registration ID. (PDS 0176 or PDS 0043)

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space filled.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space filled.

UCAF Status Indicator (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 53, length 1)
(DE 48 S3)
3 = UCAF data collection is supported by the merchant, and UCAF (MasterCard assigned Static
Accountholder Authentication Value)data must be present.
80 Byte Population Guide Page 39 of 216

Version 15.93
OmniPay Innovation in Transaction Management

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2)
01 =Key Entered.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1)(DE 22 S1)
1 =Manual, no terminal or unknown

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) (DE 22 S2)
0 =No electronic authentication or unknown

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length
1)(DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
(DE 22 S4)
0 =No terminal used

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1). (DE
22 S5)
4 =Cardholder not present, standing authorization

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) (DE 22 S6)
0 =Card not present or unknown

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1).
(DE 22 S7)
1 =Manual, no terminal

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1)(DE 22 S8)
0 =Not authenticated or unknown

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) (DE 22 S9)
0 =Not authenticated or unknown
9 =Unknown

Sample transaction: Capture Method - KE, recurring

06E mmdd 060145 2 00010080388314
06<1 000000020886978 AR405846
06<A mmdd000000 0000000000000000000000000
06<E606144000000000000410010067 00000000000090000000000000000000000000
06=0000000000000000031900MMDC123450323 599901 3N
06=51211000100040100000

6.9 MUPP Transactions

MasterCard have introduced MUPP(MasterCard Utility Payment Program) which enables enrolled Billers to process
transactions with a static AAV once a successful PIN or SecureCode authenticated transaction has taken place.

The program covers 2 area of bill payment

a) Recurring card payments for automating bill payments
b) E-billing integration, optimizing the payment experience of electronically presented bills

MUPP for Recurring payments

80 Byte Population Guide Page 40 of 216

Version 15.93
OmniPay Innovation in Transaction Management

The Biller periodically initiates transactions which may be a fixed amount or may vary with each billing. The first
transaction must be authenticated by either MasterCard SecureCode (for online initiated transactions) or PIN(for face
to face environments). If the first transaction is authorised by the issuer, the biller can omit the secure authentication
requirement on subsequent payments provided the same card account is used.

MUPP for E-Billing Payments

MUPP enables billers to optimise the payment experience of electronic bills by integrating a card based payment
option. The program will enable billers to provide consumers with a '1-click' bill payment experience.

For the first payment transaction SecureCode authentication will be required. If authorised, the biller can omit the
SecureCode authentication on subsequent payment transactions by the same customer when the same card
information is to be used.

Recurring Payment transactions - First in Series

As outlined above the first transaction in series must be full MasterCard Secure Code authenticated. MasterCard
transactions with UCAF-2 would have a capture method of eCommerce Channel Encrypt (2) and would qualify for
Full UCAF rates MasterCard and Ecommerce rates for Maestro.

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1)
J =Channel encryption; cardholder certificate not used

Charge Description (T&E Record, Position 56, Length 25)

BILL (or local language equivalent)
Note: Clients have the option of including the description of 'BILL' (or local language equivalent) in this field in order to
label the transaction as a MUPP transaction on the scheme files.

Interchange Program Qualification Flag(<1 Record, Position 58 , Length 1)

A = MasterCard Assigned ID / Program Registration Id.

Recurring Transaction Flag (Bankcard and T & E Detail Addendum Record 1 (<1), Position 59, length 1) must equal to
F(first in series of recurring).
Only those clients that authorize through Omnipay must flag first in series MC transactions with a value of F in the
Recurring Transaction Flag field. Other clients if authorizing transactions initiating the recurring series will need to consider
whether to include the value of F or space fill this field. This decision should be based on both the authorisation response
and clearing message.

Interchange Program Value Field (<1 Record, Position 60 , Length 10).

'XXXXXX' =('X' Depicts an individual digit of the MAID or Program Reg ID)
The MasterCard Assigned ID should be 6 digits in length. Program Registration Ids should be 3
characters long and space-filled to the right. If Field contains a MasterCard Assigned Id, this will
populate PDS 0176, else it will populate PDS 0043 with the Program Registration ID.

UCAF Status Indicator (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 53, length 1).
(DE 48 S3)
2 =Both merchant and issuer are UCAF enabled,as indicated in the Authorization Request/0100 message.

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2)
81 =PAN Entry via electronic commerce, including chip.

Merchant Category Code MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 45, length 4)
4814 =Telecom Services
4816 =Computer Network/Information Services
4899 =Cable, Satellite & other Pay Television and Radio Services
4900 =Utilities

80 Byte Population Guide Page 41 of 216

Version 15.93
OmniPay Innovation in Transaction Management

6050 =Quasi Cash - Merchant Institution

6051 =Quasi Cash - Merchant
6300 =Insurance Sales, Underwriting, Premiums

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) (DE 22 S1)
1 =Manual, no terminal or unknown

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) (DE 22 S2)
0 =No electronic authentication or unknown

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
(DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
(DE 22 S4)
0 =No terminal used

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1)(DE
22 S5)
5 =Electronic order (home PC, Internet, mobile phone, PDA)

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) (DE 22 S6)
0 =Card not present or unknown

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1).
(DE 22 S7)
S =Electronic Commerce

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) (DE 22 S8)
0 =Not authenticated or unknown

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) (DE 22 S9)
0 =Not authenticated or unknown
9 =Unknown

Sample transaction: Capture Method - eCommerce Channel Encrypt , Full UCAF

06M5409640000000009 mmdd 060145 2 J00010080388314firstINseriesBILL
06<1000000000000031900978 GBR LONDON AF408800
06<A mmdd000000 0000000000000000000000000
06<B
06=0000000000000000031900MMDC123450323 481481 2N
06=51211000100050S00000

Sample transaction: Capture Method - eCommerce Channel Encrypt , ECOM

06E mmdd 060145 2 J00010080388314firstINseriesBILL
06<1000000000000032400344 GBR LONDON AF408800
06<A mmdd000000 0000000000000000000000000
06<E606144000000000000410010067 00000000000090000000000000000000000000
06=0000000000000000031900MMDC123450323 481481 2N
06=51211000100050S00000

Recurring Payment transactions - Subsequent in Series

80 Byte Population Guide Page 42 of 216

Version 15.93
OmniPay Innovation in Transaction Management

These are the subsequent MUPP transactions that are not secure authenticated as the first in series. These
transactions would have a capture method of eCommerce Channel Encrypt for MasterCard and would qualify for
Full UCAF rates if the UCAF value is 3. First transaction in series must be full MasterCard Secure Code authenticated
in order for the subsequent MUPP transactions to qualify for Full UCAF rates MasterCard and Ecommerce rates for
Maestro.

MASTERCARD
Interchange Program Qualification Flag (Bankcard and T & E Detail Record 1, Position 58 (<1), length 1)
A =MasterCard Assigned ID / Program Registration ID.

Interchange Program Value Field (Bankcard and T & E Detail Record 1, Position 60, length 10) must contain the
MasterCard Assigned ID/Program Registration ID. The MasterCard Assigned ID should be 6 digits in length. Program
Registration IDs should be 3 characters long and space-filled to the right. If Field contains a MasterCard Assigned ID,
this will populate PDS 0176; else it will populate PDS 0043 with the Program Registration ID. (PDS 0176 or PDS 0043)

Charge Description (T&E Record, Position 56, Length 25)

BILL (or local language equivalent )
Note: Clients have the option of including the description of 'BILL' (or local language equivalent) in this field in order to
label the transaction as a MUPP transaction on the scheme files.

Recurring Transaction Flag (Bankcard and T & E Detail Addendum Record 1 (<1), Position 59, length 1)
R =Recurring transaction, subsequent transactions in a series

Merchant Category Code MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 45, length 4)
4814 =Telecom Services
4816= Computer Network/Information Services
4899 =Cable, Satellite & other Pay Television and Radio Services
4900 =Utilities
6050 =Quasi Cash - Merchant Institution
6051 =Quasi Cash - Merchant
6300 =Insurance Sales, Underwriting, Premiums

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space filled.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must equal Space filled.

UCAF Status Indicator (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 53, length 1)
(DE 48 S3)
3 =UCAF data collection is supported by the merchant, and UCAF (MasterCard assigned Static
Accountholder Authentication Value)data must be present.

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2)
01 =Key Entered.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) (DE 22 S1)
1 =Manual, no terminal or unknown

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) (DE 22 S2)
0 =No electronic authentication or unknown

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
(DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length
1).(DE 22 S4)

80 Byte Population Guide Page 43 of 216

Version 15.93
OmniPay Innovation in Transaction Management

0 =No terminal used

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) (DE
22 S5)
4 =Cardholder not present, standing authorization

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) (DE 22 S6)
0 =Card not present or unknown

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
(DE 22 S7)
1 =Manual, no terminal

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1). (DE 22 S8)
0 =Not authenticated or unknown

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1).(DE 22 S9)
0 =Not authenticated or unknown
9 =Unknown

Sample transaction: Capture Method - eCommerce Channel Encrypt , Full UCAF

06M5409640000000009 mmdd 060145 2 00010080388314SubINseriesBILL
06<1000000000000031900978 GBR LONDON AR408800
06<A mmdd000000 0000000000000000000000000
06<B
06=0000000000000000031900MMDC123450323 481401 3
06=51211000100040100000

Sample transaction: Capture Method - eCommerce Channel Encrypt , Ecom

06E mmdd 060145 2 00010080388314SubINseriesBILL
06<1000000000000032400344 GBR LONDON AR408800
06<A mmdd000000 0000000000000000000000000
06<E606144000000000000410010067 00000000000090000000000000000000000000
06=0000000000000000031900MMDC123450323 481401 3
06=51211000100040100000

EBilling Payment transactions - First in Series

As outlined above the first transaction in series must be full MasterCard Secure Code authenticated. MasterCard
transactions with UCAF-2 would have a capture method of eCommerce Channel Encrypt (2) and would qualify for
Full UCAF rates MasterCard and Ecommerce rates for Maestro.

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Charge Description (T&E Record, Position 56, Length 25)

BILL (or local language equivalent)
Note: Clients have the option of including the description of 'BILL' (or local language equivalent) in this field in order to
label the transaction as a MUPP transaction on the scheme files.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1)
J =Channel encryption; cardholder certificate not used

UCAF Status Indicator (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 53, length 1)
(DE 48 S3)

80 Byte Population Guide Page 44 of 216

Version 15.93
OmniPay Innovation in Transaction Management

2 =Both merchant and issuer are UCAF enabled,as indicated in the Authorization Request/0100 message.

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2)
81 =PAN Entry via electronic commerce, including chip.

Merchant Category Code MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 45, length 4)
4814 =Telecom Services
4816 =Computer Network/Information Services
4899 =Cable, Satellite & other Pay Television and Radio Services
4900 =Utilities
6050 =Quasi Cash - Merchant Institution
6051 =Quasi Cash - Merchant
6300 =Insurance Sales, Underwriting, Premiums

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1)(DE 22 S1)
1 =Manual, no terminal or unknown

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1)(DE 22 S2)
0 =No electronic authentication or unknown

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
(DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1).
(DE 22 S4)
0 =No terminal used

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1). (DE
22 S5)
5 =Electronic order (home PC, Internet, mobile phone, PDA)

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) (DE 22 S6)
0 =Card not present or unknown

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
(DE 22 S7)
S =Electronic Commerce

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1)(DE 22 S8)
0 =Not authenticated or unknown

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1)(DE 22 S9)
0 =Not authenticated or unknown
9 =Unknown

Sample transaction: Capture Method - eCommerce Channel Encrypt (Full UCAF)

06M5409640000000009 mmdd 060145 2 J00010080388314firstINseriesEBILL
06<1000000000000031900978 GBR LONDON
06<A mmdd000000 0000000000000000000000000
06<B
06=0000000000000000031900MMDC123450323 481481 2N
06=51211000100050S00000

80 Byte Population Guide Page 45 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Sample transaction: Capture Method - eCommerce Channel Encrypt (Full UCAF)

06E mmdd 060145 2 J00010080388314firstINseriesEBILL
06<1000000000000032400344 GBR LONDON
06<A mmdd000000 0000000000000000000000000
06<E606144000000000000410010067 00000000000090000000000000000000000000
06=0000000000000000031900MMDC123450323 481481 2N
06=51211000100050S00000

EBilling Payment transactions - Subsequent in Series

These are the subsequent EBilling transactions that are not secure authenticated as the first in series. These
transactions would have a capture method of eCommerce Channel Encrypt for MasterCard and would qualify for
Full UCAF rates if the UCAF value is 3. First transaction in series must be full MasterCard Secure Code authenticated
in order for the subsequent MARP transactions to qualify for Full UCAF rates MasterCard and Ecommerce rates for
Maestro.

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) for MasterCard must equal J
J =Channel encryption; cardholder certificate not used

Charge Description (T&E Record, Position 56, Length 25)

BILL(or local language equivalent)
Note: Clients have the option of including the description of 'BILL' (or local language equivalent) in this field in order to
label the transaction as a MUPP transaction on the scheme files.

Interchange Program Qualification Flag(<1 Record, Position 58 , Length 1)

A =MasterCard Assigned ID / Program Registration Id.

Interchange Program Value Field (<1 Record, Position 60 , Length 10).

XXXXXX ='X' Depicts an individual digit of the MAID or Program Reg ID
The MasterCard Assigned ID should be 6 digits in length. Program Registration Ids should be 3 characters long and
space-filled to the right. If Field contains a MasterCard Assigned Id, this will populate PDS 0176, else it will populate
PDS 0043 with the Program Registration ID.

UCAF Status Indicator (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 53, length 1)
(DE 48 S3)
3 =UCAF data collection is supported by the merchant, and UCAF (MasterCard assigned Static
Accountholder Authentication Value)data must be present.

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2)
01 =Key Entered.

Merchant Category Code MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 45, length 4)
4814 =Telecom Services
4816 =Computer Network/Information Services
4899 =Cable, Satellite & other Pay Television and Radio Services
4900 =Utilities
6050 =Quasi Cash - Merchant Institution
6051 =Quasi Cash - Merchant
6300 =Insurance Sales, Underwriting, Premiums

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) (DE 22 S1)
1 =Manual, no terminal or unknown

80 Byte Population Guide Page 46 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) (DE 22 S2)
0 =No electronic authentication or unknown

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1).
(DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1).
(DE 22 S4)
0 =No terminal used

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) (DE
22 S5)
4 =Cardholder not present, standing authorization

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) (DE 22 S6)
0 =Card not present or unknown

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1).
(DE 22 S7)
1 =Manual, no terminal

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) (DE 22 S8)
0 =Not authenticated or unknown

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) (DE 22 S9)
0 =Not authenticated or unknown
9 =Unknown

Sample transaction: Capture Method - eCommerce Channel Encrypt

06M5409640000000009 mmdd 060145 2 J00010080388314SubinSeriesEBILL
06<1000000000000031900978 GBR LONDON A 408800
06<A mmdd000000 0000000000000000000000000
06<B
06=0000000000000000031900MMDC123450323 481401 3N
06=51211000100040100000

Sample transaction: Capture Method - eCommerce Channel Encrypt

06E mmdd 060145 2 J00010080388314Subin SeriesEBILL
06<1000000000000032400344 GBR LONDON A 408800
06<A mmdd000000 0000000000000000000000000
06<E606144000000000000410010067 00000000000090000000000000000000000000
06=0000000000000000031900MMDC123450323 481401 3N
06=51211000100040100000

6.10 MasterPass Transaction

MasterPass On Mastercard
E-commerce Security Level Indicators
Non-Secure Merchant UCAF (Merchant Only) Full UCAF (Fully Authenticated)
Cardholder authentication not Cardholder authentication attempted Merchant, issuer and cardholder
performed by merchant; however, issuer or participated and cardholder
cardholder didnt participate authenticated

80 Byte Population Guide Page 47 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Security Protocol-Channel Security Protocol-Channel Security Protocol-Channel

Processed through MasterPass Processed through MasterPass Processed through MasterPass
Non-SecureCode - UCAF:0 or Attempts processing UCAF:1 Issuer fully authentication UCAF:2
merchant risk based decisioning or issuer risk based decisioning
UCAF:6 UCAF:5

These transactions are Card Not Present transactions performed with a card that is stored within the MasterPass E-
wallet. The transaction qualifies at the appropriate rate for a transaction of its type, but carries a flag which identifies
it as an E-Wallet transaction. Subsequent revisions will implement a specific rate for these transactions.

All cards carried on the Masterpass E-Wallet should carry the following value:
E-Wallet Type (Bankcard and T & E Detail Addendum Record B (<B) Pos 59, Len 1).
M =MasterCard PPOL/MasterPass

Below is an example for Secured Ecommerce, with a MasterCard e-wallet.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) (TC05 TCR1 Pos 116)
5 =the cardholder was authenticated using a Visa-approved authentication methodology. The
authorization message was successfully authenticated by Verified by Visa. ***Full VbV transaction****
6 =the merchant is capable of and attempted to authenticate the cardholder using Verified by Visa, but
the cardholder did not participate.

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) (TC50 TCR00 (L) Pos 103-114)
9 =Key entered (no card reader available)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) (TC05 TCR0 Pos 160)
4 =Mail/Telephone or Electronic Commerce

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2). (TC05 TCR0 Pos 162-163)
01 =Key Entered.

AVS Response Code (VISA Detail Addendum Record 2 (#3), Position 32, Length 1) must be populated. (TC05 TCR1, Pos
127). The value is derived from the AVS field (BM44.2) in the authorization message for ISO8583 format

CVV2 Result Code (VISA Detail Addendum Record 1 (#1), Position 56, Length 1) must be populated. (TC05 TCR5, Pos
127). The value is derived from the CVV2 field (BM44.10) in the authorization message for ISO8583 format.

E-Wallet Type (Bankcard and T & E Detail Addendum Record B (<B) Pos 59, Len 1).
M =MasterCard PPOL/MasterPass

PPOL Program Data (Bankcard and T & E Detail Addendum Record B (<B) Pos 64, Len 1)
SPACE FILL

Sample transaction: Capture Method - SET/3D-SET authenticated - Visa card, MasterPass E-Wallet
06V4018440000000018 mmdd 142869 2 500010080388314
06<1000000000000030000826 GBR LONDON NN
06<A mmdd000000 0000000000000000000000000
06<B M
06#1594 00000003000082600 599901P 0
06#3 U000000 0000000030000

80 Byte Population Guide Page 48 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Sample transaction: Capture Method - SET/3D-SET non-authenticated - Visa Card, MasterPass E-Wallet
06V4018440000000018 mmdd 142869 2 600010080388314
06<1543275000000020400978 GBR www.yahoo.ie NN
06<A mmdd000000 0000000000000000000000000
06<B M
06#1594 00000003000082600 599901P 0
06#3 U000000 0000000030000

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1)
J =Channel encryption; cardholder certificate not used

UCAF Status Indicator (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 53, length 1)(DE
48 S3)
0 =UCAF data collection is not supported at the merchants website. Does not qualify for UCAF Rates
1 = UCAF data collection is supported by the merchant, and UCAF data must be present
2 = Both merchant and issuer are UCAF enabled,as indicated in the Authorization Request/0100 message.
5 =MasterPass Transaction: Issuer risk based decisioning. MasterPass Interchange rate is available.
6 =MasterPass Transaction: Merchant risk based decisioning. Standard eCom rates currently apply

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2)
81 =Ecommerce

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) (DE 22 S1)
1 =Manual, no terminal or unknown

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1). (DE 22 S2)
0 =No electronic authentication or unknown

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
(DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
(DE 22 S4)
0 =No terminal used

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) (DE
22 S5)
5 =Electronic order (home PC, Internet, mobile phone, PDA)

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) (DE 22 S6)
0 =Card not present or unknown

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
(DE 22 S7)
S =Electronic Commerce

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) (DE 22 S8)
0 =Not authenticated or unknown

80 Byte Population Guide Page 49 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) (DE 22 S9)
0 =Not authenticated or unknown
9 =Unknown

Address Verification Code (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 54, length
1) must be populated. The value is derived from the AVS field (BM60.32) in the authorization message for ISO8583
format

E-Wallet Type (Bankcard and T & E Detail Addendum Record B (<B) Pos 59, Len 1).
M = MasterCard PPOL/MasterPass (PDS 0207)

PPOL Program Data (Bankcard and T & E Detail Addendum Record B (<B) Pos 64, Len 1(value is left aligned)
1 =PPOL remote (DE 48 (Sub element 26)

Sample transaction: Capture Method - MasterCard (MasterCard card, MasterPass MasterCard E-Wallet- Merchant
UCAF)
06M5409640000000009 mmdd 060145 2 J00010080388314
06<1000000000000031900978 GBR LONDON N
06<A mmdd000000 0000000000000000000000000
06<B M 2
06=0000000000000000031900MMDC123450323 599901 5N
06=51211000100050S00000

Sample transaction: Capture Method - MasterCard (MasterCard card, MasterPass MasterCard E-Wallet- Full UCAF)
06M5409640000000009 mmdd 060145 2 J00010080388314
06<1000000000000031900978 GBR LONDON N
06<A mmdd000000 0000000000000000000000000
06<B M 2
06=0000000000000000031900MMDC123450323 599901 5N
06=51211000100050S00000

Sample transaction: Capture Method - MasterCard (MasterCard card, MasterPass MasterCard E-Wallet- Issuer Risk
Based Decisioning)
06M5409640000000009 mmdd 060145 2 J00010080388314
06<1000000000000031900978 GBR LONDON N
06<A mmdd000000 0000000000000000000000000
06<B M 5
06=0000000000000000031900MMDC123450323 599901 5N
06=51211000100050S00000

Sample transaction: Capture Method - MasterCard, MasterPass E-Wallet, Merchant Risk Based Decisioning
06M5409640000000009 mmdd 060145 2 J00010080388314
06<1000000000000031900978 GBR LONDON N
06<A mmdd000000 0000000000000000000000000
06<B M 6
06=0000000000000000031900MMDC123450323 599901 6N
06=51211000100050S00000

6.11 MasterPass Enabled Merchant- non MasterPass transaction

These transactions are Card Not Present transactions performed with a MasterPass enabled merchant, but are non
MasterPass transactions. They apply to MasterCard Transactions only.

Below is an example for Secured Ecommerce, with a MasterPass enabled Merchant.

80 Byte Population Guide Page 50 of 216

Version 15.93
OmniPay Innovation in Transaction Management

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1)
J =Channel encryption; cardholder certificate not used

UCAF Status Indicator (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 53, length 1)
(DE 48 S3)
1 = UCAF data collection is supported by the merchant, and UCAF data must be present
(Merchant UCAF)
2 = Both merchant and issuer are UCAF enabled,as indicated in the Authorization Request/0100 message
***Full secure Code transaction**** (Full UCAF)

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2)
81 =Key Entered.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1). (DE 22 S1)
1 =Manual, no terminal or unknown

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1). (DE 22 S2)
0 =No electronic authentication or unknown

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
(DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
(DE 22 S4)
0 =No terminal used

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) (DE
22 S5)
5 =Electronic order (home PC, Internet, mobile phone, PDA)

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) (DE 22 S6)
0 =Card not present or unknown

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
(DE 22 S7)
S =Electronic Commerce

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) (DE 22 S8)
0 =Not authenticated or unknown

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1)(DE 22 S9)
0 =Not authenticated or unknown
9 =Unknown

Address Verification Code (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 54, length
1) must be populated. The value is derived from the AVS field (BM60.32) in the authorization message for ISO8583
format

E-Wallet Type (Bankcard and T & E Detail Addendum Record B (<B) Pos 59, Len 1) must be populated.

80 Byte Population Guide Page 51 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Must not be 'M'

PPOL Program Data (Bankcard and T & E Detail Addendum Record B (<B) Pos 64, Len 1(value is left aligned)
A =MasterPass Enabled Merchant (PDS 0042)

Sample transaction: Capture Method - eCommerce Channel Encrypt (Merchant UCAF) - MasterCard card,
MasterPass enabled Merchant
06M5409640000000009 mmdd 060145 2 J00010080388314
06<1000000000000031900978 GBR LONDON N
06<A mmdd000000 0000000000000000000000000
06<B A
06=0000000000000000031900MMDC123450323 599901 1N
06=51211000100050S00000

Sample transaction: Capture Method - eCommerce Channel Encrypt (Full UCAF) - MasterCard, MasterPass enabled
Merchant
06M5409640000000009 mmdd 060145 2 J00010080388314
06<1000000000000031900978 GBR LONDON N
06<A mmdd000000 0000000000000000000000000
06<B A
06=0000000000000000031900MMDC123450323 599901 2N
06=51211000100050S00000

6.12 Tokenised E-Wallet

These transactions are Card Not Present transactions performed with a Digital Wallet that is not MasterPass or V.Me,
and instead of passing the Card Number of the customer on each transaction, contain a tokenised card number. In
addition a Cryptogram assuring security is used on the authorisation for the transaction. Visa have indicted that
Applepay specific transactions for Visa must be passed with a value of 7 in the ECI field.
Tokenised Ewallets are supported currently by both Visa and MasterCard. MasterCard Tokenised Wallets should use
the Digital Secure Remote Payments system as detailed in the subsection below.
ApplePay is an example of a Tokenised Ewallet that is supported by Omnipay.
Visa Specific Applepay requirements

6.13 MasterCard Digital Secure Remote Payments

These transactions are based around the concept of a secure Digital Wallet such as Apple Pay on a mobile phone or
similar device performing as Card Present or Card Not Present standard transactions with enhanced security. EMV
data is available for certain transactions despite the card not being physically present at point of sale.
MasterCard are allowing both on & off cardholder acceptor facility transactions for DSRP, these options can be
reflected in DE 22 S4 (Operating Environment), as outlined in the Digital Secure Remote Payment Acquirer
Implementation Guide chapter on POS Terminal Location Handling. MasterCard state that value of Operating
Environment - DE 22 S 4 = 4 (Off card acceptor premises) can be used when the location of the consumer at the time
of the transaction is irrelevant (even if the cardholder is coincidentally on the premises of the card acceptor).

The following details requirements for FULL EMV DSRP.

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) must be populated

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space filled

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space filled

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2)
07 =PAN auto-entry via contactless chip

80 Byte Population Guide Page 52 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) must be as follows. (DE 22 S1)

M =PAN auto-entry via contactless M/Chip

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) (DE 22 S2)
1 =PIN

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
(DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1).
(DE 22 S4)
2 =On premises of card acceptor, unattended
4 =Off premises of card acceptor, unattended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1 (DE 22
S5)
5 =Cardholder not present (electronic orderPC, internet, mobile phone or PDA)

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) (DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
(DE 22 S7)
R =Remote DSRP

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be as follows. (DE 22 S8)
1 =PIN

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be as follows (DE 22 S9)
3 =Authorising agent

On card acceptor premises; unattended terminal

06M5462970000000004 mmdd 112723 0 00010080382600
06<1 000000012600826 GBR 117 WARWICK W
06<A mmdd0000001978 0000000152880000000012133122301+00
06<B 02501600240023025016
06=0000000000000000015288112723 0627 701107 0
06=51412019M10251R13146
06@1001090627E0B8C0826978A0000000041010 0015780008000080000002
06@2000000015288 F573155C4B44FFD540000024002302501646B33C36000000000000
06@30110601003240000000000000000000000FF 005E030022R

Off card acceptor premises; unattended

06M5462970000000004 mmdd 112723 0 00010080382600
06<1 000000012600826 GBR 117 WARWICK W
06<A mmdd0000001978 0000000152880000000012133122301+00
06<B 02501600240023025016
06=0000000000000000015288112723 0627 701107 0
06=51412019M10451R13146
06@1001090627E0B8C0826978A0000000041010 0015780008000080000002
06@2000000015288 F573155C4B44FFD540000024002302501646B33C36000000000000

80 Byte Population Guide Page 53 of 216

Version 15.93
OmniPay Innovation in Transaction Management

06@30110601003240000000000000000000000FF 005E030022R

The following details requirements for UCAF DSRP.

MASTERCARD
UCAF DSRP
Similar to Ecommerce Requirements, please note ECI value is Z & UCAF indicator is 2

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) for MasterCard must equal J
Z =Channel encryption; cardholder certificate not used

UCAF Status Indicator (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 53, length 1)
(DE 48 S3)
2 = Both merchant and issuer are UCAF enabled,as indicated in the Authorization Request/0100 message

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2)
81 =PAN Entry via electronic commerce, including chip.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1)(DE 22 S1)
1 =Manual, no terminal or unknown

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1)(DE 22 S2)
0 =No electronic authentication or unknown

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length
1)(DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
(DE 22 S4)
2 =On premises of card acceptor, unattended
4 = Off premises of card acceptor, unattended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1 (DE 22
S5)
5 = Cardholder not present (electronic orderPC, internet, mobile phone or PDA)

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1)(DE 22 S6)
0 =Card not present or unknown

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)(DE
22 S7)
S =Electronic Commerce

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1)(DE 22 S8)
0 =Not authenticated or unknown

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1)(DE 22 S9)
0 =Not authenticated or unknown
9 =Unknown

80 Byte Population Guide Page 54 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Address Verification Code (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 54, length
1) must be populated. The value is derived from the AVS field (BM60.32) in the authorization message for ISO8583
format

On card acceptor premises; unattended terminal

06M5409640000000009 mmdd 060145 2 Z00010080388314
06<1000000000000031900978 GBR LONDON
06<A mmdd000000 0000000000000000000000000
06<B
06=0000000000000000031900MMDC123450323 599981 2N
06=51211000100250S00000

Off card acceptor premises; unattended

06M5409640000000009 mmdd 060145 2 Z00010080388314
06<1000000000000031900978 GBR LONDON
06<A mmdd000000 0000000000000000000000000
06<B
06=0000000000000000031900MMDC123450323 599981 2N
06=51211000100450S00000

The following details requirements for Partial Shipping DSRP.

Partial Shipping DSRP:
Similar to Ecommerce Requirements, please note ECI value is Z & UCAF indicator is the new value 7

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1)
Z =Channel encryption; cardholder certificate not used

UCAF Status Indicator (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 53, length 1).
(DE 48 S3)
7 = Partial shipment- DSRP

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2)
81 =PAN Entry via electronic commerce, including chip.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1)(DE 22 S1)
1 =Manual, no terminal or unknown

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1)(DE 22 S2)
0 =No electronic authentication or unknown

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length
1)(DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
(DE 22 S4)
2 =On premises of card acceptor, unattended
4 = Off premises of card acceptor, unattended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1 (DE 22
S5)
5 =Electronic order (home PC, Internet, mobile phone, PDA)

80 Byte Population Guide Page 55 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1)(DE 22 S6)
0 =Card not present or unknown

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)(DE
22 S7)
S =Electronic Commerce

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1)(DE 22 S8)
0 =Not authenticated or unknown

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1)(DE 22 S9)
0 =Not authenticated or unknown
9 =Unknown

Address Verification Code (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 54, length
1) must be populated. The value is derived from the AVS field (BM60.32) in the authorization message for ISO8583
format

On card acceptor premises; unattended terminal

06M5409640000000009 mmdd 060145 2 Z00010080388314
06<1000000000000031900978 GBR LONDON
06<A mmdd000000 0000000000000000000000000
06<B
06=0000000000000000031900MMDC123450323 599981 7N
06=51211000100250S00000

Off card acceptor premises; unattended

06M5409640000000009 mmdd 060145 2 Z00010080388314
06<1000000000000031900978 GBR LONDON
06<A mmdd000000 0000000000000000000000000
06<B
06=0000000000000000031900MMDC123450323 599981 7N
06=51211000100450S00000

The following details requirements for Recurring DSRP

Recurring DSRP:
Similar to Partial Shipping Requirements but requires the recurring indicator to be present, please note ECI value is Z,
UCAF indicator is the new value 7 and Recurring Flag is R.
The first in series will be a UCAF DSRP or as an EMV DSRP as outlined above.
The First in series transaction does not contain an explicit link through authorisation to the second and subsequent
transaction.

Below outlines the population for a second (and subsequent in series)

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1)
Z =Channel encryption; cardholder certificate not used

Recurring Transaction Flag (Bankcard and T & E Detail Addendum Record 1 (<1), Position 59, length 1).
R =Recurring transaction, subsequent transactions in a series

UCAF Status Indicator (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 53, length 1).
(DE 48 S3)

80 Byte Population Guide Page 56 of 216

Version 15.93
OmniPay Innovation in Transaction Management

7 =DSRP recurring payment

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2)
81 =PAN Entry via electronic commerce, including chip.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1)(DE 22 S1)
1 =Manual, no terminal or unknown

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1)(DE 22 S2)
0 =No electronic authentication or unknown

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length
1)(DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
(DE 22 S4)
4 = Off premises of card acceptor, unattended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1 (DE 22
S5)
5 =Cardholder not present (electronic orderPC, internet, mobile phone or PDA

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1)(DE 22 S6)
0 =Card not present or unknown

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)(DE
22 S7)
S =Electronic Commerce

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1)(DE 22 S8)
0 =Not authenticated or unknown

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1)(DE 22 S9)
0 =Not authenticated or unknown
9 =Unknown

Address Verification Code (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 54, length
1) must be populated. The value is derived from the AVS field (BM60.32) in the authorization message for ISO8583
format

Off card acceptor premises; unattended

06M5409640000000009 mmdd 060145 2 Z00010080388314
06<1000000000000031900978 GBR LONDON R
06<A mmdd000000 0000000000000000000000000
06<B
06=0000000000000000031900MMDC123450323 599981 7N
06=51211000100450S00000

80 Byte Population Guide Page 57 of 216

Version 15.93
OmniPay Innovation in Transaction Management

6.14 Digital Wallet

These transactions are Card Not Present transactions performed with a Digital Wallet that is not MasterPass or V.Me,
and is not tokenised. They apply to MasterCard Transactions only. MasterCard have mandated that these transaction
types be populated with the Digital Wallet ID (WID) assigned by MasterCard.

Digital wallets will not qualify for MasterPass Incentive interchange and should be treated like existing eCommerce
Transactions.

Below is an example for Secured Ecommerce from a third party digital wallet operator.

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1)
J =Channel encryption; cardholder certificate not used

UCAF Status Indicator (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 53, length 1)
(DE 48 S3)
1 = UCAF data collection is supported by the merchant, and UCAF data must be present
2 = Both merchant and issuer are UCAF enabled,as indicated in the Authorization Request/0100 message.

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2)
01 =Key Entered.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) (DE 22 S1)
1 =Manual, no terminal or unknown

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1)(DE 22 S2)
0 =No electronic authentication or unknown

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1).
(DE 22 S3)
0 =None

Operating Environment(MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1).
(DE 22 S4)
0 =No terminal used

Cardholder Present(MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1)(DE 22
S5)
5 =Electronic order (home PC, Internet, mobile phone, PDA)

Card Present(MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1)(DE 22 S6)
0 =Card not present or unknown

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1).
(DE 22 S7)
S =Electronic Commerce

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) (DE 22 S8)
0 =Not authenticated or unknown

80 Byte Population Guide Page 58 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) (DE 22 S9)
0 =Not authenticated or unknown
9 =Unknown

Address Verification Code (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 54, length
1) must be populated. The value is derived from the AVS field (BM60.32) in the authorization message for ISO8583
format

E-Wallet Type (Bankcard and T & E Detail Addendum Record B (<B) Pos 59, Len 1).
Space Fill

WID-DWO: (Bankcard and T & E Detail Addendum Record B (<B) Pos 65-68, Len 3). (PDS 0207)
This Value is provided by MasterCard. Do not populate unless in agreement with Omnipay.

Sample transaction: Capture Method - eCommerce Channel Encrypt (Merchant UCAF) - MasterCard card, Digital
Wallet enabled Merchant
06M5409640000000009 mmdd 060145 2 J00010080388314
06<1000000000000031900978 GBR LONDON N
06<A mmdd000000 0000000000000000000000000
06<B 007
06=0000000000000000031900MMDC123450323 599901 1N
06=51211000100050S00000

Sample transaction: Capture Method - eCommerce Channel Encrypt (Full UCAF) - MasterCard, Digital Wallet
enabled Merchant
06M5409640000000009 mmdd 060145 2 J00010080388314
06<1000000000000031900978 GBR LONDON N
06<A mmdd000000 0000000000000000000000000
06<B A05
06=0000000000000000031900MMDC123450323 599901 2N
06=51211000100050S00000

6.15 Visa Checkout

These transactions are Card Not Present or Card Present transactions performed with merchants registered with Visa
Checkout. These transactions are not tokenised. They apply to Visa Transactions only.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response message. (TC50
TCR0 Pos 152-157)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) for Visa must equal 7. (TC05
TCR1 Pos 116)
7 =the cardholders payment card was protected with a form of internet security, such as SSL, and
authentication was performed.

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) (TC50 TCR0 Pos 158)
9 =Key entered (no card reader available)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1). (TC05 TCR0 Pos 160)
4 =Mail/Telephone or Electronic Commerce

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2). (TC05 TCR0 Pos 162-163)
01 =Key Entered

E-Wallet Type (Bankcard and T & E Detail Addendum Record B (<B) Pos 59, Len 1).

80 Byte Population Guide Page 59 of 216

Version 15.93
OmniPay Innovation in Transaction Management

C =VISA CHECKOUT

AVS Response Code (VISA Detail Addendum Record 2 (#3), Position 32, Length 1) must be populated. (TC05 TCR1, Pos
127). The value is derived from the AVS field (BM44.2) in the authorization message for ISO8583 format.

CVV2 Result Code (VISA Detail Addendum Record 1 (#1), Position 56, Length 1) must be populated. (TC05 TCR5, Pos
127). The value is derived from the CVV2 field (BM44.10) in the authorization message for ISO8583 format.

Sample transaction: Capture Method - eCommerce, Channel Encrypt

06V4018440000000018 mmdd 142869 2 600010080388314
06<1543275000000020400978 GBR www.yahoo.ie
06<A mmdd000000 0000000000000000000000000
06<B C
06#1594 00000003000082600 599901P 0
06#3 U000000 0000000030000

80 Byte Population Guide Page 60 of 216

Version 15.93
OmniPay Innovation in Transaction Management

7 Card Present Environment Attended

These transactions are performed generally with the cardholder present, the Card Present and some level of
interaction and identification with the terminal or merchant.

Card Present Transactions are performed though NFC/DSRP, Contactless Magnetic Stripe, Contactless Chip, Contact
Chip, Contact Mag Stripe, Key Entered.

For all Card Present Transactions, the Terminal Capability reflects the ultimate ability of the terminal. This means the
transactions that the terminal is capable of, whether or not that is used during this particular transaction. For
instance, a Visa Contactless transaction on a terminal capable of Contactless, would have a POS Terminal Capability of
'5', which includes contactless. A Terminal capable of only contactless transactions would have a value of '8' in this
field. This applies also to Card Data Input Capability for Mastercard. 'M' indicating Contactless M/Chip or 'A' indicating
Contactless Mag Stripe, is also capable of any contact transaction.

7.1 PAN Key Entry Signature Transaction

These are card present transactions where the card details are entered manually at a POS (Point of Sale) terminal with
signature verification. These transactions would have a capture method of card present, signature' for Visa and
MasterCard. For Visa, these transactions would qualify for Standard or non-electronic rates. For MasterCard these
transactions would qualify for Base rates.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. (TC 05 TCR 5 pos 35-36)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1)(TC50 TCR00 (L) Pos 103-114)
2 =Magnetic stripe capable
5 =Chip read capable

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1). (TC05 TCR0 Pos 160)
1 =Signature

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2). (TC05 TCR0 Pos 162-163)
01 =Key entered

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1). (TC05 TCR1 Pos 124)
Space =Not applicable to this transaction
9 =MPOS Acceptance Device

Sample transaction: Capture Method - card present, signature

06V4018440000000018 mmdd 467041 00010080378498
06<1000000000000010101826 GBR LONDON NN
06<A mmdd000000 0000000000000000000000000
06<B
06#1521 00000001010182600 599901 0

80 Byte Population Guide Page 61 of 216

Version 15.93
OmniPay Innovation in Transaction Management

06#3 U000000 0000000010101

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag Bankcard and T & E Detail Record, Position 32,length 1)

SPACE FILL

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2)
01 =Key entered

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) (DE 22 S1)
6 =PAN key entry only

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) (DE 22 S2)
0 =No electronic authentication or unknown

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1).
(DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1).
(DE 22 S4)
1 =On premises of card acceptor, attended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) (DE
22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) (DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1).
(DE 22 S7)
1 =PAN Manual Entry

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) (DE 22 S8)
5 =Manual signature verification

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) (DE 22 S9)
4 =Merchant

Sample transaction: Capture Method card present, signature

06M5409640000000009 mmdd 724169 00010080378497
06<1000000000000010909826 GBR LONDON N
06<A mmdd000000 0000000000000000000000000
06<B
06=0000000000000000010909MMDC123450320 599901
06=51211000600101654000

80 Byte Population Guide Page 62 of 216

Version 15.93
OmniPay Innovation in Transaction Management

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE
6 0 0 1 0 1 6 5 4
2, 5,6,B,C,E 0,1,2,5,6,9 0,1, 9 1,3 0 1 1,6 5 4

7.2 Voice Authorised transaction - Signature

These are card present transactions where the card details are communicated via phone to the acquirer at a POS
(Point of Sale) terminal with signature verification. These transactions would have a capture method of card present,
signature' for Visa and MasterCard. For Visa, these transactions would qualify for Standard or non-electronic rates.
For MasterCard these transactions would qualify for Base rates.

This is a narrowly occurring transaction in specific circumstances

Prerequisites-
A hybrid terminal with an online connection to the acquirer failed in sending a chip
fallback transaction (in which DE 22, subfield 1 = 80) to the issuer.
or
A hybrid terminal with no online connection to the acquirer failed to read the chip card.

The above conditions must be fulfilled.

The merchant is prompted to read the magnetic stripe from the card, the magstripe is
successfully read and indicates a service code 2XX (or 6XX if card is domestic).
To complete the transaction in both cases, a voice transaction takes place during which
the merchant communicates the PAN and the expiry date originating from the magstripe
track 2 data to the acquirer. The acquirer then sends an online transaction to the issuer in
which the value of DE 22, subfield 1 = 79 and in

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag Bankcard and T & E Detail Record, Position 32,length 1)

SPACE FILL

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2)
01 =Key entered

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) (DE 22 S1)
6 =PAN key entry only

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) (DE 22 S2)
0 =No electronic authentication or unknown

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1).
(DE 22 S3)
0 =None
80 Byte Population Guide Page 63 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1).
(DE 22 S4)
1 =On premises of card acceptor, attended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) (DE
22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) (DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1).
(DE 22 S7)
6 =Voice Authorisation with Acquirer by Merchant

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) (DE 22 S8)
5 =Manual signature verification

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) (DE 22 S9)
4 =Merchant

Sample transaction: Capture Method card present, signature

06M5409640000000009 mmdd 724169 00010080378497
06<1000000000000010909826 GBR LONDON N
06<A mmdd000000 0000000000000000000000000
06<B
06=0000000000000000010909MMDC123450320 599901
06=51211000600101654000

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE
6 0 0 1 0 1 6 5 4
2, 5,6,B,C,E 0,1,2,5,6,9 0,1, 9 1,3 0 1 1,6 5 4

7.3 Magnetic Stripe NO CVM Transaction

These are card present transactions where the cards magnetic strip (track 2) is captured electronically at a POS (Point
of Sale) terminal and are authorised online where the authorisation request is sent to the issuer through the schemes
for an authorisation code. There is NO cardholder verification. No CVM is a valid authentication method that may
result from CVM fallback, PIN Entry Bypass, or specific payment programs such as Quick Payment Service in case of
MasterCard, and Small Ticket Payment (previously known as Express Payment Service - EPS) in case of Visa. These
transactions would have a capture method of MS, online auth, no cvm.For Visa, these would qualify for Standard
rates. For MasterCard these transactions would also qualify for Electronic or Enhanced Electronic rates.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

80 Byte Population Guide Page 64 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved.(TC 05 TCR 5 pos 35-36)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1). (TC50 TCR00 (L) Pos 103-114)
2 =Magnetic stripe capable
5 =Chip read capable (Indicates a Mag stripe may also be possible)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
Space =Undefined

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
90 =Full contents of the magnetic stripe read and sent. Track 1 or 2.

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1) must be space. (TC05 TCR1 Pos 124)
Space =Not applicable to this transaction
9 =MPOS Acceptance Device

Sample transaction: Capture Method MS, online auth, no cvm

06V4018440000000018 mmdd 021877 0000000000220
06<1 000001000000826
06<A mmdd0000003826 000001000000 192400
06<B 90881800399922596090
06#152 00000076494082600000000000000000 000090
06#3 000000 0000000020400

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2)
90 =Full contents of the magnetic stripe read and sent. Track 1 or 2.
80 =PAN auto-entry via magnetic chip the full track data has been read and transmitted in Track 2 Data
(DE 035) without alteration or truncation. This mode is used as fallback to PAN auto-entry via ICC
when the IC could not be used.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) (DE 22 S1)
2 =Magnetic stripe only terminal
5 =ICC read

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) (DE 22 S2)
0 =No electronic authentication or unknown

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1).
(DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
(DE 22 S4)
80 Byte Population Guide Page 65 of 216

Version 15.93
OmniPay Innovation in Transaction Management

1 =on premises of card acceptor, attended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1). (DE
22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) (DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
(DE 22 S7)
B =Magnetic stripe read input; track data captured and passed unaltered

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1). (DE 22 S8)
0 =Not authenticated or unknown

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) (DE 22 S9)
0 =Not authenticated or unknown

Extended Service Code (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 55, length 3) is
the three-digit value on the magnetic stripe (tracks 1 and 2) and on the chip of a MasterCard branded payment card
which must be passed on the 80byte transaction. MasterCard uses the first byte to determine the applicable
interchange program hence this value must be passed for all electronically captured transaction in UK (CIC A, M),
Poland, AP, LAC, SAMEA and AP-SAMEA region. Zero filled otherwise. Note: Only the following combinations of values
are eligible to qualify for Electronic or Chip rates. (DE 40)
1 =International Card, when Card Data Input Capability is 2, B, A,
5 =National Use Only, when Card Data Input Capability is 2, B, A
2 =International Card ICC, when Card Data Input Capability is 5, M, C, D, E
6 =National Use Only ICC, when Card Data Input Capability is 5, M, C, D, E

Sample transaction: Capture Method MS, online auth, no cvm

06M5409640000000009 mmdd 08072B 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A mmdd0000003826 000001000000 192400
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336690 101
06=51101000200101B000008401 ASTRONAUT BLVD.

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE
2 0 0 1 0 1 B 0 0
2, B, 5 0,1,2,5,6,9 0,1, 9 1,3 0 1 B 0 0

7.4 Magnetic Stripe (Not Reliable) NO CVM Transaction

These are card present transactions where the cards magnetic strip (track 2) is captured electronically at a POS (Point
of Sale) terminal and are authorised online where the authorisation request is sent to the issuer through the schemes
for an authorisation code. There is NO cardholder verification. These transactions would have a capture method of
MS, CVV not reliable, no cvm these would qualify for Electronic Data Capture rates for Visa and Electronic or
Standard rates for MasterCard.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

80 Byte Population Guide Page 66 of 216

Version 15.93
OmniPay Innovation in Transaction Management

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. (TC 05 TCR 5 pos 35-36)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1)(TC50 TCR00 (L) Pos 103-114)
2 =Magnetic stripe capable
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1)(TC05 TCR0 Pos 160)
Space =Undefined

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2). (TC05 TCR0 Pos 162-163)
02 =Magnetic stripe read (other than Track 1).

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1). (TC05 TCR1 Pos 124)
Space =Not applicable to this transaction
9 =MPOS Acceptance Device

Sample transaction: Capture Method MS, CVV not reliable, no cvm

06V4018440000000018 mmdd 021877 0000000000220
06<1 000001000000826
06<A mmdd0000003826 000001000000 192400
06<B 90881800399922596090
06#152 00000076494082600000000000000000 000002
06#3 000000 0000000020400

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2)
02 =Magnetic stripe read (other than Track 1).

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) (DE 22 S1)
2 =Magnetic stripe only terminal
5 =ICC read

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1). (DE 22 S2)
0 =No electronic authentication or unknown

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1).
(DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1).
(DE 22 S4)
1 =On premises of card acceptor, attended

80 Byte Population Guide Page 67 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1). (DE
22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) (DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1).
(DE 22 S7)
2 =Magnetic stripe read

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be as follows. (DE 22 S8)
0 =Not authenticated or unknown

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be as follows (DE 22 S9)
0 =Not authenticated or unknown

Sample transaction: Capture Method MS, CVV not reliable, no cvm

06M5409640000000009 mmdd 08072B 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A mmdd0000003826 000001000000 192400
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336602
06=511010002001012000008401 ASTRONAUT BLVD.

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE
2 0 0 1 0 1 2 0 0
2,5 0,1,2,5,6,9 0,1, 9 1,3 0 1 2 0 0

7.5 Magnetic Stripe Signature Transaction

These are card present transactions where the cards magnetic strip (track 2) is captured electronically at a POS (Point
of Sale) terminal is not reliable and are authorised online where the authorisation request is sent to the issuer through
the schemes for an authorisation code. These transactions are signature verified and have a capture method of MS,
online auth, signature and would qualify for Electronic Online Auth rates for Visa and Electronic or Enhanced
Electronic rates for MasterCard.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. (TC 05 TCR 5 pos 35-36)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1). (TC50 TCR00 (L) Pos 103-114)
2 =Magnetic stripe capable
5 =Chip read capable (Visa only)

80 Byte Population Guide Page 68 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1). (TC05 TCR0 Pos 160)
1 =Signature

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2). (TC05 TCR0 Pos 162-163)
90 =Full contents of the magnetic stripe read and sent. Track 1 or 2.

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1). (TC05 TCR1 Pos 124)
Space =Not applicable to this transaction
9 =MPOS Acceptance Device

Sample transaction: Capture Method MS, online auth, signature

06V4018440000000018 mmdd 021877 0000000000220
06<1 000001000000826
06<A mmdd0000003826 000001000000 192400
06<B 90881800399922596090
06#1521 00000076494082600000000000000000 000090
06#3 000000 0000000020400

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2)
90 =Full contents of the magnetic stripe read and sent. Track 1 or 2.
80 =PAN auto-entry via magnetic chip the full track data has been read and transmitted in Track 2 Data
(DE035) without alteration or truncation. This mode is used as fallback to PAN auto-entry via ICC when
the IC could not be used.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) (DE 22 S1)
2 =Magnetic stripe only terminal
5 =ICC read

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1). (DE 22 S2)
0 =No electronic authentication or unknown

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1).
(DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1).
(DE 22 S4)
1 =on premises of card acceptor, attended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) (DE
22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1). (DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
(DE 22 S7)
80 Byte Population Guide Page 69 of 216

Version 15.93
OmniPay Innovation in Transaction Management

B =Magnetic stripe read; track data captured and passed unaltered

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1). (DE 22 S8)
5 =Manual signature verification

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1). (DE 22 S9)
4 =Merchant

Sample transaction: Capture Method MS, online auth, signature

06M5409640000000009 mmdd 08072B 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A mmdd0000003826 000001000000 192400
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336690
06=51101000B00101B540008401 ASTRONAUT BLVD

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE
2 0 0 1 0 1 B 5 4
2, 5, A, B, C, D,M 0,1,2,5,6,9 0,1, 9 1,3 0 1 B 5 4

7.6 Magnetic Stripe (No Reliable) Signature Transaction

These are card present transactions where the cards magnetic strip (track 2) is captured electronically at a POS (Point
of Sale) terminal is not reliable and are authorised online where the authorisation request is sent to the issuer through
the schemes for an authorisation code. These transactions are signature verified and have a capture method of MS,
CVV not reliable, signature and would qualify for Electronic Data Capture rates for Visa and Electronic or Enhanced
Electronic rates for MasterCard.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. (TC 05 TCR 5 pos 35-36)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) (TC50 TCR00 (L) Pos 103-114)
2 =Magnetic stripe capable
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
1 =Signature

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2). (TC05 TCR0 Pos 162-163)
02 =Magnetic stripe read (other than Track 1).

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1). (TC05 TCR1 Pos 124)
Space =Not applicable to this transaction
9 =MPOS Acceptance Device

80 Byte Population Guide Page 70 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Sample transaction: Capture Method MS, CVV not reliable, signature

06V4018440000000018 mmdd 021877 0000000000220
06<1 000001000000826
06<A mmdd0000003826 000001000000 192400
06<B 90881800399922596090
06#1521 00000076494082600000000000000000 000002
06#3 000000 0000000020400

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) must be as
follows
02 =Magnetic stripe read (other than Track 1) (address Verification data could not be read)

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1). (DE 22 S1)
2 =Magnetic stripe only terminal
5 =ICC read
B =Magnetic stripe reader and key entry

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) (DE 22 S2)
0 =No electronic authentication or unknown

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1) .
(DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
must be as follows. (DE 22 S4)
1 =On premises of card acceptor, attended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) (DE
22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) (DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
(DE 22 S7)
2 =Magnetic stripe read

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be the following'. (DE 22 S8)
5 =Manual signature verification

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be the following'. (DE 22 S9)
4 =Merchant

Sample transaction: Capture Method MS, CVV not reliable, signature

80 Byte Population Guide Page 71 of 216

Version 15.93
OmniPay Innovation in Transaction Management

06M5409640000000009 mmdd 08072B 37442839 BUDGET RENT A CAR

06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A mmdd0000003826 000001000000 192400
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336602 101
06=511010002001012540008401 ASTRONAUT BLVD.

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE
2 0 0 1 0 1 2 5 4
2, 5, A, B, C, D,M 0,1,2,5,6,9 0,1, 9 1,3 0 1 2 5 4

7.7 Magnetic Stripe - Online PIN Transaction

These are card present transactions where the cards magnetic strip (track 2) is captured electronically at a POS (Point
of Sale) terminal and are authorised online where the authorisation request is sent to the issuer through the schemes
for an authorisation code. The cardholder verification is by PIN and the encrypted PIN is forwarded to the issuer for
verification. These transactions would have a capture method of MS, online auth, online pin and would qualify for
Electronic or Electronic Online Auth or EMV rates for Visa and Electronic or Enhanced Electronic rates for
MasterCard

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. (TC 05 TCR 5 pos 35-36)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be 2 or 5. (TC50 TCR00 (L)
Pos 103-114)
2 =Magnetic stripe capable
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
2 =PIN

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
90 =Full contents of the magnetic stripe read and sent. Track1or2.

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1) must be space. (TC05 TCR1 Pos 124)
Space =Not applicable to this transaction
9 =MPOS Acceptance Device

Sample transaction: Capture Method MS, online auth, online pin

06V4018440000000018 mmdd 021877 0000000000220
06<1 000001000000826
06<A mmdd0000003826 000001000000 192400
06<B 90881800399922596090
06#1522 00000076494082600000000000000000 000090

80 Byte Population Guide Page 72 of 216

Version 15.93
OmniPay Innovation in Transaction Management

06#3 000000 0000000020400

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) must be
90 =Full contents of the magnetic stripe read and sent. Track1or2.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) must be (DE 22 S1)
5 =ICC read
B =Magnetic stripe reader and key entry

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) must be '1'. (DE 22 S2)
1 =PIN

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
must be '0'. (DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
must be 1. (DE 22 S4)
1 =on premises of card acceptor, attended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) must
be 0. (DE 22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) must be '1'.
(DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
must be (DE 22 S7)
B =Magnetic stripe read; track data captured and passed unaltered

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be as follows. (DE 22 S8)
1 =PIN

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be '3'. (DE 22 S9)
3 =Authorizing agent

Sample transaction: Capture Method MS, online auth, online pin

06M5409640000000009 mmdd 021877 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A090891766 mmdd 0000001124CAPE CANAVERAFL 0000000116300000000012728180500-05
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336690
06=511010002101012130008401 ASTRONAUT BLVD.

80 Byte Population Guide Page 73 of 216

Version 15.93
OmniPay Innovation in Transaction Management

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE
2 1 0 1 0 1 B 1 3
2, 5, A, B, C, D,M 1 0,1, 9 1,3 0 1 B 1 3

7.8 Magnetic Stripe (Not Reliable) - Online PIN Transaction

These are card present transactions where the cards magnetic strip (track 2) is captured electronically at a POS (Point
of Sale) terminal and are authorised online where the authorisation request is sent to the issuer through the schemes
for an authorisation code. The cardholder verification is by PIN and the encrypted PIN is forwarded to the issuer for
verification. These transactions would have a capture method of MS, CVV not reliable, online pin and would qualify
for Electronic Data Capture rates for Visa and Electronic or Enhanced Electronic rates for MasterCard.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. (TC 05 TCR 5 pos 35-36)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be 2 or 5. (TC50 TCR00 (L)
Pos 103-114)
2 =Magnetic stripe capable
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
2 =PIN

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
02 =Magnetic stripe read (other than Track 1) but not transmitted, CVV not reliable.

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1) must be space. (TC05 TCR1 Pos 124)
Space =Not applicable to this transaction
9 =MPOS Acceptance Device

Sample transaction: Capture Method MS, CVV not reliable, online pin
06V4018440000000018 mmdd 021877 0000000000220
06<1 000001000000826
06<A mmdd0000003826 000001000000 192400
06<B 90881800399922596090
06#1522 00000076494082600000000000000000 000002
06#3 000000 0000000020400

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space

80 Byte Population Guide Page 74 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) must be
02 =Magnetic stripe read (other than Track 1) but not transmitted, CVV not reliable.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) must be (DE 22 S1)
2 =Magnetic stripe only terminal
5 =ICC read
B =Magnetic stripe reader and key entry

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) must be '1'. (DE 22 S2)
1 =PIN

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
must be '0'. (DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
must be 1. (DE 22 S4)
1 =on premises of card acceptor, attended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) must
be 0. (DE 22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) must be '1'.
(DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
must be (DE 22 S7)
2 =Magnetic stripe read

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be as follows. (DE 22 S8)
1 =PIN

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be '3'. (DE 22 S9)
3 =Authorizing agent

Sample transaction: Capture Method MS, CVV not reliable, online pin
06M5409640000000009 mmdd 021877 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A090891766 mmdd 0000001124CAPE CANAVERAFL 0000000116300000000012728180500-05
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336602 201
06=511010002101012130008401 ASTRONAUT BLVD.

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE
2 1 0 1 0 1 2 1 3
2, A, B, C, D,M 1 0,1, 9 1,3 0 1 2 1 3

80 Byte Population Guide Page 75 of 216

Version 15.93
OmniPay Innovation in Transaction Management

7.9 Chip read NO CVM Transaction

These are transaction captured at a certified EMV-compliant terminal by reading the chip on the card, at a POS (Point
of Sale) terminal and are authorised online where the authorisation request is sent to the issuer through the schemes
for an authorisation code or offline at the terminal. There is NO cardholder verification. No CVM is a valid
authentication method that may result from CVM fallback, PIN Entry Bypass, or specific payment programs such as
Quick Payment Service in case of MasterCard, and Small Ticket Payment (previously known as Express Payment
Service - EPS) in case of Visa. These transactions have a capture method of ICC, online auth, no cvm if the
authorisation happens online or a capture method of ICC, offline auth, no cvm when the transaction is authorised
offline at the terminal. These transactions would qualify for Chip full & Electronic rates in inter-region or Standard
rates for Visa and Chip rates for MasterCard.

EMV records should be provided for all Chip read transactions where possible.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

Authorization Amount (VISA Detail Addendum Record 1 (#1), Position 16, Length 12) must be populated and cant be
zero

Authorization Currency code (VISA Detail Addendum Record 1 (#1), Position 26, Length 3) must be populated and
cant be blank

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. For offline authorisation at the terminal, it must
be Y1 or Y3 as shown below. (TC 05 TCR 5 pos 35-36)
Y1 =Offline approval
Y3 =Unable to go online, approval

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be 5. (TC50 TCR00 (L) Pos
103-114)
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
Space =Undefined

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be 05. (TC05 TCR0 Pos 162-163)
05 =Card data was chip read and data is reliable.

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1) must be space. (TC05 TCR1 Pos 124)
Space =Not applicable to this transaction
9 =MPOS Acceptance Device

Sample transaction: Capture Method ICC, online auth, no cvm

06V4018440000000018 mmdd 111760 1 IPN09051400000
06<1 000000006026978
06<A mmdd000000 0000000000000000000000000110704
06<B OASE02
06#1 5 N 00000000602697800000000000000000 554205
06#3 000000 0000000020400

80 Byte Population Guide Page 76 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Sample transaction: Capture Method ICC, offline auth, no cvm

06V4018440000000018 mmdd 111760 1 IPN09051400000
06<1 000000006026978
06<A mmdd000000 0000000000000000000000000110704
06<B OASE02
06#1 5 N 000000006026978Y1000000000000000 554205
06#3 000000 0000000020400

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) must be 05
05 =Card data was chip read and data is reliable.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) must be (DE 22 S1)
5 =ICC capable

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) must be '1'. (DE 22 S2)
1 =PIN

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
must be '0'. (DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
must be 1. (DE 22 S4)
1 =on premises of card acceptor, attended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) must
be 0. (DE 22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) must be '1'.
(DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
must be. (DE 22 S7)
5 =ICC capable
C =Online Chip (Online authorisation)
F =Offline Chip (Offline authorisation)

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be as follows. (DE 22 S8)
0 =Not authenticated or unknown

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be as follows (DE 22 S9)
0 =Not authenticated or unknown

Sample transaction: Capture Method - ICC, online auth, no cvm

06M5462970000000004 mmdd 005458 1 IPM09052000000

80 Byte Population Guide Page 77 of 216

Version 15.93
OmniPay Innovation in Transaction Management

06<1 000000011000978
06<A mmdd000000 0000000000000000000000000110704
06<B OASE01
06=0000000000000000011000MCC0158000520 554105
06=51412019510101500146

Sample transaction: Capture Method - ICC, offline auth, no cvm

06M5462970000000004 mmdd 005458 1 IPM09052000000
06<1 000000011000978
06<A mmdd000000 0000000000000000000000000110704
06<B OASE01
06=0000000000000000011000MCC0158000520 554105
06=51412019510101F00146

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE
5 1 0 1 0 1 C 0 0
5, M,C,D,E 0,1,2,5,6,9 0,1, 9 1,3 0 1 5, C, F 0 0

7.10 Chip read (Not Reliable) NO CVM Transaction

These are transaction captured at a certified EMV-compliant terminal by reading the chip on the card, at a POS (Point
of Sale) terminal is not reliable and are authorised online where the authorisation request is sent to the issuer through
the schemes for an authorisation code or offline at the terminal. There is NO cardholder verification. For Visa, these
transactions have a capture method of ICC, CVV not reliable, no cvm and would qualify for Standard rates.

EMV records must be provided for all Chip read transactions where possible. It is MANDATORY for First Presentment
MasterCard Chip transactions to contain EMV data.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

Authorization Amount (VISA Detail Addendum Record 1 (#1), Position 16, Length 12) must be populated and cant be
zero

Authorization Currency code (VISA Detail Addendum Record 1 (#1), Position 26, Length 3) must be populated and
cant be blank

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. (TC 05 TCR 5 pos 35-36)

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be 5. (TC50 TCR00 (L) Pos
103-114)
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
Space =Undefined

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be (TC05 TCR0 Pos 162-163)

80 Byte Population Guide Page 78 of 216

Version 15.93
OmniPay Innovation in Transaction Management

95 =Card data was chip read and data is potentially unreliable.

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1) must be space. (TC05 TCR1 Pos 124)
Space =Not applicable to this transaction
9 =MPOS Acceptance Device

Sample transaction: Capture Method ICC, CVV not reliable, no cvm

06V4018440000000018 mmdd 111760 1 IPN09051400000
06<1 000000006026978
06<A mmdd000000 0000000000000000000000000110704
06<B OASE02
06#1 5 N 00000000602697800000000000000000 554295
06#3 000000 0000000020400

7.11 Chip read - Signature Transaction

These are transaction captured at a certified EMV-compliant terminal by reading the chip on the card, at a POS (Point
of Sale) terminal by dipping the card and are authorised online where the authorisation request is sent to the issuer
through the schemes for an authorisation code or offline at the terminal. The cardholder verification is Signature.
These transactions have a capture method of ICC, online auth, signature if the authorisation happens online or a
capture method of ICC, offline auth, signature when the transaction is authorised offline at the terminal. These
transactions would qualify for Chip full or EMV rates for Visa and Chip rates for MasterCard.

EMV records must be provided for all Chip read transactions where possible. It is MANDATORY for First Presentment
MasterCard Chip transactions to contain EMV data.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

Authorization Amount (VISA Detail Addendum Record 1 (#1), Position 16, Length 12) must be populated and cant be
zero

Authorization Currency code (VISA Detail Addendum Record 1 (#1), Position 26, Length 3) must be populated and
cant be blank

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. For offline authorisation at the terminal, it must
be Y1 or Y3 as shown below. (TC 05 TCR 5 pos 35-36)
Y1 =Offline approval
Y3 =Unable to go online, approval

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be 5. (TC50 TCR00 (L) Pos
103-114)
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be (TC05 TCR0 Pos 160)
1 =Signature

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be 05. (TC05 TCR0 Pos 162-163)
05 =Card data was chip read and data is reliable.

80 Byte Population Guide Page 79 of 216

Version 15.93
OmniPay Innovation in Transaction Management

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1) must be space. (TC05 TCR1 Pos 124)
Space =Not applicable to this transaction
9 =MPOS Acceptance Device

Sample transaction: Capture Method ICC, online auth, signature

06V4018440000000018 mmdd 111760 1 IPN09051400000
06<1 000000006026978
06<A mmdd000000 0000000000000000000000000110704
06<B OASE02
06#1 51N 00000000602697800000000000000000 554205
06#3 000000 0000000020400

Sample transaction: Capture Method ICC, offline auth, signature

06V4018440000000018 mmdd 111760 1 IPN09051400000
06<1 000000006026978
06<A mmdd000000 0000000000000000000000000110704
06<B OASE02
06#1 51N 000000006026978Y1000000000000000 554205
06#3 000000 0000000020400

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) must be 05
05 =Card data was chip read and data is reliable.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) must be (DE 22 S1)
5 =ICC capable

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) must be '1'. (DE 22 S2)
1 =PIN

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
must be '0'. (DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
must be 1. (DE 22 S4)
1 =on premises of card acceptor, attended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) must
be 0. (DE 22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) must be '1'.
(DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
must be (DE 22 S7)
5 =ICC capable

80 Byte Population Guide Page 80 of 216

Version 15.93
OmniPay Innovation in Transaction Management

C =Online Chip (Online authorisation)

F =Offline Chip (Offline authorisation)

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be 5. (DE 22 S8)
5 =Manual signature verification

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be '4'. (DE 22 S9)
4 =Merchant

Sample transaction: Capture Method ICC, online auth, signature

06M5462970000000004 mmdd 005458 1 IPM09052000000
06<1 000000011000978
06<A mmdd000000 0000000000000000000000000110704
06<B OASE01
06=0000000000000000011000MCC0158000520 554105
06=51412019510101554146

Sample transaction: Capture Method ICC, offline auth, signature

06M5462970000000004 mmdd 005458 1 IPM09052000000
06<1 000000011000978
06<A mmdd000000 0000000000000000000000000110704
06<B OASE01
06=0000000000000000011000MCC0158000520 554105
06=51412019510101F54146

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE
5 1 0 1 0 1 C 5 4
5, M,C,D,E 0,1,2,5,6,9 0,1, 9 1,3 0 1 5, C, F 5 4

7.12 Chip read (Not Reliable) Signature Transaction

These are transaction captured at a certified EMV-compliant terminal by reading the chip on the card, at a POS (Point
of Sale) terminal is not reliable and are authorised online where the authorisation request is sent to the issuer through
the schemes for an authorisation code or offline at the terminal. The cardholder verification is Signature. For Visa,
these transactions have a capture method of ICC, CVV not reliable, signature and would qualify for Electronic Data
Capture rates.

EMV records must be provided for all Chip read transactions where possible. It is MANDATORY for First Presentment
MasterCard Chip transactions to contain EMV data.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

Authorization Amount (VISA Detail Addendum Record 1 (#1), Position 16, Length 12) must be populated and cant be
zero

Authorization Currency code (VISA Detail Addendum Record 1 (#1), Position 26, Length 3) must be populated and
cant be blank

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. (TC 05 TCR 5 pos 35-36)

80 Byte Population Guide Page 81 of 216

Version 15.93
OmniPay Innovation in Transaction Management

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be 5. (TC50 TCR00 (L) Pos
103-114)
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
1 =Signature

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be (TC05 TCR0 Pos 162-163)
95 =Card data was chip read and data is potentially unreliable.

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1) must be space. (TC05 TCR1 Pos 124)
Space =Not applicable to this transaction
9 =MPOS Acceptance Device

Sample transaction: Capture Method ICC, CVV not reliable, no cvm

06V4018440000000018 mmdd 111760 1 IPN09051400000
06<1 000000006026978
06<A mmdd000000 0000000000000000000000000110704
06<B OASE02
06#1 51N 00000000602697800000000000000000 554295
06#3 000000 0000000020400

7.13 Chip read - Online PIN Transaction

These are transaction captured at a certified EMV-compliant terminal by reading the chip on the card, at a POS (Point
of Sale) terminal and are authorised online where the authorisation request is sent to the issuer through the schemes
for an authorisation code. The cardholder verification is by PIN and the encrypted PIN is sent to the issuer for online
verification. For Visa, these transactions would have a capture method of ICC, online auth, pin and for MasterCard,
these transactions would have a capture method of ICC, online auth, online pin where the authorisation happens
online. They would qualify for Chip or Chip Online rates for Visa and Chip rates for MasterCard.

Please note that Visa does not differentiate between online and offline PIN where as MasterCard makes that
distinction. Also the offline authorisation with online PIN verification is not a valid scenario.

EMV records must be provided for all Chip read transactions where possible. It is MANDATORY for First Presentment
MasterCard Chip transactions to contain EMV data.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

Authorization Amount (VISA Detail Addendum Record 1 (#1), Position 16, Length 12) must be populated and cant be
zero

Authorization Currency code (VISA Detail Addendum Record 1 (#1), Position 26, Length 3) must be populated and
cant be blank

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. (TC 05 TCR 5 pos 35-36)

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

80 Byte Population Guide Page 82 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be 5. (TC50 TCR00 (L) Pos
103-114)
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be 2. (TC05 TCR0 Pos 160)
2 =PIN

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be 05. (TC05 TCR0 Pos 162-163)
05 =Card data was chip read and data is reliable.

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1) must be space. (TC05 TCR1 Pos 124)
Space =Not applicable to this transaction
9 =MPOS Acceptance Device

Sample transaction: Capture Method ICC, online auth, pin

06V4018440000000018 mmdd 111760 1 IPN09051400000
06<1 000000006026978
06<A mmdd000000 0000000000000000000000000110704
06<B OASE02
06#1 52N 00000000602697800000000000000000 554205
06#3 000000 0000000020400

MASTERCARD

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.
MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space
Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space
ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) must be 05
05 =Card data was chip read and data is reliable.).

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) must be (DE 22 S1)
5 =ICC capable

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) must be '1'. (DE 22 S2)
1 =PIN

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
must be '0'. (DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
must be 1. (DE 22 S4)
1 =on premises of card acceptor, attended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) must
be 0. (DE 22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) must be '1'.
(DE 22 S6)
1 =Card present

80 Byte Population Guide Page 83 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
must be as follows. (DE 22 S7)
5 =ICC capable
C =Online Chip (Online authorisation)

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be 1. (DE 22 S8)
1 =PIN

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be '3'. (DE 22 S9)
3 =Authorizing agent

Sample transaction: Capture Method ICC, online auth, online pin

06M5462970000000004 mmdd 005476 1 IPM09052000000
06<1 000000011500978
06<A mmdd000000 0000000000000000000000000110704
06<B OASE01
06=0000000000000000011500MCC0158520520 554105
06=51412019510101513146

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE
5 1 0 1 0 1 C 1 3
5, M,C,D,E 0,1,2,5,6,9 0,1, 9 1,3 0 1 5, C 1 3

7.14 Chip read - Offline PIN Transaction

These are transaction captured at a certified EMV-compliant terminal by reading the chip on the card, at a POS (Point
of Sale) terminal and are authorised online where the authorisation request is sent to the issuer through the schemes
for an authorisation code or authorised offline at the ICC terminal. The cardholder verification is by PIN and the PIN is
NOT sent to the issuer for verification but verified offline at the ICC terminal. For Visa, these transactions would have a
capture method of ICC, offline auth, offline pin for offline authorisation and ICC, online auth, pin for online
authorisations These transactions would qualify for the Chip or Chip Offline rates. For MasterCard these
transactions would have a capture method of ICC, online auth, offline pin when authorised online and ICC, offline
auth, offline pin if authorised offline at the terminal. These transactions would qualify for Chip rates.

Visa does not differentiate between online and offline PIN hence this is not applicable.

EMV records must be provided for all Chip read transactions where possible. It is MANDATORY for First Presentment
MasterCard Chip transactions to contain EMV data.
VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

Authorization Amount (VISA Detail Addendum Record 1 (#1), Position 16, Length 12) must be populated and cant be
zero

Authorization Currency code (VISA Detail Addendum Record 1 (#1), Position 26, Length 3) must be populated and
cant be blank

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this

80 Byte Population Guide Page 84 of 216

Version 15.93
OmniPay Innovation in Transaction Management

code could result in less favourable interchange rates being achieved. For offline authorisation at the terminal, it must
be Y1 or Y3 as shown below. (TC 05 TCR 5 pos 35-36)
Y1 =Offline approval
Y3 =Unable to go online, approval

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be 5. (TC50 TCR00 (L) Pos
103-114)
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be 2. (TC05 TCR0 Pos 160)
2 =PIN

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be 05. (TC05 TCR0 Pos 162-163)
05 =Card data was chip read and data is reliable.

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1) must be space. (TC05 TCR1 Pos 124)
Space =Not applicable to this transaction
9 =MPOS Acceptance Device

Sample transaction: Capture Method ICC, offline auth, offline pin

06V4018440000000018 mmdd 111760 1 IPN09051400000
06<1 000000006026978
06<A mmdd000000 0000000000000000000000000110704
06<B OASE02
06#1 52N 000000006026978Y1000000000000000 554205
06#3 000000 0000000020400

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) must be 05
05 =Card data was chip read and data is reliable.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) must be (DE 22 S1)
5 =ICC capable

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) must be '1'. (DE 22 S2)
1 =PIN

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
must be '0'. (DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
must be 1. (DE 22 S4)
1 =on premises of card acceptor, attended

80 Byte Population Guide Page 85 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) must
be 0. (DE 22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) must be '1'.
(DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
must be as follows. (DE 22 S7)
5 =ICC capable
C =Online Chip (Online authorisation)
F =Offline Chip (Offline authorisation) - if Offline Chip is populated, Auth Code must be left blank.

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be 1. (DE 22 S8)
1 =PIN

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be '1'. (DE 22 S9)
1 =ICC terminal

Sample transaction: Capture Method ICC, online auth, offline pin

06M5462970000000004 mmdd 005476 1 IPM09052000000
06<1 000000011500978
06<A mmdd000000 0000000000000000000000000110704
06<B OASE01
06=0000000000000000011500MCC0158520520 554105
06=51412019510101511146

Sample transaction: Capture Method ICC, offline auth, offline pin

06M5462970000000004 mmdd 005476 1 IPM09052000000
06<1 000000011500978
06<A mmdd000000 0000000000000000000000000110704
06<B OASE01
06=0000000000000000011500MCC0158520520 554105
06=51412019510101F11146

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE
5 1 0 1 0 1 C 1 1
5, M,C,D,E 0,1,2,5,6,9 0,1, 9 1,3 0 1 5, C, F 1 1

7.15 Chip read (Not Reliable) PIN Transaction

These are transaction captured at a certified EMV-compliant terminal by reading the chip on the card, at a POS (Point
of Sale) terminal and the data is not reliable, authorised online where the authorisation request is sent to the issuer
through the schemes for an authorisation code or offline at the terminal. The cardholder verification is PIN. For Visa,
these transactions have a capture method of ICC, CVV not reliable, pin and would qualify for Electronic Data Capture
or Standard rates.

Visa does not differentiate between online and offline PIN hence this is not applicable.

EMV records must be provided for all Chip read transactions where possible. It is MANDATORY for First Presentment
MasterCard Chip transactions to contain EMV data.

80 Byte Population Guide Page 86 of 216

Version 15.93
OmniPay Innovation in Transaction Management

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

Authorization Amount (VISA Detail Addendum Record 1 (#1), Position 16, Length 12) must be populated and cant be
zero

Authorization Currency code (VISA Detail Addendum Record 1 (#1), Position 26, Length 3) must be populated and
cant be blank

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. For offline authorisation at the terminal, it must
be Y1 or Y3 as shown below. (TC 05 TCR 5 pos 35-36)
Y1 =Offline approval
Y3 =Unable to go online, approval

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be 5. (TC50 TCR00 (L) Pos
103-114)
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
2 =PIN

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be (TC05 TCR0 Pos 162-163)
95 =Card data was chip read and data is potentially unreliable.

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1) must be space. (TC05 TCR1 Pos 124)
Space =Not applicable to this transaction
9 =MPOS Acceptance Device

Sample transaction: Capture Method ICC, CVV not reliable, pin

06V4018440000000018 mmdd 111760 1 IPN09051400000
06<1 000000006026978
06<A mmdd000000 0000000000000000000000000110704
06<B OASE02
06#1 52N 00000000602697800000000000000000 554295
06#3 000000 0000000020400

7.16 Acquirer Chip Transaction

These are transactions captured at a certified EMV-compliant terminal but the card is not Chip & PIN. This is reflected
in the Visa BIN table under Technology Flag. If the Technology Flag is NOT set to A then the Visa BIN is NOT EMV
enabled. When the non-chip card is used in a EMV-compliant terminal, the resulting transaction will achieve an
Acquirer chip rate for both Visa and MasterCard. This rate is mainly available in Asia Pacific for MasterCard.

EMV records should be provided for all Chip read transactions where possible.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

80 Byte Population Guide Page 87 of 216

Version 15.93
OmniPay Innovation in Transaction Management

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. (TC 05 TCR 5 pos 35-36)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be 2. (TC50 TCR00 (L) Pos
103-114)
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
1 =Signature

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
90 =Full contents of the magnetic stripe read and sent. Track1or2.

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1) must be space. (TC05 TCR1 Pos 124)
Space =Not applicable to this transaction
9 =MPOS Acceptance Device

Sample transaction: Capture Method Card Swiped, Signature

06V4006660000000007 mmdd 056135 000356641007692 1520710101
06<1 000000150000356 101N
06<A mmdd000000 0000000000000000000000000110704
06<B 21263000000881004827
06#1 51 00000015000035600 594390
06#3 000000 0000000020400

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) must be 90
90 =Full contents of the magnetic stripe read and sent. Track1or2.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) must be 5 or C. (DE 22 S1)
5 =ICC capable
C =Online Chip

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
must be 1. (DE 22 S4)
1 =on premises of card acceptor, attended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) must
be 0. (DE 22 S5)
0 =Cardholder present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
must be '2'. (DE 22 S7)
2 =Magnetic stripe read

80 Byte Population Guide Page 88 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be as follows. (DE 22 S8)
5 =Manual signature verification

Extended Service Code (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 55, length 3) is
the three-digit value on the magnetic stripe (tracks 1 and 2) and on the chip of a MasterCard branded payment card
which must be passed on the 80byte transaction. MasterCard uses the first byte to determine the applicable
interchange program hence this value must be passed for all electronically captured transaction in UK (CIC A, M),
Poland, AP, LAC, SAMEA and AP-SAMEA region. Zero filled otherwise. Note: Only the following combinations of values
are eligible to qualify for Electronic or Chip rates. (DE 40)
1 =International Card, when Card Data Input Capability is 2, B, A,
5 =National Use Only, when Card Data Input Capability is 2, B, A

Sample transaction: Capture Method Card Swiped, Signature

06M5120490000000007 mmdd 028486 315799424334248
06<1 000000120500344 BRN12345 402-935-7733
06<A mmdd000000 0000000000000000000000000110704
06<B 00019116332533424800
06=00000000000000000130009999999990820 571990 101
06=50709000510101254546

7.17 Issuer Chip Transaction

These are transactions captured at a non EMV-compliant terminal but the card is Chip & PIN. This is reflected in the
Visa BIN table under Technology Flag. If the Technology Flag is set to A then the Visa BIN is EMV enabled. When
the chip enabled card is used in a non EMV-compliant terminal, the resulting transaction will achieve an Issuer chip
rate for both Visa and MasterCard. This rate is mainly available in Asia Pacific for MasterCard.

EMV records should be provided for all Chip read transactions where possible.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. (TC 05 TCR 5 pos 35-36)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be 2. (TC50 TCR00 (L) Pos
103-114)
2 =Magnetic stripe capable

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
1 =Signature

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
90 =Full contents of the magnetic stripe read and sent. Track1or2.

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1) must be space. (TC05 TCR1 Pos 124)
Space =Not applicable to this transaction

80 Byte Population Guide Page 89 of 216

Version 15.93
OmniPay Innovation in Transaction Management

9 =MPOS Acceptance Device

Sample transaction: Capture Method Card Swiped, Signature

06V4510140000000009 mmdd 056135 000356641007692 1520710101
06<1 000000150000356 101N
06<A mmdd000000 0000000000000000000000000110704
06<B 21263000000881004827
06#1 21 00000015000035600 594390
06#3 000000 0000000020400

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) must be Space filled

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) must be 90
90 =Full contents of the magnetic stripe read and sent. Track1or2.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) must be 2. (DE 22 S1)
2 =Magnetic Stripe only terminal

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
must be 1. (DE 22 S4)
1 =on premises of card acceptor, attended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) must
be 0. (DE 22 S5)
0 =Cardholder present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
must be '2'. (DE 22 S7)
2 =Magnetic stripe read

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be as follows. (DE 22 S8)
5 =Manual signature verification

Extended Service Code (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 55, length 3) is
the three-digit value on the magnetic stripe (tracks 1 and 2) and on the chip of a MasterCard branded payment card
which must be passed on the 80byte transaction. MasterCard uses the first byte to determine the applicable
interchange program hence this value must be passed for all electronically captured transaction in UK (CIC A, M),
Poland, AP, LAC, SAMEA and AP-SAMEA region. Zero filled otherwise. Note: Only the following combinations of values
are eligible to qualify for Electronic or Chip rates. (DE 40)
2 =International Card ICC, when Card Data Input Capability is 5, M, C, D, E
6 =National Use Only ICC, when Card Data Input Capability is 5, M, C, D, E

Sample transaction: Capture Method Card Swiped, Signature

06M5120490000000007 mmdd 028486 315799424334248
06<1 000000130500344 BRN12345 402-935-7733
06<A mmdd000000 BRN0000000000000000000000163325
06<B 00019116332533424800
06=00000000000000000130009999999990820 571990 201
06=50709000210101254546

80 Byte Population Guide Page 90 of 216

Version 15.93
OmniPay Innovation in Transaction Management

7.18 EMV - Online PIN Transaction

These are transaction captured at a certified EMV-compliant terminal by reading the chip on the card. These
transactions are authorised online where the authorisation request is sent to the issuer through the schemes for an
authorisation code. The cardholder verification is by PIN and the PIN is also sent to the issuer for online verification.
EMV is supported for Visa, MasterCard, Maestro, Amex, UPI and JCB.

EMV Detail addendum records of record type @1, @2, @3 should be present to achieve the EMV rates otherwise the
transaction will clear as non-EMV chip based transaction. For MasterCard these transactions would also qualify for
Chip rates whereas for Visa, these transactions would qualify for EMV or Chip Full Data rates.

The EMV addendum records must be present and populated in the 80 byte file for all EMV transactions. Please refer
to the Section 7 in the 80 byte spec on how to populate the EMV Detail addendum records. Chip transactions can
qualify for the EMV rates without the EMV addendum records in some regions.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

Authorization Amount (VISA Detail Addendum Record 1 (#1), Position 1, Length 12) must be populated and cant be
zero

Authorization Currency code (VISA Detail Addendum Record 1 (#1), Position 26, Length 3) must be populated and
cant be blank

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. (TC 05 TCR 5 pos 35-36)

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be 5. (TC50 TCR00 (L) Pos
103-114)
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be 2. (TC05 TCR0 Pos 160)
2 =PIN

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be 05. (TC05 TCR0 Pos 162-163)
05 =Card data was chip read and data is reliable.

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1) must be space. (TC05 TCR1 Pos 124)
Space =Not applicable to this transaction
9 =MPOS Acceptance Device

Following fields must be populated for all Visa EMV transactions:

ICC Card Sequence Number (EMV Detail Addendum Record 1 (@1), Position 5, Length 3) EMV Tag: 5F34
Terminal Transaction Date (EMV) (EMV Detail Addendum Record 1 (@1), Position 8, Length 6) EMV Tag: 9A
Terminal Country Code (EMV) (EMV Detail Addendum Record 1 (@1), Position 20, Length 3) EMV Tag: 9F1A
Terminal Serial Number (EMV) (EMV Detail Addendum Record 2 (@2), Position 53, Length 8) EMV Tag: 9F1E

Following fields must display hexadecimal for all Visa EMV transactions:
Terminal Capability Profile (EMV) (EMV Detail Addendum Record 1 (@1), Position 14, Length 6) EMV Tag: 9F33

80 Byte Population Guide Page 91 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Application Transaction Counter (EMV) (EMV Detail Addendum Record 1 (@1), Position 58, Length 4) EMV Tag:
9F36
ICC Application Interchange Profile (EMV) (EMV Detail Addendum Record 1 (@1), Position 62, Length 4) EMV
Tag: 82
Terminal Verification Results (EMV) (EMV Detail Addendum Record 1 (@1), Position 66, Length 10) EMV Tag: 95
ICC Application Cryptogram (EMV) (EMV Detail Addendum Record 2 (@2), Position 27, Length 16) EMV Tag: 9F26
Issuer Script 1 Results (EMV) (EMV Detail Addendum Record 2 (@2), Position 17, Length 10) EMV Tag: 9F5B
Unpredictable Number (EMV) (EMV Detail Addendum Record 2 (@2), Position 61, Length 8) EMV Tag: 9F37

Please note that the Transaction Currency Code (EMV) (EMV Detail Addendum Record 1 (@1), Position 23, Length 3)
(EMV Tag: 5F2A) should contain the DCC currency code for all DCC EMV transactions.

Sample transaction: Capture Method ICC, online auth, pin

06V4916740000000006 mmdd 615294 0 00010080382600
06<1 000000004250826 GBR 117 WARWICK W
06<A mmdd0000002826 0000000000000000000000000093205+00
06<B 02501600240923025016
06#1552N5016 00000000425082600000002409001316 701105
06#3 000000 0000000004250
06@1001090628E0B8C0826826A0000000031010 00195C000000008000008C
06@2000000004250 BA12640EFC2CBB124000002409230250162ADB98A6000000000000
06@306020A0364BC00 0041030222

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) must be 05
05 =Card data was chip read and data is reliable.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) must be (DE 22 S1)
5 =ICC capable

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) must be '1'. (DE 22 S2)
1 =PIN

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
must be '0'. (DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
must be 1. (DE 22 S4)
1 =on premises of card acceptor, attended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) must
be 0. (DE 22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) must be '1'.
(DE 22 S6)
1 =Card present

80 Byte Population Guide Page 92 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
must be as follows. (DE 22 S7)
5 =ICC capable
C =Online Chip (Online authorisation)

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be 1. (DE 22 S8)
1 =PIN

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be '3'. (DE 22 S9)
3 =Authorizing agent

Following fields are mandatory for all MasterCard EMV transactions:

ICC Application Cryptogram (EMV) (EMV Detail Addendum Record 2 (@2), Position 27, Length 16) EMV Tag: 9F26
Cryptogram Information Data (EMV) (EMV Detail Addendum Record 2 (@2), Position 43, Length 2) EMV Tag:
9F27
Issuer Application Data (EMV) (EMV Detail Addendum Record 3 (@3), Position 5, Length 64) EMV Tag: 9F10.
Mandatory if data is provided by the ICC.
Unpredictable Number (EMV) (EMV Detail Addendum Record 2 (@2), Position 61, Length 8) EMV Tag: 9F37
Application Transaction Counter (EMV) (EMV Detail Addendum Record 1 (@1), Position 58, Length 4) EMV Tag:
9F36
Terminal Verification Results (EMV) (EMV Detail Addendum Record 1 (@1), Position 66, Length 10) EMV Tag: 95
Terminal Transaction Date (EMV) (EMV Detail Addendum Record 1 (@1), Position 8, Length 6) EMV Tag: 9A
Transaction Type (EMV) (EMV Detail Addendum Record 3 (@3), Position 69, Length 2) EMV Tag: 9C Must have a
valid value and cannot be space filled.
Cryptogram Amount (EMV) (EMV Detail Addendum Record 2 (@2), Position 5, Length 12) EMV Tag: 9 F02
Transaction Currency Code (EMV Detail Addendum Record 1 (@1), Position 23, Length 3) EMV Tag: 5F2A
ICC Application Interchange Profile (EMV) (EMV Detail Addendum Record 1 (@1), Position 62, Length 4) EMV
Tag: 82
Terminal Country Code (EMV) (EMV Detail Addendum Record 1 (@1), Position 20, Length 3) EMV Tag: 9F1A
Transaction Category Code (EMV) (EMV Detail Addendum Record 3 (@3), Position 79, Length 1) EMV Tag: 9F53
Amount, Other (EMV) (EMV Detail Addendum Record 2 (@2), Position 69, Length 12) EMV Tag: 9F03. When cash
back is permitted by product rules:
If there is a cash back amount, carries the amount and presence is mandatory
If there is no cash back amount, the value is zero, and may be absent, or present with a zero value

Please note that the Transaction Currency Code (EMV) (EMV Detail Addendum Record 1 (@1), Position 23, Length 3)
(EMV Tag: 5F2A) should contain the DCC currency code for all DCC EMV transactions.

Sample transaction: Capture Method ICC, online auth, online pin

06M5462970000000004 mmdd 112723 0 00010080382600
06<1 000000012600826 GBR 117 WARWICK W
06<A mmdd0000001978 0000000152880000000012133122301+00
06<B 02501600240023025016
06=0000000000000000015288112723 0627 701105 0
06=51412019510101513146
06@1001090627E0B8C0826978A0000000041010 0015780008000080000002
06@2000000015288 F573155C4B44FFD540000024002302501646B33C36000000000000
06@30110601003240000000000000000000000FF 005E030022R

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE
5 1 0 1 0 1 5 1 3
5, M,C,D,E 0,1,2,5,6,9 0,1, 9 1,3 0 1 5, C 1 3

80 Byte Population Guide Page 93 of 216

Version 15.93
OmniPay Innovation in Transaction Management

7.19 Magnetic Stripe 'No CVM' Contactless Transactions

Visa payWave enables cardholders to make contactless payments using a specially adapted credit, debit or prepaid
card. An antenna is embedded in the card, which communicates with the payment terminal. Cardholders do not need
to insert their card into a terminal, sign their name or enter a PIN. Instead, they simply wave their card in front of a
special Visa payWave reader. Transactions take place securely in less than a second. Visa payWave supports all Visa
products including Visa Electron and V PAY. The transaction amount for contactless transaction is GBP 30.00 / EUR
30.00.

PayPass is MasterCard Internationals proximity payments program. It allows consumers to make MasterCard
payments without having to hand over or swipe a payment card. To make a payment, the consumer simply taps their
PayPass card or device on to a PayPass reader. The details are read from the card or device using the contactless
interface and an enhanced payment transaction is then performed. The transaction amount must be less than or
equal to GBP 30.00\EUR 30.00 for contactless transaction.

There is no cardholder verification and these transactions have a capture method of MS, contactless, no cvm and for
Visa these transactions would qualify for specific payWave rates and for MasterCard these transactions would qualify
for the specific PayPass rates.

Contactless limits are subject to change.

Transactions over the Contactless limit may be permitted, but pushed to PIN or Signature verification as per the guide
below.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) must be space filled

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space filled. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space filled. (TC05
TCR1 Pos 116)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be 8 or 5. (TC50 TCR00 (L)
Pos 103-114)
8 =Contactless capable (Visa only)
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1). (TC05 TCR0 Pos 160)
Space =Not applicable to this transaction
POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
91 =PAN auto-entry via contactless magnetic stripe. Full unaltered Track II data for Visa.

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1). (TC05 TCR1 Pos 124)
Space =Not Applicable
9 = mPOS Acceptance Device

Form Factor Indicator (VISA Detail Addendum Record 1 (#3), Position 67, Length 8). (TC05 TCR7 Pos 151-158)
Mandatory Field

Sample transaction: Capture Method MS, contactless, no cvm

06V4018440000000018 mmdd 0000000000220
06<1 000001000000826
06<A mmdd0000003826 000001000000 192400
06<B 90881800399922596090
06#155 00000076494082600000000000000000 000091

80 Byte Population Guide Page 94 of 216

Version 15.93
OmniPay Innovation in Transaction Management

06#3 000000 0000000020400

Sample transaction: Capture Method MS, contactless, no cvm

06V4018440000000018 mmdd 0000000000220
06<1 000001000000826
06<A mmdd0000003826 000001000000 192400
06<B 90881800399922596090
06#158 00000076494082600000000000000000 000091
06#3 000000 0000000020400

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) must be space filled.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space filled

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space filled

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) must be as
follows
91 =PAN auto-entry via contactless magnetic stripe. Full unaltered Track I or Track II data or MasterCard.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) must be as follows. (DE 22 S1)
A =PAN auto-entry via contactless magnetic stripe - Please note that if a terminal is capable of Contactless
M/Chip and M/Stripe transactions, M should be populated here.
M =PAN auto-entry via contactless M/Chip -

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) must be '1'. (DE 22 S2)
1 =PIN

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
must be '0'. (DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
must be 1. (DE 22 S4)
1 =on premises of card acceptor, attended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) must
be 0. (DE 22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) must be '1'.
(DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
must be as follows. (DE 22 S7)
A =PAN auto-entry via contactless magnetic stripe

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be as follows. (DE 22 S8)
0 =Not authenticated or Unknown

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be as follows (DE 22 S9)
0 =Not authenticated
80 Byte Population Guide Page 95 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Extended Service Code (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 55, length 3) is
the three-digit value on the magnetic stripe (tracks 1 and 2) and on the chip of a MasterCard branded payment card
which must be passed on the 80byte transaction. MasterCard uses the first byte to determine the applicable
interchange program hence this value must be passed for all electronically captured transaction in POLAND, AP, LAC,
SAMEA and AP-SAMEA region. Zero filled otherwise.
This is passed through from the BM035 field in the Auth Message. Must be populated for Domestic transactions
within Europe, advisable elsewhere.

Sample transaction: Capture Method MS, contactless, no cvm

06M5409640000000009 mmdd 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A mmdd0000003826 000001000000 192400
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336691
06=5110100010101A000008401 ASTRONAUT BLVD.

Sample transaction: Capture Method MS, contactless, no cvm

06M5409640000000009 mmdd 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A mmdd0000003826 000001000000 192400
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336691
06=51101000M10101A000008401 ASTRONAUT BLVD

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE
A 1 0 1 0 1 A 0 0
A, M 1 0 1,3 0 1 A 0 0

7.20 Magnetic Stripe Signature Contactless Transaction

Cardholder verification is signature and these transactions have a capture method of MS, contactless, signature and
for Visa these transactions would qualify for specific payWave rates and for MasterCard these transactions would
qualify for the specific PayPass rates.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) must be space filled

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space filled. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space filled. (TC05
TCR1 Pos 116)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be 8 or 5. (TC50 TCR00 (L)
Pos 103-114)
8 =Contactless capable (Visa only)
5 =Chip read capable (Visa only)- A terminal capable of chip read and Contactless transactions, 5 should be
populated.

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be (TC05 TCR0 Pos 160)
1 =Signature

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
91 =PAN auto-entry via contactless magnetic stripe. Full unaltered Track II data for Visa.

80 Byte Population Guide Page 96 of 216

Version 15.93
OmniPay Innovation in Transaction Management

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1). (TC05 TCR1 Pos 124)
Space =Not Applicable
9 = mPOS Acceptance Device

Form Factor Indicator (VISA Detail Addendum Record 1 (#3), Position 67, Length 8). (TC05 TCR7 Pos 151-158)
Mandatory Field

Sample transaction: Capture Method MS, contactless, signature

06V4018440000000018 mmdd 0000000000220
06<1 000001000000826
06<A mmdd0000003826 000001000000 192400
06<B 90881800399922596090
06#1551 00000076494082600000000000000000 000091
06#3 000000 0000000020400

Sample transaction: Capture Method MS, contactless, signature

06V4018440000000018 mmdd 0000000000220
06<1 000001000000826
06<A mmdd0000003826 000001000000 192400
06<B 90881800399922596090
06#1581 00000076494082600000000000000000 000091
06#3 000000 0000000020400

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) must be space filled.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space filled

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space filled

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) must be as
follows
91 =PAN auto-entry via contactless magnetic stripe. Full unaltered Track I or Track II data or MasterCard.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) must be as follows. (DE 22 S1)
A =PAN auto-entry via contactless magnetic stripe- Please note that if a terminal is capable of Contactless
M/Chip and M/Stripe transactions, M should be populated here.
M =PAN auto-entry via contactless M/Chip

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) must be '1'. (DE 22 S2)
1 =PIN

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
must be '0'. (DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
must be 1. (DE 22 S4)
1 =on premises of card acceptor, attended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) must
be 0. (DE 22 S5)
0 =Cardholder present
80 Byte Population Guide Page 97 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) must be '1'.
(DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
must be as follows. (DE 22 S7)
A =PAN auto-entry via contactless magnetic stripe

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be as follows. (DE 22 S8)
5 =Manual signature verification

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be as follows (DE 22 S9)
4 =Merchant

Extended Service Code (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 55, length 3) is
the three-digit value on the magnetic stripe (tracks 1 and 2) and on the chip of a MasterCard branded payment card
which must be passed on the 80byte transaction. MasterCard uses the first byte to determine the applicable
interchange program hence this value must be passed for all electronically captured transaction in POLAND, AP, LAC,
SAMEA and AP-SAMEA region. Zero filled otherwise.
This is passed through from the BM035 field in the Auth Message. Must be populated for Domestic transactions
within Europe, advisable elsewhere.

Sample transaction: Capture Method MS, contactless, signature

06M5409640000000009 mmdd 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A mmdd0000003826 000001000000 192400
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336691
06=51101000A10101A540008401 ASTRONAUT BLVD.

Sample transaction: Capture Method MS, contactless, no cvm

06M5409640000000009 mmdd 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A mmdd0000003826 000001000000 192400
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336691
06=51101000M10101A540008401 ASTRONAUT BLVD

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE
A 1 0 1 0 1 A 5 4
A, M 1 0 1,3 0 1 A 5 4, 5, 9

7.21 Magnetic Stripe Online PIN Contactless Transaction

Cardholder verification is by online PIN and these transactions have a capture method of MS, contactless, online pin
and for Visa these transactions would qualify for specific payWave rates and for MasterCard these transactions would
qualify for the specific PayPass rates.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) must be space filled

80 Byte Population Guide Page 98 of 216

Version 15.93
OmniPay Innovation in Transaction Management

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space filled. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space filled. (TC05
TCR1 Pos 116)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be 8 or 5. (TC50 TCR00 (L)
Pos 103-114)
8 =Contactless only (Visa only)
5 =Chip read capable (Visa only) A terminal capable of chip read and Contactless
transactions, 5 should be populated.

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be (TC05 TCR0 Pos 160)
2 =PIN

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
91 =PAN auto-entry via contactless magnetic stripe. Full unaltered Track II data for Visa.

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1). (TC05 TCR1 Pos 124)
Space =Not Applicable
9 = mPOS Acceptance Device

Form Factor Indicator (VISA Detail Addendum Record 1 (#3), Position 67, Length 8). (TC05 TCR7 Pos 151-158)
Mandatory Field

Sample transaction: Capture Method MS, contactless, online pin

06V4018440000000018 mmdd 0000000000220
06<1 000001000000826
06<A mmdd0000003826 000001000000 192400
06<B 90881800399922596090
06#1552 00000076494082600000000000000000 000091
06#3 000000 0000000020400

Sample transaction: Capture Method MS, contactless, online pin

06V4018440000000018 mmdd 0000000000220
06<1 000001000000826
06<A mmdd0000003826 000001000000 192400
06<B 90881800399922596090
06#1582 00000076494082600000000000000000 000091
06#3 000000 0000000020400

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) must be space filled.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space filled

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space filled

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) must be as
follows
91 =PAN auto-entry via contactless magnetic stripe. Full unaltered Track I or Track II data or MasterCard.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) must be as follows. (DE 22 S1)
A =PAN auto-entry via contactless magnetic stripe- Please note that if a terminal is capable of
Contactless M/Chip and M/Stripe transactions, M should be populated here.
M =PAN auto-entry via contactless M/Chip

80 Byte Population Guide Page 99 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) must be '1'. (DE 22 S2)
1 =PIN

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
must be '0'. (DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
must be 1. (DE 22 S4)
1 =on premises of card acceptor, attended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) must
be 0. (DE 22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) must be '1'.
(DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
must be as follows. (DE 22 S7)
A =PAN auto-entry via contactless magnetic stripe

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be as follows. (DE 22 S8)
1 =PIN

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be as follows (DE 22 S9)
3 =Authorising agent

Extended Service Code (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 55, length 3) is
the three-digit value on the magnetic stripe (tracks 1 and 2) and on the chip of a MasterCard branded payment card
which must be passed on the 80byte transaction. MasterCard uses the first byte to determine the applicable
interchange program hence this value must be passed for all electronically captured transaction in POLAND, AP, LAC,
SAMEA and AP-SAMEA region. Zero filled otherwise.
This is passed through from the BM035 field in the Auth Message. Must be populated for Domestic transactions
within Europe, advisable elsewhere.

Sample transaction: Capture Method MS, contactless, online pin

06M5409640000000009 mmdd 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A mmdd0000003826 000001000000 192400
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336691
06=51101000A10101A130008401 ASTRONAUT BLVD.

Sample transaction: Capture Method MS, contactless, online pin

06M5409640000000009 mmdd 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A mmdd0000003826 000001000000 192400
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336691
06=51101000M10101A130008401 ASTRONAUT BLVD

80 Byte Population Guide Page 100 of 216

Version 15.93
OmniPay Innovation in Transaction Management

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE
A 1 0 1 0 1 A 1 3
A, M 1 0 1,3 0 1 A 1 3

7.22 Chip read NO CVM Contactless Transaction

There is no cardholder verification and these transactions have a capture method of ICC, contactless, no cvm and for
Visa these transactions would qualify for specific payWave rates and for MasterCard these transactions would qualify
for the specific PayPass rates.

EMV records should be provided for all Chip read transactions where possible.
Contactless limits are subject to change.

Transactions over the Contactless limit may be permitted, but pushed to PIN or Signature verification as per the guide
below.
VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) must be space filled

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space filled. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space filled. (TC05
TCR1 Pos 116)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be 8 or 5. (TC50 TCR00 (L)
Pos 103-114)
8 =Contactless (Visa only)
5 =Chip read capable (Visa only) A terminal capable of chip read and Contactless
transactions, 5 should be populated.

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be space filled. (TC05 TCR0 Pos 160)

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
07 =PAN auto-entry via contactless M/Chip. Contactless Chip transaction using Visa Smart Card chip data
MasterCard and Visa only

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1). (TC05 TCR1 Pos 124)
Space =Not Applicable
9 = mPOS Acceptance Device

Form Factor Indicator (VISA Detail Addendum Record 1 (#3), Position 67, Length 8). (TC05 TCR7 Pos 151-158)
Mandatory Field

Sample transaction: Capture Method ICC, contactless, no cvm

06V4018440000000018 mmdd 0000000000220
06<1 000001000000826
06<A mmdd0000003826 000001000000 192400
06<B 90881800399922596090
06#155 00000076494082600000000000000000 000007
06#3 000000 0000000020400

Sample transaction: Capture Method ICC, contactless, no cvm

06V4018440000000018 mmdd 0000000000220
06<1 000001000000826
06<A mmdd0000003826 000001000000 192400
06<B 90881800399922596090
80 Byte Population Guide Page 101 of 216

Version 15.93
OmniPay Innovation in Transaction Management

06#158 00000076494082600000000000000000 000007

06#3 000000 0000000020400

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) must be space filled.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space filled

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space filled

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) must be as
follows
07 =PAN auto-entry via contactless M/Chip. Contactless Chip transaction using Visa Smart Card
chip data MasterCard and Visa only

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) must be as follows. (DE 22 S1)
M =PAN auto-entry via contactless M/Chip

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) must be '1'. (DE 22 S2)
1 =PIN

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
must be '0'. (DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
must be 1. (DE 22 S4)
1 =on premises of card acceptor, attended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) must
be 0. (DE 22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) must be '1'.
(DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
must be as follows. (DE 22 S7)
M =PAN auto-entry via contactless M/Chip

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be as follows. (DE 22 S8)
0 =Not authenticated or Unknown

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be as follows (DE 22 S9)
0 =Not authenticated
Extended Service Code (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 55, length 3) is
the three-digit value on the magnetic stripe (tracks 1 and 2) and on the chip of a MasterCard branded payment card
which must be passed on the 80byte transaction. MasterCard uses the first byte to determine the applicable
interchange program hence this value must be passed for all electronically captured transaction in POLAND, AP, LAC,
SAMEA and AP-SAMEA region. Zero filled otherwise.
This is passed through from the BM035 field in the Auth Message. Must be populated for Domestic transactions
within Europe, advisable elsewhere.

80 Byte Population Guide Page 102 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Sample transaction: Capture Method ICC, contactless, no cvm

06M5409640000000009 mmdd 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A mmdd0000003826 000001000000 192400
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336607
06=51101000M10101M000008401 ASTRONAUT BLVD.

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE
M 1 0 1, 3 0 1 M 0 0
M 1 0 1,3 0 1 M 0 0

7.23 Chip read Signature Contactless Transaction

Cardholder verification is signature and these transactions have a capture method of ICC, contactless, signature and
for Visa these transactions would qualify for specific payWave rates and for MasterCard these transactions would
qualify for the specific PayPass rates.

EMV records should be provided for all Chip read transactions where possible.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) must be space filled

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space filled. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space filled. (TC05
TCR1 Pos 116)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be 8 or 5. (TC50 TCR00 (L)
Pos 103-114)
8 =Contactless only
5 =Chip read capable (Visa only) A terminal capable of chip read and Contactless transactions, 5 should be
populated.

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be (TC05 TCR0 Pos 160)
1 =Signature

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
07 =PAN auto-entry via contactless M/Chip. Contactless Chip transaction using Visa Smart Card chip data
MasterCard and Visa only

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1). (TC05 TCR1 Pos 124)
Space =Not Applicable
9 = mPOS Acceptance Device

Form Factor Indicator (VISA Detail Addendum Record 1 (#3), Position 67, Length 8). (TC05 TCR7 Pos 151-158)
Mandatory Field

Sample transaction: Capture Method ICC, contactless, signature

06V4018440000000018 mmdd 0000000000220
06<1 000001000000826
06<A mmdd0000003826 000001000000 192400
06<B 90881800399922596090

80 Byte Population Guide Page 103 of 216

Version 15.93
OmniPay Innovation in Transaction Management

06#1551 00000076494082600000000000000000 000007

06#3 000000 0000000020400

Sample transaction: Capture Method ICC, contactless, signature

06V4018440000000018 mmdd 0000000000220
06<1 000001000000826
06<A mmdd0000003826 000001000000 192400
06<B 90881800399922596090
06#1581 00000076494082600000000000000000 000007
06#3 000000 0000000020400

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) must be space filled.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space filled

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space filled

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) must be as
follows
07 =PAN auto-entry via contactless M/Chip. Contactless Chip transaction using Visa Smart Card chip
data MasterCard and Visa only

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) must be as follows. (DE 22 S1)
M =PAN auto-entry via contactless M/Chip

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) must be '1'. (DE 22 S2)
1 =PIN

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
must be '0'. (DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
must be 1. (DE 22 S4)
1 =on premises of card acceptor, attended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) must
be 0. (DE 22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) must be '1'.
(DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
must be as follows. (DE 22 S7)
M =PAN auto-entry via contactless M/Chip

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be as follows. (DE 22 S8)
5 =Manual signature verification

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be as follows (DE 22 S9)
4 =Merchant
80 Byte Population Guide Page 104 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Extended Service Code (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 55, length 3) is
the three-digit value on the magnetic stripe (tracks 1 and 2) and on the chip of a MasterCard branded payment card
which must be passed on the 80byte transaction. MasterCard uses the first byte to determine the applicable
interchange program hence this value must be passed for all electronically captured transaction in POLAND, AP, LAC,
SAMEA and AP-SAMEA region. Zero filled otherwise.
This is passed through from the BM035 field in the Auth Message. Must be populated for Domestic transactions
within Europe, advisable elsewhere.

Sample transaction: Capture Method ICC, contactless, signature

06M5409640000000009 mmdd 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A mmdd0000003826 000001000000 192400
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336607
06=51101000M10101M540008401 ASTRONAUT BLVD

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE
M 1 0 1 0 1 M 5 4, 5, 9

7.24 Chip read PIN Contactless Transaction

Cardholder verification is by online PIN and these transactions have a capture method of ICC, contactless, pin for Visa
qualifying for specific payWave rates. For MasterCard these transactions have a capture method of ICC, contactless,
online pin if PIN is verified online or ICC, contactless, offline pin if PIN is verified offline at the terminal. Both these
transactions would qualify for the specific PayPass rates.

Visa does not differentiate between online and offline PIN hence this is not applicable.

EMV records should be provided for all Chip read transactions where possible.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) may be space filled - A populated Auth Code
would indicate online authorisation

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space filled. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space filled. (TC05
TCR1 Pos 116)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be 8 or 5. (TC50 TCR00 (L)
Pos 103-114)
8 =Contactless only
5 =Chip read capable. Terminal may be capable of Mag Stripe also.

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be (TC05 TCR0 Pos 160)
2 =PIN

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
07 =PAN auto-entry via contactless M/Chip. Contactless Chip transaction using Visa Smart Card chip data
MasterCard and Visa only.

80 Byte Population Guide Page 105 of 216

Version 15.93
OmniPay Innovation in Transaction Management

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1). (TC05 TCR1 Pos 124)
Space =Not Applicable
9 = mPOS Acceptance Device

Form Factor Indicator (VISA Detail Addendum Record 1 (#3), Position 67, Length 8). (TC05 TCR7 Pos 151-158)
Mandatory Field

Sample transaction: Capture Method ICC, contactless, pin

06V4018440000000018 mmdd 0000000000220
06<1 000001000000826
06<A mmdd0000003826 000001000000 192400
06<B 90881800399922596090
06#1552 00000076494082600000000000000000 000007
06#3 000000 0000000020400

Sample transaction: Capture Method ICC, contactless, pin

06V4018440000000018 mmdd 0000000000220
06<1 000001000000826
06<A mmdd0000003826 000001000000 192400
06<B 90881800399922596090
06#1582 00000076494082600000000000000000 000007
06#3 000000 0000000020400

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) must be space filled.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space filled

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space filled

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) must be as
follows
07 =PAN auto-entry via contactless M/Chip. Contactless Chip transaction using Visa Smart Card chip
data MasterCard and Visa only

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) must be as follows. (DE 22 S1)
M =PAN auto-entry via contactless M/Chip

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) must be '1'. (DE 22 S2)
1 =PIN
Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
must be '0'. (DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
must be 1. (DE 22 S4)
1 =on premises of card acceptor, attended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) must
be 0. (DE 22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) must be '1'.
(DE 22 S6)
1 =Card present

80 Byte Population Guide Page 106 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
must be as follows. (DE 22 S7)
M =PAN auto-entry via contactless M/Chip

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be as follows. (DE 22 S8)
1 =PIN

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be as follows (DE 22 S9)
1 =ICC terminal
3 =Authorising agent

Extended Service Code (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 55, length 3) is
the three-digit value on the magnetic stripe (tracks 1 and 2) and on the chip of a MasterCard branded payment card
which must be passed on the 80byte transaction. MasterCard uses the first byte to determine the applicable
interchange program hence this value must be passed for all electronically captured transaction in POLAND, AP, LAC,
SAMEA and AP-SAMEA region. Zero filled otherwise.
This is passed through from the BM035 field in the Auth Message. Must be populated for Domestic transactions
within Europe, advisable elsewhere.

Sample transaction: Capture Method ICC, contactless, online pin

06M5409640000000009 mmdd 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A mmdd0000003826 000001000000 192400
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336607
06=51101000M10101M130008401 ASTRONAUT BLVD

Sample transaction: Capture Method ICC, contactless, offline pin

06M5409640000000009 mmdd 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A mmdd0000003826 000001000000 192400
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336607
06=51101000M10101M110008401 ASTRONAUT BLVD

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE
M 1 0 1 0 1 M 1 1, 3

7.25 Purchase with Cash back

A Purchase with Cash Back transaction is a Debit transaction in which a purchase was conducted and cash was
dispensed by the merchant at the point of interaction. Purchase with Cash back can only be used with MasterCard
Debit & Maestro Card Products as well as Visa Debit or PrePaid Cards. The purchase, cash back, and total transaction
components of the purchase with cash back transaction must be in the same currency. For Purchase With Cash Back
Transactions interchange fees are applied only to the purchase part of the transaction (total transaction amount
cashback amount) and the interchange on the cash back part of the transaction is zero for MasterCard. MasterCard
transactions will qualify for the regular capture methods and the interchange rates based on how the transaction was
captured. There are no new interchange rates for MasterCard.

The Visa Cash-Back Service Program is an optional domestic program that allows cardholders to obtain cash
conveniently during a purchase transaction at a merchant location. Cash back transactions must be authorised online,
face to face with cardholder verification, in locally currency and local issued cards on a purchase transaction only. For
some Visa European countries, interchange on the cash back part of the transaction could qualify for a base fee and
these rates will need to be developed based on client requirements.

80 Byte Population Guide Page 107 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Please Supply <E Record with these type transactions.

Cash back Amount (Bankcard and T & E Detail Addendum Record E (<E), Position 54, length 12): Must contain the
Amount of Cash received back from the total transaction (DE 54 S5)

Transaction Amount (Bankcard and T & E Detail Addendum Record 1 (<1), Position 11, length 12) must equal to the
total transaction amount (purchase amount plus the cash back amount) for the transaction. (DE 4)

Sample transaction:
06V4042640000000013 mmdd 015634 100700000663 9760656501 07 O10
06<1 000000010000826 1212121212121
06<A mmdd0000002 Munich DEU0000000000000000000000000
06<B
06<E 000000003000
06#1521A1125 00000000000097800000000000007734 581202

06M5116565000000069 mmdd 481650 185349003143 ZW4

06<1 000000010000826 1212121212121
06<A mmdd0000002 Munich DEU0000000000000000000000000
06<B
06<E 000000003000
06=0000000000000000019600BankRefNo0705 799901 1
06=50000000100910V09001

80 Byte Population Guide Page 108 of 216

Version 15.93
OmniPay Innovation in Transaction Management

8 Card Present Environment Un-Attended

There are 3 types of unattended terminals supported based on their characteristics; they are Limited Amount
Terminal (LAT), Self Service Terminal (SST), Automated Dispensing Machine (ADM).Such transaction types are
classified as below:
Type A (Limited Amount Terminal - LAT) Transactions are not authorised and there is no cardholder
verification performed. Transaction amount is limited to less than 40 or equivalent. By default, a Type A
transaction cannot be an EMV chip-read transaction.
For Visa, this terminal type is reflected in the 80 byte file as CAT level indicator of 1 for Visa.
For MasterCard, this terminal type is reflected in the 80 byte file on the Operating environment field as U
which means CAT level 3, unattended
Not currently supported by Omnipay Platform

Type B (Self Service Terminal - SST) Transactions are authorised online for Magnetic stripe date and
online/offline for EMV chip read. There is no cardholder verification performed and the transaction amount is
limited to less than 100 or local currency equivalent.
For Visa, this terminal type is reflected in the 80 byte file as CAT level indicator of 3 for Visa.
For MasterCard, this terminal type is reflected in the 80 byte file on the Operating environment field as T
which means CAT level 2, unattended

Type C (Automated Dispensing Machine - ADM) Transactions are authorised online for Magnetic stripe data
and online/offline for EMV chip read. Cardholder verification method must be online PIN verification or offline
PIN verification (with an EMV compliant chip card). There is no transaction ceiling amount.
For Visa, this terminal type is reflected in the 80 byte file as CAT level indicator of 2 for Visa.
For MasterCard, this terminal type is reflected in the 80 byte file on the Operating environment field as S
which means CAT level 1, unattended.

Importantly these three definitions relate to the transactions themselves rather than the type of terminal from
which they originate. This means that a single Unattended Acceptance Terminal may be capable of processing more
than one type of transaction. Common examples of unattended transactions are self service checkout in
Supermarkets, pay at pump in petrol stations, car park payments, ticket purchase for transport/cinemas, vending
machines, self check in at hotels and toll payments etc.

8.1 Magnetic Stripe No CVM LAT Transaction

These are card present transactions where the cards magnetic strip (track 2) is captured electronically at a POS (Point
of Sale) terminal and are not authorised. There is no cardholder verification and the transaction amount is limited to
less than 40. These transactions would have a capture method of MS, not auth, no cvm. For Visa, these transactions
would qualify for non-Electronic rates and for MasterCard these transactions would also qualify for Electronic or
Enhanced Electronic rates.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. (TC 05 TCR 5 pos 35-36)

80 Byte Population Guide Page 109 of 216

Version 15.93
OmniPay Innovation in Transaction Management

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be (TC50 TCR00 (L) Pos
103-114)
2 =Magnetic stripe capable
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
3 =Unattended terminal, no PIN pad

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
90 =Full contents of the magnetic stripe read and sent. Track1or2.

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1) must be (TC05 TCR1 Pos 124)
1 =Type A UAT (Limited amount terminal)

CVV2 Result Code (VISA Detail Addendum Record 1 (#1), Position 56, Length 1) must be populated. (TC05 TCR5, Pos
127). The value is derived from the CVV2 field (BM44.10) in the authorization message for ISO8583 format..

Sample transaction: Capture Method MS, not auth, no cvm

06V4018440000000018 mmdd 0000000000220
06<1 000001000000826
06<A mmdd000000 0000000000000000000000000093205+00
06<B 90881800399922596090
06#1523 00000076494082600000000000000000 000090P 1
06#3 000000 0000000004250

Sample transaction: Capture Method MS, not auth, no cvm

06V4018440000000018 mmdd 0000000000220
06<1 000001000000826
06<A mmdd000000 0000000000000000000000000093205+00
06<B 90881800399922596090
06#1553 00000076494082600000000000000000 000090P 1
06#3 000000 0000000004250

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) must be
90 =Full contents of the magnetic stripe read and sent. Track 1 or 2 data(Address Data is Reliable)

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) must be (DE 22 S1)
2 =Magnetic stripe only terminal
5 =ICC capable
D =Magnetic stripe reader and ICC

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) must be as follows (DE 22 S2)
0 =Unknown
1 =PIN

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
must be '0'. (DE 22 S3)

80 Byte Population Guide Page 110 of 216

Version 15.93
OmniPay Innovation in Transaction Management

0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
must be (DE 22 S4)
5 =On premises of cardholder, unattended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) must
be 0. (DE 22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) must be '1'.
(DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
must be (DE 22 S7)
B =Magnetic stripe read input; track data captured and passed unaltered

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be as follows. (DE 22 S8)
0 =Not authenticated

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be as follows (DE 22 S9)
0 =Not authenticated

CAT Level Indicator (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 80, length 1) must
be as follows (PDS 23)
U =CAT level 3, Limited Amount Terminal, Unattended

Sample transaction: Capture Method MS, not auth, no cvm

06M5409640000000009 mmdd 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A mmdd000000 0000000000000000000000000093205+00
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336690NN0
06=51101000200501B000008401 ASTRONAUT BLVD. U

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE CAT
2 0 0 2 0 1 B 0 0 U
2, 5, D 0, 1 0,1,9 2,4,5,6 0 1 B 0 0 U

8.2 Magnetic Stripe (Not Reliable) No CVM LAT Transaction

These are card present transactions where the cards magnetic strip (track 2) is captured electronically at a POS (Point
of Sale) terminal and are not authorised. There is no cardholder verification and the transaction amount is limited to
less than 40. These transactions would have a capture method of MS, CVV not reliable, no cvm. For Visa, these
transactions would qualify for non-Electronic rates and for MasterCard these transactions would also qualify for
Electronic or Enhanced Electronic rates.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

80 Byte Population Guide Page 111 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. (TC 05 TCR 5 pos 35-36)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be (TC50 TCR00 (L) Pos
103-114)
2 =Magnetic stripe capable
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
3 =Unattended terminal, no PIN pad

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
02 =Magnetic stripe read (other than Track 1).

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1) must be (TC05 TCR1 Pos 124)
1 =Type A UAT (Limited amount terminal)

CVV2 Result Code (VISA Detail Addendum Record 1 (#1), Position 56, Length 1) must be populated. (TC05 TCR5, Pos
127). The value is derived from the CVV2 field (BM44.10) in the authorization message for ISO8583 format.

Sample transaction: Capture Method MS, CVV not reliable, no cvm

06V4018440000000018 mmdd 0000000000220
06<1 000001000000826
06<A mmdd000000 0000000000000000000000000093205+00
06<B 90881800399922596090
06#1523 00000076494082600000000000000000 000002P 1
06#3 000000 0000000004250

Sample transaction: Capture Method MS, CVV not reliable, no cvm

06V4018440000000018 mmdd 0000000000220
06<1 000001000000826
06<A mmdd000000 0000000000000000000000000093205+00
06<B 90881800399922596090
06#1553 00000076494082600000000000000000 000002P 1
06#3 000000 0000000004250

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) must be
02 =Magnetic stripe read (other than Track 1).

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) must be (DE 22 S1)
2 =Magnetic stripe only terminal
5 =ICC capable
D =Magnetic stripe reader and ICC

80 Byte Population Guide Page 112 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) must be as follows (DE 22 S2)
0 =Unknown
1 =PIN

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
must be '0'. (DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
must be (DE 22 S4)
2 = On Premises of Card Acceptor, unattended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) must
be 0. (DE 22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) must be '1'.
(DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
must be (DE 22 S7)
2 =Magnetic stripe read Track Data not required or not captured

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be as follows. (DE 22 S8)
0 =Not authenticated

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be as follows (DE 22 S9)
0 =Not authenticated

CAT Level Indicator (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 80, length 1) must
be as follows (PDS 23)
U = CAT level 3, Limited Amount Terminal, Unattended

Sample transaction: Capture Method CARD SWIPED, CAT 3

06M5409640000000009 mmdd 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A mmdd000000 0000000000000000000000000093205+00
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336602NN0
06=511010002005012000008401 ASTRONAUT BLVD. U

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE CAT
2 0 0 2 0 1 2 0 0 U
2, 5, D 0, 1 0,1,9 2,4,5,6 0 1 2 0 0 U

8.3 Magnetic Stripe NO CVMSST Transaction

These are card present transactions where the cards magnetic strip (track 2) is captured electronically at a certified
EMV-compliant terminal at a POS (Point of Sale) terminal and are authorised online where the authorisation request is
sent to the issuer through the schemes for an authorisation code. There is no cardholder verification and the
transaction amount is limited to less than 100. These transactions would have a capture method of MS, online auth,

80 Byte Population Guide Page 113 of 216

Version 15.93
OmniPay Innovation in Transaction Management

no cvm. For Visa, these transactions would qualify for non-Electronic rates and for MasterCard these transactions
would also qualify for Electronic or Enhanced Electronic rates.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. (TC 05 TCR 5 pos 35-36)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be (TC50 TCR00 (L) Pos
103-114)
2 =Magnetic stripe capable
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
3 =Unattended terminal, no PIN pad

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
90 =Full contents of the magnetic stripe read and sent. Track1 or 2.

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1) must be. (TC05 TCR1 Pos 124)
3 =Type B; Self service terminal, Online/offline auth, No Customer Verification

Sample transaction: Capture Method MS, online auth, no cvm

06V4018440000000018 mmdd 123456 0000000000220
06<1 000001000000826
06<A mmdd000000 0000000000000000000000000093205+00
06<B 90881800399922596090
06#1523 00000076494082600000000000000000 000090 3
06#3 000000 0000000004250

Sample transaction: Capture Method MS, online auth, no cvm

06V4018440000000018 mmdd 123456 0000000000220
06<1 000001000000826
06<A mmdd000000 0000000000000000000000000093205+00
06<B 90881800399922596090
06#1553 00000076494082600000000000000000 000090 3
06#3 000000 0000000004250

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) must be
90 =Full contents of the magnetic stripe read and sent. Track 1or 2.

80 Byte Population Guide Page 114 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) must be (DE 22 S1)
2 =Magnetic stripe read

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) must be as follows (DE 22 S2)
0 =Unknown
1 =PIN

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
must be '0'. (DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
must be (DE 22 S4)
2 =On premises of card acceptor, unattended

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) must
be 0. (DE 22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) must be '1'.
(DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length
1).(DE 22 S7)
B =Magnetic stripe read input; track data captured and passed unaltered.

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be as follows. (DE 22 S8)
0 =Not authenticated

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be as follows (DE 22 S9)
0 =Not authenticated

CAT Level Indicator (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 80, length 1) must
be as follows (PDS 23)
T =CAT level 2, Self Service Terminal, Unattended

Sample transaction: Capture Method MS, online auth, no cvm

06M5409640000000009 mmdd 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A mmdd000000 0000000000000000000000000093205+00
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336690NN0
06=51101000200501B000008401 ASTRONAUT BLVD. T

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE CAT
2 0 0 2 0 1 B 0 0 T

80 Byte Population Guide Page 115 of 216

Version 15.93
OmniPay Innovation in Transaction Management

8.4 Magnetic Stripe (Not Reliable) No CVM SST Transaction

These are card present transactions where the cards magnetic strip (track 2) is captured electronically at a POS (Point
of Sale) terminal and are authorised online where the authorisation request is sent to the issuer through the schemes
for an authorisation code. There is no cardholder verification and the transaction amount is limited to less than 40.
These transactions would have a capture method of MS, CVV not reliable, no cvm. For Visa, these transactions would
qualify for non-Electronic rates and for MasterCard these transactions would also qualify for Electronic or Enhanced
Electronic rates.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. (TC 05 TCR 5 pos 35-36)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be (TC50 TCR00 (L) Pos
103-114)
2 =Magnetic stripe capable
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
3 =Unattended terminal, no PIN pad

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
02 =Magnetic stripe read (other than Track 1).

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1) must be (TC05 TCR1 Pos 124)
3 =Type B; Self service terminal, Online/offline auth, No Customer Verification

CVV2 Result Code (VISA Detail Addendum Record 1 (#1), Position 56, Length 1) must be populated. (TC05 TCR5, Pos
127). The value is derived from the CVV2 field (BM44.10) in the authorization message for ISO8583 format.

Sample transaction: Capture Method MS, CVV not reliable, no cvm

06V4018440000000018 mmdd 0000000000220
06<1 000001000000826
06<A mmdd000000 0000000000000000000000000093205+00
06<B 90881800399922596090
06#1523 00000076494082600000000000000000 000002P 3
06#3 000000 0000000004250

Sample transaction: Capture Method MS, CVV not reliable, no cvm

06V4018440000000018 mmdd 0000000000220
06<1 000001000000826
06<A mmdd000000 0000000000000000000000000093205+00
06<B 90881800399922596090
06#1553 00000076494082600000000000000000 000002P 3
06#3 000000 0000000004250

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

80 Byte Population Guide Page 116 of 216

Version 15.93
OmniPay Innovation in Transaction Management

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) must be
02 =Magnetic stripe read (other than Track 1).

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) must be (DE 22 S1)
2 =Magnetic stripe only terminal
5 =ICC capable
D =Magnetic stripe reader and ICC

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) must be as follows (DE 22 S2)
0 =Unknown
1 =PIN

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
must be '0'. (DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
must be (DE 22 S4)
2 =On premises of card Acceptor, Unattended.

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) must
be 0. (DE 22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) must be '1'.
(DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)(DE
22 S7)
2 =Magnetic stripe read Track Data not required or not captured

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be as follows. (DE 22 S8)
0 =Not authenticated

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be as follows (DE 22 S9)
0 =Not authenticated

CAT Level Indicator (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 80, length 1) must
be as follows (PDS 23)
T =CAT level 2, Self Service Terminal, Unattended

Sample transaction: Capture Method CARD SWIPED, CAT 3

06M5409640000000009 mmdd 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A mmdd000000 0000000000000000000000000093205+00
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336602NN0
06=511010002005012000008401 ASTRONAUT BLVD. T

80 Byte Population Guide Page 117 of 216

Version 15.93
OmniPay Innovation in Transaction Management

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE CAT
2 0 0 2 0 1 2 0 0 T
2, 5, D 0, 1 0,1,9 2,4,5,6 0 1 2 0 0 T

8.5 Chip read NO CVMSST Transaction

These are transaction captured at a certified EMV-compliant terminal by reading the chip on the card, at a POS (Point
of Sale) terminal and are authorised online where the authorisation request is sent to the issuer through the schemes
for an authorisation code. They can also be authorised offline and there is no cardholder verification. Transaction
amount is limited to less than 100. These transactions have a capture method of ICC, online auth, no cvm if the
authorisation happens online or a capture method of ICC, offline auth, no cvm when the transaction is authorised
offline at the terminal.
These transactions would qualify for Chip full rates in inter-region or Standard rates for Visa and Chip rates for
MasterCard.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) must be space filled

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space filled. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space filled. (TC05
TCR1 Pos 116)

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. For offline authorisation at the terminal, it must
be Y1 or Y3 as shown below. (TC 05 TCR 5 pos 35-36)
Y1 =Offline approval
Y3 =Unable to go online, approval

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be (TC50 TCR00 (L) Pos 103-
114)
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be (TC05 TCR0 Pos 160)
3 =Unattended terminal, no PIN pad

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
05 =Card data was chip read and data is reliable.

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1) must be (TC05 TCR1 Pos 124)
3 =Type B; Self service terminal, Online/offline auth, No Customer Verification

Sample transaction: Capture Method MS, online auth, no cvm

06V4018440000000018 mmdd 123456 0000000000220
06<1 000001000000826
06<A mmdd000000 0000000000000000000000000093205+00
06<B 90881800399922596090
06#1553 00000076494082600000000000000000 000005 3
06#3 000000 0000000004250

Sample transaction: Capture Method MS, offline auth, no cvm

06V4018440000000018 mmdd 123456 0000000000220
80 Byte Population Guide Page 118 of 216

Version 15.93
OmniPay Innovation in Transaction Management

06<1 000001000000826
06<A mmdd000000 0000000000000000000000000093205+00
06<B 90881800399922596090
06#1 53 000000006026978Y1000000000000000 554205 3
06#3 000000 0000000004250

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) must be space filled.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space filled

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space filled

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) must be as
follows
05 =Card data was chip read and data is reliable

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) must be as follows. (DE 22 S1)
5 =ICC capable

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) must be as follows (DE 22 S2)
0 =Unknown
1 =PIN

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
must be '0'. (DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
must be (DE 22 S4)
2 =On premises of card Acceptor, Unattended
Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) must
be 0. (DE 22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) must be '1'.
(DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
must be as follows. (DE 22 S7)
5 =ICC capable
C =Online Chip (Online authorisation)
F =Offline Chip (Offline authorisation)

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be as follows. (DE 22 S8)
0 =Not authenticated or Unknown

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be as follows (DE 22 S9)
0 =Not authenticated

CAT Level Indicator (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 80, length 1) must
be as follows (PDS 23)
T =CAT level 2, Self Service Terminal, Unattended
80 Byte Population Guide Page 119 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Sample transaction: Capture Method ICC, online auth, no cvm

06M5409640000000009 mmdd 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A mmdd0000003826 000001000000 192400
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336605
06=51101000500501C000008401 ASTRONAUT BLVD. T

Sample transaction: Capture Method ICC, offline auth, no cvm

06M5409640000000009 mmdd 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A mmdd0000003826 000001000000 192400
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336605
06=51101000500501F000008401 ASTRONAUT BLVD. T
*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE CAT
5 1 0 2 0 1 C 0 0 T
5 1 0,1,9 2,4,5,6 0 1 5, C, F 0 0 T

8.6 Chip read (Not Reliable) No CVM SST Transaction

These are transaction captured at a certified EMV-compliant terminal by reading the chip on the card, at a POS (Point
of Sale) terminal is not reliable and are not authorised. There is no cardholder verification and the transaction amount
is limited to less than 40. These transactions would have a capture method of ICC, CVV not reliable, no cvm. These
transactions would qualify for Chip full rates in inter-region or Standard rates for Visa and Chip rates for MasterCard

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. (TC 05 TCR 5 pos 35-36)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be (TC50 TCR00 (L) Pos
103-114)
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
3 =Unattended terminal, no PIN pad

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
95 =Card data was chip read and data is potentially unreliable.

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1) must be (TC05 TCR1 Pos 124)
3 =Type B; Self service terminal, Online/offline auth, No Customer Verification

80 Byte Population Guide Page 120 of 216

Version 15.93
OmniPay Innovation in Transaction Management

CVV2 Result Code (VISA Detail Addendum Record 1 (#1), Position 56, Length 1) must be populated. (TC05 TCR5, Pos
127). The value is derived from the CVV2 field (BM44.10) in the authorization message for ISO8583 format.

Sample transaction: Capture Method ICC, CVV not reliable, no cvm

06V4018440000000018 mmdd 0000000000220
06<1 000001000000826
06<A mmdd000000 0000000000000000000000000093205+00
06<B 90881800399922596090
06#1553 00000076494082600000000000000000 000095P 3
06#3 000000 0000000004250

8.7 Magnetic Stripe Online PIN ADM Transaction

These are card present transactions where the cards magnetic strip (track 2) is captured electronically at a POS (Point
of Sale) terminal and are authorised online where the authorisation request is sent to the issuer through the schemes
for an authorisation code. The cardholder verification is by PIN and the encrypted PIN is forwarded to the issuer for
verification. There is no transaction ceiling amount. These transactions would have a capture method of MS, online
auth, online pin and would qualify for Electronic or Electronic Online Auth or EMV rates for Visa and Electronic
or Enhanced Electronic rates for MasterCard

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. (TC 05 TCR 5 pos 35-36)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be 2 or 5. (TC50 TCR00 (L)
Pos 103-114)
2 =Magnetic stripe capable
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
2 =PIN

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
90 =Full contents of the magnetic stripe read and sent. Track1or2.

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1) must be (TC05 TCR1 Pos 124)
2 =Type C; Automated dispensing Terminal, Online/Offline auth, online/offline Customer verification

Sample transaction: Capture Method MS, online auth, online pin

06V4018440000000018 mmdd 021877 0000000000220
06<1 000001000000826
06<A mmdd0000003826 000001000000 192400
06<B 90881800399922596090
06#1522 00000076494082600000000000000000 000090 2
06#3 000000 0000000020400

Sample transaction: Capture Method MS, online auth, online pin

06V4018440000000018 mmdd 021877 0000000000220

80 Byte Population Guide Page 121 of 216

Version 15.93
OmniPay Innovation in Transaction Management

06<1 000001000000826
06<A mmdd0000003826 000001000000 192400
06<B 90881800399922596090
06#1552 00000076494082600000000000000000 000090 2
06#3 000000 0000000020400

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) must be
90 =Full contents of the magnetic stripe read and sent. Track1or2.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1)(DE 22 S1)
2 =Magnetic stripe only terminal
D =Magnetic stripe reader and ICC

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) must be '1'. (DE 22 S2)
1 =PIN

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
must be '0'. (DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
must be (DE 22 S4)
2 =On Premises of card acceptor, unattended.

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) must
be 0. (DE 22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) must be '1'.
(DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
must be (DE 22 S7)
B =Magnetic stripe read; track data captured and passed unaltered

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be as follows. (DE 22 S8)
1 =PIN

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be '3'. (DE 22 S9)
3 =Authorizing agent

Extended Service Code (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 55, length 3) is
the three-digit value on the magnetic stripe (tracks 1 and 2) and on the chip of a MasterCard branded payment card
which must be passed on the 80byte transaction. MasterCard uses the first byte to determine the applicable
interchange program hence this value must be passed for all electronically captured transaction in POLAND, AP, LAC,

80 Byte Population Guide Page 122 of 216

Version 15.93
OmniPay Innovation in Transaction Management

SAMEA and AP-SAMEA region. Zero filled otherwise. Note: Only the following combinations of values are eligible to
qualify for Electronic or Chip rates. (DE 40)
1 =International Card, when Card Data Input Capability is 2
5 =National Use Only, when Card Data Input Capability is 2
2 =International Card ICC, when Card Data Input Capability is 5
6 =National Use Only ICC, when Card Data Input Capability is 5

CAT Level Indicator (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 80, length 1) must
be as follows (PDS 23)
S =CAT level 1, Automated Dispensing Machine, Unattended

Sample transaction: Capture Method MS, online auth, online pin

06M5409640000000009 mmdd 021877 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A090891766 mmdd 0000001124CAPE CANAVERAFL 0000000116300000000012728180500-05
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336690
06=51101000210501B130008401 ASTRONAUT BLVD. S

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE CAT
2 1 0 2 0 1 B 1 3 S
2, D 1 0,1, 9 2,4,5,6 0 1 B 1 3 S

8.8 Magnetic Stripe (Not Reliable) Online PIN ADM Transaction

These are card present transactions where the cards magnetic strip (track 2) is captured electronically at a POS (Point
of Sale) terminal and are authorised online where the authorisation request is sent to the issuer through the schemes
for an authorisation code. The cardholder verification is by PIN and the encrypted PIN is forwarded to the issuer for
verification. There is no transaction ceiling amount. These transactions would have a capture method of MS, CVV not
reliable, online and would qualify for Electronic or Electronic Online Auth or EMV rates for Visa and Electronic or
Enhanced Electronic rates for MasterCard

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. (TC 05 TCR 5 pos 35-36)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be 2 or 5. (TC50 TCR00 (L)
Pos 103-114)
2 =Magnetic stripe capable
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
2 =PIN

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
02 =Magnetic stripe read (other than Track 1).

80 Byte Population Guide Page 123 of 216

Version 15.93
OmniPay Innovation in Transaction Management

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1) must be (TC05 TCR1 Pos 124)
2 =Type C; Automated dispensing Terminal, Online/Offline auth, online/offline Customer verification

Sample transaction: Capture Method MS, CVV not reliable, online

06V4018440000000018 mmdd 021877 0000000000220
06<1 000001000000826
06<A mmdd0000003826 000001000000 192400
06<B 90881800399922596090
06#1522 00000076494082600000000000000000 000002 2
06#3 000000 0000000020400

Sample transaction: Capture Method MS, CVV not reliable, online

06V4018440000000018 mmdd 021877 0000000000220
06<1 000001000000826
06<A mmdd0000003826 000001000000 192400
06<B 90881800399922596090
06#1552 00000076494082600000000000000000 000002 2
06#3 000000 0000000020400

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) must be
02 =Magnetic stripe read (other than Track 1).

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) must be (DE 22 S1)
2 =Magnetic stripe only terminal
D =Magnetic stripe reader and ICC

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) must be '1'. (DE 22 S2)
1 =PIN

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
must be '0'. (DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
must be (DE 22 S4)
2 =On Premises of card acceptor, unattended.

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) must
be 0. (DE 22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) must be '1'.
(DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
must be (DE 22 S7)
2 =Magnetic stripe read Track Data not required or not captured

80 Byte Population Guide Page 124 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be as follows. (DE 22 S8)
1 =PIN

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be '3'. (DE 22 S9)
3 =Authorizing agent

Extended Service Code (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 55, length 3) is
the three-digit value on the magnetic stripe (tracks 1 and 2) and on the chip of a MasterCard branded payment card
which must be passed on the 80byte transaction. MasterCard uses the first byte to determine the applicable
interchange program hence this value must be passed for all electronically captured transaction in POLAND, AP, LAC,
SAMEA and AP-SAMEA region. Zero filled otherwise. Note: Only the following combinations of values are eligible to
qualify for Electronic or Chip rates. (DE 40)
1 =International Card, when Card Data Input Capability is 2
5 =National Use Only, when Card Data Input Capability is 2
2 =International Card ICC, when Card Data Input Capability is 5
6 =National Use Only ICC, when Card Data Input Capability is 5

CAT Level Indicator (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 80, length 1) must
be as follows (PDS 23)
S= CAT level 1, Automated Dispensing Machine, Unattended

Sample transaction: Capture Method MS, online auth, online pin

06M5409640000000009 mmdd 021877 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A090891766 mmdd 0000001124CAPE CANAVERAFL 0000000116300000000012728180500-05
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336602
06=511010002105012130008401 ASTRONAUT BLVD. S

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE CAT
2 1 0 2 0 1 2 1 3 S
2, D 1 0,1, 9 2,4,5,6 0 1 2 1 3 S

8.9 Chip read - Online PIN ADM Transaction

These are transaction captured at a certified EMV-compliant terminal by reading the chip on the card, at a POS (Point
of Sale) terminal and are authorised online where the authorisation request is sent to the issuer through the schemes
for an authorisation code. The cardholder verification is by PIN and the encrypted PIN is forwarded to the issuer for
verification. There is no transaction ceiling amount. For Visa, these transactions would have a capture method of ICC,
online auth, pin and for MasterCard, these transactions would have a capture method of ICC, online auth, online pin
where the authorisation happens online. They would qualify for Chip or Chip Online rates for Visa and Chip rates
for MasterCard.

Please note that Visa does not differentiate between online and offline PIN where as MasterCard makes that
distinction. Also the offline authorisation with online PIN verification is not a valid scenario.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

Authorization Amount (VISA Detail Addendum Record 1 (#1), Position 16, Length 12) must be populated and cant be
zero

80 Byte Population Guide Page 125 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Authorization Currency code (VISA Detail Addendum Record 1 (#1), Position 26, Length 3) must be populated and
cant be blank

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. (TC 05 TCR 5 pos 35-36)

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1)(TC50 TCR00 (L) Pos 103-114)
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1)(TC05 TCR0 Pos 160)
2 =PIN

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2)(TC05 TCR0 Pos 162-163)
05 =Card data was chip read and data is reliable.

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1)(TC05 TCR1 Pos 124)
2 =Type C; Automated dispensing Terminal, Online/Offline auth, online/offline Customer verification

Sample transaction: Capture Method ICC, online auth, pin

06V4018440000000018 mmdd 111760 1 IPN09051400000
06<1 000000006026978
06<A mmdd000000 0000000000000000000000000110704
06<B OASE02
06#1552 00000076494082600000000000000000 000005 2
06#3 000000 0000000020400

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2)
05 =Card data was chip read and data is reliable.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1)(DE 22 S1)
5 =ICC capable

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) must be '1'. (DE 22 S2)
1 =PIN

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
(DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
(DE 22 S4)
2 =On Card Acceptor Premises, Cardholder Present
80 Byte Population Guide Page 126 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1). (DE
22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) must be '1'.
(DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)(DE
22 S7)
5 =ICC capable
C =Online Chip (Online authorisation)

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be 1. (DE 22 S8)
1 =PIN

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be '3'. (DE 22 S9)
3 =Authorizing agent

CAT Level Indicator (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 80, length 1) must
be as follows (PDS 23)
S= CAT level 1, Automated Dispensing Machine, Unattended

Sample transaction: Capture Method MS, online auth, online pin

06M5409640000000009 mmdd 021877 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A090891766 mmdd 0000001124CAPE CANAVERAFL 0000000116300000000012728180500-05
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336690
06=511010005105015130008401 ASTRONAUT BLVD. S

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE CAT
5 1 0 2 0 1 5 1 3 S
5, D 1 0,1, 9 2,4,5,6 0 1 5, C 1 3 S

8.10 Chip read - Offline PIN ADM Transaction

These are transaction captured at a certified EMV-compliant terminal by reading the chip on the card, at a POS (Point
of Sale) terminal and are authorised online where the authorisation request is sent to the issuer through the schemes
for an authorisation code or authorised offline at the ICC terminal. The cardholder verification is by PIN and the PIN is
NOT sent to the issuer for verification but verified offline at the ICC terminal. For Visa, these transactions would have a
capture method of ICC, offline auth, offline pin for offline authorisation and ICC, online auth, pin for online
authorisations. These transactions would qualify for the Chip or Chip Offline rates. For MasterCard these
transactions would have a capture method of ICC, online auth, offline pin when authorised online and ICC, offline
auth, offline pin if authorised offline at the terminal. These transactions would qualify for Chip rates.

Please note that Visa does not differentiate between online and offline PIN where as MasterCard makes that
distinction. Also the offline authorisation with online PIN verification is not a valid scenario.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

80 Byte Population Guide Page 127 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Authorization Amount (VISA Detail Addendum Record 1 (#1), Position 16, Length 12) must be populated and cant be
zero

Authorization Currency code (VISA Detail Addendum Record 1 (#1), Position 26, Length 3) must be populated and
cant be blank

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. For offline authorisation at the terminal, it must
be Y1 or Y3 as shown below. (TC 05 TCR 5 pos 35-36)
Y1 =Offline approval
Y3 =Unable to go online, approval

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be 5. (TC50 TCR00 (L) Pos
103-114)
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be 2. (TC05 TCR0 Pos 160)
2 =PIN

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be 05. (TC05 TCR0 Pos 162-163)
05 =Card data was chip read and data is reliable. .

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1) must be space. (TC05 TCR1 Pos 124)
2 =Type C; Automated dispensing Terminal, Online/Offline auth, online/offline Customer verification

Sample transaction: Capture Method ICC, offline auth, offline pin

06V4018440000000018 mmdd 111760 1 IPN09051400000
06<1 000000006026978
06<A mmdd000000 0000000000000000000000000110704
06<B OASE02
06#1552 000000764940826Y1000000000000000 000005 2
06#3 000000 0000000020400

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space

ENTRY Mode (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 49, length 2) must be 05
05 =Card data was chip read and data is reliable.

Card Data Input Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 12, length
1) must be (DE 22 S1)
5 =ICC capable

Cardholder Authentication Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
13, length 1) must be '1'. (DE 22 S2)
80 Byte Population Guide Page 128 of 216

Version 15.93
OmniPay Innovation in Transaction Management

1 =PIN

Card Capture Capability (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 14, length 1)
must be '0'. (DE 22 S3)
0 =None

Operating Environment (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 15, length 1)
must be (DE 22 S4)
2 =Card Acceptor Premises, Cardholder Present.
Cardholder Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 16, length 1) must
be 0. (DE 22 S5)
0 =Cardholder present

Card Present (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 17, length 1) must be '1'.
(DE 22 S6)
1 =Card present

Card Data Input Mode (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 18, length 1)
must be as follows. (DE 22 S7)
5 =ICC capable
C =Online Chip (Online authorisation)
F =Offline Chip (Offline authorisation)

Cardholder Authentication Method (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position
19, length 1) must be 1. (DE 22 S8)
1 =PIN

Cardholder Authentication Entity (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 20,
length 1) must be (DE 22 S9)
1 =ICC terminal

CAT Level Indicator (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 80, length 1) must
be as follows (PDS 23)
S= CAT level 1, Automated Dispensing Machine, Unattended

Sample transaction: Capture Method MS, online auth, offline pin

06M5409640000000009 mmdd 021877 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A090891766 mmdd 0000001124CAPE CANAVERAFL 0000000116300000000012728180500-05
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336690
06=511010005105015110008401 ASTRONAUT BLVD. S

Sample transaction: Capture Method MS, offline auth, offline pin

06M5409640000000009 mmdd 021877 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A090891766 mmdd 0000001124CAPE CANAVERAFL 0000000116300000000012728180500-05
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336690
06=51101000510501F110008401 ASTRONAUT BLVD. S

*First row lists the values used in the example above whereas the second row lists all the valid values for this capture
method
CIC CAC CCC TOE CHP CP CDIM CAM CAE CAT
5 1 0 2 0 1 5 1 1 S
5, D 1 0,1, 9 2,4,5,6 0 1 5, C, F 1 1 S

80 Byte Population Guide Page 129 of 216

Version 15.93
OmniPay Innovation in Transaction Management

8.11 Chip read (Not Reliable) Online PIN ADM Transaction

These are transaction captured at a certified EMV-compliant terminal by reading the chip on the card, at a POS (Point
of Sale) terminal is not reliable and are authorised online where the authorisation request is sent to the issuer through
the schemes for an authorisation code. The cardholder verification is by PIN and the encrypted PIN is forwarded to the
issuer for verification. There is no transaction ceiling amount. These transactions would have a capture method ICC,
CVV not reliable, pin. These transactions would qualify for Chip full rates in inter-region or Standard rates for Visa
and Chip rates for MasterCard

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space. (TC05 TCR1 Pos 116)

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space. (TC05 TCR1
Pos 116)

Authorization Response Code (VISA Detail Addendum Record 1 (#1), Position 29, Length 2) must be populated. This
field should contain the Response Code received in the Authorization Response (V.I.P. Field 39). Failing to submit this
code could result in less favourable interchange rates being achieved. (TC 05 TCR 5 pos 35-36)

POS Terminal capability (VISA Detail Addendum Record 1 (#1), Position 6, Length 1) must be 5. (TC50 TCR00 (L) Pos
103-114)
5 =Chip read capable (Visa only)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be 2. (TC05 TCR0 Pos 160)
2 =PIN

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be (TC05 TCR0 Pos 162-163)
95 =Card data was chip read and data is potentially unreliable.

CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1) must be space. (TC05 TCR1 Pos 124)
2 =Type C; Automated dispensing Terminal, Online/Offline auth, online/offline Customer verification

CVV2 Result Code (VISA Detail Addendum Record 1 (#1), Position 56, Length 1) must be populated. (TC05 TCR5, Pos
127). The value is derived from the CVV2 field (BM44.10) in the authorization message for ISO8583 format

Sample transaction: Capture Method ICC, CVV not reliable, pin

06V4018440000000018 mmdd 0000000000220
06<1 000001000000826
06<A mmdd000000 0000000000000000000000000093205+00
06<B 90881800399922596090
06#1552 00000076494082600000000000000000 000095P 2
06#3 000000 0000000004250

80 Byte Population Guide Page 130 of 216

Version 15.93
OmniPay Innovation in Transaction Management

9 Credit/Money Transfer
This section lists the information required to qualify for the Credit & Payment rates in addition to the setup for the
card capture methods as outlined in the previous sections based on how these transactions are captured either by
Mail order, Telephone order, e-Commerce or at a POS terminal.

9.1 OC/CFT Transactions

These are Original Credit Transfer (OC) or Cardholder Funds Transfer (CFT) transactions and they qualify for CFT rates
for Visa. These are refund transactions with unique MCC codes to identify them as OC or CFT. Original credit
transactions are not required to be authorised but the original credit transaction limit is $50,000 in all regions.
Effective 1 April 2011, the original credit transaction limit for Visa Europe disbursement transactions will increase from
US $50,000 to EUR 80,000 (or local currency equivalent) but it remains the same for the rest of the region at $50,000.

VISA
Merchant Category Code VISA Detail Addendum Record 1 (#1,pos 50)must be (TC50 TCR0 Pos 133-136)
7995 =Gambling transaction (If supported for the institution)- Non Money Transfer
4829 =Wire Transfer Money Orders (WTMOs) - Money Transfer
6012 =Financial Services - Money Transfer

Please note that there are no restrictions on using other MCC codes to attain Original Credit Interchange - these type
of operations are permitted on all MCCs.

Original Credit Identifier (VISA Detail Addendum Record 1 (#1), Position 57, Length 1) must be as follows'. Please note
that if you space fill this field then the transaction will process as regular refund and will not be eligible for the
preferential CFT (Cardholder Funds Transfer) rates.
1 =Original Credit transaction (non money transfer such as gaming) All Non Money Transfer transactions
must pass the #8,#9 record
2 =Original Credit transaction (Money Transfer) - All Money Transfer transactions must pass the #7, #8,#9
record

Business Application ID (Visa Original Credit Money Transfer Record (#8), Position 5, Length 2)
Must contain one of the following values:
For NON-Money Transfer OCT:
BB Business to Business
BP Bill Payment
CP Card Bill Payment
FD Funds Disbursement (General)
GD Government Disbursement
GP Gambling Payment (other than Online)
MD Merchant Disbursement
OG Online Gambling Payout
PD Payroll/Pension Disbursement
PS Payment to Government
PS Payment For Goods And Services
TU Top Up
For Money Transfer OCT:
The field must contain one of the following values:
MI (where MCC is 4829)- Interregional Visa OC transactions on a MCC Code of 4829 are not
currently supported on the Omnipay Platform
BI (where MCC is 6012)

Senders Reference Number (Visa Original Credit Money Transfer Record (#8), Position 7, Length 16) must contain
Reference Number from whom the funds are to be taken.

80 Byte Population Guide Page 131 of 216

Version 15.93
OmniPay Innovation in Transaction Management

For Non-Money Transfer OCT: For Cross Border Transactions, this field must contain the number used by the
merchant or originator to track the funds disbursement, such as an invoice number or other type of tracking number,
if not applicable a value of '123' should be utilised, left justified and space filled.
For Money Transfer OCT: This field contains a reference number for the transaction supplied by the sender.

Sender Account Number (Visa Original Credit Money Transfer Record (#8), Position 23, Length 33) must contain
senders name from whom the funds are to be taken.
For Non-Money Transfer OCT- Must Contain Spaces
For Money Transfer OCT- This field contains the sender's card number or bank account from which the funds are to be
taken.

Sender City (Visa Original Credit Money Transfer Record (#8), Position 56, Length 24) must contain senders name
from whom the funds are to be taken.
For Non-Money Transfer OCT-: For Cross Border Transactions, this field must contain Merchant/Government Entity's
City.
For Money Transfer OCT- This field contains the City of the person or entity from which funds are to be taken.

Senders Name (Visa Original Credit Money Transfer Record (#9), Position 5, Length 25) must contain senders name
from whom the funds are to be taken.
For Non-Money Transfer OCT: For Cross Border Transactions, this field must contain Merchant/Government Entity's
Name.
For Money Transfer OCT: This field contains the name of the person or entity from which funds are to be taken.

Senders Address (Visa Original Credit Money Transfer Record (#9), Position 35, Length 34) must contain the senders
address.
For Non-Money Transfer OCT: This field must contain the merchant / government entitys address.
For Money Transfer OCT: The field contains the address of the person or entity for the account from which funds are
to be taken

Senders Country (Visa Original Credit Money Transfer Record (#9), Position 69, Length 3)
For Non-Money Transfer OCT: For Cross Border Transactions, this field must contain Merchant/Government Entity's
Country Code.
For Money Transfer OCT: This field contains the Country Code of the person or entity from which funds are to be
taken.

Senders Name (Visa Original Credit Money Transfer Record (#7), Position 5, Length 25) must contain senders name
from whom the funds are to be taken.
For Money Transfer OCT: This field contains the name of the person or entity from which funds are to be taken.

Senders Address, Account number(Visa Original Credit Money Transfer Record (#7), Position 30, Length 50) must
contain the senders address.
For Money Transfer OCT: The field contains the address of the person or entity for the account from which funds are
to be taken

#7 is Mandatory for Money Transfer transactions

#8 & #9 Records must be populated for all Visa Original Credit (Money Transfer & Non Money Transfer)
transactions, otherwise Visa will reject the transactions

Sample Transaction for the above example: Non gaming (Money Transfer)
07V4018440000000018 mmdd 70002044495551 PAYPAL *WITHDRAWAL
07<1 000000001797978 LUXL-2240 4029357733 2
07<A mmdd000000 4029357733 LUX0000000000000000000000000000000
07#1 94 000000000000 000000000000000000048290102
07#3 000000 000000000000
07#7MARTIN QUINLAN ACCOUNT NUMBER CITY COUNTRY POSTCODE NEW-

07V4018440000000018 mmdd 70002044495551 PAYPAL *WITHDRAWAL

80 Byte Population Guide Page 132 of 216

Version 15.93
OmniPay Innovation in Transaction Management

07<1 000000001797978 LUXL-2240 4029357733 2

07<A mmdd000000 4029357733 LUX0000000000000000000000000000000
07#1 94 000000000000 000000000000000000048290102
07#3 000000 000000000000
07#7MARTIN QUINLAN ACCOUNT NUMBERCITY COUNTRY POSTCODE
07#8PP3848586123237851ACCOUNT NUMBER CITY
07#9Linus Ingoldsby Address FRA

**Effective 13.2 #7 record is optional but is mandatory in Money Transfer Transactions

Sample Transaction for the above example: Gaming (Non Money Transfer)
07V4018440000000018 mmdd 70002044495551 PAYPAL *WITHDRAWAL
07<1 000000001797978 LUXL-2240 4029357733 2
07<A mmdd000000 4029357733 LUX0000000000000000000000000000000
07#1 94 000000000000 000000000000000000079950101
07#3 000000 000000000000

NEW-

07V4018440000000018 mmdd 70002044495551 PAYPAL *WITHDRAWAL

07<1 000000001797978 LUXL-2240 4029357733 2
07<A mmdd000000 4029357733 LUX0000000000000000000000000000000
07#1 94 000000000000 000000000000000000079950101
07#3 000000 000000000000
07#7MARTIN QUINLAN ACCOUNT NUMBERCITY COUNTRY POSTCODE
07#8OG3848586123237851 CITY
07#9Linus Ingoldsby Address FRA

9.2 Payment Transaction /Payment of Winnings

These are Payment transactions (PT) or Payment of winnings (POW) for MasterCard and they qualify for Payment
Transaction rates. These are standalone refund transactions with unique MCC codes to identify them as PT or POW.
POW is a gambling transaction only supported within the European regions and will NOT qualify for the PT rates in the
international region. OmniPay system recognises these as Quasi-cash transactions and populates the clearing files
according. Payment Transaction and POW are required to be authorised.

Refunds for a Gaming Merchant (7995 MCC) for both MasterCard and Maestro must populate 'G' in the IPQF
(Bankcard and T & E Detail Addendum Record 1, Pos 58, Length 1) field when processing. It is recommended that this
activity be cleared with MasterCard before processing.

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Merchant Category Code MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 45, length 4)
(DE 26)
7995 =Gambling transaction (If supported for the institution)
6533 =Payment Transaction (Payment Service ProviderMerchantPayment Transaction)
6532 =Payment Transaction (Payment Service ProviderMember Financial Institution Payment
Transaction)

Payers Name (MasterCard Payment Transaction Person to Person Addendum Record (=9), Position 5, length 20) must
contain the payers full name or user ID.

Payers Address (MasterCard Payment Transaction Person to Person Addendum Record (=9), Position 25, length 25)
must contain the payers street address.

80 Byte Population Guide Page 133 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Payers City (MasterCard Payment Transaction Person to Person Addendum Record (=9), Position 50, length 15) must
contain the payers city.

Payers State/Province code (MasterCard Payment Transaction Person to Person Addendum Record (=9), Position 65,
length 3) must contain the payers state/province code.

Payers Country code (MasterCard Payment Transaction Person to Person Addendum Record (=9), Position 68, length
3) must contain the payers country code.

Payers Postal code (MasterCard Payment Transaction Person to Person Addendum Record (=9), Position 71, length
10) must contain the payers postal (ZIP) code.

Sample Transaction for the above example:

07M5409640000000009 mmdd J0002043566229 PAYPAL *WWWITEMGARD
07<1 000000017282208 HKG000000000 4029357733
07<A mmdd000000 4029357733 HKG0000000000000000000000000000000
07=0000000000000000000000 0000 653381
07=51101000100050S09000
07=9MARTIN QUINLAN PAYER ADDRESS DUBLIN DUB035ZIP CODE

80 Byte Population Guide Page 134 of 216

Version 15.93
OmniPay Innovation in Transaction Management

10 MPOS transactions
These are Card Present transactions involving a Mobile Point for either Visa or MasterCard. The Preceding
requirements for a standard point of sale transaction are expected, in addition, the CAT level indicator for Visa and
MasterCard must be populated as per the examples below.

VISA
CAT Level Indicator (VISA Detail Addendum Record 1 (#1), Position 62, Length 1) must be space. (TC05 TCR1 Pos 124)
9 = mPOS Acceptance Device

Sample transaction: Capture Method - ICC, offline auth, offline pin

06V4018440000000018 mmdd 111760 1 IPN09051400000
06<1 000000006026978
06<A mmdd000000 0000000000000000000000000110704
06<B OASE02
06#1552 000000764940826Y1000000000000000 000005 9
06#3 000000 0000000020400

MASTERCARD
CAT Level Indicator (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 80, length 1) must
be as follows (PDS 23)
9 =Mobile Acceptance Solution

Sample transaction: Capture Method - MS, offline auth, offline pin

06M5409640000000009 mmdd 021877 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A090891766 mmdd 0000001124CAPE CANAVERAFL 0000000116300000000012728180500-05
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336690
06=51101000510501F110008401 ASTRONAUT BLVD. S 9

MASTERCARD
CAT Level Indicator (MasterCard Interchange Compliance Detail Addendum Record 3 (=5), Position 80, length 1) must
be as follows (PDS 23)
9= Mobile Acceptance Solution

Sample transaction: Capture Method - MS, offline auth, offline pin

06M5409640000000009 mmdd 021877 37442839 BUDGET RENT A CAR
06<1 000000009137840FL USA32920 CAPE CANAVERA
06<A090891766 mmdd 0000001124CAPE CANAVERAFL 0000000116300000000012728180500-05
06<B 38BC
06=0000000000000000025456MCSBU88NU0328 336690
06=51101000510501F110008401 ASTRONAUT BLVD. S 9

80 Byte Population Guide Page 135 of 216

Version 15.93
OmniPay Innovation in Transaction Management

11 ATM Automated Cash disbursements

These are cash disbursement transactions that occur at an Automated Teller Machine (ATM) and are identified by the
MCC code of 6011. ATM transactions are processed as purchase transactions on the platform and OmniPay system
recognises these as ATM transactions by the MCC code and populates the clearing files accordingly. Currently we
support ATM interchange rates for Visa only and we dont support any MasterCard ATM rates. Visa refund
transactions with an MCC 6011 and all MasterCard transactions with an MCC of 6011 will receive front end rejection
on OmniPay platform. Both cardholder and the card must be present for these transactions and the transactions must
be authorised. Whilst Interchange Reimbursement Fees are payable by acquirer to issuer for original POS transactions,
for cash disbursement transactions, issuer pays acquirer the ATM and Manual Cash Disbursement Fees.

VISA
Merchant Category Code (VISA Detail Addendum Record 1 (#1), Position 50, Length 4): MCC must be 6011. (TC50
TCR0 Pos 133-136)

Sample transaction: Capture Method - Cust. present, key-entry

06V4018440000000018 mmdd 467041 00010080378498
06<1000000000000010101826 GBR LONDON NN
06<A mmdd000000 0000000000000000000000000
06#159 00000001010182600 601101P 0
06#3 U000000 0000000010101

80 Byte Population Guide Page 136 of 216

Version 15.93
OmniPay Innovation in Transaction Management

12 Payment Facilitator Transactions

MasterCard is implementing identification enhancements that will help identify the payment facilitator, sub-
merchant, and/or independent sales organisation that may be participating in a transaction.
A Payment Facilitator is a Service Provider registered by an Acquirer to facilitate the acquiring of transactions from
Sub-merchants.
Payment Facilitator support must be previously agreed with Omnipay and MasterCard prior to implementation.
Where applicable, the Payment Facilitator ID and Independent Sales Organisation ID must always be values assigned
by MasterCard and must be the same value in both the Authorisation and Clearing transactions.
Payment Facilitator transactions are only relevant to By Transaction or By Transaction Reject merchant setups.

Omnipay do not have visibility on the validity of the Submerchant ID submitted.

Financial penalty assessments will apply from 1st December 2015 for November 2015 data.

MasterCard
Sub Merchant ID (MasterCard Interchange Compliance Detail Addendum Record 1(=0) Position 65-79): Must be
populated as agreed with MasterCard. (IPM PDS 0208 S2)

Card Acceptor ID code (<C Position 35-54)If this non mandatory field is populated, it will supersede the Merchant ID
that is provided on the Summary record, and will go to scheme in its place for this transaction. (DE 42) This is only
relevant to PSPs that were previously using this field.

Card Acceptor Name/Location (Bankcard and T&E Detail Record, Position 56-80) (DE 43 S1) - Contains the name of
Payment Facilitator and Sub-merchant info, if applicable.
The Payment Facilitator name must be 3, 7 or 12 characters in length, followed by an asterisk, and the sub-merchant
name as indicated in the sample below. Space fill to get to the required field length.

Card Acceptor Street (Bankcard and T&E Detail Record 3 (=5), Position 24-79) (DE 43 S2) - must contain the card
acceptor street address for the sub-merchant, not the Payment Facilitator.

Card Acceptor City (Bankcard and T&E Detail Record 1 (<1), Position 42-54)(DE 43 S3) - must contain the card
acceptor City for the sub-merchant, not the Payment Facilitator.

Card Acceptor Postal Code (Bankcard and T&E Detail Record 1 (<1), Position 32-41) (DE 43 S4) - must contain the
card acceptor Postal Code for the sub-merchant, not the Payment Facilitator.

Card Acceptor State (Bankcard and T&E Detail Record 1 (<1), Position 26-28) (DE 43 S5) - must contain the card
acceptor State for the sub-merchant, not the Payment Facilitator, if in the US or Canada. If it is outside these areas, it
can be populated with all spaces, a province or region code, or the same three-position country code that is populated
in Card Acceptor Country, as below.

Card Acceptor Country (Bankcard and T&E Detail Record 1 (<1), Position 29-31) (DE 43 S6) - must contain the card
acceptor Country Code for the sub-merchant, not the Payment Facilitator.

Sample transaction: Capture Method - MS, offline auth, offline pin

06M5409640000000009 mmdd 060145 2 J00010080388314PAYMENTNAMEID*SUBNAME
06<1000002000000031900840CA USA20 City
06<A mmdd000000 0000000000000000000000000
06<B
06=0000000000000000031900MMDC123450323 599981 2N
06=51211000100050S00000PATRICK STREET 123451234512345

80 Byte Population Guide Page 137 of 216

Version 15.93
OmniPay Innovation in Transaction Management

13 Manual Cash disbursements

These are manual cash disbursement transactions and are identified by the MCC code of 6010. Manual cash
transactions are processed as purchase transactions on the platform and OmniPay system recognises these by the
MCC code and populates the clearing files accordingly. Currently we support Manual cash Disbursement interchange
rates for Visa and MasterCard. Both Visa and MasterCard refund transactions with an MCC 6010 will receive front end
rejection on OmniPay platform. Both cardholder and the card must be present for these transactions and the
transactions must be authorised. Whilst Interchange Reimbursement Fees are payable by acquirer to issuer for
original POS transactions, for cash disbursement transactions, issuer pays acquirer the ATM and Manual Cash
Disbursement Fees.

VISA
Merchant Category Code (VISA Detail Addendum Record 1 (#1), Position 50, Length 4): MCC must be 6010. (TC50
TCR0 Pos 133-136)

Sample transaction: Capture Method - Cust. present, key-entry

06V4018440000000018 mmdd 467041 00010080378498
06<1000000000000010101826 GBR LONDON NN
06<A mmdd000000 0000000000000000000000000
06#159 00000001010182600 601001P 0
06#3 U000000 0000000010101

MASTERCARD
Merchant Category Code MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 45, length 4):
MCC must be 6010. (DE 26)

Sample transaction: Capture Method - Cust. present, key-entry

06M5409640000000009 mmdd 724169 00010080378497
06<1000000000000010909826 GBR LONDON N
06<A mmdd000000 0000000000000000000000000
06=0000000000000000010909MMDC123450320 601001
06=51211000100000109000

80 Byte Population Guide Page 138 of 216

Version 15.93
OmniPay Innovation in Transaction Management

14 Quasi-Cash Transactions
Quasi-Cash transactions refer to sale of items directly convertible to cash, including, but not limited to:
Casino gaming chips
Money orders
Deposits
Wire Transfer money orders
Travelers cheques (if not processed as a Cash Disbursement)
Visa Travel Money Cards (if not processed as a Cash Disbursement)
Foreign Currency (if not processed as a Cash Disbursement)

Quasi cash transactions are purchase transactions identified by the MCC code of 4829, 6051 or 7995 for Visa and
MasterCard. For Visa transactions, Original Credit Identifier (VISA Detail Addendum Record 1 (#1), Position 57, Length
1) must be space filled to indicate its a Non-Original Credit transaction. OmniPay system then recognises these as
Quasi-cash transactions and populates the clearing files accordingly.

Maestro and MasterCard Refunds of Quasi Cash transactions can be processed with Interchange Program
Qualification set to 'G'

VISA
Merchant Category Code (VISA Detail Addendum Record 1 (#1), Position 50, Length 4): MCC must be 4829, 6051 or
7995. (TC50 TCR0 Pos 133-136)

Sample transaction: Capture Method - Cust. present, key-entry (Purchase)

06V4018440000000018 mmdd 467041 00010080378498
06<1000000000000010101826 GBR LONDON NN
06<A mmdd000000 0000000000000000000000000
06#159 00000001010182600 605101P
06#3 U000000 0000000010101

Refund of a Quasi Cash transaction should be submitted as a regular refund with the Original Credit Identifier (VISA
Detail Addendum Record 1 (#1), Position 57, Length 1) populated with a space to ensure the refund transaction is not
processed as Visa Original Credit transaction.

Sample transaction: Capture Method - Cust. present, key-entry (Refund)

07V4018440000000018 mmdd 467041 00010080378498
07<1000000000000010101826 GBR LONDON NN
07<A mmdd000000 0000000000000000000000000
07#159 00000001010182600 605101
07#3 U000000 0000000010101

MASTERCARD
Merchant Category Code MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 45, length 4):
MCC must be 4829, 6051 or 7995. (DE 26)

Sample transaction: Capture Method - Cust. present, key-entry (Purchase)

06M5409640000000009 mmdd 724169 00010080378497
06<1000000000000010909826 GBR LONDON N
06<A mmdd000000 0000000000000000000000000
06=0000000000000000010909MMDC123450320 799501
06=51211000100000109000

80 Byte Population Guide Page 139 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Refund of a Quasi Cash transaction should be submitted as a regular refund to ensure the refund transaction is not
processed as MasterCard Payment Transaction or Payment of Winnings transaction.

Interchange Program Qualification Flag (Bankcard and T & E Detail Addendum Record 1 (<1), Position 58, length 1)
must be as follows:
G =Maestro Gambling Refund transaction (as opposed to Payment of Winnings)

Sample transaction: Capture Method - Cust. present, key-entry (Refund)

07M5409640000000009 mmdd 724169 00010080378497
07<1000000000000042000752 GBR LONDON G
07<A mmdd000000 0000000000000000000000000
07=0000000000000000010909MMDC123450320 799501
07=51211000100000109000

80 Byte Population Guide Page 140 of 216

Version 15.93
OmniPay Innovation in Transaction Management

15 Dynamic Currency Conversion (DCC)

DCC can be offered in a card present environment at the POS terminal as well as in a card not present environment
such as an eCommerce website.
If the cardholder accepts the DCC, the transaction is put through in the cardholder currency and the DCC indicator
is 1 or 4
If the cardholder declines the DCC, the transaction is put through in the base currency and the DCC indicator is 3
If the cardholder currency is non-convertible, the transaction is put through in the base currency and the DCC
indicator is 2

EMV data: EMV Data passed to scheme should reflect the converted DCC Amount and Currency that is to be paid by
the cardholder, not the Transaction Amount and Currency that is to be paid to the merchant.

Dynamic Currency Conversion Indicator (Bankcard and T & E Detail Addendum Record A (<A), Position 25, Length 1),
should be one of the values listed below.
1 =Converted
2 =Not Convertible
3 =Convertible but declined by the cardholder
4 =Converted. Adjustment to an original DCC sale (i.e. a refund at a later date of an initial DCC. sale
transaction, which attains the Conversion Rate of the initial transaction).
Space filled for non-DCC transactions

Transaction Amount (Bankcard and T & E Detail Addendum Record 1 (<1), Position 11, length 12) must equal to the
original amount which will be funded to the merchant.

Transaction Currency (Bankcard and T & E Detail Addendum Record 1 (<1), Position 23, length 3) must equal the
currency the merchant is funded in.

Dynamic Currency Conversion Amount (Bankcard and T & E Detail Addendum Record A (<A), Position 45, Length 12)
should be populated with the conversion amount. Right justified, zero filled. If DCC is refused or not convertible, on a
DCC 80 byte, zero fill.

Alignment of the decimal point in this field will be based on the Dynamic Currency Conversion Currency Code in
position 26.

Dynamic Currency Conversion Currency Code (Bankcard and T & E Detail Addendum Record A (<A), Position 26,
Length 3) should be populated with the currency code of the issuing bank. This should only be filled when the DCC
indicator is populated. If DCC declined or not convertible on a DCC 80 byte, populate with Transaction Currency Code.

Dynamic Currency Conversion Rate (Bankcard and T & E Detail Addendum Record A (<A), Position 57, Length 13)
should be populated with the conversion rate used to convert the Transaction amount into the Dynamic Currency
Conversion Amount. Right justified, zero filled. Zero fill if DCC declined or not convertible on a DCC 80 byte.

Transaction Currency Code (EMV) (EMV Detail Addendum Record 1 (@1), Position 23, Length 3) (EMV Tag: 5F2A)
should contain the DCC currency Code for all DCC EMV transactions. If DCC is declined or not converitble, this will
equal the Transaction Currency Code also.

Sample Transaction for DCC Approved transaction:

06V4*****0000000007 mmdd 757662 4 00010070000005
06<1 000000014336840
06<A mmdd0000001826X 0000000105050000001364723124830
06<B 9999390107 55559939
06#1521N9939 00000001433639200000000000000107 701190
06#3 000000 0000000014336

80 Byte Population Guide Page 141 of 216

Version 15.93
OmniPay Innovation in Transaction Management

06@1000111003E0B8C8056826 05375C000000008000008C
06@2000000002500 8B8C42909F2420E340 035116150F106783000000000000
06@306090A0364000000000000000000000000000000000000000000000000000000 41030222

06M5*****0000000003 mmdd 071256 23602730892

06<1 000000020600978
06<A mmdd0000001826BRUSSELS 0000000182640000000008866083813
06<B 23602730892 55556027
06=0000000000000000018264MNW47HBPE1004 701105 S000
06=51410000511101511144
06@1001111003E0B8C8056826 009F5C0000000080000002
06@2000000021600 616B53ED3172EEF740 035116028172C90A000000000000
06@306050A0364200000000000000000000000000000000000000000000000000000 41030222H

Sample Transaction for DCC Not Convertible:

06V456354******4704 0213 262678

06<1412168000000160000978
06<A 02130000002978 0000000000000000000000000120814+01
06<B 604411121978AL021281
06#1 52A 00000016000097800000000000000000 573205P
06#3 000000 0000000000000
06@1000160213E0F8C8528978A0000000031010 00353D000080008000
06@2000000160000 BAA293458343A3D880 33888341A916BBF4000000000000
06@306030A03A42002 0044030221

Sample Transaction for DCC Declined:

06V456354******4704 0213 262678

06<1412168000000160000978
06<A 02130000003978 0000000000000000000000000120814+01
06<B 604411121978AL021281
06#1 52A 00000016000097800000000000000000 573205P
06#3 000000 0000000000000
06@1000160213E0F8C8528978A0000000031010 00353D000080008000
06@2000000160000 BAA293458343A3D880 33888341A916BBF4000000000000
06@306030A03A42002 0044030221

80 Byte Population Guide Page 142 of 216

Version 15.93
OmniPay Innovation in Transaction Management

16 Airline with AID

This section lists the information required to qualify for the airline rates in addition to the setup for the card capture
methods as outlined in the previous sections based on how these transactions are captured either by Mail order, Telephone
order, e-Commerce or at a POS terminal. The airline transactions should include the trip leg details in the airline addendum
records on the 80 byte to qualify for the Airline incentive rates.

As part of compliance release 15.1 Visa mandate that transactions with Airline MCCs which are not ticket purchases within
Europe or the United States must contain Airline Itinerary Ancillary Data. The new Records will be used to identify charges
for a number of ancillary services such as ticket upgrades, baggage fee, food & beverage purchases etc. These new fields will
also be used to identify changes for ticket charges such as cancellation charges, partial airline ticket refunds and ancillary fee
cancellations. Please review section 18: Airline Ancillary Data for details on this new element.

MasterCard commercial transactions with an Airline MCC can obtain incentive rates when they submit the outlined
addendum records. These incentive rates are available in Domestic UK, Intra EEA, Intra Eastern, Intra Western, Intra EU
and Intra Euro zone.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Charge Description (Bankcard and T & E Detail Record, Position 56, length 25) should have the DBA name populated.
For airline MCCs other than 4511, the DBA name should be the shortened version. Typically this contains the
abbreviated Airline and it should not exceed first nine positions.
V I R A T L
Ticket number should NOT be populated in the charge description field. Charge Description field should be space
filled if a merchant has decided to use the DBA Name from the Merchant Master File.

Merchant Category Code (VISA Detail Addendum Record 1 (#1), Position 50, Length 4): MCC must be 3000-3299 or
4511. (TC50 TCR0 Pos 133-136)

Passenger Name (Visa Passenger Itinerary General Detail Addendum Record 1 (#4), Position 7, and Length 20): The
passenger name should be a valid left justified string with trailing spaces. (TCR 3, 27-46)

Departure Date (Visa Passenger Itinerary General Detail Addendum Record 1 (#4), Position 27, and Length 6): The
date should be of the format MMDDYY or it may contain zeroes. Date can be in future. (TCR 3, 47-52)

Origin City (Visa Passenger Itinerary General Detail Addendum Record 1 (#4), Position 33, Length 3): The originating
airport names standard abbreviation. This should not contain all spaces or zeroes. For Miscellaneous Airline Charges,
value must be XAA (TCR 3, 53-55)

Ticket Number (Visa Passenger Itinerary General Detail Addendum Record 2 (#5), Position 5, Length 15): The number
on the ticket. (TCR0 104-116)

Trip Leg Data: (These fields should be populated on the trip leg addendum record for each trip leg)

Carrier Code (Visa Passenger Trip Leg Specific Detail Addendum Record (#6), Position 5, length 2, Per Trip Leg):
Contains the standard abbreviation for the airline or railway carrier issuing the ticket. This should not contain all
spaces or zeroes. (TCR 3, 56-57)

Service Class (Visa Passenger Trip Leg Specific Detail Addendum Record (#6), Position 7, length 1, Per Trip Leg): The
service type (for example, coach or first class). This should not be a space or zero. (TCR 3, 58)

Stopover Code (Visa Passenger Trip Leg Specific Detail Addendum Record (#6), Position 8, length 1, Per Trip Leg): The
entry must be a space, O, or X for all trip legs. (TCR 3, 59)
80 Byte Population Guide Page 143 of 216

Version 15.93
OmniPay Innovation in Transaction Management

O =Stopover allowed
X =Stopover not allowed

Destination City (Visa Passenger Trip Leg Specific Detail Addendum Record (#6), Position 9, length 3, Per Trip Leg):
Destination City Airport Code. This should not contain all spaces or zeroes. (TCR 3, 60-62)

Sample transaction: Capture Method - SET/3D-SET non-authenticated

06V4008360000000002 mmdd 286222 0 600010080000035VIR ATL
06<1000000000000060400344 GBR LONDON NN
06<A mmdd000000 0000000000000000000000000
06#1594 00000006040034400 314401N 0
06#3 000000 0000000060400
06#404HEMLIN/KAYLA LOUISE 051409DFW91266313EGENCIA UK LTD
06#50863537085575
06#6VSKXLAXKOWSPU VSKXAKLKOWSPU VSKOADLKOWSPU

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Charge Description (Bankcard and T & E Detail Record, Position 56, length 25) should have the DBA name populated.
For airline MCCs other than 4511, the DBA name should be the shortened version. Typically this contains the
abbreviated Airline and it should not exceed first nine positions.
V I R A T L
Ticket number should NOT be populated in the charge description field. Charge Description field should be space
filled if a merchant has decided to use the DBA Name from the Merchant Master File.

Merchant Category Code (MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 45, length 4):
MCC must be 3000-3299 or 4511. (DE 26)

Number of Legs (MC Passenger Transport Detail - General Ticket Addendum Record 1 (=6), Position 5, length 3): Total
number of trip legs, should be greater than 000 and cant be space filled.

Passenger Name (MC Passenger Transport Detail - General Ticket Addendum Record 1 (=6), Position 8, length 29): The
name of the passenger to whom the ticket was issued. (PDS 0505)

Ticket Number (MC Passenger Transport Detail - General Ticket Addendum Record 1 (=6), Position 37, length 15): The
number on the ticket. (PDS 0506)

Issuing Carrier (MC Passenger Transport Detail - General Ticket Addendum Record 1 (=6), Position 52, length 4):
Contains the standard abbreviation for the airline or railway carrier issuing the ticket. (PDS 0507)
Please note that this field is required for US Domestic Airline transactions but NOT for Incentive rates in
Europe.

Total Fare (MC Passenger Transport Detail - General Ticket Addendum Record 1 (=6), Position 56, length 12): Can be
all zeroes but if present Total Fare should equal the transaction amount. (PDS 0512)
Please note that this field can be all zeroes for US Domestic Airline transactions but is required to match the
transaction amount for all non-US airline transactions especially in EU.

Customer Code (MC Passenger Transport Detail - General Ticket Addendum Record 2 (=7), Position 43, length 17):
Contains internal reference. (PDS 0508)
Please note that this field is required to achieve Incentive rates in Europe but is not required for US Domestic
Airline transactions.

Trip Leg Data: (These fields should be populated on the trip leg addendum record for each trip leg) - Trip leg total 0-
999 is the limit.

80 Byte Population Guide Page 144 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Travel Date (MC Passenger Transport Detail Trip Leg Data Addendum Record (=8), Position 8, length 6): Format
YYMMDD. (PDS 0520)

Carrier Code (MC Passenger Transport DetailTrip Leg Data Addendum Record (=8), Position 14, length 2): The standard
abbreviation for the airline or railway carrier. (PDS 0521)

Service Class Code (MC Passenger Transport Detail Trip Leg Data Addendum Record (=8), Position 16, length 2): The
service type (for example, coach or first class). (PDS 0522)
Please note that this field is required to achieve airline rates in US Domestic but is not required for Incentive rates in
Europe.

City of Origin/Airport Code (MC Passenger Transport Detail Trip Leg Data Addendum Record (=8), Position 18,
length 5): The originating airport or railway names standard abbreviation. (PDS 0523)

City of Destination/Airport Code (MC Passenger Transport Detail Trip Leg Data Addendum Record (=8), Position 23,
length 5): The destination airport or railway names standard abbreviation. (PDS 0524)

Sample transaction: Capture Method Merchant UCAF Incentive

06M5218040000000003 mmdd 006691 1 J VIR ATL
06<1000000000000040603702NY USA12345 New York
06<A mmdd000000 0000000000000000000000000000000
06=0000000000000000040600MCC0126800218 314481 1
06=51211000100590V09000
06=6004MCDONALD/RHYS JAMES MR 0863537067057 VS86000000110330
06=791266033OPODO LTD BSVT001
06=8001090613VSG NSN AKL XGEU04
06=8002090613VSG AKL LHR XGEU04
06=8003090613VSG LHR MAN OGEU04
06=8004090613VSL MAN LHR XLEU04

Sample transaction: MC US Dom Passenger Transport Enhanced Rate (FPI Code AL6)
06M5401680000000003 mmdd 03114B 0 J00010080000295JetBlue
06<1000000000000121939840 USA LONDON N
06<A mmdd000000 0000000000000000000000000
06=0000000000000000121939MCC01F6F40709 317401 1
06=51203000100010V09000
06=6002ROTH WALTER MR 2156582230 B6 0000001219390000000000000
06=7 Jet Blue Airway EVZHY2
06=8001090723B6Q SFO LHR 20 0430P
06=8002090730B6X LHR ORD 39 1100A

Sample transaction: MC US Dom Passenger Transport Rate (FPI Code K23)

06M5401680000000003 mmdd 009563M2 00010080000280JetBlue
06<1000000000000050684840 USA LONDON N
06<A mmdd000000 0000000000000000000000000
06=0000000000000000050684MDS8WDPF90709 317401
06=51203000100020000000
06=6002PIETERSEN CHRISTOPHER MR 2156581666 B6 0000000506840000000000000
06=7 Jet Blue Airway EGPKTL
06=8001090723B6G JFK LHR 46 0730P
06=8002090728B6G LHR JFK 3 0930A

80 Byte Population Guide Page 145 of 216

Version 15.93
OmniPay Innovation in Transaction Management

17 Airline Without AID Data

This section lists the information required for Airline transactions that do not include the Airline Itinerary data such as
the trip leg details in the airline addendum records. This is in addition to the setup for the card capture methods as
outlined in the previous sections based on how these transactions are captured either by Mail order, Telephone order,
e-Commerce or at a POS terminal. These airline transactions will not qualify for the Airline incentive rates without the
AID. Transactions should contain an airline MCC, ticket number and the Airline abbreviation. If the airline rates are not
available or if the airline requirements are not met then the next best rate is achieved based on the capture method.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Charge Description (Bankcard and T & E Detail Record, Position 56, length 25) should have the DBA name populated.
For airline MCCs other than 4511, the DBA name should be the shortened version. Typically this contains the
abbreviated Airline and it should not exceed first nine positions.
Ticket number should NOT be populated in the charge description field. The Charge Description will be space filled
if a merchant has decided to use the DBA Name from the Merchant Master File.

Merchant Category Code (VISA Detail Addendum Record 1 (#1), Position 50, Length 4): MCC must be 3000-3299 or
4511. (TC50 TCR0 Pos 133-136)

Ticket Number (Visa Passenger Itinerary General Detail Addendum Record 2 (#5), Position 5, Length 15): The number
on the ticket. (TCR0 104-116)

Sample transaction: Capture Method - SET/3D-SET Authenticated

06V4787270000000018 mmdd 833235 9 500010080000026VIR ATL
06<1000000000000070600344 GBR LONDON NN
06<A mmdd000000 0000000000000000000000000
06#1594 00000007060034400 314401N 0
06#3 000000 0000000070600
06#400 000000 0
06#588888707 REALEX PAYMENTS

MASTERCARD
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Charge Description (Bankcard and T & E Detail Record, Position 56, length 25) should have the DBA name populated.
For airline MCCs other than 4511, the DBA name should be the shortened version. Typically this contains the
abbreviated Airline and it should not exceed first nine positions.
Ticket number should NOT be populated in the charge description field. The Charge Description will be space filled
if a merchant has decided to use the DBA Name from the Merchant Master File.

Merchant Category Code MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 45, length 4):
MCC must be 3000-3299 or 4511. (DE 26)

Ticket Number (MC Passenger Transport Detail - General Ticket Addendum Record1, Position 37, length 15): The
number on the ticket. (PDS 0506)

Apart from the ticket number, rest of the data on the MC Passenger Transport Detail - General Ticket Addendum
Record 1 (=6) can be populated with default values as per the 80 byte spec.
At least one MC Passenger Transport Detail Trip Leg Data Addendum Record (=8) should be provided. This record
can be populated with default values as per the 80 byte spec.

Sample transaction: Capture Method Merchant UCAF

06M5458830000000006 mmdd 006691 1 J VIR ATL
06<1000000000000040604702NY USA12345 New York

80 Byte Population Guide Page 146 of 216

Version 15.93
OmniPay Innovation in Transaction Management

06<A mmdd000000 0000000000000000000000000

06=0000000000000000040600MCC0126800218 314401 1
06=51211000100590V09000
06=6001 123456789012 000000000000
06=8001000000

80 Byte Population Guide Page 147 of 216

Version 15.93
OmniPay Innovation in Transaction Management

18 Airline Ancillary Data

This section lists the information required to qualify for Airline Ancillary Data Rates in addition to the setup for the
card capture methods as outlined in the previous sections, based on how these transactions are captured either by
Mail order, Telephone order, e-Commerce or at a POS terminal. The Airline Ancillary Data must transactions include
Data as detailed below in order to qualify for Incentive rates.

As part of compliance release 15.1 Visa mandate that Airline Ancillary transactions (This refers to ad-hoc transactions
that are not classed as Airline ticket sales or refunds, but use an Airline MCC) must contain Airline Ancillary Data. The
new Records will be used to identify charges for a number of ancillary services such as ticket upgrades, baggage fee,
food & beverage purchases which are not purchased as part of the original ticket. These new fields will also be used to
identify changes for ticket charges such as cancellation charges, partial airline ticket refunds and ancillary fee
cancellations.

Airline Ancillary Data Transactions are processed on a separate transaction to Airline with AID transactions but are
linked via ticket number to the original transaction.

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Charge Description (Bankcard and T & E Detail Record, Position 56, length 25) should have the DBA name populated.
For airline MCCs other than 4511, the DBA name should be the shortened version. Typically this contains the
abbreviated Airline and it should not exceed first nine positions.
V I R A T L
Ticket number should NOT be populated in the charge description field. Charge Description field should be space
filled if a merchant has decided to use the DBA Name from the Merchant Master File.

Merchant Category Code (VISA Detail Addendum Record 1 (#1), Position 50, Length 4): MCC must be 3000-3299 or
4511. (TC50 TCR0 Pos 133-136)

Ancillary Addendum Record #A, #B

Business Format Code (Ancillary Addendum Record #A Position 5, Length 2) (TCR3, 17-18)
AN=Identifies transaction as Airline Ancillary

Ancillary Ticket/Document Number (Ancillary Addendum Record #A Position 7, Length 15) (TCR3, 19-33)
Must be populated with form number from carrier assigned for transaction.

Ancillary Service Category 1(Ancillary Addendum Record #A Position 22, Length 4) (TCR3, 34-37)
Populated with data found in 80 byte spec, Appendix Q
If All Spaces, will get Standard Rate if aiming for CPS or EIRF

Ancillary Service Sub-Category 1 (Ancillary Addendum Record #A Position 26, Length 4) (TCR3, 38-41)
Valid data or all spaces.

Ancillary Service Category 2 (Ancillary Addendum Record #A Position 30, Length 4) (TCR3, 42-45)
Valid Data or all spaces.

Ancillary Service Sub-Category 2 Ancillary Addendum Record #A (Position 34, Length 4) (TCR3, 46-49)
Valid Data or all spaces.

Ancillary Service Category 3 (Ancillary Addendum Record #A Position 38, Length 4) (TCR3, 50-53)
Valid Data or all spaces.

Ancillary Service Sub-Category 3 (Ancillary Addendum Record #A Position 42, Length 4) (TCR3, 54-57)
80 Byte Population Guide Page 148 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Valid Data or all spaces.

Ancillary Service Category 4 (Ancillary Addendum Record #A Position 46, Length 4) (TCR3, 58-61)
Valid Data or all spaces.

Ancillary Service Sub-Category 4 (Ancillary Addendum Record #A Position 50, Length 4) (TCR3, 62-65)
Valid Data or all spaces.

Passenger Name (Ancillary Addendum Record #A Position 54, Length 4) (TCR3, 66-85)
Valid Data or all spaces. All spaces will cause Standard rates to apply.

Credit Reason Indicator 1 (Ancillary Addendum Record #A Position 74, Length 4) (TCR3, 101)
A=Passenger Transport Ancillary Cancellation
B=Airline Ticket and Passenger Transport
O=Other
REFUND ONLY

Credit Reason Indicator 1 (Ancillary Addendum Record #A Position 75, Length 4) (TCR3, 101)
A=Passenger Transport Ancillary Cancellation
B=Airline Ticket and Passenger Transport
O=Other
P=Partial Refund of Airline Ticket
Space= Not Used
REFUND ONLY

Credit Reason Indicator 1 (Ancillary Addendum Record #A Position 75, Length 4) (TCR3, 166)
A=Passenger Transport Ancillary Cancellation
B=Airline Ticket and Passenger Transport
O=Other
P=Partial Refund of Airline Ticket
Space= Not Used
REFUND ONLY

Ticket Charge Indicator (Ancillary Addendum Record #A Position 75, Length 4) (TCR3, 167)
C=Change to existing Tickert
N= New ticket
Space- Not used
REFUND ONLY

Issued in connection with Ticket Number (Ancillary Addendum Record #B Position 5, Length 20) (TCR3, 86-100)
Must contain document number of related transaction if applicable.
Mandatory for all regions in order to receive Airline rate.

Sample transaction: Capture Method - SET/3D-SET non-authenticated

06V4008360000000002 mmdd 286222 0 600010080000035VIR ATL
06<1000000000000060400344 GBR LONDON NN
06<A mmdd000000 0000000000000000000000000
06#1594 00000006040034400 314401N 0
06#3 000000 0000000060400
06#AAN12345123451234512341234123412341234Bob Smith ABN
06#B123451234512345

80 Byte Population Guide Page 149 of 216

Version 15.93
OmniPay Innovation in Transaction Management

19 MasterCard Incentive Rates

Commercial card transactions with an Airline Hotel / Car Rental / Purchasing (non T&E) MCC can obtain optimal
interchange when they submit the outlined addendum records for MasterCard. MasterCard Incentive rates are
available in Domestic UK, Intra EEA, Intra Eastern, Intra Western, Intra EU and Intra Euro zone. These rates apply to
commercial card products such as MasterCard Business Card, MasterCard Professional Card, MasterCard Corporate
Card, MasterCard Corporate Purchasing Card, MasterCard Corporate Fleet Card, MasterCard Electronic Business Card
and MasterCard Electronic Corporate.

Acquirers are not required to undergo any scheme certification with MasterCard to avail of these incentive rates.

For a normal transaction the regular interchange rate is debited from the acquirer and credited to the issuer. However
for a low value transaction where the incentive is higher than the calculated interchange fee, the issuer is debited and
the acquirer is credited with the difference. For example, consider a MasterCard Purchasing Card transaction that is
submitted for Intra-European POS Fallback IRD 75 Base with an interchange rate of 2.10% and a corporate incentive of
-0.50 EUR with a transaction amount of 8.00 EUR. When multiplied by the interchange rate we get an interchange fee
of 0.17 EUR. If the transaction meets corporate incentive criteria, then the corporate incentive interchange fee is a
0.50 EUR debit from the issuer and credited to the acquirer. Since the interchange fee paid by the acquirer to the
issuer of 0.17 EUR is less than the corporate incentive amount of 0.50 EUR then the net result is that the issuer is
paying the acquirer an interchange fee amount of 0.33 EUR.

19.1 Car Rental

The car rental transactions must include the following information in the Car Rental addendum records on the 80 byte
file. This section lists the information required to qualify for the Car Rental Incentive Interchange Rates in addition to
the setup for the card capture methods as outlined in the previous sections based on how these transactions are
captured either by Mail order, Telephone order, e-Commerce or at a POS terminal.

MASTERCARD
Merchant Category Code MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 45, length 4):
MCC must be 3351-3500, 7512, 7513 or 7519 (DE 26)

Customer Code (MasterCard Business/Purchase Card Addendum Record 1 (}1), Position 41, length 17) must be
populated with purchase code or the internal reference number. (PDS 0508)

Rental Details: (These fields should be populated for each car rental)

Rental Agreement Number (MasterCard Hotel and Car Rental Detail Addendum Record A (=1), Position 5, length 9)
must be populated with invoice number of original rental agreement. (PDS 0544)

Renter Name (MasterCard Hotel and Car Rental Detail Addendum Record A (=1), Position 20, length 20) must be
populated with the name of the person renting the car. (PDS 0545)

Rental Return City (MasterCard Hotel and Car Rental Detail Addendum Record A (=1), Position 40, length 18) must be
populated with the city where the car is returned. (PDS 0546)

Rental Return Date (MasterCard Hotel and Car Rental Detail Addendum Record A (=1), Position 61, length 6) must be
populated with the date on which the car is returned in format MMDDYY. (PDS 0550)

Rental Pick-Up/Check Out Date (MasterCard Hotel and Car Rental Detail Addendum Record A (=1), Position 14, length
6) must be populated with the date on which the car is picked up in format MMDDYY. (PDS 0551)

Rental Class ID (MasterCard Hotel and Car Rental Detail Addendum Record B (=A), Position 29, length 4) must be
populated with the car rental classification. (PDS 0568)

MasterCard Sample transaction: Capture Method Card Swiped, Signature

06M5474830000000139 mmdd 096515 G_123738000569

80 Byte Population Guide Page 150 of 216

Version 15.93
OmniPay Innovation in Transaction Management

06<1 000000010000978 201

06<A mmdd000000 0000000000000000000000000171943
06}1 8563217489
06=0000000000000000012300 0000 7512 0S201
06=51206000201101054000
06=17852361 042909JOE BLOGGS DUBLIN 05020985231479
06=A0000000000000000000000000007 00000000000000000000000

19.2 Hotel/Cruise Liners

The hotel or Cruise liner transactions must include the following information in the Hotel addendum records on the 80
byte file. This section lists the information required to qualify for the Incentive Interchange Rates in addition to the
setup for the card capture methods as outlined in the previous sections based on how these transactions are captured
either by Mail order, Telephone order, e-Commerce or at a POS terminal.

MASTERCARD
Merchant Category Code MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 45, length 4):
MCC must be 3501-3999 or 7011 (DE 26)

Customer Code (MasterCard Business/Purchase Card Addendum Record 1 (}1), Position 41, length 17) must be
populated with purchase code or the internal reference number. (PDS 0508)

Lodging Details: (These fields should be populated for each lodging instance)

Arrival Date (MasterCard Hotel and Car Rental Detail Addendum Record A (=1), Position 14, length 6) must be
populated with the arrival date. (PDS 0574)

Departure Date (MasterCard Hotel and Car Rental Detail Addendum Record A (=1), Position 61, length 6) must be
populated with the departure date. (PDS 0575)

Folio Number (MasterCard Hotel and Car Rental Detail Addendum Record A (=1), Position 67, length 10) must be
populated with the hotel number assigned to track expenses. (PDS 0576)

MasterCard Sample transaction: Capture Method Card Swiped, Signature

06M5474830000000147 mmdd 684368 G_123315032069
06<1 000000010000978 201
06<A mmdd000000 0000000000000000000000000082104
06}1 8563217489
06=0000000000000000006800 0000 7011 0S201
06=51208000201101054000
06=1 042709 042909965478213

19.3 Commercial Cards (Other than Airline, Hotel/Cruise, Car Rental MCCs)
These commercial card transactions must include the following information in the Business/Purchase Card Addendum
records on the 80 byte file. This section lists the information required to qualify for the Incentive Interchange Rates in
addition to the setup for the card capture methods as outlined in the previous sections based on how these
transactions are captured either by Mail order, Telephone order, e-Commerce or at a POS terminal. Currency Amounts
are included using the Currency Exponent found in the

MASTERCARD
Merchant Category Code MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 45, length 4):
MCC must NOT be 3000-3999, 4468, 4511, 4112, 5499, 5541, 5542, 5983, 7011, 7511, 7512, 7513, 7519, 9752 (DE 26)

80 Byte Population Guide Page 151 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Customer Code (MasterCard Business/Purchase Card Addendum Record 1 (}1), Position 41, length 17) must be
populated with purchase code or the internal reference number. This field must be populated when attempting to
qualify at Intra-Regional EU Commercial Incentive Interchange Rates. (PDS 0508)

Merchant/Card Acceptor Tax ID (MasterCard Business/Purchase Card Addendum Record 1 (}1), Position 26, length
15) must be populated with the Tax number of the Merchant. (PDS 0596)

Total Tax Amount (MasterCard Business/Purchase Card Addendum Record 1 (}1), Position 58, length 12) must be
populated with the Tax number of the corporation to whom the purchasing card was issued. This field must be
populated when attempting to qualify at Intra-Regional EU Commercial Incentive Interchange Rates. (PDS 0597)

Merchant Reference Number (MasterCard Business/Purchase Card Addendum Record 1 (}1), Position 5, length 17)
must be populated with merchant/supplier reference number, Store Number, Register, Number/Terminal Number,
Transaction, Number, Order Number of Invoice, number. (PDS 0600)

Corporate LID: (These fields should be populated for each instance of the corporate line item)

Item Description (MasterCard Business/Purchase Card Detail Addendum Record 1 (}4), Position 17, length 35) must be
populated with the Description of the item purchased. This field must be populated when attempting to qualify at
Intra-Regional EU Commercial Incentive Interchange Rates. (PDS 0642)

Item Quantity (MasterCard Business/Purchase Card Detail Addendum Record 1 (}4), Position 52, length 12) must be
populated with the quantity of the item purchased. This field must be populated when attempting to qualify at Intra-
Regional EU Commercial Incentive Interchange Rates. (PDS 0643 S1)

Unit Price (MasterCard Business/Purchase Card Detail Addendum Record 2 (}5), Position 39, length 12) must be
populated with the Price per unit of the item purchased (excluding VAT). This field must be populated when
attempting to qualify at Intra-Regional EU Commercial Incentive Interchange Rates. (PDS 0646)

Discount Indicator (MasterCard Business/Purchase Card Detail Addendum Record 2 (}5), Position 26, length 1) must
be populated with a Y or N when the Item Discount Amount is present. (PDS 0648 S1)

Item Discount Amount (MasterCard Business/Purchase Card Detail Addendum Record 2 (}5), Position 27, length 12)
must be populated with the Total amount of item discounted. Must not be all zeros if a discount amount exists and
last two digits are implied decimal places. Must be all zeros if discount amount does not exist.. (PDS 0648 S2)

Detail Tax rate (MasterCard Business/Purchase Card Detail Addendum Record 2 (}5), Position 5, length 4) must be
populated with the detailed tax rate applied in relationship to a specific tax amount. This subfield must be numeric
and may not contain all zeros. 2 Decimal points implied (0090=9% rate) (PDS 0682 S3)

Item Discount Rate (MasterCard Business/Purchase Card Detail Addendum Record 2 (}5), Position 9, length 5) must be
populated with the item discount rate. This is required if Item Discount Amount is present. 2 Decimal points implied
(0090=9% rate) (PDS 0648 S3)

Sample Transaction for the above example:

06M5474830000000139 mmdd 832842 J3865429044 2CO.COM*BEHAPPY
06<1 000000010000826 GBRE1W 1YT 877-294-0273
06<A mmdd000000 877-294-0273 0000000000000000000000000000000
06}1963258741 470493581 3126724123 000000002000Y
06}2
06}3 000000001500
06}4 ADVERTISEMENT SERVICES 000000000001
06}5002000500000000002000Y000000001500000000011500 3126724123 Y
06=0000000000000000069515MCSN43U2H0114 899901 2
06=510110001000106090001785 O'BRIEN RD

80 Byte Population Guide Page 152 of 216

Version 15.93
OmniPay Innovation in Transaction Management

19.4 Commercial Cards (Airline MCCs)

These commercial card transactions must include the following information in the Passenger Transport Detail
Addendum records on the 80 byte file. This section lists the information required to qualify for the Incentive
Interchange Rates in addition to the setup for the card capture methods as outlined in the previous sections based on
how these transactions are captured either by Mail order, Telephone order, e-Commerce or at a POS terminal.
If the acquirer meets the requirements and provides the required additional data, MasterCard calculates the fee
amount by deducting the incentive rate from the applicable interchange fee rate. Required additional data are defined
by card acceptor business code (MCC).

MASTERCARD
Merchant Category Code MasterCard Interchange Compliance Detail Addendum Record 1 (=0), Position 45, length 4):
MCC must be 3000-3299 or 4511 in order to qualify at Airline Commercial Incentive Rates (DE 26)

Passenger Name (MC Passenger Transport Detail - General Ticket Addendum Record 1 =6), Position 8, length 29) must
be populated with the name of the passenger to whom the ticket was issued. This field must be populated when
attempting to qualify at Airline Commercial Incentive Rates. (PDS 0505)

Ticket Number (MC Passenger Transport Detail - General Ticket Addendum Record 1 =6), Position 37, length 15) The
number on the ticket. This field must be populated when attempting to qualify at Airline Commercial Incentive Rates.
(PDS 0506)

Customer Code (MC Passenger Transport Detail - General Ticket Addendum Record 2 =7), Position 43, length 17)
Merchant Internal Reference Number. This field must be populated when attempting to qualify at Airline Commercial
Incentive Rates. (PDS 0508)

Travel Date (MC Passenger Transport Detail Trip Leg Data Addendum Record =8), Position 8, length 6) must be
populated in format YYMMDD. This field must be populated when attempting to qualify at Airline Commercial
Incentive Rates. (PDS 0520)

City of Origin/Airport Code (MC Passenger Transport Detail Trip Leg Data Addendum Record =8), The originating
airport's standard abbreviation. This field must be populated when attempting to qualify at Airline Commercial
Incentive Rates. (PDS 0523)

City of Destination/Airport Code (MC Passenger Transport Detail Trip Leg Data Addendum Record =8) Position 23,
length 5) must be populated with the originating airport's standard abbreviation. This field must be populated when
attempting to qualify at Airline Commercial Incentive Rates. (PDS 0524)

Sample Transaction for the above example:

06M5458830000000006 mmdd 006691 1 J VIR ATL

06<1000000000000040604702NY USA12345 New York
06<A mmdd000000 0000000000000000000000000
06=0000000000000000040600MCC0126800218 314401 1
06=51211000100590V09000
06=6001Bob Smith 123456789012 000000000000
06=7 CUSTOMERCODE12345
06=8 151102 DUB ATL

80 Byte Population Guide Page 153 of 216

Version 15.93
OmniPay Innovation in Transaction Management

20 Visa Car Rental Transactions

At present we dont currently support Car Rental Addendum Records for Visa on the 80 byte but we do have fields
within the 80 byte to populate different criteria for Car Rental Transactions. These fields can be found in the Visa CPS
Detail Addendum Records 1 and 2. Unlike the MasterCard hotel transactions which can qualify for incentive rates with
commercial cards, Visa does not support any specific rates (U.S. Domestic CPS Car Rental/Hotel rates are only
available within the U.S. region) and these transactions will qualify for interchange rates based on their capture
methods. This section lists the Car Rental information that can be submitted in addition to those outlined in the
previous sections for various captured methods such as Mail order, Telephone order, e-Commerce or at a POS
terminal.

VISA
Merchant Category Code (VISA Detail Addendum Record 1 (#1), Position 50, Length 4): MCC must be 3351-3500,
7512, 7513 or 7519. (TC50 TCR0 Pos 133-136)

Check in Date (VISA Detail Addendum Record 2 (#3), Position 33, Length 6) Car Rental pick up date in the format
YYMMDD. No show or prepay =scheduled pick up date. (TC 05 TCR 3 pos 38-43)

Extra Charges (VISA Detail Addendum Record 2 (#3), Position 39, Length 6) Additional charges added to customer
bill after check-out. Each position can be used to indicate a type of charge. See below for the values of extra charges.
No extra charges =Space filled. (TC 05 TCR 3 pos 28-33)
1 =Gas
2 =Extra Mileage
3 =Late Return
4 =1 Way Ser Fee
5 =Parking Violation

No show indicator (VISA Detail Addendum Record 2 (#3), Position 45, Length 1) Must be as follows (TC 05 TCR 3 pos
27)
0 =Not Applicable
1 =No Show

Total Authorised Amount (VISA Detail Addendum Record 2 (#3), Position 46, Length 12) For Car Rental transactions
this amount should be the total authorized amount. (TC 05 TCR 5 pos 50-61)

Sample transaction:
06V4543050000000134 mmdd 092244 52347460081 HOTEL TEST
06<1 000000033050826
06<A mmdd000000 877-294-0273 0000000000000000000000000000000
06#1521N7704 000000033050826 247141343865709 751290
06#342347460081 07052134 0000000033050

80 Byte Population Guide Page 154 of 216

Version 15.93
OmniPay Innovation in Transaction Management

21 Visa Hotel Transactions

At present we dont currently support Hotel Addendum Records for Visa on the 80 byte but we do have fields within
the 80 byte to populate different criteria for Hotel Transactions. These fields can be found in the Visa CPS Detail
Addendum Records 1 and 2. Unlike the MasterCard hotel transactions which can qualify for incentive rates with
commercial cards, Visa does not support any specific rates (U.S. Domestic CPS Car Rental/Hotel rates are only
available within the U.S. region) and these transactions will qualify for interchange rates based on their capture
methods. This section lists the hotel information that can be submitted in addition to those outlined in the previous
sections for various captured methods such as Mail order, Telephone order, e-Commerce or at a POS terminal.

VISA
Merchant Category Code (VISA Detail Addendum Record 1 (#1), Position 50, Length 4): MCC must be 3501-3999 or
7011. (TC50 TCR0 Pos 133-136)

Check in Date (VISA Detail Addendum Record 2 (#3), Position 33, Length 6) Hotel check-in date in the format
YYMMDD. No show or advance lodging =scheduled arrival date. (TC 05 TCR 3 pos 38-43)

Extra Charges (VISA Detail Addendum Record 2 (#3), Position 39, Length 6) Additional charges added to customer
bill after check-out. Each position can be used to indicate a type of charge. See below for the values of extra charges.
No extra charges =Space filled. (TC 05 TCR 3 pos 28-33)
2 =Restaurant
3 =Gift Shop
4 =Mini Bar
5 =Telephone
6 =Other
7 =Laundry

No show indicator (VISA Detail Addendum Record 2 (#3), Position 45, Length 1) Must be as follows (TC 05 TCR 3 pos
27)
0 =Not Applicable
1 =No Show

Total Authorised Amount (VISA Detail Addendum Record 2 (#3), Position 46, Length 12) For Hotels transactions this
amount should be the total authorized amount. (TC 05 TCR 5 pos 50-61)

Sample transaction:
06V4543050000000134 mmdd 092244 52347460081 HOTEL TEST
06<1 000000033050826
06<A mmdd000000 877-294-0273 0000000000000000000000000000000
06#1521N7704 000000033050826 247141343865709 701190
06#342347460081 07052127 0000000033050

80 Byte Population Guide Page 155 of 216

Version 15.93
OmniPay Innovation in Transaction Management

22 Visa Incentive Rates

These commercial card transactions must include the following information in the Commercial Card addendum
records on the 80 byte file. In order to avail of these incentive rates, the acquirer has to undergo a scheme
rd
certification with Visa and tax audit involving a 3 party in each country they wish to process these transactions.

22.1 Corporate LID Rates

This section lists the information required to qualify for the Corporate Line Item Data Incentive Interchange Rates in
addition to the setup for the card capture methods as outlined in the previous sections based on how these
transactions are captured either by Mail order, Telephone order, e-Commerce or at a POS terminal.
Currency exponent is consistent with values in <1 record.

VISA
Customer Reference ID (VISA Commercial/Purchase Card Addendum Record 1 (%1), Position 55, length 17) must be
populated with Cardholder/customer data. Data will appear on customers statement. Zeroes are allowed but not
spaces (TC05 TCR06 Pos 111-127)

Purchase Identifier (Suppler Invoice Number) (VISA Commercial/Purchase Card Addendum Record 1 (%1), Position 5,
length 25) must be populated with merchant defined data (i.e., store number, register/terminal number, transaction
number, order number). (TC50TCR00(A) Pos 100-114)

VAT rate for Freight/Shipping (VISA Commercial/Purchase Card Addendum Record 1 (%1), Position 72, length 4) must
be populated with VAT for the freight/shipping amount. Zeroes are allowed but not spaces. 2 Decimal points implied
(00090=9% rate) (TC50 TCR00 (A) Pos 152-155)

National Tax (VISA Purchase Card Addendum Record 2 (%2), Position 5, length 12) must be populated with the
amount of national tax or value added tax. Non-US only (TC05 TCR06 Pos 18-29)

Merchant VAT Registration (VISA Purchase Card Addendum Record 2 (%2), Position 17, length 20) must be populated
with Identification number assigned by the taxing authorities to the merchant. Where the National Tax Included is 1
then the Supplier VAT Reg. No. must not be all spaces if attempting to qualify at LID/SUMM interchange. (TC05 TCR06
Pos 31-50)

Summary Commodity Code (VISA Purchase Card Addendum Record 2 (%2), Position 50, length 4) must be populated
with the European value added tax requirement. Must be populated with LID when attempting to qualify at LID
interchange or populated as SUMM when attempting to qualify at SUMM interchange. Non-US only (TC05 TCR06 Pos
76-79)

Freight/Shipping Amount (VISA Purchase Card Addendum Record 3 (%3), Position 12, length 5) must be populated
with the freight amount on total purchase. Zeroes are allowed but not spaces. (TC50 TCR00 (A) Pos 53-64) The total
freight/shipping amount applied to a transaction. Merchants can choose to deliver the contents of a single transaction
in multiple shipments and this field reflects the total cost of those deliveries. Must not be all zeros if a freight/shipping
amount exists and last two digits are implied decimal places. Must be all zeros if freight/ shipping amount does not
exist.

Discount Amount (VISA Purchase Card Addendum Record 3 (%3), Position 52, length 12) must be populated with the
total amount of discount. Zeroes are allowed but not spaces. (TC50 TCR00 (A) Pos 41-52) The total discount amount
applied to a transaction (i.e. total transaction percentage discounts, fixed transaction amount reductions or
summarization of line item discounts). Must not be all zeros if a discount amount exist, decimal placement follows
Transaction Amount currency. Must be all zeros if discount amount does not exist.

National Tax Included (VISA Purchase Card Addendum Record 3 (%3), Position 70, length 1) must be populated with
the European value added tax requirement. To qualify for LID/SUMM interchange this field must always be populated
with a '1'. (TC05 TCR06 Pos 30)
0 =Not subject to tax.

80 Byte Population Guide Page 156 of 216

Version 15.93
OmniPay Innovation in Transaction Management

1 =Subject to tax.

Item Descriptor (VISA Purchase Card Detail Addendum Record 1 (%4), Position 20, length 26) must be populated with
the description of the item purchased. Must be populated in order to obtain LID interchange (TC50 TCR00 (L) Pos 53-
78)

Quantity (VISA Purchase Card Detail Addendum Record 1 (%4), Position 46, length 12) must be populated with the
quantity of items purchased. Four decimal digits implied, must be numeric and non zero (TC50 TCR00 (L) Pos 91-102)

Unit of Measure Code (VISA Purchase Card Detail Addendum Record 1 (%4), Position 58, length 12) must be
populated with unit measure. Zeroes are allowed but not spaces (TC50 TCR00 (L) Pos 103-114) Must not be all
spaces or all zeros

Unit Cost (VISA Purchase Card Detail Addendum Record 2 (%5), Position 5, length 12) must be populated with unit
cost of item purchased. Zeroes are allowed but not spaces (TC50 TCR00 (L) Pos 115-126) Must not be all spaces or all
zeros

VAT/Tax rate (VISA Purchase Card Detail Addendum Record 2 (%5), Position 31, length 4) must be populated with rate
used to generate VAT. Non-US only. Zeroes are allowed but not spaces. 2 Decimal points implied (0090=9% rate)
(TC50 TCR00 (L) Pos 139-142)

Discount Per Line Item (VISA Purchase Card Detail Addendum Record 2 (%5), Position 47, length 12) must be numeric.
Zeroes are allowed but not spaces (TC50 TCR00 (L) Pos 143-154)

Line Item Total (VISA Purchase Card Detail Addendum Record 2 (%5), Position 59, length 12) must be numeric. Zeroes
are allowed but not spaces (TC50 TCR00 (L) Pos 155-166) This field is a calculation of the unit cost multiplied by the
quantity and less the discount per line item. The calculation is reflected as: [Unit Cost * Quantity] - Discount per Line
Item = Line Item Total. Must not be all spaces or all zeros, and last two digits are implied decimal places (if
Transaction Amount is a 2 decimal point currency). The Sum of all Line Item Totals for a transaction should equal the
Transaction Amount on the <1 field.

Sample Transaction for the above example:

06V4484450000000129 mmdd 863927T 5127943460 SIGMA-ALDRICH
06<1 000000028500036 GBRE1W 1YT 61-29841-0555
06<A mmdd 000000 61-29841-0555 0000000000000000000000000000000
06#1594 00000002841303600 596901
06#315127943460 000000 0000000000000
06%1321456987 00000000300000000000350009632587410 0010
06%2000000003000GB18150620 LID 0000000000007891236540
06%3000000002500GBRE1W 1YT000000002300GBRF2X 2ZUGBR000000005500 1
06%40000 DIRECT MARKETING PURCH 000000200000TPR
06%5000000120000 000000003500001022369852147 000000001300000000120000

22.2 Purchase VAT Rates

This section lists the information required to qualify for the Purchase VAT Incentive Interchange Rates in addition to
the setup for the card capture methods as outlined in the previous sections based on how these transactions are
captured either by Mail order, Telephone order, e-Commerce or at a POS terminal.

VISA
Customer Reference ID (VISA Commercial/Purchase Card Addendum Record 1 (%1), Position 56, length 17) must be
populated with Cardholder/customer data. Data will appear on customers statement. Zeroes are allowed but not
spaces (TC05 TCR06 Pos 111-127)

Purchase Identifier (Suppler Invoice Number) (VISA Commercial/Purchase Card Addendum Record 1 (%1), Position 5,
length 25) must be populated with merchant defined data (i.e., store number, register/terminal number, transaction
number, order number). (TC50TCR00(A) Pos 100-114)

80 Byte Population Guide Page 157 of 216

Version 15.93
OmniPay Innovation in Transaction Management

VAT rate for Freight/Shipping (VISA Commercial/Purchase Card Addendum Record 1 (%1), Position 72, length 4) must
be populated with VAT for the freight/shipping amount. Zeroes are allowed but not spaces. 2 Decimal points implied
(00090=9% rate) (TC50 TCR00 (A) Pos 152-155)

Item Commodity Code (VISA Commercial/Purchase Card Detail Addendum Record 1, Position 5, length 12) must be
populated with commodity code used to classify the item purchased. (TC50 TCR00 (L) Pos 41-52) The United Nations
Standard Products and Services Code (UNSPSC) is widely deployed.

National Tax (VISA Purchase Card Addendum Record 2 (%2), Position 5, length 12) must be populated with the
amount of national tax or value added tax. Non-US only. (TC05 TCR06 Pos 18-29)

Merchant VAT Registration (VISA Purchase Card Addendum Record 2 (%2), Position 17, length 20) must be populated
with Identification number assigned by the taxing authorities to the merchant. Where the National Tax Included is 1
then the Supplier VAT Reg. No. must not be all spaces if attempting to qualify at LID/SUMM interchange. (TC05 TCR06
Pos 31-50)

Summary Commodity Code (VISA Purchase Card Addendum Record 2 (%2), Position 50, length 4) must be populated
with the European value added tax requirement. Non-US only (TC05 TCR06 Pos 76-79)

Freight/Shipping Amount (VISA Purchase Card Addendum Record 3 (%3), Position 12, length 5) must be populated
with the freight amount on total purchase. Zeroes are allowed but not spaces. (TC50 TCR00 (A) Pos 53-64) The total
freight/shipping amount applied to a transaction. Merchants can choose to deliver the contents of a single transaction
in multiple shipments and this field reflects the total cost of those deliveries. Must not be all zeros if a freight/shipping
amount exists and last two digits are implied decimal places. Must be all zeros if freight/ shipping amount does not
exist.

National Tax Included (VISA Purchase Card Addendum Record 3 (%3), Position 70, length 1) must be populated with
the European value added tax requirement (TC05 TCR06 Pos 30)
0 =Not subject to tax.
1 =Subject to tax.

VAT/Tax rate (VISA Purchase Card Detail Addendum Record 2 (%5), Position 31, length 4) must be populated with rate
used to generate VAT. Non-US only. Zeroes are allowed but not spaces. 2 Decimal points implied (00090=9% rate)
(TC50 TCR00 (L) Pos 139-142)

Line Item Total (VISA Purchase Card Detail Addendum Record 2 (%5), Position 59, length 12) must be numeric (TC50
TCR00 (L) Pos 155-166) This field is a calculation of the unit cost multiplied by the quantity and less the discount per
line item. The calculation is reflected as: [Unit Cost * Quantity] - Discount per Line Item = Line Item Total. Must not be
all spaces or all zeros, and last two digits are implied decimal places.

Sample Transaction for the above example:

06V4484450000000145 mmdd 405869T 5127943460 SIGMA-ALDRICH
06<1 000000028413036 GBRE1W 1YT 61-29841-0555
06<A mmdd 000000 61-29841-0555 0000000000000000000000000000000
06#1594 00000002841303600 596901
06#315127943460 000000 0000000000000
06%1321456987 00000000300000000000350009632587410 0010
06%2000000003000GB18150620 SUMM000000000000
06%3000000000000 000000000000 000000000000 1
06%47464
06%5000000000000 0000000035000010 000000001200

80 Byte Population Guide Page 158 of 216

Version 15.93
OmniPay Innovation in Transaction Management

23 VISA CPS Rate Qualification

VISA domestic transactions in certain countries can qualify for VISA CPS rates. CPS rates are allowed in USA through
the Omnipay platform. This section lists the information required to qualify for the CPS Rates in addition to the setup
for the card capture methods as outlined in the previous sections based on how these transactions are captured
either by Mail order, Telephone order, e-Commerce or at a POS terminal.

US issued cards with a US merchant and the acquiring BIN domiciled in the US can qualify for the Visa CPS rates. If a
non-US issued card is used with a US merchant and the acquiring BIN domiciled in the US, the transaction will qualify
for the US Inter-regional rates.

CPS Passenger Transport programs can only be attained on consumer credit and debit issued US cards. Corporate and
Purchasing cards issued in the US can avail of the corporate and purchasing travel service programs provided the Airline
Itinerary Data is present in the 80 Byte file. Commercial cards cannot qualify for the CPS Passenger Transport rates but
would qualify for rates based on their capture methods.

Business, Signature Business, Business Enhanced cards issued in the US are not supported by any travel service
program, however if the Airline Addendum is populated on the 80 byte for one of these card brands, it is possible to
qualify for Business EIRF.

Airline transactions with non-US issued cards will achieve US INTR AIRLINE rate.

VISA
Sample transaction: Visa CPS Card Not Present Rate (Excl CPS Retail 2) (FPI Code 231)
06V4500040000000003 mmdd 083341T 34913852 EHARMONY
06<1 000000002995124
06<A0911715027 mmdd 001988 PASADENA CA 0000000000000000000000000000000
06<B34913852 0001
06#1594V0001 0000000029951240008YDDD3701754329999739901 G
06#3143407033 0000000000 000000 0000000000000

Sample transaction: Visa CPS Retail Key-Entry Rate (FPI Code 152)
06V4980000000000006 mmdd 002772 11101008 GUCCI #67
06<1 000000008620840NV USA89109 LAS VEGAS
06<A0911214121 mmdd 0000001392LAS VEGAS NV 0000000087820000001018773185815-05
06<B 020
06#1521K020 0000000087823920008YDDD3701754329999569901M
06#3 G000000 000000000000

Sample transaction: Visa CPS Retail Credit Rate (FPI Code 106)
06V4048660000000007 mmdd 218328 0461000607860 ROSS STORE #461
06<1 000000001383840
06<A mmdd 0000001710 0000000131040000000094750145702-05
06#1521E0006 0000000131047100008YDDD3701754329999533190
06#310461000607860 000000 000000013104

23.1 Visa CPS/Card Not Present MOTO

These transactions are similar to those discussed in 18.1 but are captured as Mail Order or Telephone order or non-
secure ecommerce transactions. These transactions would qualify for CPS card not present (FPI Code 133).

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

80 Byte Population Guide Page 159 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Authorization Date (Bankcard and T & E Detail Addendum Record A (<A), Position 15, Length 4), should be populated
in MMDD format. Purchase date should be within one day of authorization date.

Authorization Characteristics Indicator (VISA Detail Addendum Record 1 (#1), Position 8, Length 1) should be one of
the values listed below (TC05 TCR0 Pos 151)
V - Card not present. AVS required.
R - Card not present. AVS not required.

Authorization Source (VISA Detail Addendum Record 1 (#1), Position 5, Length 1), should not be spaces for CPS
transactions.

Transaction Identifier (VISA Detail Addendum Record 1 (#1), Position 31, Length 4) must be same as in the
Authorization Responses. (TC05 TCR5 Pos 5-19)
Positions 1 and 2 contain proprietary information used by Visa; position 3 contains the last digit of the current year;
positions 4 through 6 contain the Greenwich mean time (GMT) date (Julian date in the format YDDD); positions 7
through 11 contain the GMT in relative seconds since start of day; positions 12 through 15 contain a sequence
number.
Transaction ID is mandated for all Visa transactions where merchant country is USA, if this is not provided then the
acquirer is likely to incur Zero Floor Limit/Misuse of authorization Assessment Fee's.

Validation code (VISA Detail Addendum Record 1 (#1), Position 46, Length 4) this field must contain the
Validation Code received in the Authorization Response. For test purposes please use 9999.

Product ID (VISA Detail Addendum Record 1 (#1), Position 60, Length 2) must be populated. (TC05 TCR5 Pos 136-137).
The value is derived from the Base I authorization field 62.23 from Visa for Card Level Results

Merchant Category Code (VISA Detail Addendum Record 1 (#1), Position 50, Length 4): MCC must be present and
valid. (TC50 TCR0 Pos 133-136)

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must equal M or T. (TC05 TCR1 Pos 116)
M =Mail Order Transaction
T =Telephone Order Transaction

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
4 =Mail/Telephone or non-secure Electronic Commerce

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
01 =Key Entered card present or ecommerce transactions

AVS Response Code (VISA Detail Addendum Record 2 (#3), Position 32, Length 1) must be populated if ACI is V. (TC05
TCR1, Pos 127). The value is derived from the AVS field (BM44.2) in the authorization message for ISO8583 format.

Merchant City (Bankcard and T & E Detail Addendum Record A (<A), Position 29, Length 13) should be populated with
the merchant's Customer Service Telephone Number. For all MOTO transactions, the Telephone number must be left-
justified and contain three numeric values followed by a hyphen and at least seven more nonblank characters (XXX-
XXXXXXX). To qualify for the CPS/Card Not Present PSIRF, this field must contain a merchants customer service
Telephone number.

Product ID (VISA Detail Addendum Record 1 (#1), Position 60, Length 2) must be populated. (TC05 TCR5 Pos 136-137).
The value is derived from the Base I authorization field 62.23 from Visa for Card Level Results

Sample transaction: Capture Method Telephone (FPI Code 133)

06V4264980000000006 mmdd 484851T 10000149
06<1000000000000010000840
06<A mmdd000000 888-4521505 0000000000000000000000000
06<B

80 Byte Population Guide Page 160 of 216

Version 15.93
OmniPay Innovation in Transaction Management

06#1594V 000000010000840000002856578013069999490001N H
06#3 000000 0000000000000

Sample transaction: Capture Method Mail (FPI Code 183)

06V4267840000000009 mmdd 464018M 10000151
06<1000000000000010200840
06<A mmdd000000 888-4521505 0000000000000000000000000
06<B
06#1594R 000000010200840000002867578013069999490001N
06#3 000000 0000000000000

23.2 Visa CPS Recurring Transactions

These transactions are similar to those discussed in 18.1 but are captured as Recurring payments transactions. These
transactions would qualify for CPS card not present (FPI Code 133).

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Authorization Date (Bankcard and T & E Detail Addendum Record A (<A), Position 15, Length 4), should be populated
in MMDD format. Purchase date should be within one day of authorization date.

Authorization Characteristics Indicator (VISA Detail Addendum Record 1 (#1), Position 8, Length 1) should be one of
the values listed below (TC05 TCR0 Pos 151)
V - Card not present. AVS required.
R - Card not present. AVS not required.

Authorization Source (VISA Detail Addendum Record 1 (#1), Position 5, Length 1), should not be spaces for CPS
transactions.

Transaction Identifier (VISA Detail Addendum Record 1 (#1), Position 31, Length 4) must be same as in the
Authorization Responses. (TC05 TCR5 Pos 5-19)
Positions 1 and 2 contain proprietary information used by Visa; position 3 contains the last digit of the current year;
positions 4 through 6 contain the Greenwich mean time (GMT) date (Julian date in the format YDDD); positions 7
through 11 contain the GMT in relative seconds since start of day; positions 12 through 15 contain a sequence
number.
Transaction ID is mandated for all Visa transactions where merchant country is USA, if this is not provided then the
acquirer is likely to incur Zero Floor Limit/Misuse of authorization Assessment Fee's.

Validation code (VISA Detail Addendum Record 1 (#1), Position 46, Length 4) this field must contain the
Validation Code received in the Authorization Response. For test purposes please use 9999.

Product ID (VISA Detail Addendum Record 1 (#1), Position 60, Length 2) must be populated. (TC05 TCR5 Pos 136-137).
The value is derived from the Base I authorization field 62.23 from Visa for Card Level Results

Merchant Category Code (VISA Detail Addendum Record 1 (#1), Position 50, Length 4): MCC must be 4119, 4899,
4900, 5960, 5968, 5975, 5976, 5983,6300, 7277, 8011, 8021, 8031, 8041, 8042, 8043, 8049, 8050, 8062, 8071, 8099,
8211, 8220, 8299, 8351, 8398, 9211, 9222 and 9399 when ACI is R. (TC50 TCR0 Pos 133-136)

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space filled. (TC05 TCR1 Pos 116)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
4 =Mail/Telephone or non-secure Electronic Commerce

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
01 =Key Entered card present or ecommerce transactions

80 Byte Population Guide Page 161 of 216

Version 15.93
OmniPay Innovation in Transaction Management

AVS Response Code (VISA Detail Addendum Record 2 (#3), Position 32, Length 1) must be populated if ACI is V. (TC05
TCR1, Pos 127). The value is derived from the AVS field (BM44.2) in the authorization message for ISO8583 format.

Merchant City (Bankcard and T & E Detail Addendum Record A (<A), Position 29, Length 13) should be populated with
the merchant's Customer Service Telephone Number, URL or e-Mail address. For all MOTO transactions, the
Telephone number must be left-justified and contain three numeric values followed by a hyphen and at least seven
more nonblank characters (XXX-XXXXXXX). To qualify for the CPS/Card Not Present PSIRF, this field must contain a
merchants customer service Telephone number. URL or e-Mail address applicable for recurring transactions from
select MCCs (4812, 4814, 4899, 4900, 5960, 5968, 6300, 7298, 7997, 8675, and 8699)

Sample transaction: Capture Method Recurring, where first in series was MOTO transaction
06V4264980000000006 mmdd 484851 10000149
06<1000000000000010000840 YR
06<A mmdd000000 888-4521505 0000000000000000000000000
06<B
06#1594V 000000010000840000002856578013069999490001
06#3 000000 0000000000000

Sample transaction: Capture Method Recurring, where first in series was MOTO transaction
06V4264980000000006 mmdd 484851 10000149
06<1000000000000010000840 YR
06<A09117N1849 mmdd AMAZON.CO.UK TX 0000000000000000000000000000000
06<B
06#1594V 000000010000840000002856578013069999490001
06#3 000000 0000000000000

23.3 Visa CPS Electronic Commerce (basic)

These transactions are captured as non-secure ecommerce transactions. These transactions would qualify for CPS
Electronic Commerce Basic Credit (FPI Code 158) and CPS Electronic Commerce Basic Debit (FPI Code 186)

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Authorization Date (Bankcard and T & E Detail Addendum Record A (<A), Position 15, Length 4), should be populated
in MMDD format. Purchase date should be within one day of authorization date.

Authorization Characteristics Indicator (VISA Detail Addendum Record 1 (#1), Position 8, Length 1) should be one of
the values listed below (TC05 TCR0 Pos 151)
W - CPS/E-Commerce Basic (ECI is 7). AVS is required.

Authorization Source (VISA Detail Addendum Record 1 (#1), Position 5, Length 1), should not be spaces for CPS
transactions.

Transaction Identifier (VISA Detail Addendum Record 1 (#1), Position 31, Length 4) must be same as in the
Authorization Responses. (TC05 TCR5 Pos 5-19)
Positions 1 and 2 contain proprietary information used by Visa; position 3 contains the last digit of the current year;
positions 4 through 6 contain the Greenwich mean time (GMT) date (Julian date in the format YDDD); positions 7
through 11 contain the GMT in relative seconds since start of day; positions 12 through 15 contain a sequence
number.
Transaction ID is mandated for all Visa transactions where merchant country is USA, if this is not provided then the
acquirer is likely to incur Zero Floor Limit/Misuse of authorization Assessment Fee's.

Validation code (VISA Detail Addendum Record 1 (#1), Position 46, Length 4) this field must contain the
Validation Code received in the Authorization Response. For test purposes please use 9999.

80 Byte Population Guide Page 162 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Product ID (VISA Detail Addendum Record 1 (#1), Position 60, Length 2) must be populated. (TC05 TCR5 Pos 136-137).
The value is derived from the Base I authorization field 62.23 from Visa for Card Level Results

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) for Visa must be as follows.
(TC05 TCR1 Pos 116)
7 =the cardholders payment card was protected with a form of internet security, such as SSL, but
authentication was not performed.

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
4 =Mail/Telephone or non-secure Electronic Commerce

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
01 =Key Entered card present or ecommerce transactions

AVS Response Code (VISA Detail Addendum Record 2 (#3), Position 32, Length 1) must be populated if ACI is V or W.
(TC05 TCR1, Pos 127). The value is derived from the AVS field (BM44.2) in the authorization message for ISO8583
format.

Merchant City (Bankcard and T & E Detail Addendum Record A (<A), Position 29, Length 13) should be populated with
the merchant's Customer Service Telephone Number, URL or e-Mail address. For all ecommerce transactions where
the ECI is 5, 6 or 7 or the MCC is 4816, this field must contain a URL or an email address. The field edits do not require
'www.' to precede the URL address.

Sample transaction: Visa CPS Electronic Basic Rate (FPI Code 158)
06V4217660000000002 mmdd 006211 743474035 NCIC OPERATOR SVCS
06<1 000000000547124TX USA75601 8003822887
06<A09117N1849 mmdd AMAZON.CO.UK TX 0000000000000000000000000000000
06#1594W 0000000005471240008YDDD370175432999939901 H
06#312843474006 8003822887 000000 0000000000000

23.4 Visa CPS/E-Commerce Preferred

These transactions are captured in an ecommerce environment and are secure authenticated. These transactions
would qualify for CPS/E-Commerce Preferred (FPI code 162, 187)

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Authorization Date (Bankcard and T & E Detail Addendum Record A (<A), Position 15, Length 4), should be populated
in MMDD format. Purchase date should be within one day of authorization date.

Authorization Characteristics Indicator (VISA Detail Addendum Record 1 (#1), Position 8, Length 1) should be one of
the values listed below (TC05 TCR0 Pos 151)
U - Card not present3-D Secure Electronic Commerce (ECI is 5)
S - Electronic Commerce 3-D Secure Attempts (ECI is 6) Visa Consumer Card only.

Authorization Source (VISA Detail Addendum Record 1 (#1), Position 5, Length 1), should not be spaces for CPS
transactions.

Transaction Identifier (VISA Detail Addendum Record 1 (#1), Position 31, Length 4) must be same as in the
Authorization Responses. (TC05 TCR5 Pos 5-19)
Positions 1 and 2 contain proprietary information used by Visa; position 3 contains the last digit of the current year;
positions 4 through 6 contain the Greenwich mean time (GMT) date (Julian date in the format YDDD); positions 7
through 11 contain the GMT in relative seconds since start of day; positions 12 through 15 contain a sequence
number.

80 Byte Population Guide Page 163 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Transaction ID is mandated for all Visa transactions where merchant country is USA, if this is not provided then the
acquirer is likely to incur Zero Floor Limit/Misuse of authorization Assessment Fee's.

Validation code (VISA Detail Addendum Record 1 (#1), Position 46, Length 4) this field must contain the
Validation Code received in the Authorization Response. For test purposes please use 9999.

Product ID (VISA Detail Addendum Record 1 (#1), Position 60, Length 2) must be populated. (TC05 TCR5 Pos 136-137).
The value is derived from the Base I authorization field 62.23 from Visa for Card Level Results

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) for Visa must be as follows.
(TC05 TCR1 Pos 116)
5 =the cardholder was authenticated using a Visa-approved authentication methodology. The
authorization message was successfully authenticated by Verified by Visa. ***Full VbV transaction****
6 =the merchant is capable of and attempted to authenticate the cardholder using Verified by Visa, but
the cardholder did not participate.

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
4 =Mail/Telephone or Electronic Commerce

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
01 =Key Entered card present or ecommerce transactions

Merchant City (Bankcard and T & E Detail Addendum Record A (<A), Position 29, Length 13) should be populated with
the merchant's Customer Service Telephone Number, URL or e-Mail address. For all ecommerce transactions where
the ECI is 5, 6 or 7 or the MCC is 4816, this field must contain a URL or an email address. The field edits do not require
'www.' to precede the URL address.

AVS Response Code (VISA Detail Addendum Record 2 (#3), Position 32, Length 1) must be populated. (TC05 TCR1, Pos
127). The value is derived from the AVS field (BM44.2) in the authorization message for ISO8583 format.
Sample transaction: Visa CPS Electronic Commerce (Preferred) Rate (FPI Code 162)
06V4028560000000003 mmdd 245214 629386689 RES BOOKINGADVISOR COM
06<1 000000013975840
06<A09117N1849 mmdd AMAZON.CO.UK TX 0000000000000000000000000000000
06#1594S 0000001115673440008YDDD3701754329999472201
06#3129386689 000000 000000111567

Sample transaction: Visa CPS Electronic Commerce (Preferred) Rate (FPI Code 187)
06V mmdd 152119 5 10000152
06<1000000000000010400840
06<A09117N1849 mmdd AMAZON.CO.UK TX 0000000000000000000000000000000
06<E4266070000000000008 00000000000000090000000000000000000000000
06#1594U 000000010400840000002868578013069999490001N
06#3 000000 0000000000000

23.5 Visa CPS/Passenger Transport: Card Present

At present we currently support Airline Addendum Records for Visa on the 80 byte and Visa supports specific CPS
interchange rates such as CPS Passenger Transport rates only available within the U.S. region. This section lists the
Airline itinerary information that should be submitted in addition to those outlined in the previous sections for various
captured methods such as card present transactions at a POS terminal.

Please note that only the consumer cards can qualify for the Passenger Transport rates and commercial cards with the
airline itinerary data will qualify for the Business EIRF rates, or Corporate/Purchasing Travel Service Programs. If
multiple tickets are purchased in a single payment and if this payment is submitted as multiple clearing transactions
with the same card number and authorization code then all these transactions should be submitted together in a

80 Byte Population Guide Page 164 of 216

Version 15.93
OmniPay Innovation in Transaction Management

sequence on the 80 byte settlement file. These transactions will then be cleared on the Visa Base II file in the same
sequence with the sequence number and sequence count details included. Multiple clearing messages are identified
by the ticket sequence number and count.

These transactions would qualify for CPS Passenger Transport Debit Rate (FPI Code 191) and CPS Passenger Transport
Credit Rate (FPI Code 103)

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Authorization Date (Bankcard and T & E Detail Addendum Record A (<A), Position 15, Length 4), should be populated
in MMDD format. Purchase date should be within one day of authorization date.

Authorization Characteristics Indicator (VISA Detail Addendum Record 1 (#1), Position 8, Length 1) should be one of
the values listed below (TC05 TCR0 Pos 151)
A - Card present.
E - Card present with merchant name and location data.

Authorization Source (VISA Detail Addendum Record 1 (#1), Position 5, Length 1), should not be spaces for CPS
transactions.

Transaction Identifier (VISA Detail Addendum Record 1 (#1), Position 31, Length 4) must be same as in the
Authorization Responses. (TC05 TCR5 Pos 5-19)
Positions 1 and 2 contain proprietary information used by Visa; position 3 contains the last digit of the current year;
positions 4 through 6 contain the Greenwich mean time (GMT) date (Julian date in the format YDDD); positions 7
through 11 contain the GMT in relative seconds since start of day; positions 12 through 15 contain a sequence
number.
Transaction ID is mandated for all Visa transactions where merchant country is USA, if this is not provided then the
acquirer is likely to incur Zero Floor Limit/Misuse of authorization Assessment Fee's.

Validation code (VISA Detail Addendum Record 1 (#1), Position 46, Length 4) this field must contain the
Validation Code received in the Authorization Response. For test purposes please use 9999.

Product ID (VISA Detail Addendum Record 1 (#1), Position 60, Length 2) must be populated. (TC05 TCR5 Pos 136-137).
The value is derived from the Base I authorization field 62.23 from Visa for Card Level Results

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) for Visa must be space filled.
(TC05 TCR1 Pos 116)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
1 =Signature for card present transactions
2 =PIN for card present transactions

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
05 =Card data was chip read and data is reliable. POS Terminal Capability should be set to a 5.
90 =Full contents of the magnetic stripe read and sent. Track 1 or 2.

AVS Response Code (VISA Detail Addendum Record 2 (#3), Position 32, Length 1) maybe populated, its optional.
(TC05 TCR1, Pos 127). The value is derived from the AVS field (BM44.2) in the authorization message for ISO8583
format.

Merchant Category Code (VISA Detail Addendum Record 1 (#1), Position 50, Length 4): MCC must be 3000-3299 or
4511. (TC50 TCR0 Pos 133-136)

80 Byte Population Guide Page 165 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Number of Trip Legs (Visa Passenger Itinerary General Detail Addendum Record 1 (#4), Position 5, Length 2): This
value must contain the number of legs per transaction. Must contain value greater than 00 and less than or equal to
04. Must not be space filled.

Passenger Name (Visa Passenger Itinerary General Detail Addendum Record 1 (#4), Position 7, and Length 20): The
passenger name should be a valid left justified string with trailing spaces. (TCR 3, 27-46)

Departure Date (Visa Passenger Itinerary General Detail Addendum Record 1 (#4), Position 27, and Length 6): The
date should be of the format MMDDYY or it may contain zeroes. Date can be in future. (TCR 3, 47-52)

Origin City (Visa Passenger Itinerary General Detail Addendum Record 1 (#4), Position 33, Length 3): The originating
airport names standard abbreviation. This should not contain all spaces or zeroes. (TCR 3, 53-55)

Ticket Number (Visa Passenger Itinerary General Detail Addendum Record 2 (#5), Position 5, Length 15): The number
on the ticket. (TCR0 104-116)

Trip Leg Data: (This data must be populated for Trip Leg 1, and it is best practise to provide data for each trip leg)

Carrier Code (Visa Passenger Trip Leg Specific Detail Addendum Record (#6), Position 5, length 2, Per Trip Leg):
Contains the standard abbreviation for the airline carrier issuing the ticket. This should not contain all spaces or
zeroes. (TCR 3, 56-57)

Service Class (Visa Passenger Trip Leg Specific Detail Addendum Record (#6), Position 7, length 1, Per Trip Leg): The
service type (for example, coach or first class). This should not be a space or zero. (TCR 3, 58)

Stopover Code (Visa Passenger Trip Leg Specific Detail Addendum Record (#6), Position 8, length 1, Per Trip Leg): The
entry must be a space, O, or X for all trip legs. (TCR 3, 59)
O =Stopover allowed
X =Stopover not allowed

Destination City (Visa Passenger Trip Leg Specific Detail Addendum Record (#6), Position 9, length 3, Per Trip Leg):
Destination City Airport Code. This should not contain all spaces or zeroes. (TCR 3, 60-62)

23.6 Visa CPS/Passenger Transport: Card Not Present

These transactions are similar to those discussed in 18.1 but are captured as Mail Order or Telephone order or non-
secure ecommerce transactions. These transactions would qualify for CPS Passenger Transport Debit Rate (FPI Code
191) and CPS Passenger Transport (FPI Code 103)

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Authorization Date (Bankcard and T & E Detail Addendum Record A (<A), Position 15, Length 4), should be populated
in MMDD format. Purchase date should be within one day of authorization date..

Authorization Characteristics Indicator (VISA Detail Addendum Record 1 (#1), Position 8, Length 1) should be one of
the values listed below (TC05 TCR0 Pos 151)
V - Card not present. AVS is required.
P - Card not present (Preferred Customer participation requested). AVS not required
W - PS/E-Commerce Basic (ECI is 7). AVS may be required.

Authorization Source (VISA Detail Addendum Record 1 (#1), Position 5, Length 1), should not be spaces for CPS
transactions.

80 Byte Population Guide Page 166 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Transaction Identifier (VISA Detail Addendum Record 1 (#1), Position 31, Length 4) must be same as in the
Authorization Responses. (TC05 TCR5 Pos 5-19)
Positions 1 and 2 contain proprietary information used by Visa; position 3 contains the last digit of the current year;
positions 4 through 6 contain the Greenwich mean time (GMT) date (Julian date in the format YDDD); positions 7
through 11 contain the GMT in relative seconds since start of day; positions 12 through 15 contain a sequence
number.
Transaction ID is mandated for all Visa transactions where merchant country is USA, if this is not provided then the
acquirer is likely to incur Zero Floor Limit/Misuse of authorization Assessment Fee's.

Validation code (VISA Detail Addendum Record 1 (#1), Position 46, Length 4) this field must contain the
Validation Code received in the Authorization Response. For test purposes please use 9999.

Product ID (VISA Detail Addendum Record 1 (#1), Position 60, Length 2) must be populated. (TC05 TCR5 Pos 136-137).
The value is derived from the Base I authorization field 62.23 from Visa for Card Level Results

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) for Visa must be as follows.
(TC05 TCR1 Pos 116)
7 =the cardholders payment card was protected with a form of internet security, such as SSL, but
authentication was not performed.
OR
MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must equal M or T. (TC05 TCR1 Pos 116)
M =Mail Order Transaction
T =Telephone Order Transaction

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
4 =Mail/Telephone or non-secure Electronic Commerce

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
01 =Key Entered card present or ecommerce transactions

Merchant City (Bankcard and T & E Detail Addendum Record A (<A), Position 42, Length 13) should be populated with
the merchant's Customer Service Telephone Number. For all MOTO transactions, the Telephone number must be left-
justified and contain three numeric values followed by a hyphen and at least seven more nonblank characters (XXX-
XXXXXXX). To qualify for the CPS/Card Not Present PSIRF, this field must contain a merchants customer service
Telephone number. (TC05 TCR0 Pos 117-129)

AVS Response Code (VISA Detail Addendum Record 2 (#3), Position 32, Length 1) must be populated if ACI is V or W
(TC05 TCR1, Pos 127). The value is derived from the AVS field (BM44.2) in the authorization message for ISO8583
format.

Merchant Category Code (VISA Detail Addendum Record 1 (#1), Position 50, Length 4): MCC must be 3000-3299 or
4511. (TC50 TCR0 Pos 133-136)

Ticket Number (Visa Passenger Itinerary General Detail Addendum Record 2 (#5), Position 5, Length 15): The number
on the ticket. (TCR0 104-116)

Passenger Name (Visa Passenger Itinerary General Detail Addendum Record 1 (#4), Position 7, and Length 20): The
passenger name should be a valid left justified string with trailing spaces. (TCR 3, 27-46)

Departure Date (Visa Passenger Itinerary General Detail Addendum Record 1 (#4), Position 27, and Length 6): The
date should be of the format MMDDYY or it may contain zeroes. Date can be in future. (TCR 3, 47-52)

Origin City (Visa Passenger Itinerary General Detail Addendum Record 1 (#4), Position 33, Length 3): The originating
airport names standard abbreviation. This should not contain all spaces or zeroes. (TCR 3, 53-55)

80 Byte Population Guide Page 167 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Number of Trip Legs (Visa Passenger Itinerary General Detail Addendum Record 1 (#4), Position 5, Length 2): This
value must contain the number of legs per transaction. Must contain value greater than 00 and less than or equal to
04. Must not be space filled.

Trip Leg Data: (Trip Leg Data for First Leg must be populated. Second and subsequent legs should be populated as best
practise)

Carrier Code (Visa Passenger Trip Leg Specific Detail Addendum Record (#6), Position 5, length 2, Per Trip Leg):
Contains the standard abbreviation for the airline or railway carrier issuing the ticket. This should not contain all
spaces or zeroes. (TCR 3, 56-57)

Service Class (Visa Passenger Trip Leg Specific Detail Addendum Record (#6), Position 7, length 1, Per Trip Leg): The
service type (for example, coach or first class). This should not be a space or zero. (TCR 3, 58)

Stopover Code (Visa Passenger Trip Leg Specific Detail Addendum Record (#6), Position 8, length 1, Per Trip Leg): The
entry must be a space, O, or X for all trip legs. (TCR 3, 59)
O =Stopover allowed
X =Stopover not allowed

Destination City (Visa Passenger Trip Leg Specific Detail Addendum Record (#6), Position 9, length 3, Per Trip Leg):
Destination City Airport Code. This should not contain all spaces or zeroes. (TCR 3, 60-62)

Sample transaction: Visa CPS Passenger Transport Debit Rate (FPI Code 191)
06V4803560000000004 mmdd 654321 7101PRODECI7D33VIR ATL
06<1 000000031606978CT USA06850 NORWALK
06<A09117N1849 mmdd 190-12345598 TX 0000000000000000000000000000000
06#1504W 000000031700USD 08YDDD3701754329999314401
06#31F4FL34 Y000000 0000000031700
06#404HEMLIN/KAYLA LOUISE 051409DFW91266313EGENCIA UK LTD
06#50863537085575
06#6VSKXLAXKOWSPU VSKXAKLKOWSPU VSKOADLKOWSPU

23.7 Visa CPS/E-Commerce Preferred: Passenger Transport

These transactions are similar to those discussed in 18.1 but these transactions are captured in an ecommerce
environment and are secure authenticated. These transactions would qualify for CPS/E-Commerce Preferred -
Passenger Transport (FPI code 168 (Credit Rate), 192 (Debit Rate)).

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Authorization Date (Bankcard and T & E Detail Addendum Record A (<A), Position 15, Length 4), should be populated
in MMDD format. Purchase date should be within one day of authorization date.

Authorization Characteristics Indicator (VISA Detail Addendum Record 1 (#1), Position 8, Length 1) should be one of
the values listed below (TC05 TCR0 Pos 151)
U - Card not present3-D Secure Electronic Commerce (ECI is 5)
S - Electronic Commerce 3-D Secure Attempts (ECI is 6) Visa Consumer Card only.

Authorization Source (VISA Detail Addendum Record 1 (#1), Position 5, Length 1), should not be spaces for CPS
transactions.

Transaction Identifier (VISA Detail Addendum Record 1 (#1), Position 31, Length 4) must be same as in the
Authorization Responses. (TC05 TCR5 Pos 5-19)
Positions 1 and 2 contain proprietary information used by Visa; position 3 contains the last digit of the current year;
positions 4 through 6 contain the Greenwich mean time (GMT) date (Julian date in the format YDDD); positions 7

80 Byte Population Guide Page 168 of 216

Version 15.93
OmniPay Innovation in Transaction Management

through 11 contain the GMT in relative seconds since start of day; positions 12 through 15 contain a sequence
number.
Transaction ID is mandated for all Visa transactions where merchant country is USA, if this is not provided then the
acquirer is likely to incur Zero Floor Limit/Misuse of authorization Assessment Fee's.

Validation code (VISA Detail Addendum Record 1 (#1), Position 46, Length 4) this field must contain the
Validation Code received in the Authorization Response. For test purposes please use 9999.

Product ID (VISA Detail Addendum Record 1 (#1), Position 60, Length 2) must be populated. (TC05 TCR5 Pos 136-137).
The value is derived from the Base I authorization field 62.23 from Visa for Card Level Results

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) for Visa must be as follows.
(TC05 TCR1 Pos 116)
5 =the cardholder was authenticated using a Visa-approved authentication methodology. The
authorization message was successfully authenticated by Verified by Visa. ***Full VbV transaction****
6 =the merchant is capable of and attempted to authenticate the cardholder using Verified by Visa,
but the cardholder did not participate.

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
4 =Mail/Telephone or Electronic Commerce

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
01 =Key Entered card present or ecommerce transactions

Merchant City (Bankcard and T & E Detail Addendum Record A (<A), Position 29, Length 13) should be populated with
the merchant's Customer Service Telephone Number, URL or e-Mail address. For all ecommerce transactions where
the ECI is 5, 6 or 7 or the MCC is 4816, this field must contain a URL or an email address. The field edits do not require
'www.' to precede the URL address.

AVS Response Code (VISA Detail Addendum Record 2 (#3), Position 32, Length 1) must be populated. (TC05 TCR1, Pos
127). The value is derived from the AVS field (BM44.2) in the authorization message for ISO8583 format..

Merchant Category Code (VISA Detail Addendum Record 1 (#1), Position 50, Length 4): MCC must be 3000-3299 or
4511. (TC50 TCR0 Pos 133-136)

Ticket Number (Visa Passenger Itinerary General Detail Addendum Record 2 (#5), Position 5, Length 15): The number
on the ticket. (TCR0 104-116)

Passenger Name (Visa Passenger Itinerary General Detail Addendum Record 1 (#4), Position 7, and Length 20): The
passenger name should be a valid left justified string with trailing spaces. (TCR 3, 27-46)

Departure Date (Visa Passenger Itinerary General Detail Addendum Record 1 (#4), Position 27, and Length 6): The
date should be of the format MMDDYY or it may contain zeroes. Date can be in future. (TCR 3, 47-52)

Origin City (Visa Passenger Itinerary General Detail Addendum Record 1 (#4), Position 33, Length 3): The originating
airport names standard abbreviation. This should not contain all spaces or zeroes. (TCR 3, 53-55)

Number of Trip Legs (Visa Passenger Itinerary General Detail Addendum Record 1 (#4), Position 5, Length 2): This
value must contain the number of legs per transaction. Must contain value greater than 00 and less than or equal to
04. Must not be space filled.

Trip Leg Data: (These fields must be populated on the trip leg addendum record for first trip leg, and is best practise
for second and subsequent trip legs)

Carrier Code (Visa Passenger Trip Leg Specific Detail Addendum Record (#6), Position 5, length 2, Per Trip Leg):
Contains the standard abbreviation for the airline or railway carrier issuing the ticket. This should not contain all
spaces or zeroes. (TCR 3, 56-57)

80 Byte Population Guide Page 169 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Service Class (Visa Passenger Trip Leg Specific Detail Addendum Record (#6), Position 7, length 1, Per Trip Leg): The
service type (for example, coach or first class). This should not be a space or zero. (TCR 3, 58)

Stopover Code (Visa Passenger Trip Leg Specific Detail Addendum Record (#6), Position 8, length 1, Per Trip Leg): The
entry must be a space, O, or X for all trip legs. (TCR 3, 59)
O =Stopover allowed
X =Stopover not allowed

Destination City (Visa Passenger Trip Leg Specific Detail Addendum Record (#6), Position 9, length 3, Per Trip Leg):
Destination City Airport Code. This should not contain all spaces or zeroes. (TCR 3, 60-62)

Sample transaction: Visa CPS Passenger Transport Debit Rate (FPI Code 191)
06V4002090000000001 mmdd 111111 5101PRODECI7D33VIR ATL
06<1 000000031606978CT USA06850 NORWALK
06<A09117N1849 mmdd AMAZON.CO.UK TX 0000000000000000000000000000000
06#1504U 000000031700USD 08YDDD3701754329999314401
06#31F4FL34 Y000000 0000000031700
06#402DEMEO/ALESSANDRA 050509EWR 1
06#593221533762733
06#6VSUOLHRUBP 18 VSUOEWRUBP 17

Sample transaction: Visa CPS Passenger Transport Rate (FPI Code 103)
06V4002510000000008 mmdd 111111 6101PRODECI7D33VIR ATL
06<1 000000031606978CT USA06850 NORWALK
06<A09117N1849 mmdd AMAZON.CO.UK TX 0000000000000000000000000000000
06#1504S 000000031700USD 08YDDD3701754329999314401
06#31F4FL34 Y000000 0000000031700
06#402DEMEO/ALESSANDRA 050509EWR 1
06#593221533762733
06#6VSUOLHRUBP 18 VSUOEWRUBP 17

23.8 Visa CPS/Hotel and Car Rental: Card Present

At present we dont currently support Car Rental Addendum Records for Visa on the 80 byte but we do have fields
within the 80 byte to populate different criteria for Car Rental Transactions. Visa supports specific CPS interchange
rates such as CPS Car Rental/Hotel only available within the U.S. region. This section lists the Hotel/Car Rental
information that should be submitted in addition to those outlined in the previous sections for various captured
methods such as at a POS terminal.

These transactions would qualify for CPS Car Rental/Hotel Card Present (FPI code 132, 188).

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Authorization Date (Bankcard and T & E Detail Addendum Record A (<A), Position 15, Length 4), should be populated
in MMDD format. Purchase date should be within one day of authorization date.

Authorization Characteristics Indicator (VISA Detail Addendum Record 1 (#1), Position 8, Length 1) should be one of
the values listed below (TC05 TCR0 Pos 151)
A - Card present.
E - Card present with merchant name and location data.

Authorization Source (VISA Detail Addendum Record 1 (#1), Position 5, Length 1), should not be spaces for CPS
transactions.

80 Byte Population Guide Page 170 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Transaction Identifier (VISA Detail Addendum Record 1 (#1), Position 31, Length 4) must be same as in the
Authorization Responses. (TC05 TCR5 Pos 5-19)
Positions 1 and 2 contain proprietary information used by Visa; position 3 contains the last digit of the current year;
positions 4 through 6 contain the Greenwich mean time (GMT) date (Julian date in the format YDDD); positions 7
through 11 contain the GMT in relative seconds since start of day; positions 12 through 15 contain a sequence
number.
Transaction ID is mandated for all Visa transactions where merchant country is USA, if this is not provided then the
acquirer is likely to incur Zero Floor Limit/Misuse of authorization Assessment Fee's.

Validation code (VISA Detail Addendum Record 1 (#1), Position 46, Length 4) this field must contain the
Validation Code received in the Authorization Response. For test purposes please use 9999.

Product ID (VISA Detail Addendum Record 1 (#1), Position 60, Length 2) must be populated. (TC05 TCR5 Pos 136-137).
The value is derived from the Base I authorization field 62.23 from Visa for Card Level Results

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) for Visa must be space filled.
(TC05 TCR1 Pos 116)

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
1 =Signature for card present transactions
2 =PIN for card present transactions

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
05 =Card data was chip read and data is reliable. POS Terminal Capability should be set to a 5.
90 =Full contents of the magnetic stripe read and sent. Track 1 or 2.

AVS Response Code (VISA Detail Addendum Record 2 (#3), Position 32, Length 1) maybe populated, its optional.
(TC05 TCR1, Pos 127). The value is derived from the AVS field (BM44.2) in the authorization message for ISO8583
format.

Merchant Category Code (VISA Detail Addendum Record 1 (#1), Position 50, Length 4): MCC must be 3351-3500,
7512, 7513 or 7519 for Car Rental or 3501-3999 or 7011 for Hotel. (TC50 TCR0 Pos 133-136)

Purchase Identifier Indicator (VISA Detail Addendum Record 2 (#3), Position 5, Length 1) must be as follows. (TC 05
TCR 4 pos 51-58)
3 =Rental Agreement Number (Car Rental)
4 =Hotel Folio Number (Hotel)

Market Specific Auth Indicator (VISA Detail Addendum Record 2 (#3), Position 31, Length 1) must be as follows. (TC 05
TCR 5 pos 49)
H =Hotel
A =Auto

Check in Date (VISA Detail Addendum Record 2 (#3), Position 33, Length 6) Car Rental pick up date in the format
YYMMDD. No show or prepay =scheduled pick up date. (TC 05 TCR 3 pos 38-43)

Extra Charges (VISA Detail Addendum Record 2 (#3), Position 39, Length 6) Additional charges added to customer
bill after check-out. Each position can be used to indicate a type of charge. See below for the values of extra charges.
No extra charges =Space filled. (TC 05 TCR 3 pos 28-33)
1 =Gas
2 =Extra Mileage
3 =Late Return
4 =1 Way Ser Fee
5 =Parking Violation

80 Byte Population Guide Page 171 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Total Authorised Amount (VISA Detail Addendum Record 2 (#3), Position 46, Length 12) For Hotel/Car Rental
transactions this amount should be the total authorized amount. (TC 05 TCR 5 pos 50-61)

Sample transaction: Visa CPS Car Rental Hotel CNP Rate (FPI Code 115)

23.9 Visa CPS/Hotel and Car Rental: Card Not Present

These transactions are similar to those discussed in 18.4 but these transactions are captured as Mail order, Telephone
order etc. These transactions would qualify for CPS Car Rental Hotel CNP (FPI code 115, 189).

VISA
Authorization Date (Bankcard and T & E Detail Addendum Record A (<A), Position 15, Length 4), should be populated
in MMDD format. Purchase date should be within one day of authorization date.

Authorization Characteristics Indicator (VISA Detail Addendum Record 1 (#1), Position 8, Length 1) should be one of
the values listed below (TC05 TCR0 Pos 151)
P - Card not present (Preferred Customer participation requested)

Authorization Source (VISA Detail Addendum Record 1 (#1), Position 5, Length 1), should not be spaces for CPS
transactions.

Transaction Identifier (VISA Detail Addendum Record 1 (#1), Position 31, Length 4) must be same as in the
Authorization Responses. (TC05 TCR5 Pos 5-19)
Positions 1 and 2 contain proprietary information used by Visa; position 3 contains the last digit of the current year;
positions 4 through 6 contain the Greenwich mean time (GMT) date (Julian date in the format YDDD); positions 7
through 11 contain the GMT in relative seconds since start of day; positions 12 through 15 contain a sequence
number.
Transaction ID is mandated for all Visa transactions where merchant country is USA, if this is not provided then the
acquirer is likely to incur Zero Floor Limit/Misuse of authorization Assessment Fee's.

Validation code (VISA Detail Addendum Record 1 (#1), Position 46, Length 4) this field must contain the
Validation Code received in the Authorization Response. For test purposes please use 9999.

Product ID (VISA Detail Addendum Record 1 (#1), Position 60, Length 2) must be populated. (TC05 TCR5 Pos 136-137).
The value is derived from the Base I authorization field 62.23 from Visa for Card Level Results

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) for Visa must be as follows.
(TC05 TCR1 Pos 116)
7 =the cardholders payment card was protected with a form of internet security, such as SSL, but
authentication was not performed.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must equal M or T. (TC05 TCR1 Pos 116)
M =Mail Order Transaction
T =Telephone Order Transaction

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
4 =Mail/Telephone or non-secure Electronic Commerce

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
01 =Key Entered card present or ecommerce transactions

Merchant City (Bankcard and T & E Detail Addendum Record A (<A), Position 29, Length 13) should be populated with
the merchant's Customer Service Telephone Number, URL or e-Mail address. For all MOTO transactions, the
Telephone number must be left-justified and contain three numeric values followed by a hyphen and at least seven
more nonblank characters (XXX-XXXXXXX). To qualify for the CPS/Card Not Present PSIRF, this field must contain a
merchants customer service Telephone number. For all ecommerce transactions where the ECI is 5, 6 or 7 or the MCC

80 Byte Population Guide Page 172 of 216

Version 15.93
OmniPay Innovation in Transaction Management

is 4816, this field must contain a URL or an email address. The field edits do not require 'www.' to precede the URL
address.

AVS Response Code (VISA Detail Addendum Record 2 (#3), Position 32, Length 1) must be populated. (TC05 TCR1, Pos
127). The value is derived from the AVS field (BM44.2) in the authorization message for ISO8583 format.

Merchant Category Code (VISA Detail Addendum Record 1 (#1), Position 50, Length 4): MCC must be 3351-3500,
7512, 7513 or 7519 for Car Rental or 3501-3999 or 7011 for Hotel. (TC50 TCR0 Pos 133-136)

Purchase Identifier Indicator (VISA Detail Addendum Record 2 (#3), Position 5, Length 1) must be as follows. (TC 05
TCR 4 pos 51-58)
3 =Rental Agreement Number (Car Rental)
4 =Hotel Folio Number (Hotel)

Market Specific Auth Indicator (VISA Detail Addendum Record 2 (#3), Position 31, Length 1) must be as follows. (TC 05
TCR 5 pos 49)
H =Hotel
A =Auto

Check in Date (VISA Detail Addendum Record 2 (#3), Position 33, Length 6) Car Rental pick up date in the format
YYMMDD. No show or prepay =scheduled pick up date. (TC 05 TCR 3 pos 38-43)

Extra Charges (VISA Detail Addendum Record 2 (#3), Position 39, Length 6) Additional charges added to customer
bill after check-out. Each position can be used to indicate a type of charge. See below for the values of extra charges.
No extra charges =Space filled. (TC 05 TCR 3 pos 28-33)
1 =Gas
2 =Extra Mileage
3 =Late Return
4 =1 Way Ser Fee
5 =Parking Violation

Total Authorised Amount (VISA Detail Addendum Record 2 (#3), Position 46, Length 12) For Hotel/Car Rental
transactions this amount should be the total authorized amount. (TC 05 TCR 5 pos 50-61)

Sample transaction: Visa CPS Car Rental Hotel CNP Rate (FPI Code 115)
06V4835190000000002 mmdd 083003 64954438 AVIS RENT-A-CAR
06<1 000000003432840CA USA94128 SAN FRANCISCO
06<A09117N1849 mmdd AMAZON.CO.UK TX 0000000000000000000000000000000
06<B 090B
06#1504P 000000031700USD 08YDDD3701754329999338901
06#3364954438 A 090421 0000000027398

23.10 Visa CPS/E-Commerce Preferred: Hotel & Car Rental

These transactions are similar to those discussed in 18.5 but these transactions are captured in an ecommerce
environment and are secure authenticated. These transactions would qualify for CPS/E-Commerce Preferred - Hotel &
Car Rental (FPI code 169, 190).

VISA
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Authorization Date (Bankcard and T & E Detail Addendum Record A (<A), Position 15, Length 4), should be populated
in MMDD format. Purchase date should be within one day of authorization date.

Authorization Characteristics Indicator (VISA Detail Addendum Record 1 (#1), Position 8, Length 1) should be one of
the values listed below (TC05 TCR0 Pos 151)
U - Card not present3-D Secure Electronic Commerce (ECI is 5)

80 Byte Population Guide Page 173 of 216

Version 15.93
OmniPay Innovation in Transaction Management

S - Electronic Commerce 3-D Secure Attempts (ECI is 6) Visa Consumer Card only.

Authorization Source (VISA Detail Addendum Record 1 (#1), Position 5, Length 1), should not be spaces for CPS
transactions.

Transaction Identifier (VISA Detail Addendum Record 1 (#1), Position 31, Length 4) must be same as in the
Authorization Responses. (TC05 TCR5 Pos 5-19)
Positions 1 and 2 contain proprietary information used by Visa; position 3 contains the last digit of the current year;
positions 4 through 6 contain the Greenwich mean time (GMT) date (Julian date in the format YDDD); positions 7
through 11 contain the GMT in relative seconds since start of day; positions 12 through 15 contain a sequence
number.
Transaction ID is mandated for all Visa transactions where merchant country is USA, if this is not provided then the
acquirer is likely to incur Zero Floor Limit/Misuse of authorization Assessment Fee's.

Validation code (VISA Detail Addendum Record 1 (#1), Position 46, Length 4) this field must contain the
Validation Code received in the Authorization Response. For test purposes please use 9999.

Product ID (VISA Detail Addendum Record 1 (#1), Position 60, Length 2) must be populated. (TC05 TCR5 Pos 136-137).
The value is derived from the Base I authorization field 62.23 from Visa for Card Level Results

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) for Visa must be as follows.
(TC05 TCR1 Pos 116)
5 =the cardholder was authenticated using a Visa-approved authentication methodology. The
authorization message was successfully authenticated by Verified by Visa. ***Full VbV transaction****
6 =the merchant is capable of and attempted to authenticate the cardholder using Verified by Visa, but
the cardholder did not participate.

Cardholder ID (VISA Detail Addendum Record 1 (#1), Position 7, Length 1) must be as follows. (TC05 TCR0 Pos 160)
4 =Mail/Telephone or Electronic Commerce

POS Entry Mode (VISA Detail Addendum Record 1 (#1), Position 54, Length 2) must be as follows. (TC05 TCR0 Pos 162-
163)
01 =Key Entered card present or ecommerce transactions

Merchant City (Bankcard and T & E Detail Addendum Record A (<A), Position 29, Length 13) should be populated with
the merchant's Customer Service Telephone Number, URL or e-Mail address. For all ecommerce transactions where
the ECI is 5, 6 or 7 or the MCC is 4816, this field must contain a URL or an email address. The field edits do not require
'www.' to precede the URL address.

AVS Response Code (VISA Detail Addendum Record 2 (#3), Position 32, Length 1) must be populated. (TC05 TCR1, Pos
127). The value is derived from the AVS field (BM44.2) in the authorization message for ISO8583 format.

Merchant Category Code (VISA Detail Addendum Record 1 (#1), Position 50, Length 4): MCC must be 3351-3500,
7512, 7513 or 7519 for Car Rental or 3501-3999 or 7011 for Hotel. (TC50 TCR0 Pos 133-136)

Purchase Identifier Indicator (VISA Detail Addendum Record 2 (#3), Position 5, Length 1) must be as follows. (TC 05
TCR 4 pos 51-58)
3 =Rental Agreement Number (Car Rental)
4 =Hotel Folio Number (Hotel)

Market Specific Auth Indicator (VISA Detail Addendum Record 2 (#3), Position 31, Length 1) must be as follows. (TC 05
TCR 5 pos 49)
H =Hotel
A =Auto

Check in Date (VISA Detail Addendum Record 2 (#3), Position 33, Length 6) Car Rental pick up date in the format
YYMMDD. No show or prepay =scheduled pick up date. (TC 05 TCR 3 pos 38-43)

80 Byte Population Guide Page 174 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Extra Charges (VISA Detail Addendum Record 2 (#3), Position 39, Length 6) Additional charges added to customer
bill after check-out. Each position can be used to indicate a type of charge. See below for the values of extra charges.
No extra charges =Space filled. (TC 05 TCR 3 pos 28-33)
1 =Gas
2 =Extra Mileage
3 =Late Return
4 =1 Way Ser Fee
5 =Parking Violation

Total Authorised Amount (VISA Detail Addendum Record 2 (#3), Position 46, Length 12) For Hotel/Car Rental
transactions this amount should be the total authorized amount. (TC 05 TCR 5 pos 50-61)

80 Byte Population Guide Page 175 of 216

Version 15.93
OmniPay Innovation in Transaction Management

24 JCB (Japan Credit Bureau) Transactions

This section outlines the fields and records that need to be populated on the 80 byte file to submit JCB transactions.
JCB cards use the BIN range of 352800-358999 and clearing files are generated for JCB transactions. Interchange rates
for JCB are setup independently for each acquirer but this section outlines the fields required for various capture
methods supported. Luhn Check validation is carried out on the card numbers similar to Visa and MasterCard at
Modulus 10.

Following fields are optional and if they are left space filled, transactions shouldnt reject and should just be assigned a
terminal capability of Manual and a capture method of Manual
POS Terminal Capability (<K, Pos 25)
Cardholder ID (<K, Pos 26)
PAN Entry Mode (<K, Pos 23-24)

Non-Secure Ecommerce Transaction

These are ecommerce transactions where the Ecommerce transactions originated from merchants not participating in
3D secure.

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response message.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) for JCB must be Space Filled.

POS Terminal capability (JCB Compliance Detail Record 1(<K), Position 25, length 1) must be 9.
9 =Key entered (no card reader available)

Cardholder ID (JCB Compliance Detail Record 1 (<K), Position 26, length 1) must be '4'.
4 =Mail/Telephone or Electronic Commerce

PAN Entry Mode (JCB Compliance Detail Record 1 (<K), Position 23, length 2) must be '81'.
81 =Electronic Commerce

Sample transaction: Capture Method eCommerce, Channel Encrypt

06J352800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06<K1109091520089999 8194

Secure Ecommerce Transaction

These are authenticated and non authenticated ecommerce transactions where the merchant and the issuer are
participating in JCBs JSecure program, which offers enhanced security to shop online with the JCB card. This is
similar to the 3D secure authentication for MasterCard and Verified by Visa (VbV) for Visa.

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) for JCB must equal 5, 6, or
7
5 =Secure authenticated transaction
6 =Merchant attempted to receive Secure authentication, and authentication failed due to Issuer or
cardholder non-participation for Secure
7 =Unauthenticated Secured Transaction.

80 Byte Population Guide Page 176 of 216

Version 15.93
OmniPay Innovation in Transaction Management

POS Terminal capability (JCB Compliance Detail Record 1 (<K) (<K), Position 25, length 1) must be 9
9 =Key entered (no card reader available)

Cardholder ID (JCB Compliance Detail Record 1 (<K) (<K), Position 26, length 1) must be '4'.
4 =Mail/Telephone or Electronic Commerce

PAN Entry Mode (JCB Compliance Detail Record 1 (<K) (<K), Position 23, length 2) must be '81'.
81 =Electronic Commerce

Sample transaction: Capture Method - SET/3D-SET authenticated

06J352800xxxxxxxxxx 727782 5POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06<K1109091520089999 8194

Sample transaction: Capture Method - SET/3D-SET non-authenticated

06J352800xxxxxxxxxx 727782 6POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06<K1109091520089999 8194

Sample transaction: Capture Method - eCommerce, Channel Encrypt

06J352800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06<K1109091520089999 8194

Note : On transactions with ECI 7(Auths) these are Unauthenticated Secured transactions, ECI on the 80byte should be
space filled, Entry mode is 81 indicating these are Ecom transactions originated from merchants not participating in
3Dsecure.

MOTO
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must equal M or T.
M =Mail Order Transaction
T =Telephone Order Transaction

POS Terminal capability (JCB Compliance Detail Record 1 (<K), Position 25, length 1) must be 9.
9 =Key entered (no card reader available)

Cardholder ID (JCB Compliance Detail Record 1 (<K), Position 26, length 1) must be '4'.
4 =Mail/Telephone or Electronic Commerce

POS Entry Mode (JCB Compliance Detail Record 1 (<K) (<K), Position 23, length 2) must be '01'. ( Data Record
Format1 Pos 46-47, Data Record Format4 Pos 225-226, Data Record Format1 Pos 46-47)
01 =Key entered.

Sample transaction: Capture Method Mail Order

06J352800xxxxxxxxxx 727782M POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06<K1109091520089999 0194

80 Byte Population Guide Page 177 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Recurring
These transactions are authorised as Recurring transactions, a recurring flag exists for the authorisations. However,
no such flag exists on the clearing side. Transactions will clear to the scheme as per capture of the transaction i.e. a
Moto or Ecommerce transaction etc for both First in Series and Subsequent in series. Transactions will qualify at
Ecom or Base rates.
(First transaction in Series)
Interchange Program Qualification Flag (Bankcard and T & E Detail Record 1, Position 58 (<1), length 1) must be
space filled

Recurring Transaction Flag (Bankcard and T & E Detail Record 1, Position 59 (<1), length 1) must be Space filled

Sample Transaction for the above example: JCB Secure eCom transaction as first in series
06J352800xxxxxxxxxx 727782 5POSI0709080000
06<1000000000000040000978 GBR LONDON
06<A 0402000000 0000000000000000000000000
06<B
06<K1109091520089999 8194

Sample Transaction for the above example: JCB Mail Order transaction as first in series
06J352800xxxxxxxxxx 727782M POSI0709080000
06<1000000000000040000978 GBR LONDON
06<A 0402000000 0000000000000000000000000
06<B
06<K1109091520089999 0194

Recurring (Subsequent transactions in Series)

Interchange Program Qualification Flag (Bankcard and T & E Detail Record 1, Position 58 (<1), length 1) must be
space filled

Recurring Transaction Flag (Bankcard and T & E Detail Record 1, Position 59 (<1), length 1) must be Space filled

Sample Transaction for the above example: JCB Secure eCom transaction as subsequent in series
06J352800xxxxxxxxxx 727782 5POSI0709080000
06<1000000000000040000978 GBR LONDON
06<A 0402000000 0000000000000000000000000
06<B
06<K1109091520089999 8194

Sample Transaction for the above example: JCB Mail Order transaction as Subsequent in series
06J352800xxxxxxxxxx 727782M POSI0709080000
06<1000000000000040000978 GBR LONDON
06<A 0402000000 0000000000000000000000000
06<B
06<K1109091520089999 0194

Manual Cash Disbursements

Merchant Category Code (JCB Compliance Detail Record 1 (<K) (<K), Position 17, length 4): MCC must be 6010. (Data
Record Format1 Pos 156-159, Data Record Format12 Pos 156-159)

Sample transaction: Capture Method - Cust. present, key-entry

06J352800xxxxxxxxxx 727782 POSI0709080000
06<1000000000000010101826 GBR LONDON NN
06<A 0320000000 0000000000000000000000000
06<B
06<K1109091520086010 0194

80 Byte Population Guide Page 178 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Quasi Cash Transaction

Transaction Date (JCB Compliance Detail Record 1 (<K) (<K), Position 9, length 8) in MMDDYYYY format is mandatory.
(Data Record Format1 Pos 8-15, Data Record Format2 Pos 8-15, Data Record Format4 Pos 157-164, Data Record
Format12 Pos 8-15 )

Merchant Category Code (JCB Compliance Detail Record 1 (<K) (<K), Position 17, length 4): MCC must be 4829, 6051
or 7995. (Data Record Format1 Pos 156-159, Data Record Format12 Pos 156-159)

Sample transaction: Capture Method - Cust. present, key-entry

06J352800xxxxxxxxxx 727782 POSI0709080000
06<1000000000000010101826 GBR LONDON NN
06<A 0320000000 0000000000000000000000000
06<B
06<K1109091520086051 0194

Airline Transaction
Airline addendum record is dropped from the clearing file if any of the mandatory details are not provided for airline
transactions but the transaction is not front end rejected.

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Charge Description (Bankcard and T & E Detail Record, Position 56, length 25) should have the DBA name populated.
For airline MCCs other than 4511, the DBA name should be the shortened version. Typically this contains the
abbreviated Airline and it should not exceed first nine positions.
V I R A T L
Ticket number should NOT be populated in the charge description field. Charge Description field should be space
filled if a merchant has decided to use the DBA Name from the Merchant Master File.

Merchant Category Code (JCB Compliance Detail Record 1 (<K) (<K), Position 17, length 4): MCC must be 3000-3299
or 4511. (Data Record Format1 Pos 156-159, Data Record Format12 Pos 156-159)

Card Expiration Date (JCB Compliance Detail Record 1 (<K) (<K), Position 5, length 4) in MMYY format is mandatory for
airline transactions. (Data Record Format2 Pos 41-44, Data Record Format4 Pos 26-29)

Passenger Name (JCB Passenger Itinerary General Detail Addendum Record 1 (<L), Position 32, and Length 26): The
passenger name should be a valid left justified string with trailing spaces. All Spaces not allowed. (Data Record
Format4 Pos 64-89)

Departure Date (JCB Passenger Itinerary General Detail Addendum Record 1 (<L), Position 68, and Length 8): The date
should be of the format MMDDYYYY or it may contain zeroes. Date can be in future. (Data Record Format4 Pos
163-170)

Ticket Identifier (JCB Passenger Itinerary General Detail Addendum Record 1 (<L), Position 13, and Length 19): The
number on the ticket. All Spaces not allowed. (Data Record Format4 Pos 45-63)

Travel Agent Code (JCB Passenger Itinerary General Detail Addendum Record 1 (<L), Position 5, and Length 8): An
entry should be supplied if a travel agency issued the ticket. Mandatory, All Spaces not allowed. (Data Record
Format4 Pos 33-40)

City of Destination (JCB Passenger Itinerary General Detail Addendum Record 1 (<L), Position 65, and Length 3)
Destination City Airport Code. All Spaces not allowed. (Data Record Format4 Pos 160-162)

Trip leg details:

Routing (JCB Passenger Itinerary General Detail Addendum Record 1 (<L), Position 5, and Length 70) contains the
passenger itinerary. At least one flight information should be included and this cant have any spaces. Up to 10
iterations are allowed in this field. (Data Record Format2 Pos 90-159)

80 Byte Population Guide Page 179 of 216

Version 15.93
OmniPay Innovation in Transaction Management

S1 3Bytes: Official city/airport code where a stopover is made.

S2 2Bytes: Airline Service Class.
S3 2Bytes: Official Ticketing Carrier Code.

Sample transaction: Capture Method - SET/3D-SET non-authenticated

06J352800xxxxxxxxxx 727782 6POSI0709080000
06<1000000000000010101826 GBR LONDON NN
06<A 0320000000 0000000000000000000000000
06<B
06<K1109091520083144 0194
06<LBUTVL011952314708996354 MURPHY MR.X LAXBCVA 12202008
06<MLONKAVS

Attended Card present Manual Entry

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

POS Terminal capability (JCB Compliance Detail Record 1 (<K) (<K), Position 25, length 1) must be 9.
9 =Key entered (no card reader available)

Cardholder ID (JCB Compliance Detail Record 1 (<K), Position 26, length 1) must be as follows.
Undefined =space filled

PAN Entry Mode (JCB Compliance Detail Record 1 (<K), Position 23, length 2) must be '01'.
01 =Manual

Sample transaction: Capture Method - Cust. present, key-entry

06J352800xxxxxxxxxx 727782 POSI0709080000
06<1000000000000010101826 GBR LONDON
06<A 0320000000 0000000000000000000000000
06<B
06<K1109091520085999 019

Attended Card present Magnetic Stripe Signature Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

POS Terminal capability (JCB Compliance Detail Record 1 (<K), Position 25, length 1) must be 2.
2 =Magnetic stripe capable

Cardholder ID (JCB Compliance Detail Record 1 (<K), Position 26, length 1) must be as follows.
1 =Signature

PAN Entry Mode (JCB Compliance Detail Record 1 (<K), Position 23, length 2) should be '02 or '97''.

02 =Magstripe read
97 =Magstripe read after the attempted processing using data on chip.

Sample transaction: Capture Method Card swiped, signature

06J352800xxxxxxxxxx 727782 POSI0709080000
06<1000000000000010101826 GBR LONDON

80 Byte Population Guide Page 180 of 216

Version 15.93
OmniPay Innovation in Transaction Management

06<A 0320000000 0000000000000000000000000

06<B
06<K1109091520085999 0221

Attended Card present Magnetic Stripe PIN Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.
MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.
Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

POS Terminal capability (JCB Compliance Detail Record 1 (<K), Position 25, length 1) must be 2
2 =Magnetic stripe capable

Cardholder ID (JCB Compliance Detail Record 1 (<K), Position 26, length 1) must be as follows.
2 =PIN

PAN Entry Mode (JCB Compliance Detail Record 1 (<K), Position 23, length 2) should be '05' or '97'. (Data Record
Format1 Pos 46-47, Data Record Format4 Pos 225-226, Data Record Format1 Pos 46-47)
97 =Magstripe read after the attempted processing using data on chip.
02 =Magstripe read

Sample transaction: Capture Method Card swiped, PIN

06J352800xxxxxxxxxx 727782 POSI0709080000
06<1000000000000010101826 GBR LONDON
06<A 0320000000 0000000000000000000000000
06<B
06<K1109091520085999 9722

Attended Card present Chip Signature Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

POS Terminal capability (JCB Compliance Detail Record 1 (<K), Position 25, length 1) must be 5.
5 =Chip read capable

Cardholder ID (JCB Compliance Detail Record 1 (<K), Position 26, length 1) must be 1.
1 =Signature

Pan Entry Mode (JCB Compliance Detail Record 1 (<K), Position 23, length 2) must be '05'. (Data Record Format1 Pos
46-47, Data Record Format4 Pos 225-226, Data Record Format1 Pos 46-47)
05 =Card data was chip read and data is reliable. POS Terminal Capability should be set to a 5 (ICC capable).

Sample transaction: Capture Method Chip read, signature

06J352800xxxxxxxxxx 727782 POSI0709080000
06<1000000000000010101826 GBR LONDON
06<A 0320000000 0000000000000000000000000
06<B
06<K1109091520085999 0551

Attended Card present Chip PIN Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

80 Byte Population Guide Page 181 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

POS Terminal capability (JCB Compliance Detail Record 1 (<K), Position 25, length 1) must be 5.
5 =Chip read capable

Cardholder ID (JCB Compliance Detail Record 1 (<K), Position 26, length 1) must be 2.
2 =PIN

Pan Entry Mode (JCB Compliance Detail Record 1 (<K), Position 23, length 2) must be '05'. (Data Record Format1 Pos
46-47, Data Record Format4 Pos 225-226, Data Record Format1 Pos 46-47)
05 =Card data was chip read and data is reliable. POS Terminal Capability should be set to a 5 (ICC capable).

Sample transaction: Capture Method Chip initiated the transaction

06J352800xxxxxxxxxx 727782 POSI0709080000
06<1000000000000010101826 GBR LONDON
06<A 0320000000 0000000000000000000000000
06<B
06<K1109091520085999 0552

Attended Card present EMV Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

POS Terminal capability (JCB Compliance Detail Record 1 (<K), Position 25, length 1) must be 5.
5 =Chip read capable

Cardholder ID (JCB Compliance Detail Record 1 (<K), Position 26, length 1) must be as follows.
2 =PIN

Pan Entry Mode (JCB Compliance Detail Record 1 (<K), Position 23, length 2) must be '05'. (Data Record Format1 Pos
46-47, Data Record Format4 Pos 225-226, Data Record Format1 Pos 46-47)
05 =Card data was chip read and data is reliable. POS Terminal Capability should be set to a 5.

Sample transaction: Capture Method Chip initiated the transaction

06J352800xxxxxxxxxx 727782 POSI0709080000
06<1000000000000010101826 GBR LONDON
06<A 0320000000 0000000000000000000000000
06<B
06<K1109091520085999 0552
06@1001090628E0B8C0826826A0000000031010 00195C000000008000008C
06@2000000004250 BA12640EFC2CBB124000002409230250162ADB98A6000000000000
06@306020A0364BC00 0041030222

80 Byte Population Guide Page 182 of 216

Version 15.93
OmniPay Innovation in Transaction Management

25 Diners/Discover Transactions
This section outlines the fields and records that need to be populated on the 80 byte file to submit Diners/Discover
transactions. All the Diners/Discover transactions should be submitted with a card brand of D in order to be
recognised as an Diners/Discover transaction. Diners dont distinguish between Card Types (consumer, commercial)
and Diners interchange isnt determined by the terminal capability and mode of capture of the transaction. BIN ranges
can be 14-16 digits long. All Diners cards begin 36 and are 14 digits in length. All Discover cards begin with a 6 and are
16 digits in length. Luhn Check validation is carried out on the card numbers similar to Visa and MasterCard at
Modulus 10.

BIN range for Diners/Discover is as follows:

360000 369999 Diners
601100 601109 Discover
601120 601149 Discover
601174 601174 Discover
601177 601179 Discover
601186 601199 Discover
644000 649999 Discover
650000 659999 Discover

We have implement new fields on the 80 byte (these will be on the updated Diners Addendum Record 1, <D record)
that will enable us determine the capture method and terminal capability of each transaction. Please note that the
new fields are optional fields. If they are left space filled, transactions wouldnt reject and would be assigned a
terminal capability of Manual and a capture method of Manual. The new fields are:
POS Terminal Capability (<D, Pos 64)
Cardholder ID (<D, Pos 65)
POS Entry Mode (<D, Pos 66)
Diners Mobile POS Indicator(<D, Pos 70)

Non-Secure Ecommerce Transaction

These are non-secure ecommerce transactions where the merchant and the issuer are not participating in Diners
'ProtectBuy program, which offers enhanced security to shop online with the Diners Club card.

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response message.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) for Diners must be space
filled.

POS Terminal capability (Diners Club Addendum Record 1 (<D), Position 64, length 1) must be 9.
9 =Key entered (no card reader available)

Cardholder ID (Diners Club Addendum Record 1 (<D), Position 65, length 1) must be '4'.
4 =Mail/Telephone or Electronic Commerce

80 Byte Population Guide Page 183 of 216

Version 15.93
OmniPay Innovation in Transaction Management

POS Entry Mode (Diners Club Addendum Record 1 (<D), Position 66, length 2) must be as follows
TI =Acquired via the Internet (for sale/purchase transactions)
TJ =Credit to a TI charge (for refunds from a sale/purchase transaction)

Diners Action Code (Diners Club Addendum Record 1 (<D), Position 68, length 2) must be populated with value from
Auth- Xpress DE 39

Sample transaction: Capture Method - eCommerce, Channel Encrypt

06D362800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06<D11125999 0000000000000094TI00
k
07D362800xxxxxxxxxx 727782 POSI0709080000
07<1 000002004000840
07<A 0323000000 0000000000000000000000000
07<B
07<D11125999 0000000000000094TJ00

Secure Ecommerce Transaction

These are secure ecommerce transactions where the merchant and the issuer are participating in Diner's 'ProtectBuy
program, which offers enhanced security to shop online with the Diners Club card. This is similar to the 3D secure
authentication for MasterCard and Verified by Visa (VbV) for Visa.

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) for Diners must equal 5 or
6.
5 =the cardholder was authenticated using a Visa-approved authentication methodology. The
authorization message was successfully authenticated.
6 =the merchant is capable of and attempted to authenticate the cardholder using J Secure, but the
cardholder did not participate.
7 =the cardholders payment card was protected with a form of internet security, such as SSL, but
authentication was not performed.
8 =the cardholders payment card was NOT protected with a form of internet security, such as SSL and
authentication was not performed

POS Terminal capability (Diners Club Addendum Record 1 (<D), Position 64, length 1) must be 9.
9 =Key entered (no card reader available)

Cardholder ID (Diners Club Addendum Record 1 (<D), Position 65, length 1) must be '4'.they /
4 =Mail/Telephone or Electronic Commerce

POS Entry Mode (Diners Club Addendum Record 1 (<D), Position 66, length 2) must be as follows
TI - Acquired via the Internet (for sale/purchase transactions)
TJ - Credit to a TI charge (for refunds from a sale/purchase transaction)
Diners Action Code (Diners Club Addendum Record 1 (<D), Position 68, length 2) must be populated with value from
Auth- Xpress DE 39

Sample transaction: Capture Method - SET/3D-SET authenticated

06D362800xxxxxxxxxx 727782 5POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06<D11125999 0000000000000094TI

80 Byte Population Guide Page 184 of 216

Version 15.93
OmniPay Innovation in Transaction Management

07D362800xxxxxxxxxx 727782 5POSI0709080000

07<1 000002004000840
07<A 0323000000 0000000000000000000000000
07<B
07<D11125999 0000000000000094TJ

Sample transaction: Capture Method - SET/3D-SET non-authenticated

06D362800xxxxxxxxxx 727782 6POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06<D11125999 0000000000000094TI

07D362800xxxxxxxxxx 727782 6POSI0709080000

07<1 000002004000840
07<A 0323000000 0000000000000000000000000
07<B
07<D11125999 0000000000000094TJ

Sample transaction: Capture Method - eCommerce, Channel Encrypt

06D362800xxxxxxxxxx 727782 7POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06<D11125999 0000000000000094TI

07D362800xxxxxxxxxx 727782 7POSI0709080000

07<1 000002004000840
07<A 0323000000 0000000000000000000000000
07<B
07<D11125999 0000000000000094TJ

Sample transaction: Capture Method -

06D362800xxxxxxxxxx 727782 8POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06<D11125999 0000000000000094TI

07D362800xxxxxxxxxx 727782 8POSI0709080000

07<1 000002004000840
07<A 0323000000 0000000000000000000000000
07<B
07<D11125999 0000000000000094TJ

MOTO
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must equal M or T.
M =Mail Order Transaction
T =Telephone Order Transaction

POS Terminal capability (Diners Club Addendum Record 1 (<D), Position 64, length 1) must be 9.
9 =Key entered (no card reader available)

Cardholder ID (Diners Club Addendum Record 1 (<D), Position 65, length 1) must be '4'.
4 =Mail/Telephone or Electronic Commerce

80 Byte Population Guide Page 185 of 216

Version 15.93
OmniPay Innovation in Transaction Management

POS Entry Mode (Diners Club Addendum Record 1 (<D), Position 66, length 2) must be as follows
TD - Acquired with paper back-up (for sale/purchase transactions)
TF=Credit to a TD charge (for refunds from a sale/purchase transaction)

Diners Action Code (Diners Club Addendum Record 1 (<D), Position 68, length 2) must be populated with value from
Auth- Xpress DE 39

Sample transaction: Capture Method Mail Order

06D362800xxxxxxxxxx 727782M POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06<D11125999 0000000000000094TD00

07D362800xxxxxxxxxx 727782M POSI0709080000

07<1 000002004000840
07<A 0323000000 0000000000000000000000000
07<B
07<D11125999 0000000000000094TF00

Sample transaction: Capture Method Telephone Order

06D362800xxxxxxxxxx 727782T POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06<D11125999 0000000000000094TD
00
06D362800xxxxxxxxxx 727782T POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06<D11125999 0000000000000094TF

Recurring (First transaction in Series)

Interchange Program Qualification Flag (Bankcard and T & E Detail Record 1, Position 58 (<1), length 1)
Should be space-filled

Recurring Transaction Flag (Bankcard and T & E Detail Record 1, Position 59 (<1), length 1)
Should be space-filled

Diners Action Code (Diners Club Addendum Record 1 (<D), Position 68, length 2) must be populated with value from
Auth- Xpress DE 39

Sample Transaction for the above example: Secure eCom transaction as first in series
06D362800xxxxxxxxxx 727782 5POSI0709080000
06<1000000000000040000978 GBR LONDON
06<A 0323000000 0000000000000000000000000
06<B
06<D11125999 0000000000000094TI

Recurring (Subsequent transactions in Series)

Interchange Program Qualification Flag (Bankcard and T & E Detail Record 1, Position 58 (<1), length 1) must equal
Y.
Y =Qualifies for RT rate Participation (VAU enabled or VAU authenticated)
N =Recurring rate is NOT sought

Recurring Transaction Flag (Bankcard and T & E Detail Record 1, Position 59 (<1), length 1) must equal to R.

80 Byte Population Guide Page 186 of 216

Version 15.93
OmniPay Innovation in Transaction Management

R =Recurring transaction, subsequent transactions in a series

POS Entry Mode (Diners Club Addendum Record 1 (<D), Position 66, length 2) must be as follows
TD=Acquired with paper back-up (for sale/purchase transactions)
TF=Credit to a TD charge (for refunds from a sale/purchase transaction)

Diners Action Code (Diners Club Addendum Record 1 (<D), Position 68, length 2) must be populated with value from
Auth- Xpress DE 39

Sample Transaction for the above example: transaction as recurring in series

06D362800xxxxxxxxxx 727782 7POSI0709080000
06<1000000000000040000978 GBR LONDON YR
06<A 0323000000 0000000000000000000000000
06<B
06<D11125999 0000000000000094TD

07D362800xxxxxxxxxx 727782 7POSI0709080000

07<1000000000000040000978 GBR LONDON YR
07<A 0323000000 0000000000000000000000000
07<B
07<D11125999 0000000000000094TF

Manual Cash Disbursements

Merchant Category Code (Diners Club Addendum Record 1 (<D), Position 9, length 4): MCC must be 6010.
Diners Action Code (Diners Club Addendum Record 1 (<D), Position 68, length 2) must be populated with value from
Auth- Xpress DE 39

Sample transaction: Capture Method - Cust. present, key-entry

06D362800xxxxxxxxxx 727782 POSI0709080000
06<1000000000000040000978 GBR LONDON
06<A 0323000000 0000000000000000000000000
06<B
06<D11126010 0000000000000094TD

Quasi Cash Transaction

Merchant Category Code (Diners Club Addendum Record 1 (<D), Position 9, length 4): MCC must be 4829, 6051 or
7995.
Diners Action Code (Diners Club Addendum Record 1 (<D), Position 68, length 2) must be populated with value from
Auth- Xpress DE 39

Sample transaction: Capture Method - Cust. present, key-entry

06D362800xxxxxxxxxx 727782 POSI0709080000
06<1000000000000040000978 GBR LONDON
06<A 0323000000 0000000000000000000000000
06<B
06<D11126051 0000000000000094TD

Attended Card present Manual Entry

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

POS Terminal capability (Diners Club Addendum Record 1 (<D), Position 64, length 1) must be 9.
9 =Key entered (no card reader available)

80 Byte Population Guide Page 187 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Cardholder ID (Diners Club Addendum Record 1 (<D), Position 65, length 1) must be as follows
Space - Undefined

POS Entry Mode (Diners Club Addendum Record 1 (<D), Position 66, length 2) must be as follows
TD - Acquired with paper back-up (for sale/purchase transactions)
TF - Credit to a TD charge (for refunds from a sale/purchase transaction)
Diners Action Code (Diners Club Addendum Record 1 (<D), Position 68, length 2) must be populated with value from
Auth- Xpress DE 39

Sample transaction: Capture Method - Cust. present, key-entry

06D362800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06<D11125999 000000000000009 TD

07D362800xxxxxxxxxx 727782 POSI0709080000

07<1 000002004000840
07<A 0323000000 0000000000000000000000000
07<B
07<D11125999 000000000000009 TF

Attended Card present Magnetic Stripe Signature Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

POS Terminal capability (Diners Club Addendum Record 1 (<D), Position 64, length 1) must be 2.
2 =Magnetic stripe capable

Cardholder ID (Diners Club Addendum Record 1 (<D), Position 65, length 1) must be as follows.
1 =Signature

POS Entry Mode (Diners Club Addendum Record 1 (<D), Position 66, length 2) must be as follows
TE - Acquired Electronically (for sale/purchase transactions)
TG - Credit to a TE charge (for refunds from a sale/purchase transaction)

Diners Action Code (Diners Club Addendum Record 1 (<D), Position 68, length 2) must be populated with value from
Auth- Xpress DE 39

Sample transaction: Capture Method Card swiped, signature

06D362800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06<D11125999 0000000000000021TE

07D362800xxxxxxxxxx 727782 POSI0709080000

07<1 000002004000840
07<A 0323000000 0000000000000000000000000
07<B
07<D11125999 0000000000000021TG

Attended Card present Magnetic Stripe PIN Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.
80 Byte Population Guide Page 188 of 216

Version 15.93
OmniPay Innovation in Transaction Management

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

POS Terminal capability (Diners Club Addendum Record 1 (<D), Position 64, length 1) must be 2.
2 =Magnetic stripe capable

Cardholder ID (Diners Club Addendum Record 1 (<D), Position 65, length 1) must be as follows.
2 - PIN

POS Entry Mode (Diners Club Addendum Record 1 (<D), Position 66, length 2) must be as follows
TE - Acquired Electronically (for sale/purchase transactions)
TG - Credit to a TE charge (for refunds from a sale/purchase transaction)

Diners Action Code (Diners Club Addendum Record 1 (<D), Position 68, length 2) must be populated with value from
Auth- Xpress DE 39

Sample transaction: Capture Method Card swiped, PIN

06D362800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06<D11125999 0000000000000022TE

07D362800xxxxxxxxxx 727782 POSI0709080000

07<1 000002004000840
07<A 0323000000 0000000000000000000000000
07<B
07<D11125999 0000000000000022TG

Attended Card present Chip Signature Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

POS Terminal capability (Diners Club Addendum Record 1, Position 64, length 1) must be 5.
5 =Chip read capable

Cardholder ID (Diners Club Addendum Record 1, Position 65, length 1) must be as follows.
1 =Signature

POS Entry Mode (Diners Club Addendum Record 1, Position 66, length 2) must be as follows
TK =Acquired with ICC data (for sale/purchase transactions)
TL =Credit to a TK charge (for refunds from a sale/purchase transaction)

Diners Action Code (Diners Club Addendum Record 1 (<D), Position 68, length 2) must be populated with value from
Auth- Xpress DE 39

Sample transaction: Capture Method Chip read, signature

06D362800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06<D11125999 0000000000000051TK

80 Byte Population Guide Page 189 of 216

Version 15.93
OmniPay Innovation in Transaction Management

07D362800xxxxxxxxxx 727782 POSI0709080000

07<1 000002004000840
07<A 0323000000 0000000000000000000000000
07<B
07<D11125999 0000000000000051TL

Attended Card present Chip PIN Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

POS Terminal capability (Diners Club Addendum Record 1, Position 64, length 1) must be 5.
5 =Chip read capable

Cardholder ID (Diners Club Addendum Record 1, Position 65, length 1) must be as follows.
2 =PIN

POS Entry Mode (Diners Club Addendum Record 1, Position 66, length 2) must be as follows
TK =Acquired with ICC data (for sale/purchase transactions)
TL =Credit to a TK charge (for refunds from a sale/purchase transaction)

Diners Action Code (Diners Club Addendum Record 1 (<D), Position 68, length 2) must be populated with value from
Auth- Xpress DE 39

Sample transaction: Capture Method Chip initiated the transaction

06D362800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06<D11125999 0000000000000052TK

07D362800xxxxxxxxxx 727782 POSI0709080000

07<1 000002004000840
07<A 0323000000 0000000000000000000000000
07<B
07<D11125999 0000000000000052TL

Attended Card present EMV Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

POS Terminal capability (Diners Club Addendum Record 1, Position 64, length 1) must be 5.
5 =Chip read capable

Cardholder ID (Diners Club Addendum Record 1, Position 65, length 1) must be as follows.
2 =PIN

POS Entry Mode (Diners Club Addendum Record 1, Position 66, length 2) must be as follows
TK -Acquired with ICC data (for sale/purchase transactions)
TL =Credit to a TK charge (for refunds from a sale/purchase transaction)
Diners Action Code (Diners Club Addendum Record 1 (<D), Position 68, length 2) must be populated with value from
Auth- Xpress DE 39
80 Byte Population Guide Page 190 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Application PAN Sequence Number (EMV Detail Addendum Record 1 (@1), Pos 5, length 3) identifies and
differentiates cards with the same PAN, this is mandatory.

Application Interchange Profile (EMV Detail Addendum Record 1 (@1), Pos 62, length 3) Indicates the capabilities of
the card to support specific functions in the application, this is mandatory.

Application Transaction Counter (EMV Detail Addendum Record 1 (@1), Pos 58, length 4) Global counter maintained
by the card application in the ICC, this is mandatory.

Application Cryptogram (TC/AAC) (EMV Detail Addendum Record 2 (@2), Pos 27, length 16) Cryptogram computed by
the D-PAS card application and returned to the terminal in the response of the GENERATE AC command (i.e., TC,
ARQC, AAC), this is mandatory.

Amount Authorised (EMV Detail Addendum Record 2 (@2), Pos 5, length 12) Authorized amount of the transaction
(excluding adjustments), this is mandatory.

Cryptogram Information Data (EMV Detail Addendum Record 2 (@2), Pos 43, length 2) indicates the type of
cryptogram (TC, ARQC, or AAC) returned by the card and the actions to be performed by the terminal, this is
mandatory

Terminal Country Code (EMV Detail Addendum Record 1 (@1), Pos 20, length 3) indicates the country of the terminal,
represented according to ISO 3166, this is mandatory.

Terminal Capabilities (EMV Detail Addendum Record 1 (@1), Pos 14, length 6) indicates the card data input, CVM, and
security capabilities of the terminal, this is mandatory.

Terminal Type (EMV Detail Addendum Record 3 (@3), Pos 77, length 2) indicates the terminal type, this is mandatory.

Terminal Verification Results (TVR) (EMV Detail Addendum Record 1 (@1), Pos 66, length 10) status of the different
functions as seen from the terminal, this is mandatory.

Transaction Date (EMV Detail Addendum Record 1 (@1), Pos 8, length 6) Local date that the transaction was
authorized, this is mandatory.

Transaction Type (EMV Detail Addendum Record 3 (@3), Pos 69, length 2) indicates the type of financial transaction
represented by the first two digits of the ISO 8583:1987 Processing Code, this is mandatory.

Transaction Currency Code (EMV Detail Addendum Record 1 (@1), Pos 23, length 3) indicates the currency code of
the transaction according to ISO 4217, this is mandatory

Sample transaction: Capture Method Chip initiated the transaction

06D362800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06<D11125999 0000000000000052TK
06@1002100214E0F0C8528978A0000000031010 006E5C000080008000
06@2000000038834 6918E30EF1C6523A80 09321706C5E4A948000000000000
06@306010A03A40000

07D362800xxxxxxxxxx 727782 POSI0709080000

07<1 000002004000840
07<A 0323000000 0000000000000000000000000
07<B
07<D11125999 0000000000000052TL
07@1002100214E0F0C8528978A0000000031010 006E5C000080008000
07@2000000038834 6918E30EF1C6523A80 09321706C5E4A948000000000000

80 Byte Population Guide Page 191 of 216

Version 15.93
OmniPay Innovation in Transaction Management

07@306010A03A40000

Airline Transaction
Airline itinerary details are not mandatory for Diners and have no impact on the interchange as there are no incentive
rates for airline transactions. There is no validation performed on the values submitted in the Diners Airline
addendum records and these will be passed on to the scheme as they are submitted in the incoming 80byte file. We
have listed the commonly used airline itinerary details below that are generally used for information purpose.

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

Charge Description (Bankcard and T & E Detail Record, Position 56, length 25) should have the DBA name populated.
For airline MCCs other than 4511, the DBA name should be the shortened version. Typically this contains the
abbreviated Airline and it should not exceed first nine positions.
Ticket number should NOT be populated in the charge description field. Charge Description field should be space
filled if a merchant has decided to use the DBA Name from the Merchant Master File.

Merchant Category Code (Diners Club Addendum Record 1, Position 9, length 4): MCC must be 3000-3299 or 4511.

Passenger Name (Diners Passenger Transport Detail - General Ticket Addendum Record 1, Position 5, and Length 42):
The passenger name should be left justified string with trailing spaces. Default to spaces.

Ticket Number (Diners Passenger Transport Detail - General Ticket Addendum Record 1, Position 47, and Length 10):
The number on the ticket, left justified. If space or zero filled, this field will not be extracted to the outgoing file.

Issuing Carrier (Diners Passenger Transport Detail - General Ticket Addendum Record 1, Position 78, and Length 3):
Standard abbreviation of the airline, left justified with trailing spaces. Default to spaces.

Trip leg details:

Leg Number (Diners Passenger Transport Detail Trip Leg Data Addendum Record, Position 5, and Length 3): This field
can be populated with the specific leg number. Zero fill if unavailable.

Carrier Code (Diners Passenger Transport Detail Trip Leg Data Addendum Record, Position 8, and Length 4): Alpha
numeric airline code, left justified with trailing spaces. If space or zero filled, this field will not be extracted to the
outgoing file.

Departure Date (Diners Passenger Transport Detail Trip Leg Data Addendum Record, Position 22, and Length 6):
Must be populated in the format YYMMDD. If space or zero filled, this field will not be extracted to the outgoing file.

Departure Airport Code (Diners Passenger Transport Detail Trip Leg Data Addendum Record, Position 22, and
Length 6): Must be populated with departure airport code. If space or zero filled, this field will not be extracted to the
outgoing file.

Arrival Airport Code (Diners Passenger Transport Detail Trip Leg Data Addendum Record, Position 22, and Length 6):
Must be populated with arrival airport code. If space or zero filled, this field will not be extracted to the outgoing file.

Stopover Allowed (Diners Passenger Transport Detail Trip Leg Data Addendum Record, Position 79, and Length 1):
Indicates if a routing stop over is allowed (Y=Yes, N= No). If space or zero filled, this field will not be extracted to the
outgoing file.

Sample transaction: Capture Method - SET/3D-SET non-authenticated

06D362800xxxxxxxxxx 727782M POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06<D11124511 0000000000000094TD
06<RJBLOGGS 98745632129003214 BA

80 Byte Population Guide Page 192 of 216

Version 15.93
OmniPay Innovation in Transaction Management

06<S
06<T001BA B123DUB 100223 LHR100223 000000000025000

Attended Card present - Mobile Point of Sale Card Present Transaction

Diners Mobile POS Indicator (Diners Club Addendum Record 1, Position 66, length 2) must be as follows
M =MPOS transaction performed.

Diners Action Code (Diners Club Addendum Record 1 (<D), Position 68, length 2) must be populated with value from
Auth- Xpress DE 39

Sample transaction: Capture Method Chip initiated the transaction

06D362800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06<D11125999 0000000000000052TK M

07D362800xxxxxxxxxx 727782 POSI0709080000

07<1 000002004000840
07<A 0323000000 0000000000000000000000000
07<B
07<D11125999 0000000000000052TL M

80 Byte Population Guide Page 193 of 216

Version 15.93
OmniPay Innovation in Transaction Management

26 ELV Transactions
This section outlines the fields and records that need to be populated on the 80 byte file to submit ELV transactions.
All the ELV transactions should be submitted with a card brand of Z in order to be recognised as an ELV transaction.
Clearing file is generated by OmniPay for the ELV transactions. We currently dont support any new interchange rates
for ELV transactions but this section outlines the fields required for various capture methods supported. Refunds are
not allowed on the ELV transactions. Bank sort code validation is performed for these transactions.

Following fields are optional and if they are left space filled, transactions shouldnt reject and should just be assigned a
terminal capability of manual and a capture method of manual.
POS Terminal Capability =(<P, Pos 75)
Cardholder ID =(<P, Pos 76)
POS Entry Mode =(<P, Pos 73-74)

ELV Transaction
Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response message.

Bank Sort Code (Bank Account/Direct Debit Transaction Compliance Record 1 (<N), Position 5, length 9) if its zero or
space filled, the transaction will reject. Left justified with trailing spaces. (EDD CAPTURE record, AccBankID field)

Account Number (Bank Account/Direct Debit Transaction Compliance Record 1 (<N), Position 14, length 10) if its zero
or space filled, the transaction will reject. Left justified with trailing spaces. (EDD CAPTURE record, AccNr field)

Bank Name (Bank Account/Direct Debit Transaction Compliance Record 1 (<N), Position 24, length 20) is an optional
field. Left justified with trailing spaces. (EDD CAPTURE record, AccBankName field)

Account Owners Name (Bank Account/Direct Debit Transaction Compliance Record 1 (<N), Position 44, length 37) if
its zero or space filled, the transaction will reject. Left justified with trailing spaces. (EDD CAPTURE record, AccOwner
field)

Order description 1 (ELV Compliance Record (<P), Position 5, length 27) when populated will take precedence over
the value in Charge Description field on the 06Z record. Left justified with trailing spaces. (EDD CAPTURE record,
OrderDesc1 field)

Transaction Identifier (Bank Account/Direct Debit Transaction Compliance Record 2 (<O), Position 5, length 64)
contains the Transaction ID as generated by the merchants ERP software (order number). Left justified with trailing
spaces. (EDD CAPTURE record, TransID field)

Merchant Category Code (Bank Account/Direct Debit Transaction Compliance Record 2 (<O), Position 69, length 4) if
its not populated, this value is taken from the Merchant Master File (MMF).

Payment Type (Bank Account/Direct Debit Transaction Compliance Record 2 (<O), Position 77, length 1) must be 'E'.
E =ELV Transaction

POS Terminal capability (Bank Account/Direct Debit Transaction Compliance Record 2 (<O), Position 75, length 1)
must be 9.
9 =Key entered (no card reader available)

Cardholder ID (Bank Account/Direct Debit Transaction Compliance Record 2 (<O), Position 76, length 1) must be as
follows.
Undefined =space filled

80 Byte Population Guide Page 194 of 216

Version 15.93
OmniPay Innovation in Transaction Management

POS Entry Mode (Bank Account/Direct Debit Transaction Compliance Record 2 (<O), Position 73, length 2) must be
'01'.
01 =Key entered

Sample transaction: Capture Method - Cust. present, key-entry

06Z 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06<N12070000 7812365891Deutsche Bank Joe Bloggs
06<O9874563211236123654798 5999019 E
06<PMERCHANT DBA NAME Tables and Chairs

80 Byte Population Guide Page 195 of 216

Version 15.93
OmniPay Innovation in Transaction Management

27 UPI (CHINA UNION PAY) Transactions

This section outlines the fields and records that need to be populated on the 80 byte file to submit UPI transactions.
BINS are assigned and managed by UPI. UPI produces a file containing the applicable UPI BIN ranges in a fixed file
format on a daily basis. BINs assigned to UPI co-branded cards will appear on both the UPI BIN table. For UPI credit
cards, the PAN length is always 16 digits. For Debit Card, the PAN length can vary between 13 to 19 digits . BINs within
the UPI card scheme can begin with a 4, 5 or a 6.
Interchange rates for UPI are setup independently for each acquirer but this section outlines the fields required for
various capture methods supported. Luhn Check validation is carried out on the card numbers similar to Visa and
MasterCard at Modulus 10.
The following fields will be used to determine the Terminal Capability and Capture Method:
Transaction Initiating Channel =Record #C (Position 29-30)
PAN Entry Mode =Record #C (Position 31-32)
Cardholder ID Method =Record #C (Position 33)

Attended Card present Manual Entry - No CVM

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

Transaction Initiating Channel (UPI Addendum Record 1 (#C) Position 29, length 2) should be
00 =Not Defined
03 =POS (Manually captured transactions at POS)

Cardholder ID (UPI Addendum Record 1 (#C) Position 33, length 1) must be '0'
0 =Unknown

PAN Entry Mode (UPI Addendum Record 1 (#C) Position 31, length 2) must be '01'.
01 =Manual

Sample transaction: Capture Method - Cust. present, Manual-entry

06H452800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06#C123456789015999 000103763000

Attended Card present Manual Entry - Signature Transaction

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

Transaction Initiating Channel (UPI Addendum Record 1 (#C) Position 29, length 2) should be
00 =Not Defined
03 =POS (Manually captured transactions at POS)

Cardholder ID (UPI Addendum Record 1 (#C) Position 33, length 1) must be '2'.

80 Byte Population Guide Page 196 of 216

Version 15.93
OmniPay Innovation in Transaction Management

2 =Pin excluded in the transaction

PAN Entry Mode (UPI Addendum Record 1 (#C) Position 31, length 2) must be '01'.
01 =Manual

Sample transaction: Capture Method - Cust. present, Manual-entry

06H452800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06#C123456789015999 000123763000

Attended Card present Magnetic Stripe - No CVM Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

Transaction Initiating Channel (UPI Addendum Record 1 (#C) Position 29, length 2) must be 03.
03 =POS
Cardholder ID (UPI Addendum Record 1 (#C) Position 33, length 1) must be '0'.
0 =Unknown
PAN Entry Mode (UPI Addendum Record 1 (#C) Position 31, length 2) must be '90'.
90 =Mag Stripe Read and reliable, track 2 data must exist

Sample transaction: Capture Method Card swiped, Online Auth , No CVM

06H452800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06#C123456789015999 039003763000

Attended Card present Magnetic Stripe Signature Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

Transaction Initiating Channel (UPI Addendum Record 1 (#C) Position 29, length 2) must be 03.
03 =POS
Cardholder ID (UPI Addendum Record 1 (#C) Position 33, length 1) must be '2'.
2 =Pin excluded in the transaction
PAN Entry Mode (UPI Addendum Record 1 (#C) Position 31, length 2) must be '90'.
90 =Mag Stripe Read and reliable, track 2 data must exist

Sample transaction: Capture Method Card swiped, Online Auth , signature

06H452800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06#C123456789015999 039023763000

80 Byte Population Guide Page 197 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Attended Card present Magnetic Stripe PIN Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

Transaction Initiating Channel (UPI Addendum Record 1 (#C) Position 29, length 2) must be 03.
03 =POS
Cardholder ID (UPI Addendum Record 1 (#C) Position 33, length 1) must be '1'.
1 =Pin included in the transaction
PAN Entry Mode (UPI Addendum Record 1 (#C) Position 31, length 2) must be '90'.
90 =Mag Stripe Read and reliable, track 2 data must exist

Sample transaction: Capture Method Card swiped, Online Auth , Pin

06H452800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06#C123456789015999 039013763000

Attended Card present Magnetic Stripe (non Reliable) - No CVM Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

Transaction Initiating Channel (UPI Addendum Record 1 (#C) Position 29, length 2) must be 03.
03 =POS

Cardholder ID (UPI Addendum Record 1 (#C) Position 33, length 1) must be '0'.
0 =Unknown

PAN Entry Mode (UPI Addendum Record 1 (#C) Position 31, length 2) must be '02'.
02 =Mag Stripe Read

Sample transaction: Capture Method Card swiped, CVV Not Reliable, No CVM
06H452800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06#C123456789015999 030203763000

Attended Card present Magnetic Stripe (non Reliable) - Signature Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

Transaction Initiating Channel (UPI Addendum Record 1 (#C) Position 29, length 2) must be 03.
03 =POS
Cardholder ID (UPI Addendum Record 1 (#C) Position 33, length 1) must be '2'.
2 =Pin excluded in the transaction
PAN Entry Mode (UPI Addendum Record 1 (#C) Position 31, length 2) must be '02'.
02 =Mag Stripe Read

80 Byte Population Guide Page 198 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Sample transaction: Capture Method Card swiped, CVV Not Reliable, signature
06H452800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06#C123456789015999 030223763000

Attended Card present Magnetic Stripe (non Reliable) - PIN Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

Transaction Initiating Channel (UPI Addendum Record 1 (#C) Position 29, length 2) must be 03.
03 =POS

Cardholder ID (UPI Addendum Record 1 (#C) Position 33, length 1) must be '1'.
1 =Pin included in the transaction

PAN Entry Mode (UPI Addendum Record 1 (#C) Position 31, length 2) must be '02'.
02 =Mag Stripe Read

Sample transaction: Capture Method Card swiped, CVV Not Reliable, Pin
06H452800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06#C123456789015999 030213763000

Attended Card present Chip - No CVM Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

Transaction Initiating Channel (UPI Addendum Record 1 (#C) Position 29, length 2) must be 03.
03 =POS

Cardholder ID (UPI Addendum Record 1 (#C) Position 33, length 1) must be '0'.
0 =Unknown

PAN Entry Mode (UPI Addendum Record 1 (#C) Position 31, length 2) must be '05'.
05 =ICC Read, Mag Stripe Data Reliable

Sample transaction: Capture Method Chip Read, Online Auth , No CVM

06H452800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06#C123456789015999 030503763000

Attended Card present Chip Signature Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

80 Byte Population Guide Page 199 of 216

Version 15.93
OmniPay Innovation in Transaction Management

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

Transaction Initiating Channel (UPI Addendum Record 1 (#C) Position 29, length 2) must be 03.
03 =POS

Cardholder ID (UPI Addendum Record 1 (#C) Position 33, length 1) must be '2'.
2 =Pin excluded in the transaction

PAN Entry Mode (UPI Addendum Record 1 (#C) Position 31, length 2) must be '05'.
05 =ICC Read, Mag Stripe Data Reliable

Sample transaction: Capture Method Chip Read, Online Auth , signature

06H452800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06#C123456789015999 030523763000

Attended Card present Chip & PIN Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

Transaction Initiating Channel (UPI Addendum Record 1 (#C) Position 29, length 2) must be 03.
03 =POS

Cardholder ID (UPI Addendum Record 1 (#C) Position 33, length 1) must be '1'.
1 =Pin included in the transaction

PAN Entry Mode (UPI Addendum Record 1 (#C) Position 31, length 2) must be '05'.
05 =ICC Read, Mag Stripe Data Reliable

Sample transaction: Capture Method Chip Read, Online Auth , Pin

06H452800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06#C123456789015999 030513763000

Attended Card present EMV Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

Transaction Initiating Channel (UPI Addendum Record 1 (#C) Position 29, length 2) must be 03.
03 =POS

Cardholder ID (UPI Addendum Record 1 (#C) Position 33, length 1) must be '1'.
1 =Pin included in the transaction
PAN Entry Mode (UPI Addendum Record 1 (#C) Position 31, length 2) must be '05'.
05 =ICC Read, Mag Stripe Data Reliable

80 Byte Population Guide Page 200 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Sample transaction: Capture Method Chip Read, Online Auth , Pin with EMV details
06H452800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06#C123456789015999 030513763000
06@1001090628E0B8C0826826A0000000031010 00195C000000008000008C
06@2000000004250 BA12640EFC2CBB124000002409230250162ADB98A6000000000000
06@306020A0364BC00 0041030222
06@4BA12640EFC2CBB1240000250162ADB98A60009

Attended Card present Chip (non Reliable) - No CVM Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

Transaction Initiating Channel (UPI Addendum Record 1 (#C) Position 29, length 2) must be 03.
03 =POS

Cardholder ID (UPI Addendum Record 1 (#C) Position 33, length 1) must be '0'.
0 =Pin included in the transaction

PAN Entry Mode (UPI Addendum Record 1 (#C) Position 31, length 2) must be '95'.
95 =ICC Card, data may be unreliable

Sample transaction: Capture Method Chip Read, CVV Non Reliable , No CVM
06H452800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06#C123456789015999 039503763000

Attended Card present Chip (non Reliable) Signature Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

Transaction Initiating Channel (UPI Addendum Record 1 (#C) Position 29, length 2) must be 03.
03 =POS

Cardholder ID (UPI Addendum Record 1 (#C) Position 33, length 1) must be '2'.
2 =Pin excluded in the transaction

PAN Entry Mode (UPI Addendum Record 1 (#C) Position 31, length 2) must be '95'.
95 =ICC Card, data may be unreliable

Sample transaction: Capture Method Chip Read, CVV Non Reliable, signature
06H452800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06#C123456789015999 039523763000

80 Byte Population Guide Page 201 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Attended Card present Chip (non Reliable) & PIN Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

Transaction Initiating Channel (UPI Addendum Record 1 (#C) Position 29, length 2) must be 03.
03 =POS

Cardholder ID (UPI Addendum Record 1 (#C) Position 33, length 1) must be '1'.
1 =Pin included in the transaction

PAN Entry Mode (UPI Addendum Record 1 (#C) Position 31, length 2) must be '95'.
95 =ICC Card, data may be unreliable

Sample transaction: Capture Method Chip Read, CVV Non Reliable, Pin
06H452800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06#C123456789015999 039513763000

CONTACTLESS Attended Card present Magnetic Stripe - No CVM Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

Transaction Initiating Channel (UPI Addendum Record 1 (#C) Position 29, length 2) must be 03.
03 =POS
Cardholder ID (UPI Addendum Record 1 (#C) Position 33, length 1) must be '0'.
0 =Pin included in the transaction
PAN Entry Mode (UPI Addendum Record 1 (#C) Position 31, length 2) must be '91'.
91 =Contactless Magstripe Read

Sample transaction: Capture Method Contactless Magstripe read, No CVM

06H452800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06#C123456789015999 039103763000

CONTACTLESS Attended Card present Magnetic Stripe Signature Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

Transaction Initiating Channel (UPI Addendum Record 1 (#C) Position 29, length 2) must be 03.
03 =POS

Cardholder ID (UPI Addendum Record 1 (#C) Position 33, length 1) must be '2'.
80 Byte Population Guide Page 202 of 216

Version 15.93
OmniPay Innovation in Transaction Management

2 =Pin excluded in the transaction

PAN Entry Mode (UPI Addendum Record 1 (#C) Position 31, length 2) must be '91'.
91 Contactless Magstripe Read

Sample transaction: Capture Method Contactless Magstripe read, signature

06H452800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06#C123456789015999 039123763000

CONTACTLESS Attended Card present Magnetic Stripe PIN Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.
MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.
Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

Transaction Initiating Channel (UPI Addendum Record 1 (#C) Position 29, length 2) must be 03.
03 =POS

Cardholder ID (UPI Addendum Record 1 (#C) Position 33, length 1) must be '1'.
1 =Pin included in the transaction

PAN Entry Mode (UPI Addendum Record 1 (#C) Position 31, length 2) must be '91'.
91 Contactless Magstripe Read

Sample transaction: Capture Method Contactless Magstripe read, Pin

06H452800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06#C123456789015999 039113763000

CONTACTLESS Attended Card present Chip - No CVM Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

Transaction Initiating Channel (UPI Addendum Record 1 (#C) Position 29, length 2) must be 03.
03 =POS

Cardholder ID (UPI Addendum Record 1 (#C) Position 33, length 1) must be '0'.
0 =Unknown

PAN Entry Mode (UPI Addendum Record 1 (#C) Position 31, length 2) must be '07'.
07 =Fast UPIIC Debit/Credit ICC read (Contactless)

Sample transaction: Capture Method Contactless Chip Read, No CVM

06H452800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06#C123456789015999 030703763000

80 Byte Population Guide Page 203 of 216

Version 15.93
OmniPay Innovation in Transaction Management

CONTACTLESS Attended Card present Chip Signature Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6) From Authorization Response Message

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

Transaction Initiating Channel (UPI Addendum Record 1 (#C) Position 29, length 2) must be 03.
03 =POS

Cardholder ID (UPI Addendum Record 1 (#C) Position 33, length 1) must be '2'.
2 =Pin excluded in the transaction

PAN Entry Mode (UPI Addendum Record 1 (#C) Position 31, length 2) must be '07'.
07 =Fast UPIIC Debit/Credit ICC read (Contactless)

Sample transaction: Capture Method Contactless Chip Read, signature

06H452800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06#C123456789015999 030723763000

CONTACTLESS Attended Card present Chip & PIN Transactions

Auth Code (Bankcard and T & E Detail Record, Position 26, length 6): From Authorization Response Message.

MOTO Flag (Bankcard and T & E Detail Record, Position 32, length 1)must be space.

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1) must be space.

Transaction Initiating Channel (UPI Addendum Record 1 (#C) Position 29, length 2) must be 03.
03 =POS

Cardholder ID (UPI Addendum Record 1 (#C) Position 33, length 1) must be '1'.
1 =Pin included in the transaction

PAN Entry Mode (UPI Addendum Record 1 (#C) Position 31, length 2) must be '07'.
07 =Fast UPIIC Debit/Credit ICC read (Contactless)

Sample transaction: Capture Method Contactless Chip Read, Pin

06H452800xxxxxxxxxx 727782 POSI0709080000
06<1 000002004000840
06<A 0323000000 0000000000000000000000000
06<B
06#C123456789015999 030713763000

80 Byte Population Guide Page 204 of 216

Version 15.93
OmniPay Innovation in Transaction Management

28 Australian Debit Card Transactions

This section outlines the fields and records that need to be populated on the 80 byte file to submit Australian Debit
Card (ePAL) transactions. The card length can be between 16-19 digits. BINs within the Australian Debit Card (ePAL)
card scheme can begin with a 4 or a 5. At present, 16 digit card numbers are carried on the <E record.
These transactions are conveyance only. They will not be sent to scheme.
The only permissible currency for these transactions is AUD.
Interchange rates for Australian Debit (ePAL) Card transactions are identified within the transaction itself. The FPI
code is defined within the #Q record.
EPAL transactions can be Chip and Pin, Mag Stripe (with Pin), Contactless (No CVM).
Online and Offline Pin are acceptable, but as transaction information is carried on '#1 record' Offline and Online
cannot be distinguished.
EMV Details may be carried

Attended Card present Chip & PIN Transactions

ATM Account Selection (Visa Detail Addendum Record #1, Position 58, length 1) Stipulates the type of account used.
Valid Values:
1 =Savings account
2 =Checking Account

Type Indicator (Bankcard and T & E Detail Record #Q, Position 5, length 1) Stipulates the type of fee contained in the
Fee Identifier.
Valid Values:
ePAL Australia.(AUD only) (1)

Fee ID (Bankcard and T & E Detail Record #Q, Position 6-8, length 1) Defined as below according to transaction type. FPI
codes can only be taken from selection below
a: Purchase Only AUS DEBIT <$15 (QT1)
b: Purchase Only AUS DEBIT >$15 (QT2)
c: AUS DEBIT PLUS CASH OUT (QT3)
d: CASH ONLY (QT4)
e: Charity and Medicare (QT5)
Credit/Debit Flag (Bankcard and T & E Detail Record #Q, Position 9, length 1)
a: Credit to Merchant (C)
b: Debit to Merchant (D)
Fee Value (Bankcard and T & E Detail Record #Q) Position 10-21, length 12) The amount of the fee paid to the
merchant.
The Fee Value amount is expressed in the minor unit of currency, without a decimal separator, in accordance with ISO
standards for currency notation. For example, a fee value of AUD$1 is expressed as 000000000100
Sample transaction: Card Present Australian Debit Card Transaction of greater than $15
06K 0826 001569 160759001260
06<1000000000000000050036 NN

80 Byte Population Guide Page 205 of 216

Version 15.93
OmniPay Innovation in Transaction Management

06<A 0826 0000000000000000000000000160759

06<B 160759001260CALF100F
06<E4434200002981730 CALF100F 000000000000
06#1 22 00000000400003600000000000000000 601290 1 00000000
06#Q1QT1D000000000200

80 Byte Population Guide Page 206 of 216

Version 15.93
OmniPay Innovation in Transaction Management

29 iDeal Transactions
This section outlines the fields and records that need to be populated on the 80 byte file to submit iDeal transactions.
These transactions are Ecommerce only, and only within Domestic Netherlands.. These are the only transactions with
the <O record that can be credit or debit. All other transactions containing the <O record must be Sales Drafts.
These transactions are unique to the platform in that they do not possess a Card number on either the Bankcard and
T&E Record or <E record. Transactions are instead identified by IBN number on the <O record.

Ecommerce
Cardholder Number (Bankcard and T & E Detail Record, Position 4, length 16) Must be Space filled for iDeal
transactions

Card Type Ext Code (Bankcard and T & E Detail Record, Position 20, length 1)
I =iDeal transaction

Electronic Commerce Indicator (Bankcard and T & E Detail Record, Position 41, length 1).
5 = Secured transaction

POS Terminal capability (Bank Account/Direct Debit Transaction Compliance Record 2 (<O), Position 75, length 1)
must be 9
9 =Key entered (no card reader available)

Cardholder ID (Bank Account/Direct Debit Transaction Compliance Record 2 (<O), Position 76, Length 1) must be '4'.
4 =Mail/Telephone or Electronic Commerce

POS Entry Mode (Bank Account/Direct Debit Transaction Compliance Record 2 (<O), Position 73, length 2) must
be 01
01 =Key Entered.

Merchant City (VISA Detail Addendum Record A (<A), Position 29, Length 13) Optional field used to populate the
Consumer city in the case of a sale / refunds.

Custom Data (Bankcard and T&E Detail Addendum Record B (<B), Position 5, Length 30)
Populated with iDeal Transaction ID.

Cardholder Name (Bankcard and T&E Detail Addendum Record C (<C), Position 55, Length 25)
Populated with Consumer Name.

Transaction Identifier(Bank Account/Direct Debit Transaction Compliance Record 2 (<O)), Position 5, Length 64)
For Ideal transactions, the 35 character Purchase ID can be stored in positions 5-39; this is optional (but
recommended) to include for Sales / Refund.
IBAN must be populated on position 40-57 for Refunds only. This should be left justified.
Use trailing spaces with the remaining

Payment Type(Bank Account/Direct Debit Transaction Compliance Record 2 (<O)), Position 77, Length 1)
I= iDeal

Transaction Time VISA Detail Addendum Record A (<A), Position 70, Length 6) must be populated with the
Transmission time for Sales, Optional for Refunds.

Sample transaction: Capture Method - SET/3D-SET authenticated

06Z I0618 064846 538545335
06<1000000000000070000826 DEU
06<A 0618000000XXXXCITYXXXXX 0000000000000000000000000125531+0200
06<BXXXXXIDEALTRANSACTIONIDXXXXXXX
80 Byte Population Guide Page 207 of 216

Version 15.93
OmniPay Innovation in Transaction Management

06<C XXXXXXXXCONSUMERNAMEXXXXX
06<0XXXXXXXXXXPURCHASE IDXXXXXXXXXXXXX XXXXXIBANXXXXXXXX I
06#1594 000000070000826062015061810535615330451101
06#31 000000 000000070000 HHMMSS

80 Byte Population Guide Page 208 of 216

Version 15.93
OmniPay Innovation in Transaction Management

30 Pre-Authorisation, Top-Ups & Clearing:

A Pre-authorisation transaction is used to request Approval for an estimated transaction amount because the final
transaction amount will only be known some time later. This type of message is typically sent for transactions such as
car rentals, hotel rooms and petrol. The reason for the pre-authorisation is to authenticate the card and the
cardholder and also to check funds availability. We have outlined below our expectation on how the Pre-
authorisations, top-up Auths, reversals and the corresponding clearing transaction details should be presented on the
80byte file for the different scenarios that are likely to be seen.

1. If the pre-auth amount was 100 and the final amount comes to 110 then the PSP is not required to
perform a top-up auth for 10 as it would be within the scheme tolerance assuming its 15% then the
following values are expected in the 80byte transaction.
Transaction amount =110
Total authorised amount =100 (For Visa only)
Auth code =from the 100 authorisation
Authorised amount =100 corresponding to the above auth code

2. If the pre-auth amount was 100 and the final amount comes to 150 then the PSP should perform a top-up
auth for 50 as it would exceed the scheme tolerance assuming its 15%. In which case, we would expect the
PSP to raise a new top-up auth for 50. Following values are expected in the 80byte transaction.
Transaction amount =150
Total authorised amount =150 (For Visa only)
Auth code =from the 100 authorisation
Authorised amount =100 corresponding to the above auth code
Top-Up Auth =50

3. If the pre-auth amount was 100 and the final amount comes to 80 then the PSP does not need to perform
a top-up auth as its within the pre-auth amount. Its our understanding that the clients would then reverse
portion of the pre-authorised amount 20 which was not used out of the 100 using a partial-reversal or they
can reverse the full 100 and submit a fresh auth for 80.Following values are expected in the 80byte
transaction.
Transaction amount =80
Total authorised amount =80 (For Visa only)
Auth code =from the 100 authorisation
Authorised amount =100 corresponding to the above auth code

80 Byte Population Guide Page 209 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Multi-Currency Sample 80byte I

Multi-Currency transactions are batched per Merchant Number (MID) per transaction currency (Mandatory)

00 Sample 80byte_MI 0402 FDMS

06V4085480000000004 0402 587523 2 500010080388314 Merchant 1 EUR Currency
06<1000000000000040000978 GBR LONDON NN
06<A 0402000000 0000000000000000000000000
06<B
06#1594 00000004000097800 599901M 0
06#3 000000 0000000040000
07V4085480000000004 0402 587523 2 500010080388314 Merchant 1 EUR Currency
07<1000000000000040000978 GBR LONDON NN
07<A 0402000000 0000000000000000000000000
07<B
07#1594 00000004000097800 599901M 0
07#3 000000 0000000040000
06M5409640000000009 0402 157009 2 J00010080388314 Merchant 1 EUR Currency
06<1000000000000042000978 GBR LONDON N
06<A 0402000000 0000000000000000000000000
06<B
06=0000000000000000042000MMDC123450402 599901 1
06=51211000100010V09000
70 Merchant 1 000000042000 TEST BATCHID - TBC
06V4085480000000004 0402 503314 2 700010080388314 Merchant 1 CHF Currency
06<1000000000000040000752 GBR LONDON
06<A 0402000000 0000000000000000000000000
06<B
06#1594 00000004000075200 599901M 0
06#3 000000 0000000040000
06M5409640000000009 0402 622472 2 J00010080388314 Merchant 1 CHF Currency
06<1000000000000042000752 GBR LONDON
06<A 0402000000 0000000000000000000000000
06<B
06=0000000000000000042000MMDC123450402 599901 0
06=50000000100010V09000
06M5586900000000002 0402 191958 2 J00010080388314 Merchant 1 CHF Currency
06<1000000000000043000752 GBR LONDON
06<A 0402000000 0000000000000000000000000

80 Byte Population Guide Page 210 of 216

Version 15.93
OmniPay Innovation in Transaction Management

06<B
06=0000000000000000043000MMDC123450402 599901 0
06=50000000100010V09000
70 Merchant 1 000000125000 TEST BATCHID - TBC
06V4008360000000002 0402 200448T7 00010080378497 Merchant 1 JPY Currency
06<1000000000000040500392 GBR LONDON NN
06<A 0402000000 0000000000000000000000000
06<B
06#1594 00000004050039200 599901M 0
06#3 000000 0000000040500
06M5451680000000002 0402 292538T7 00010080378497 Merchant 1 JPY Currency
06<1000000000000042500392 GBR LONDON
06<A 0402000000 0000000000000000000000000
06<B
06=0000000000000000042500MMDC123450402 599901
06=51211000100030000000
07M5451680000000002 0402 179038T7 00010080378497 Merchant 1 JPY Currency
07<1000000000000042500392 GBR LONDON
07<A 0402000000 0000000000000000000000000
07<B
07=0000000000000000042500MMDC123450402 599901
07=50000000100030000000
70 Merchant 2 000000040500 TEST BATCHID - TBC
80 000000000207500 000059

80 Byte Population Guide Page 211 of 216

Version 15.93
OmniPay Innovation in Transaction Management

Multi-Currency Sample 80byte II

Multi-Currency transactions are batched per Merchant Number (MID) per transaction currency per card scheme
(Optional)
00 Sample 80byte_ca 1130 FDMS
06M5488030000000007 1129 111220 JS41 Merchant 1 HKD Curr MC bat
06<1 000000011800344
06<A 1129000000 0000000000000000000000000104556+01
06<B 33309054234 12345
06=0000000000000000011800MCC1260271129 599901 2
06=51211000100010S09000
70 Merchant 1 000000011800 BAT101130_01
06V4006820000000007 1129 415408 6S24 Merchant 1 HKD Curr VI ba
06<1 000000010200344
06<A 1129000000 0000000000000000000000000104528+01
06<B 33309054209 12345
06#1894 1234 00000001020034400 100054214 599901N
06#3 I000000 0000000010200
07V4140040000000009 1129 958319 7S28 Merchant 1 HKD Curr VI ba
07<1 000000010200344
07<A 1129000000 0000000000000000000000000104536+01
07<B 33309054215 12345
07#1894 1234 00000001060034400 100054225 599901N
07#3 I000000 0000000010600
06V4297720000000007 1129 806945 6S29 Merchant 1 HKD Curr VI ba
06<1 000000010700344
06<A 1129000000 0000000000000000000000000104538+01
06<B 33309054217 12345
06#1894 1234 00000001070034400 100054227 599901N
06#3 I000000 0000000010700
70 Merchant 1 000000010700 BAT101130_01
06M5533810000000007 1129 222283 JS35 Merchant 1 EUR Curr MC ba
06<1 000000011300978
06<A 1129000000 0000000000000000000000000104548+01
06<B 33309054226 12345
06=0000000000000000011300MCC1260221129 596901 2
06=51411000100010S09000
07M5533810000000007 1129 222283 JS36 Merchant 1 EUR Curr MC ba
07<1 000000011300978
07<A 1129000000 0000000000000000000000000104623+01
07<B 33309054226 12345
07=0000000000000000011300MCC1260221129 596901 2
07=51411000100010S09000
70 Merchant 1 000000000000 BAT101130_01
06M5520260000000018 1129 856182 JS42 Merchant 2 HKD Curr MC ba
06<1 000000011900344
06<A 1129000000 0000000000000000000000000104558+01
06<B 33309054236 12345
06=0000000000000000011900MCC1260281129 599901 2
06=51211000100010S09000
06M5163660000000003 1129 925490 JS43 Merchant 2 HKD Curr MC ba
06<1 000000012000344
06<A 1129000000 0000000000000000000000000104559+01
06<B 33309054237 12345
06=0000000000000000012000MCC1260291129 599901 1
06=51211000100010S09000

80 Byte Population Guide Page 212 of 216

Version 15.93
OmniPay Innovation in Transaction Management

70 Merchant 2 000000023900 BAT101130_01

06V4862590000000009 1129 912428 5S21 Merchant 2 HKD Curr VI ba
06<1 000000010000344
06<A 1129000000 0000000000000000000000000104525+01
06<B 33309054206 12345
06#1894 1234 00000001000034400 100054208 599901N
06#3 I000000 0000000010000
06V4859960000000009 1129 223908 7S25 Merchant 2 HKD Curr VI ba
06<1 000000010300344
06<A 1129000000 0000000000000000000000000104530+01
06<B 33309054210 12345
06#1894 1234 00000001030034400 100054216 599901N
06#3 I000000 0000000010300
06V 1129 486204 7S27 Merchant 2 HKD Curr VI ba
06<1 000000010500344
06<A 1129000000 0000000000000000000000000104534+01
06<B 33309054213 12345
06<E418905000000000000612345 00000000000000000000000000000000000000000000
06#1894 1234 00000001050034400 100054222 599901N
06#3 I000000 0000000010500
70 Merchant 2 000000030800 BAT101130_01
80 000000000077200 000074

80 Byte Population Guide Page 213 of 216

Version 15.93
OmniPay Innovation in Transaction Management

DCC Sample 80byte III

DCC transactions are batched per Merchant Number (MID) per transaction currency (merchant funding currency or
the base currency) in this (Mandatory)
00 INST 0903 xxxx
06M5157020000000008 0902 871197 J924516390802 Merchant 1 AUD Base CCY
06<1 000000001818036
06<A 09020000001344 0000000115150000071579000163906
06<B 924516390802VPOSDCC
06=00000000000000000115159999999990902 451101 0 101
06=51112000100000V00110
07M5186250000000006 0902 065407 J924516370798 Merchant 1 AUD Base CCY
07<1 000000021666036
07<A 0000001826 0000000111110000061950000163707
07<B 924516370798VPOSDCC
07=00000000000000000000009999999990902 451101 0 101
07=51112000100000V00110
06V4140040000000009 0902 870239 7924516230787 Merchant 1 AUD Base CCY
06<1 000000001626036
06<A 09020000001344 0000000103030000071579000162307
06<B 924516230787VPOSDCC
06#1 9 00000001030334400 451101
06V4028540000000005 0902 870364 7924516250789 Merchant 1 AUD Base CCY
06<1 000000000135036
06<A 09020000001392 0000000105050000070129300162513
06<B 924516250789VPOSDCC
06#1 9 00000001050539200 451101
06V4284180000000009 0902 870326 7924516240788 Merchant 1 AUD Base CCY
06<1 000000008366036
06<A 09020000001554 0000000104040000078042000162434
06<B 924516240788VPOSDCC
06#1 9 00000001040455400 451101
07V4142590000000001 0902 063829 7924516210786 Merchant 1 AUD Base CCY
07<1 000000019893036
07<A 0000001826 0000000102020000061950000162141
07<B 924516210786VPOSDCC
07#1 9 000000000000 00 451101
06V4865160000000008 0902 870603 7924516290794 Merchant 1 AUD Base CCY
06<1 000000013352036
06<A 09020000001840 0000000109090000061224000162912
06<B 924516290794VPOSDCC
06#1 9 00000001090984000 451101
06V4001880000000006 0902 870465 7924516260791 Merchant 1 AUD Base CCY
06<1 000000018737036
06<A 09020000001978 0000000107070000061750000162654
06<B 924516260791VPOSDCC
06#1 9 00000001070797800 451101
70 Merchant 1 000000002475 00000001
80 000000000002475 000045

80 Byte Population Guide Page 214 of 216

Version 15.93
OmniPay Innovation in Transaction Management

DCC Sample 80byte IV

DCC transactions are batched per Merchant Number (MID) per transaction currency (merchant funding currency or
the base currency) in this per card scheme (Optional)

00 INST 0520 xxxx

06M5157020000000008 0519 912869 J201005141113 Merchant 1 EUR Base CCY
06<1 000000001139978 NN
06<A 05190000001344 0000000114140000000100160135617+02
06<B 13911046200 75200001
06=0000000000000000001139MDC1234560519 599901 2
06=51211000100010T09000
06M5451610000000009 0519 299667 J201005141114 Merchant 1 EUR Base CCY
06<1 000000011515978 NN
06<A 05190000002978 0000000115150000000000000135618+02
06<B 13911046202 75200001
06=0000000000000000011515MDC1234560519 599901 0
06=51211000100010V09000
06M5525690000000003 0519 894035 J201005141115 Merchant 1 EUR Base CCY
06<1 000000001560978 NN
06<A 05190000001208 0000000116160000000074427135619+02
06<B 13911046204 75200001
06=0000000000000000001560MDC1234560519 599901 1
06=51211000100010S09000
06M5243400000000008 0519 811703 J201005141116 Merchant 1 EUR Base CCY
06<1 000000000095978 NN
06<A 05190000001392 0000000117170000001221670135620+02
06<B 13911046205 75200001
06=0000000000000000000095MDC1234560519 599901 1
06=51211000100010S09000
06M5521400000000001 0519 333322 J201005141117 Merchant 1 EUR Base CCY
06<1 000000013842978 NN
06<A 05190000001826 0000000118180000000008537135622+02
06<B 13911046208 75200001
06=0000000000000000013842MDC1234560519 599901 2
06=51211000100010T09000
70 Merchant1 000000028151 OGM100520_01
06V4028740000000001 0519 604391 5201005141104 Merchant 1 EUR Base CCY
06<1 000000000181978 NN
06<A 05190000001356 0000000105050000000579762135609+02
06<B 13911046186 75200001
06#1894 7520 00000000018197800000000000000000 599901P
06#3 000000 0000000000181
06V4266070000000004 0519 153902 5201005141105 Merchant 1 EUR Base CCY
06<1 000000010606978 NN
06<A 05190000002978 0000000106060000000000000135610+02
06<B 13911046188 75200001
06#1894 7520 00000001060697800000000000000000 599901P
06#3 000000 0000000010606
06V4028540000000005 0519 382292 6201005141106 Merchant 1 EUR Base CCY
06<1 000000000087978 NN
06<A 05190000001392 0000000107070000001220990135611+02
06<B 13911046190 75200001
06#1894 7520 00000000008797800000000000000000 599901P
06#3 000000 0000000000087
06V4142590000000001 0519 716421 5201005141107 Merchant 1 EUR Base CCY

80 Byte Population Guide Page 215 of 216

Version 15.93
OmniPay Innovation in Transaction Management

06<1 000000012655978 NN
06<A 05190000001826 0000000108080000000008540135612+02
06<B 13911046192 75200001
06#1894 7520 00000001265597800000000000000000 599901P
06#3 000000 0000000012655
70 Merchant1 000000023529 OGV100520_01
80 000000000051680 000058

80 Byte Population Guide Page 216 of 216

Version 15.93