Unable to authorize payment: This transaction cannot be accepted.

[newguyintown]

We use Authorize.net for our CC payment gateway. We are getting this message and are unable to process any CC transactions. I have chatted with a CSR at Authorize.net and they claim there's no way to help me unless I can get a "response reason code" for one of the failed attempts. I spoke with my host and was told due to the circumstances, there wouldn't be an code in MM for these transactions and the answer lies somewhere with Authorize.net. My host has yet to fail me, so I am sure they're right. However, this means I am stuck and the site isn't processing CC's until I figure this out.

Ideas?

[ILoveHostasaurus]

Re: Unable to authorize payment: This transaction cannot be accepted.

They're correct in that there is no way to find what the exact response code is because Merchant doesn't log it and has no way of logging it since it all occurs internal to the module. However, I've never seen this particular issue not caused by authnet or a setting on the authnet side. One of the more common issues is a problem with the merchant account and authorize.net just passing the issue back to the store where it doesn't know what to do, and then their support having no idea how to diagnose the problem. Are you still able to run a transaction via the virtual terminal in the authnet control panel? Try that and see if you get any errors. If no errors there, investigate the security settings area of the authnet panel and see if you have any anti-fraud filters turned on that could be causing it. Also see if you have hit any daily limits on either transactions or sales volume if it's been a busy day. Finally, see if there are any IP address restrictions in the authnet control panel set up, if there are, clear them and see if the problem goes away, if it does, check with the host to see if anything changed on the server.

[d_host]

Re: Unable to authorize payment: This transaction cannot be accepted.

Rex,

Do you get any of the transactions recorded in the Authorize.net history at all? Can you see if the history there shows any specific error codes on the Authorize.net end?

Even if a transaction was to fail or not go through, they should have a record of it in their system with whatever response code they are seeing on their end. That should, hopefully, help them figure out what the problem is and point you in the right direction.

If none of your test transactions are even making it to Authorize.net, that would be a different story. As David suggested - check to see if there are any IP restrictions in your account to allow transactions only from those IPs. That would be my first guess if you did not see any of these transactions at all even make it to their system...