|Disabling AVS mismatch|
I have same problem as jrockfl
|Hello! I have been reading over these forums and finally decided to join. |
Currently, we're using Authorize.net and Chase Paymentech for credit card processing.
We have AVS enabled, but we get a lot of calls about customers thinking we have billed them twice and we have to explain it is an AVS mismatch, etc.
Tonight we had a customer that had a total of 3 transactions, the first 2 two were AVS mismatch and I had to hear how this was an inconvenience to her and she has bills to pay, etc.
How do you handle AVS mismatch?
and i am thinking about disabling the AVS feature. Cause we have very low % of fraud orders anyway. In fact we have 0 cases when somebody tried to buy smng using fake(stolen) credit card info - mom and baby niche;)
However i see that sometimes the people forget about that they changed the address, so i see them submitting billing address 1, than they see the AVS mismatch error and resubmit using correct address 2.
How this situation will be handled if the AVS mismatch is disabled?
Let say customer made order using his old address? Or new address which is not yet updated with bank...
Will authorize.net still be able to charge the card?
You can use the Fraud detection suite with your own rules
and upon manual review you will be able to capture the found later
I have had AVS mismatch turned off for years. I found that it gave a mismatch for people whose billing address was a PO Box or often if they lived on a numbered street, not to mention that it is mostly useless for international charges. I have not noticed an increase in fraud. I do use authorize.net's fraud suite, though, and disallow certain countries, rapid-fire ordering, and certain ips. Works, no evil eye.
HRoth, you are right. I was loosing some customers who tried to make order, and than never come back. I just turned it on, and see some good effect.
Can you tell me more on "I do use authorize.net's fraud suite, though, and disallow certain countries, rapid-fire ordering, and certain ips."
What's are the best basic settings? All my orders coming from US.
p.s. I wish 300% increase in profit to all webmasterworld ecommerce owners in 2013;) Happy New Year!
We have loosened up the settings and now we rarely have the problem anymore. Only of if the input the 3 digit code on the back of the card incorrectly. We have it fail the the transaction.
Every order goes through our own little fraud score check.
We look for things like billing address not matching shipping address, express mail, ordering 3 or more of the same product.
Things like this force the product into a "Pending" status and has to be reviewed manually.
Authorize.net's fraud suite can disallow any transaction coming from any particular country or even whole continents. You can set it to disallow certain ip addresses if you have a pest who keeps using the same ip. You can set it to not allow people to repeatedly attempt a transaction because they have a bunch of stolen credit card numbers and are just trying to find a match--I have had in the past an individual who would try 30 numbers in a row, which is why I enabled fraud suite in the first place. You can set it so that it will reject a transaction for these reasons or let it authorize and just alert you to these things. So I have mine set so that if the ip address does not match the billing address, not in the same area, it will authorize but I will get a heads-up. This works well for me.
There are a lot of different settings in the fraud suite. I don't use most of them, because I am lucky that I don't get a lot of fraud. But I do get persistent fraudsters.
If I did not allow people to have a different shipping and billing address, I would lose a lot of business. Many people like to have stuff shipped to their job. I do make the CVV match mandatory, though, although I have read that stolen card info has that as well. But usually it will get you a slightly lower discount rate if you do that.
I could be wrong, but I thought if you disabled avs checking your transaction fee went up?