![IDTECH Vivopay Neo 2 Developer'S Manual Download Page 221](http://html.mh-extra.com/html/idtech/vivopay-neo-2/vivopay-neo-2_developers-manual_618786221.webp)
NEO 2 Interface Developer’s Guide
Copyright © 2019, International Technologies & Systems Corporation. All rights reserved.
221
Data Field
Length (bytes)
Description
SW1
1
Value of SW1 returned by the Card (SW1SW2 is 0000 if SW1
SW2 not available)
SW2
1
Value of SW2 returned by the Card (SW1SW2 is 0000 if SW1
SW2 not available)
RF State Code
1
RF State Code indicating exactly where the error occurred in
the Reader-Card transaction flow. See sub-section on
TLV Track 2
Equivalent Data
21 (including Tag &
Length)
Track 2 Equivalent Data as a TLV object.
Tag: 57 Format: b19
Amount Requested
6
Difference between the Terminal Contactless Transaction
Limit (FFF1) and Balance. Format: n12
If the Status Code is “User Interface Event” then the format and contents of the data field in
the
Response Frame
are given in the following table:
Data Item
Length (bytes)
Description
Transaction status
1
01: The reader detects the card and initiates the transaction.
For any other Status Code the data field is empty.
If the transaction failed, the
Response Frame
may have the following format. Invalid or
inappropriate cards may result in no
Response Frame
.
Activate Transaction Response Frame Format, Failed Transaction: 02-01 Command
For 02-40, see further below.
Data Item
Length
(bytes)
Description
Error Code
1
Error Code giving the reason for the failure. See sub-section on
SW1
1
Value of SW1 returned by the Card (SW1SW2 is 0000 if SW1 SW2 not
available)
SW2
1
Value of SW2 returned by the Card (SW1SW2 is 0000 if SW1 SW2 not
available)
RF State Code
1
RF State Code indicating exactly where the error occurred in the
Reader-Card transaction flow. See
TLV data
Varies
Refer to the