approval codes


R

root

A cashier did a manual entry of the cardholders number for a card that would
not swipe this weekend. The number was entered properly, but the expiration
date was off by one year. We got an approval code anyway.

He caught it as it was going through, so he called me over to do a void. I
recalled the sale for the void but RMS would NOT let me void the
transaction. It said an invalid card number was detected. NOT GOOD.

I eventually made it work in a round about kind of way... I did a Force
Return (made up term) with the same approval code then re-sold it with the
proper cc number (to keep our sales for the day balanced), then manually
went into the database and maked the 2 bunk entries as voids to avoid any
settlement issues.

We had this type of issue with the actual 16 digit card number in the past
and changed our masking technique to # to avoid this type of problem, but
there is not much you can do with a number that is the proper length.

WHY can an approval code be given to a BAD NUMBER?

The even bigger question WHY can that transaction not be voided anymore.
(you used to be able to void it)?????

I do not expect an answer in the forum. I will be submitting this query to
Tech Support, but thought people should know.
 
Ad

Advertisements

R

root

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
 
J

Jeff

root,

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



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
 
J

Jocelyn

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
 
R

root

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.
 
Ad

Advertisements

R

root

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

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top