This is a follow-up post to a problem I asked about to relate what I have found in case any one else may find it useful. Sorry, it is a little long.
Occasionally when a cashier swipes a credit card they may get a pop-up notifying them that the card number may not be valid. The box has two options, OK or CANCEL. Depending on how good the card read was, if you choose OK the credit card validation may go through fine without any intervention. Today I confirmed this is the source of many non-qualifying transactions, where the card clears as "MANUALLY ENTERED". The field RequestAccountDataSource in the VisaNetAuthorization Table value will be T (manual) instead of D (swiped). Besides paying more to your porcessor, you are also at risk if there is a chargeback because you may need a card imprint if the card status was not 'SWIPED' to prove the card was present. There is another field that does show card was present, but I have had a chargeback issue of this type already.
We have been re-training our cashiers to make sure they hit CANCEL on the credit card warning pop-up, but that is not fail-safe. I had not gotten a response to this question before, but maybe someone who is better versed in SQL can answer if it would be possible to have a trigger to check the RequestAccountDataSource value and prompt the cashier to get a card imprint if the status comes up a T, manually entered.
Marc