Authorize.net AIM error message workaround/solution

I had been getting the following error message when trying to test Authorize.net AIM transactions using the test credit card numbers, as well as when trying my own credit card in production mode:

''Your credit card could not be authorized for this reason. Please correct any information and try again or contact us for further assistance.''

After much googling I found what appears to be a solution on an osCommerce board:

In the file zencart/includes/modules/payment/authorizenet_aim.php, after line 355 in the default file, add this line :

curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, 0); 

I wonder if this is something that will be fixed in new versions? Or perhaps the problem was due to my server settings and not everyone needs this extra line. Well, I hope this helps someone else!

credit: forums.oscommerce.com/lofiversion/index.php/t199381-100.html

has been fixed alrady,

I'm using version 1.3.5 as installed through my webhost's control panel. Maybe the problem was the host, which is Crystaltech.

must have been fixed in 1.3.6 because my version of 1.3.5 doesn't have it either and I DL'd it from the download page.

After adding this, I got an error from the page saying that wasn't a valid cURL command.

Now I can't get any credit card orders in. I've never had a problem before and cURL proxy has always been false since I've started. I was getting orders this morning but now I am getting errors from my own test and one other customer that brought it to my attention.

Thoughts? I'd at least like to get the correct error. Im not sure if I ever got the correct error tho. What would my cURL proxy be? something I'd get from my webhost? or something from my SSL cert? or authorize.net?

qhome:

What would my cURL proxy be? something I'd get from my webhost? or something from my SSL cert? or authorize.net?

CURL proxy details would be provided by your webhost, since it pertains to their firewall+network configuration.

Turns out they had a hiccup on their end and all is well once again. The error still doesnt elaborate on what it is.. so there may still be a cURL proxy issue.. but at least the money is flowing again :)