NEO 2 Interface Developer’s Guide
Copyright © 2019, International Technologies & Systems Corporation. All rights reserved.
218
Tag
Description
Format
Length
(in bytes)
0 0 1 0 = TransArmor Algorithm
0 0 1 1 = Voltage Algorithm
0 1 0 0 = Visa FPE
0 1 0 1 = Verifone FPE
0 1 1 0 = TransArmor TDES-DUKPT
Bits 4 to 6: Reserved
Bit 7:
0 = No MAC Verification Data
1 = Has MAC Verification Data
DFEF73
CUP Output Message Info (CUP)
Byte 1
b8
b7 b6 b5 b4 b3 b2 b1
- - - - - - - X Authorisation Message
- - - - - - X - Confirm Message
- - - - - X - - Reversal Message
- X X X X - - - Terminal Floor Limit Check
X - - - - - - - Date Exprired
b
1
DFEF7B
If tag DFEF7A value is set to 1, after reading the card the
output data will show tag DFEF7B to indicate Apple Pay or
Google Pay.
If tag DFEF7A is not set, the output data will not output the
tag.
0 = Not Apple Pay/ Apple VAS or Google Pay/ Android VAS
1 = Apple Pay or Apple VAS
2 = Google Pay or Android VAS
FF8105
Data Record (MasterCard, container).
Contains the data from the transaction. Refer to the M/Chip
PayPass specification.
b
varies
FF8106
Discretionary Data (MasterCard, container).
Contains the discretionary data from the transaction. Refer to
the M/Chip PayPass specification.
b
varies
FFEE01
ViVOPay Group Tag. (container)
This three-byte Group Tag was created to contain ViVOpay
proprietary Tags. See tags below.
b
<=76
If a Clearing Record is returned, its potential TLVs are described in the following table.
Different card applications may have a slightly different format, or different TLVs, for the
Clearing Record. MasterCard M/Chip 3.0 does not return a clearing record.