/includes/modules/payment/authorizenet_aim.php
around line 654 you'll see:
Code:
curl_setopt($ch, CURLOPT_TIMEOUT, 15);
curl_setopt($ch, CURLOPT_CONNECTTIMEOUT, 15);
the CONNECT timeout is for "making a connection" to the AIM server.
The TIMEOUT is for the final response after connection.
15 seconds is a LONG time to complete a transaction. That's a LONG time for your customers to have to wait.
And if it's taking 15 + 15 = 30 seconds, then you should be investigating WHY it's taking so long ...whether it's something with your hosting company's server config, their connection to the internet, or Authorize.net's own network (they've outsourced it to Akamai, so maybe there are problems there).
Extending the timeout is NOT the proper solution: it's only a bandage. While it may work, it's leaving your customers hanging for a very long time ... and likely to result in multiple transactions because they give up.
Extending the timeout will NOT stop customers from refreshing/resubmitting. And thus will NOT stop the multiple-charge problems.
Bookmarks