Previous Topic

Next Topic

Book Contents

Book Index

RB D05 - Invalid record type

Record Type is a five-character, alphanumeric field containing record type information and it corresponds to Dnnnn, where D represents the detail record and nnnn represents the record type and is used for all merchants. The system validates the data element type of this field.

Possible Causes

Solutions

Level II data is being sent and they are not set up to accept Amex Level II transactions.
  1. Update the Format Code in the boarding system to '20' for Amex CPC.
  2. Transmit the batch.
    • If the batch rejects on the same transaction, restage Amex, restart the POS device, and then attempt to transmit the batch.
    • If the batch still rejects void the transaction from the batch then attempt to transmit the batch.
  3. Offline the failed transaction(s) back into the POS device then settle the batch.

Incorrect record type in the download file
  1. Correct the record type and retain the batch.
  2. Perform a partial download and re-transmit the batch.

The terminal data for this field may be corrupt

Verify the record type in the terminal.

  • If valid, retain the batch and re-transmit.
  • If invalid, correct the record type in the terminal and re-transmit.

Settle to PC flag set incorrectly

The Settle to PC flag should be set to N on standalone terminals:

  • Correct the Settle to PC flag, perform an initialize / partial download, and then re-transmit.

Settle to POS-Partner flag is set incorrectly

If the POS-partner is settling to VisaNet:

  • The Settle to POS-Partner flag should not be checked under setup-services.

If the POS-partner is settling from one PC to another PC:

  • The Settle to POS-Partner flag should be checked under setup-services.

Incorrect Visapc.ini setting (POS-partner 2 only)

In Visapc.ini, under Configuration Options, change Settle ODG 24 to equal NO.

NO must be in all caps.

In addition to the above, the following can also occur for StackM/Central Cashier merchants using DRR applications.

  1. After deleting the transaction and re-entering via the ATM re-enter key, there is still a RB D05.
  2. From e-Connections, go to the transaction information for the card being rejected. See the Card Type. This should be OT. If it is VI, this means the merchant took a credit card debit, but the card did not fall into any of the Sharing Groups to which the merchant subscribes.
  3. Also note the Record Type in this screen. A good ATM Record Type is D@@H@. The rejected card probably receives a Record Type of D@@@@.

Possible Cause

Solution

Incorrect Sharing Group

Re-enter the card into the System as an Offline Purchase.