Three separate customers on three different days have all experienced an anomoly while manually entering a credit card. The system returns a three digit authorization code and completes the transacation.
At the end of day, the EDC batch fails because the transaction was not correctly approved. The store ownere is then left holding the (empty) bag. The processor is Tysys.
Here is what the credit card folks are telling my customer:
This is concerning the issues on false issuance of authorization codes.
We have researched this matter in depth and all we can see is that this happens and only happens when a card is keyed in and only if the card # is input incorrectly. The following is what our records indicate on these transactions. .
When the incorrect card # is submitted it is then sent back as a bad card error and RMS then tries again to get an authorization. From there all we know is that somehow the transaction winds up in the batch with a 3 digit authorization code.
And the end of day the batch is submitted by RMS and the system then generates an error code and two seconds later self corrects (by removing the bad transaction) and resubmits the batch obtaining a good batch authorization resulting in the batch closing missing the bad transaction. There is no way for us to retrieve the card data on a transaction that was not actually authorized.
Recommendation to avoid this until situation is resolved. When a card is keyed and only when a card is keyed and authorized check the authorization # on the receipt to verify there is a 6 digit authorization code. This is only for when the card is keyed.
Anyone else experiencing this problem?
David Walker
*This post is locked for comments

Report
All responses (
Answers (