02-25-2015 11:44 PM
When I submit authorizeAndCapture (AuthorizeNetAIM) on sandbox it gives me this " Error connecting to AuthorizeNet" message. Is the sandbox down? I'm experiencing this since yesterday.
[_response_array:AuthorizeNetAIM_Response:private] => Array
[error] => 1
[error_message] => Error connecting to AuthorizeNet
03-31-2015 10:53 PM
I'm having the same issue since today. I think the problem is in the SDK - PHP as i'm able to connect with Curl.
I know they made some maintenance on the sandbox today. Anyone else with a similar issue?
04-01-2015 02:10 AM - edited 04-01-2015 02:12 AM
They are working on the SSL cert, should be working now. If you are still having issue, read this
04-01-2015 12:57 PM
All my sandbox project just started throwing the same error:
Response Code: 3 Response Subcode: 1 Response Reason Code: 261
Is this the same issue? The SSL cert and CURL fixes didn't help. I also can't create a new sandbox account right now....
04-01-2015 01:37 PM
We are currently investigating an issue with our sandbox server that is causing it to return response code 261. We're working to get it back up as soon as possible.
I apologize for the inconvenience.
04-01-2015 02:44 PM
We're still working on some of the systems and doing some additional testing, but as of now transaction processing should be back up. Please let me know if you continue to see any errors.
04-03-2015 09:51 AM
For the last few days the auth.net environment has been sporadically failing to respond. No code or text has been provided. When will it be fixed?
response_code = , response_reason_code = , response_reason_text =
04-06-2015 07:47 AM
Ever since March 31, I am still having problems getting the sandbox to work UNLESS I turn off "Verify SSL Certificate". I am using osCommerce and the add-on for Authorize.net, AIM module, ver. 2.1. I have seen postings elsewhere about replacing the PEM file, but in the osCommerce add-on module for AIM, if I am looking in the right place, there are two files that (to me) seem relevant: authorize.net.crt, and cacert.pem. The latter is not used if the former is present. Is a pem file the same thing as authorize.net.crt? I tried getting a new PEM from Github, and replacing the existing cacert.pem (while at the same time removing authorize.net.crt so that the pem file would be utilized) but that did not work. And, in case the new pem is the same thing as authorize.net.cert, I then tried replacing the old authorize.net.crt with the new pem file, but that didn't work either. I am pretty much in the dark here. Any suggestions?
04-06-2015 12:16 PM
Connecting to sandbox was working OK last Friday (Apr. 3), but can't connect today (Monday, Apr. 6). AIM SDK just returns "Error connecting to AuthorizeNet". Is sandbox down for maint. or something else broken?