![IDTECH Vivopay Neo 2 Скачать руководство пользователя страница 245](http://html.mh-extra.com/html/idtech/vivopay-neo-2/vivopay-neo-2_developers-manual_618786245.webp)
NEO 2 Interface Developer’s Guide
Copyright © 2019, International Technologies & Systems Corporation. All rights reserved.
245
Response Frame
Byte 0-9
Byte 10
Byte 11
Byte 12
Byte 13
Byte 14-N
Byte N + 1
Byte
N + 2
Header Tag &
Protocol
Version
Comman
d
Status
Data
Length
(MSB)
Data
Length
(LSB)
Data
CRC
(LSB)
CRC
(MSB)
ViVOtech2\0
84h
Refer to
standard
status
values
XX
XX
List of
Torn
TLV’s
Varies
Varies
The response may contain expiring torn entries. These are returned inside a Discretionary Data
tag, as shown below:
Byte 0-2
Byte 3
Bytes 4-6
Byte 7
Byte 8-N
Discretionary
Data
Tag
Length
Torn
Transaction
Tag
Length
TLV’s for Torn
Record
FF8106h
Varies
FF8101h
Varies
Varies
NOTE:
The terminal should execute the CLEAN command repeatedly, until no more torn
records are sent back to it. In other words, in the final response, the value length of tag
FF8106 shall be 0.
Refer to the M/Chip PayPass specification for the contents of the Torn Transaction Log
Record.
8.6.3.1.
Torn Transaction Log Timer
The reader keeps track of how much time has elapsed for each torn transaction record.
However, it
does not
take any action when this time has expired. Because the interface
between the terminal/POS and the Reader is a command/response interface, cleaning the
torn transaction log must be initiated by the terminal/POS.
Periodically, the POS should initiate a cleaning cycle and repeatedly issue the “Clean”
command (84-0F) at that point until the reader reports that the Torn Log has been
successfully purged.
How the POS accomplishes this is beyond the scope of the interface and this document.