Good morning,
We are using AVS, and unless the AVS results in a success response code, we do not accept the payment on our website.
The concern comes from customers that insist they are providing the correct address as it appears on their statement from the bank, but it still is not getting accepted. When we examine the response codes, these problematic ones are usually a code of W (Postal code matches, street address does not).
How sensitive is AVS? Is it a direct 1:1 match with the address on file at the bank? Are there tolerances for say abbreviations?
Is it up to the bank? If my statement says Avenue, but I use Ave during payment, is it rejected?
Thank you!
In reply to RR_Moneris:
Thank you for the response! While I was waiting, I did some more reading and I found (on Wikipedia) that AVS only considers the street number, and zip/postal code. So if on Address 1, the customer includes their street number and perhaps their unit or PO box, those additional numbers can cause the validation to fail.
As for what we're doing, we're using a PCI-DSS compliant payment processor. It takes the customer payment details and sends them off to Moneris. I'm not exactly sure how it's doing this, but there are only two address text boxes. I'm willing to bet part of the problem is what I described in the first paragraph. Customers are probably entering too much information there and it causes the street portion of the address validation to fail.
However - this assumption is all riding on whether or not what I read on Wikipedia is accurate - does AVS really only care about the street number?
In reply to GroundHog: