Contributions

Slightly modified and applied the invoice # fix for the default osC Authorize.net module found at http://www.oscommerce.com/community/contributions,4256/category,all/search,authorize.net

Now your osC order id's will show up in Authorize.net's transaction records.

This is the full package.

The previous post had a typo. This has two changes.
1) added -s to curl command
2) changed $response to $response[0] in the explode.

Brad

There were vital typos in the previous fix, so it didn't fix anything, but he was on the right track. Also clarified the description of "Login Password".

This is the complete package. Just install the files, install the Admin- Payment - Authorize.net AIM module, and configure it. If you are updating, you'll need to Remove, Install, & configure.

Modified the authorizenetaim.php file so that Set Order Status will work. (Lines 28-31).

It wasn't working for me until I added these lines. Hope it helps someone! Thanks again to all who got this module off the ground!

-j

This is the AIM module that I got working. Hopefully my fixes didn't break anyone else. Includes CVV and declares the transaction reference as a global for later use.

This is the foolproof version of Bao Nguyen's et al. Authorizenet ADC Direct Connection script. I took all of the fixes people posted and put it all in one easy package.

Enjoy!

WORKING VERSION: This file is an update for usage with php_curl.dll instead of CURL executable. It has been tested in Win32 and should work for Unix/Linux systems as well.

VERSION BELOW HAS ERRORS - this is the correct version.

This file is an update for usage with php_curl.dll instead of CURL executable. It has been tested in Win32 and should work for Unix/Linux systems as well.

For osc v2.2 with billing address support, you'll need to make a few adjustments in order to properly submit billing information to Auth.net:

In authorizenet_direct.php, just change the following lines:

------------------------------------
x_Address => "{$order->customer['street_address']}",
x_City => "{$order->customer['city']}",
x_State => "{$order->customer['state']}",
x_Zip => "{$order->customer['postcode']}",
x_Country => "{$order->customer['country']['title']}",
------------------------------------

To:

------------------------------------
x_Address => "{$order->billing['street_address']}",
x_City => "{$order->billing['city']}",
x_State => "{$order->billing['state']}",
x_Zip => "{$order->billing['postcode']}",
x_Country => "{$order->billing['country']['title']}",
------------------------------------

No additional files are necessary.

Hi all,

Since there are a lot of you requested to use Authorizenet 'ADC Direct Response' same as 'AIM Method' for the new API Check Out snapshot of OsC 2.2, I have updated my codes for ADC Direct Connection to fit these changes.

These new updated files are for snapshot on November 10, 2002, and if you are still using the old API Check Out, then you need to grab my ADC Contribution on August 28, 2002 which was written for snapshot on June 5, 2002 http://www.oscommerce.com/downloads.php/contributions,421/type,1 .

Clarification of your confusion about AIM and ADC Direct Response.
Quotes from authorizenet
"Formerly known as ADC Direct Response, Advanced Integration Method (AIM) is the preferred and highly recommended method of connection to the Payment Gateway. Using the best of web security, AIM does more to eliminate unauthorized transactions and optimize transaction security than any other connection method."

Advanced Integration Method (AIM) is the same as ADC Direct Response that I published in August 28 2002. This means everyone who don't use ADC Direct Connection needs to change to either Advanced Integration Method (AIM/ADC Direct Response) and Simple Integration Method (SIM).

Why do I use ADC ?
- Customers always stay on my site.
- ADC is quicker since it connects directly to Authorize.net systems.
- ADC is secured since it requires a password for each transaction.
- ADC is stable since customer can check out from any browser.

I have proven that other methods like WebLink and ADC Relay Response could be vulnerable and hacked.
For example:
1. Customers has been charged for 1 item, but it actually showed up in the Osc admin with 2 items!!!
2. Cusomters has been charge for 1 item, and it does not showed up in the Osc admin.

WebLink and ADC Relay Response doesn't work in Netscape6.1 and older Netscape versions and some of AOL browsers due to the error "Invalid Referer".

ADC Direct Connection is the best method to connect to Authorize.net account!!!

Regards,
Bao Nguyen

Hi all,

I used to have ADC Relay Response Method as the payment module, but this built-in module of OsCommerce doesn't work in Netscape6.1 and older Netscape versions and some of AOL browsers due to the error "Invalid Referer". I have rewrote authorizenet module to utilize the ADC Direct Connection method, and my customers can place order from any browser. I have been using Authorizenet ADC Direct Connection more than a month, and my customers did not complaint since I used it. It has been running great.

Regards,
Bn