RB D93 - Bad ODG 32

Possible Causes

Solution

Bad ODG 32 (POS Data Group).

First try to resettle the batch.

If error persists, advise the merchant to contact their software provider (i.e. PC Charge, etc). The software provider can then contact our POS lab so that we can scope the transmittal or obtain a log from the merchant. We cannot tell them the exact issue without a scope or log.

Note: If TSYS is the software provider, contact the TSYS POS Lab (x7878) for help escalating this for a scope research.

A transaction is corrupted.

1. Delete the transaction that invoked an RB.
2. Settle the batch.
3. Offline the corrected transaction and re-transmit.

Note: If the delete feature is not available, delete the batch, offline corrected transactions, and re-transmit.