Possible Causes

Solutions

For VT13DA8 software:

When scrolling through to adjust tips, the merchant pressed Enter to bypass transactions that did not need a tip.

1. Retain the batch.
2. Perform tip adjust for all transactions.
3. If there is a valid tip amount, re-enter the tip amount.
4. If there is not a valid tip amount, press 0, and move on to the next transaction.
5. When finished, transmit the batch.

SETTLE TO PC is set to "Y."

1. Update the file to indicate SETTLE TO PC = N.
2. Perform a partial download and re-transmit.

If the has retail software with a Hotel MCC code and the format is set to 11, which is for hotel software only.

-or-

If the merchant has hotel software with a Hotel MCC code and the format is set to 10, which is for retail software only.

1. Update the file to the correct format code.
2. Perform a partial download.
3. Re-transmit the batch.

For VT1TPH5 software:

American Express transaction where Folio number is blank or '0.'

1. Delete the transaction, offline it back in with a valid folio number and re-transmit.
2. Advise the merchant that the folio number must be 1 or greater.

For VT1H385 software:

American Express transaction where Purchasing Card is enabled.

1. Turn the Purchasing Card flag off.
2. Void all AMEX transactions in the batch.
3. Settle the batch.
4. Perform a partial download.
5. Offline the AMEX transactions back into the terminal, and settle the batch.

For VT1H385 software:

American Express transaction where Split Dial is enabled.

1. Delete all AMEX transactions.
2. Transmit the batch.
3. Offline the AMEX transactions back in and transmit.

Deleting these transactions may be difficult. These transactions will appear to be corrupt. You must view the details (not print) in the terminal. Write down how the Reference Number, Account Number, and Dollar Amount appear in the terminal. If the dollar amount is zero, you must first adjust the amount to $0.01, and then delete the transaction.

For Hypercom terminals uploading to POS Partner 2000:

If RRADDMERCHANT flashes on the screen,  it means that POS-partner 2000 was not activated with the terminal hierarchy.

Either the activation did not contain the V-number of the terminal or the merchant information in POS-partner 2000 does not match the terminal hierarchy.

For POS Partner only:

The Settle to POS Partner is flagged on in the Services screen.

If POS -partner is settling to host, make sure Settle to POS-partner is flagged off in the Services Screen under the Setup Menu.

This is flagged only in a PC-to-PC settlement situation.

For POS Partner only:

Check to see if a transaction has received "dual" response of exception and approval code.

1. Void/delete the same transaction and transmitted batch accepted.
2. Offline voided transaction and transmit batch.

A transaction is corrupted.

Check e-Connections and view the detail of the batch that received the RB.

All charges received (up to the one causing the error) can be verified in e-Connections. The next transaction NOT shown would be the transaction causing the error.

Void the transaction causing the RB and re-transmit the batch. (If it is hotel software, delete the transaction and re-transmit.)

For a ZON or TRANZ terminal:

The merchant entered an invalid expiration date on a keyed in offline or credit/return transaction.

Some software programs on ZON and Tranz terminals allow less than four-digits to be entered for a credit card expiration date.

1. Void the transaction causing the RB.
2. Re-enter the transaction using the proper expiration date format of MMYY.
3. Retry batch settlement.

Incorrect or invalid terminal data

1. If GB is not received, verify that the terminal data is valid as well.
2. Ensure the BIN, Date, Transaction Code, Device Code, and Batch Number fields are correct in the terminal.
3. Correct the fields that are not valid.
4. Re-transmit with the corrected information.

Incorrect date or time

1. If still receiving RB, set the calendar clock.
2. The batch then must be deleted because an invalid date was attached to the transactions.
3. Then, perform a live transaction to be sure the current date is correct, and have the merchant offline the transactions back in.

For Re-Enter Transactions (Debit, EBT or POS Check):

An incorrect Trace number my have been entered.

1. Void the transaction causing the RB.
2. Re-Enter the transaction with the correct trace number from the original receipt (this number must be six-digits).
3. Re-transmit the batch.

For Re-Enter Transactions (Debit, EBT or POS Check):

An incorrect Retrieval Reference number may have been entered.

1. Void the transaction causing the RB.
2. Re-Enter the transaction with the correct retrieval reference number from the original receipt (this number must be 12-characters).
3. Re-transmit the batch.

For VT1TPH6 software:

Incorrect settings

This problem was corrected with the release of version 6 of VT1TPH6 on 7/31/00. If the last DLL date is before 7/31/00, perform a Master Reset and FDLL.

Unknown

1. Perform a master reset and download.
2. Offline the transaction into the terminal.
3. Re-transmit the batch. If the error still persists, refer to Merchant Services.