This typically occurs on Tsys applications. It means there is a bad transaction in the
batch.
To resolve this issue the reseller or merchant needs to contact the host to find out which transaction has an issue and collect the card information needed i.e transaction number, last 4 of the card used, and the transaction amount.
On the terminal, we need to DELETE the transaction
- Menu
- System Settings
- Database
- Clear Transaction
- Enter the Transaction # (The terminal will confirm if you want to delete it)
- Then Batch the remaining transactions
Related Articles
Send Error
This is a Host response. this error appears when trying to close the batch. Contact the host to determine what is wrong with batch or if there are any corrupted transactions in the batch. The host will be able to inform you why they can not accept ...
HTTP Host Error
HTTP Host Error: This is a batch error from the host. It indicates that there is an issue with the batch URL. If the customer has never had issues batching, you can redirect the caller to the host to determine if they are experiencing any issues with ...
Comm Error/Communication Error
Comm Error This error occurs when trying to connect a Semi-Integrated terminal (SP30s, S300 etc.) to a POS or after processing a transaction. The POS can be the merchant's computer system or a PAX S80. The error will appear on the PAX terminal and it ...
Invalid Batch Sequence
This error occurs on First Data Omaha applications. This happens when the batch number in the terminal does not match the batch number the Host is expecting. Omaha's Batch numbers range from 0 to 9 You can attempt to increase or decrease the batch ...
Handshake Error
Handshake Error: This occurs during a Firmware Update The terminal is not connecting to PAXSTORE or the firmware server. If this happens during a Firmware update make sure you are using the correct Port #, IP Address, and TID. Also, verify the port ...