QUOTE (Ayla @ Sep 21 2009, 09:11 PM)

Is anyone else having a problem w/ authorize.net,
I am getting declines w/ only reason being:
Security Information
CVV Response: Unavailable
AVS Street Response: Unavailable
AVS Postal Code Response: Unavailable
Customer A:
Order 2046 & 2047 declined, then she tried again Order 2048 and got approved (all same cc info, all one minute apart)
Customer B:
Order 2050 declined, then person tried one minute later and it got approved Order 2051 (again all same cc info).
I believe there is a setting on authorize.net to decide to decline if response unavailable, is this safe to change to approve if it's just bec. response is unavail? Never ran into this issue in a year & a half of having this site but remember a couple others over past month or two as well. Also wonder what customer is seeing, does it just look like it didn't go through so they hit send again?
No it's not safe when unavailable because it isn't verifying the information. It's usually not an authorize.net error, it's usually the issuing bank that is not returning the information for Authnet to verify. If you disable authnet when unavailable its the same as turning off address verification completely. Remember that Authnet is not the only one that runs maintenance, the issuing banks do this as well and that's usually when you'll get an error like this. If you continue to get these I'd call authnet and see if it's something on their end but they boast a 99.9 uptime.