![IDTECH Vivopay Neo 2 Developer'S Manual Download Page 34](http://html.mh-extra.com/html/idtech/vivopay-neo-2/vivopay-neo-2_developers-manual_618786034.webp)
NEO 2 Interface Developer’s Guide
Copyright © 2019, International Technologies & Systems Corporation. All rights reserved.
34
Error
Code
Description
Reason for Error and Suggested Error Handling
62h
Generic Error
This is a generic or general error that is reported when a more specific reason for the
error is not known.
73h
Torn Transaction
Log Error
An error occurred while attempting to clean the torn transaction log. This might
occur if the reader could not read the time and date from the real time clock.
80h
No Merchants
have been
configured
This error usually occurs while MerchantID is empty.
81h
TLV Parse Failure This error usually occurs when failing to TLV parsing card response data.
82h
Merchant Data
Error
This error usually occurs when no merchant data is returned from the card.
83h
System Memory
Error
This error usually occurs when failing to read or write system memory.
84h
Application Skip
Error
This error usually occurs when configuration isn’t consistent on whether or not to
skip payment application.
85h
Application
Version Error
This error usually occurs when the application version number is incorrect.
88h
LTPK Error
This error code indicates the LTPK (long term private key) hasn’t been loaded.
If an error occurs during a transaction and the terminal determines that the reader must
perform exception processing, then the terminal must retry the transaction until the
transaction has been completed successfully or the terminal decides to abort. The retries must
be continued even if successive transactions fail with conditions that do not require exception
processing. This must be done to allow the reader to complete exception processing (even if
there are failures during exception processing).
Under certain conditions, such as when a customer walks away or there is a problem with the
card, the terminal may want to abort the retries even if the reader has not been able to
complete exception processing. How and when the terminal stops retrying is out of the scope
of this document.
2.3.
RF State Codes
For some Error Codes, the RF State Code indicates the exact reader-card command that failed.
This helps determine the exact place where the failure occurred.
RF State Codes
State Code
RF State
Description
00h
None
RF State Code not available
01h
PPSE
Error occurred during PPSE command
02h
SELECT
Error occurred during SELECT command
03h
GPO
Error occurred during GET PROCESSING OPTIONS command
04h
READ RECORD
Error occurred during READ RECORD command
05h
GEN AC
Error occurred during GEN AC command