approval codes

root,

First, expiration dates don't really matter anymore, so don't bother with that again.

Jeff,

Thanks for the link. An interesting read..

We are running 1.3.1004

I'm not sure how the error used to be pre-208 hotfix, but the message box I saw said something to the effect of "invalid card number detected" and then it proceeded to display the cc tender window with the credit card number field and the expiration date fields were empty. The approval code field was locked out.

Thanks for the scoop on the exp dates!

This sounds like the .0208 hotfix did not carry over to the .1004 release. hmmm

root,

I just tried it on a 1003 machine and everything worked OK. I'll try a 1004 or 1005 later today.

In addressing and working with our Technical Errors, I have learned way too much regarding the back side processing. We are not on Vital, so this may not be of any validity to you, but I do know that our Gateway host (MerchantLink) will approve any sale transaction because 'they get paid' from that too. So the result is, any card gets approved. Gateway gets the info> passes onto Processor> Processor to card holder's bank> bank does not assign approval code, just an OK response> Gateway assigns approval code. But, you would think they would not receive an ok response when things are not ok. We hold a private label card with a preamble similar to Discover (starts with a 6) but, we have learned that if the card is entered without the 5 digit preamble, it is still receiving an auth code, and erroring in settlement. This was a lovely way to find out as the actual people who host our private label for us gave out the bad card numbers. Anyway, I think you should try to talk to Vital and find out why they would auth an invalid card. My guess is because the card number is in full, and they do not match up the dates. But, I think it all comes down to people trying to get paid. Out of curiosity, in the past when I flag a trx as 'void' in the SO Database, I can only remove so much of it. I understand this is because RMS has something like 96 tables that a transaction is put through. When you void a transaction, are you going through the same motion? Just setting it's status = 1? Then what do you do? How do you compensate for the commissions on the item, the inventory (obvious answer), etc.?

Joceyn

"root" wrote:

basically, have patience, coffee, and time to sort it out.

When speaking to VITAL, they have been of no assistance. At least the CC exp date info that Jeff pointed out will eliminate the need to panic over that type of data entry eror.

looks like the approval code field lock-out part was fixed in 1005.