Authorize.net Freezing at Checkout

[Guest]

Authorize.net Freezing at Checkout

 

After spending nearly 5 hours debugging authorize issues, and trying every authnet module I could find in the contributions, I decided to peek at the code and discovered that if your host requires you to use curl through a proxy (like my clients host, godaddy.com), the freeze is what you get dealt by oscommerce. This will be true of all curl modules but I am using authorizenet_aim contribution http://www.oscommerce.com/community/contributions,4091

 

This has caused the following to happen on the clients site.

 

1. Broswer appears to redirect to https://secure.authorize.net/gateway/transact.dll but does not complete the transaction, flag it complete, or anything else.

 

2. Browser freezes and times-out at checkout_process.php and sometimes (seemingly randomly) gets stuck at checkout_confirmation.php.

 

 

Proper Authorize.net configuration:

 

Make sure you generate your API login id and transaction key from the account settings screen on secure.authorize.net

 

Transaction Version: 3 / 3.1

**Response Receipt Urls

Default Receipt: http://www.yourdomain.com/checkout_success.php

Default Relay Response: http://www.yourdomain.com/checkout_success.php

Receipt Method (LINK, GET, POST) doesnt matter. Its passed through the code

Receipt Link Text: leave blank

Silent Post Url: blank

Direct Response: NO

 

 

**Oddly enough there are 2 places to edit the receipt url in my clients auth net account. It doesnt matter where you enter the urls, but I chose to do them both on the same screen under Response Receipt Urls

 

So hopefully this will save someone hours of time and frustration.

 

After installing the contribution, modify modules/payment/authorizenet_aim.php

 

add the line:

 

// for go daddy

curl_setopt ($ch, CURLOPT_PROXY, 'http://64.202.165.130:3128');

 

around line 315 ( around the other curl configuration calls)

 

All you are doing is telling your software to use a proxy instead of making the curl call directly from the hosting server. Go Daddy, and probably other hosting companies use proxies for security. If you arent using go daddy, call your host and find out if you have to make curl calls from a proxt and if so what the ip and port address? Replace the ip and port in the php line and your all set.

 

Eric