We have a customer that does a high volume of credit cards. Problems that occur (pc charge, connections, etc.) cause double charges to occur. This has been almost eliminated at this point, but now they have a lab machine at their office with a working merchant number/setup that they correct these duplicate charges on. However, RMS continuely allows a void on the credit card to go through, instead of a return, even thought the return transaction was done on a totally different merchant account (no "vision" of the original sale) by keying in the number. The simple solution is to do them directly through PC Charge, which works fine, but some credit institutions (amex is one) wants to have a sales reciept with each return so we have to do them through the lab register. Sorry for the history story, just wanted to know if anyone else has seen this or fixed this.
I know RMS sends a "3" code for void first, then if it doesn't see the original transaction it denies the void request and resends a "2" code for return. I have captured the .inp file and it DOES have a "3".
HELP! :) Thanks!
Robbie