Just to add this to the people that are having difficulties with this module, I searched through the thread and decided to update this so you dont have to read all 34 pages to find your answers.
The most widely known issues with this module are for people that have it installed on a Windows Server and it has difficulties with cURL paths
Some people use a cURL proxy server, which needs to be setup, make sure you have the latest version of this module so that it comes with the CURL proxy server path in the admin area of your control panel.
Do this mod to your authorizenet_aim.php file
Find these lines and make them look like what appears here
curl_setopt($ch, CURLOPT_URL,$url);
curl_setopt($ch, CURLOPT_VERBOSE, 0);
curl_setopt($ch, CURLOPT_POST, 1);
curl_setopt($ch, CURLOPT_POSTFIELDS, $data);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, FALSE);
The above makes the proper error messages appear on your page.
This thread corrects the error message appearing in the address bar for people using the Simple Template Systems addon. It will now show up at the top of the page in the actual table, and its quite nice.
http://www.oscommerce.com/forums/index.php?sho...mp;#entry824441
Make sure you have SSL installed and its working correctly, you can tell if everything is good if you use your internet browser and their is a padlock in the bottom right hand corner or if you go to the file menu and click view, view source. in the first few lines of code in the window that pops up, find the tag labeled BASE HREF it should say HTTPS://yourdomain.com not HTTP://yourdomain.com
Make sure it is not a shared SSL, if it is make sure you contact your webserver provider and speak with them about gaining the necessary paths.
The V121 fix for this module is useless and doesnt solve or correct anything, and its been giving people a.net errors with duplicate transactions. Make sure you remove this mod if you have the latest module.
Make sure when you signed up for a.net it was configured for AIM 3.1 By default, the a.net control panel is configured for AIM 3.0, you have to make it version 3.1. If your a.net account is old, it may be using SIM mode. You must contact them and tell them to make it use AIM mode
A lot of the problems I experience were because my payment processor (the people that run your merchant account) was not setup correctly, it was declining every single card due to an internal error. Call them and verify they are setup and ready for a.net to be run on their servers. Most of the time this isnt a problem because a.net is a huge company and most merchant account services are ready for a.net services upon request. But sometimes the smaller ones are not, or there was an error, but just to be safe, give them a call, it will save you a lot of hassle.
Make sure that in the admin panel of oscommerce for this module, you are using your API login id and not the a.net login id. The way Vger worded the field made some believe he meant that your a.net control panel login ID was to be used, this is not the case.
Generate a few new transaction keys and be sure and disable the old ones if you are having errors.
As for hiding credit card numbers in the database you can use this mod
/catalog/checkout_process.php
Find this:
'cc_number' => $order->info['cc_number'],
and replace with this:
'cc_number' => (substr_replace($order->info['cc_number'], ' xxxx xxxx ', 4, -4)),
OR to totally remove this function from putting anything into the database, edit the above file and comment out cc_number, cc_expires, cc_type and cc_owner.
This will force oscommerce to not put anything into the database as far as credit card numbers go. Also do this samething with orders.php located in catalog/includes/classes around line 154. This is important as it will be mandatory in the near future, you are not allowed to store any credit card information at all, not even 4 digits of one.
To check if cURL is compiled correctly go to the admin control panel of oscommerce and go to tools, server info, about half way down there should be a category called cURL, if there isnt, you might not have it setup correctly.
Thats basically the top fixes for this module, if I have forgotten anything I will edit the post. Fixes/addons will appear below this line.
New 
