Error in Batch

Error In Batch

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
  1. Menu
  2. System Settings
  3. Database
  4. Clear Transaction
  5. Enter the Transaction # (The terminal will confirm if you want to delete it)
  6. Then Batch the remaining transactions

Forced Transactions
Do a forced transaction for the transaction that you just was deleted (This can only be done from a Standalone terminal and not from a Semi-Integrated terminal i.e s300, sp30s etc.)
On the terminal:
Press the down arrow until SALE changes to FORCED or on an S80 press F4 until it changes to FORCED.
Enter the amount of the forced sale
Enter the card numbers manually
Enter the Auth Code from either the original sale receipt or provided by the host
Press Enter to complete the FORCED transaction

***If the forced transaction does not process the caller will need to speak with the host about how to receive compensation for this transaction***



    • Related Articles

    • Send Error

      Host response. This error appears when batching. Contact the host to determine what is wrong with batch or if there are any bad transactions in the batch. The host will be able to inform you why they can not accept the batch information. 

    • 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 ...

    • Invalid Track Error

      The error message listed above means that the information on the Magnetic Stripe cannot be read by the terminal. The Mag Reader could be dirty, or the card is dirty. You can clean the Mag reader by taking a paper towel and running it though the mag ...