Switching from secure2.authorize.net to secure.authorize.net in our AIM
connection (https://secure.authorize.net/gateway/transact.dll) seems to
have helped. Something is wrong with the new URL?
Any update on this? I don't have access to our customers' live
Authorize.net accounts but we're seeing a similar behavior where there
are a LOT of timeouts starting today. My immediate concern is I hope
people aren't making duplicate payments by tryi...