Forum Moderators: buckworks
We use Authorize.net and have contacted them and they say there is nothing wrong, yet one can find blogs out there where there have been complaints about this problem and the common denominator was Authorize.net.
Results for the same credit card can differ .. sometimes AVS failure (no match on street/zip (N)) to insufficient information (U). In the later, AVS is not applied and the transaction gets approved.
Is this a common problem with AVS in general, or is authorize.net having a problem?
What was interesting in this case is that they were able to process is charge w/o address verification but when (after customer's approval) I had to charge a small amount extra for shipping, it declined the same card on AVS no match.
We've had other cases (international orders) where us manually adding the extra shipping onto a customers card did not affect how AVS was handled.
I don't know who (what system/subsystem/entities) actually does the AVS, but it looks like somewhere along the line there is an inconsistency in when AVS gets invoked.
Who makes that decision for a card (e.g. is it Authorize.net) and why would the decision (international vs non-international) vary when it can be demonstrated (documented issuing financial institution) that the card is outside the US?
We are OK with how AVS is handled in the US, it's just the international orders / international cards that we'd like AVS to keep its "paws" OFF!
Thats why we always ask for the bank phone number when taking an international order. We just call the bank and verify that the name and address matches the one on record with the card.
When an international card is forced into AVS, it fails and the customer cannot place their order and often will not even contact us. I don't think AVS should be invoked, but who do we contact if Authorize.net says there are no problems.
I hate to lose customers. Our merchant services guidelines/best practices says to use AVS, so we need to keep it active for US but turn it off for international orders. I don't think that's do'able with Authrorize.net. Or, maybe there is a way to do that?