Authorizenet ADC Direct Connection or AIM Method

[baonguyenx]

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.

 

Here is the link to the ADC Contribution for Osc 2.2 snapshot on November 10, 2002.

http://www.oscommerce.com/downloads.php/co...ions,650/type,1

 

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/co...ions,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

[Guest]

Configured and installed the files in your contribution, but when I try to checkout, I get the following error messages:

Warning: Failed opening 'includes/classes/cc_validation.php' for inclusion (include_path='') in /home/microsco/public_html/cart/includes/modules/payment/authorizenet.php on line 69

 

Fatal error: Cannot instantiate non-existent class: cc_validation in /home/microsco/public_html/cart/includes/modules/payment/authorizenet.php on line 71

 

I don't have a cc_validation.php file in my classes folder...or anywhere else that I can find. HELP??

[baonguyenx]

Hi,

 

That errror occurs because you are using the old API checkout process, but you installed my latest authorizenet ADC module. You need to grab my ADC Contribution on August 28, 2002 which was written for snapshot on June 5, 2002 (old API checkout)

 

http://www.oscommerce.com/downloads.php/co...ions,421/type,1 .

 

The latest authorizenet module is for new API checkout process of snapshot on November 10, 2002. This snapshot has the file catalog/includes/classes/cc_validation.php, which you are missing this file.

 

Regards,

Bn

[Guest]

Hmm, I downloaded my snapshot 2.2 sometime in September. I added your older contribution to it earlier and that's what was giving me "There has been an error processing you credit card, please try again." message that everyone else was getting. I installed the older contribution once again, and now get that error message again...so I'm back to square one. Is the only option in this to upgrade to the new snapshot? If I upgrade to the newer one, will that wipe out all the items and work I've done on my current cart? Or will it just wipe out the modifications I've made to the colors and buttons, etc.? I can handle redoing the modifcations if it means not having to completely re-enter the items...and if it means getting the authorizenet module to function properly again. It worked absolutely fine until November 1st or 2nd...

[baonguyenx]

Hi,

 

You don't need to upgrade to the latest version. Please follow step 1, 2, and 3 from the following link to troubleshoot your errors.

 

http://www.oscommerce.com/forums/viewtopic.php...=24385&start=20

 

Regards,

Bn

[Guest]

I see one area where I'm totally lost...it sounds as though you are giving directions based on Unix commands. I know NOTHING about working with Unix, all I know to do is adjust/correct files and FTP them to the server. When you say to run the command, I am clueless about where or what to do. :oops: Can you explain it for those of us who are Unix-ly-challenged?

[baonguyenx]

Hi,

 

If you don't have telnet access or you don't know much about unix commands. You can contact a Techician from your ISP provider to perfomance the following commands for you. The goal is to verify that your sever has Curl installed with OpenSSL Libraries Support.

 

I think the Technician already know what your server has. Just ask them to verify it for you.

 

Installation Procedure in 4 steps for ADC Contribution on August 28, 2002.

 

Step1: In your Telnet Server.

- You need to build Curl with OpenSSL Libraries Support in order for the following command to talk https://

// Post order info data to Authorize.net, make sure you have curl installed

// exec("/usr/bin/curl -d "$data" https://secure.authorize.net/gateway/transact.dll", $response);

 

Please verify your server by running the following commands after you build Curl with SSL support or you can request your ISP to install Curl with OpenSSL Libraries Support for you!!!

 

Did you run the command /usr/bin/curl -V ?

// It will return something like "curl 7.8 (i386-redhat-linux-gnu) libcurl 7.8 (OpenSSL 0.9.6b) (ipv6 enabled)". This means you already have curl installed. Your path to curl is /usr/bin/curl . Also, OpenSSL is already installed!!!

 

// If it does not display anything, you can try the following command:

$ whereis curl

curl: /usr/bin/curl /usr/include/curl /usr/share/man/man1/curl.1.gz

$ which curl

/usr/bin/curl

 

If you found the Curl's path, then replace it in file catalog/includes/modules/authorizenet_direct.php

// Post order info data to Authorize.net, make sure you have curl installed

exec("/usr/bin/curl -d "$data" https://secure.authorize.net/gateway/transact.dll", $response);

 

If you have Curl installed, you also need to verify if OpenSSL libraries is installed. Curl will need SSL libraries installed for it to talk https://

 

$ whereis openssl

openssl: /usr/bin/openssl /usr/local/bin/openssl /usr/local/lib/openssl /usr/include/openssl /usr/share/man/man1/openssl.1ss l.gz

$ which openssl

/usr/bin/openssl

$ type openssl

openssl is /usr/bin/openssl

 

If you see one of the above, then SSL libraries is installed

 

 

Step2: In your folder OsCommerce catalog

 

- From this contribution, open my file catalog/includes/modules/authorizenet_direct.php and set x_PASSWORD to your authorizenet admin password!!!

If your curl is not located at /usr/bin/curl, then change it to the correct path.

Copy my catalog/includes/modules/authorizenet_direct.php to your directory catalog/includes/modules/ .

 

- Backup your file catalog/includes/modules/payment/authorizenet.php to somewhere else, and replace it with my catalog/includes/modules/payment/authorizenet.php

 

- Backup your file catalog/checkout_process.php to somewhere else, and replace it with my catalog/checkout_process.php

 

Or you can mannually made these changes at the top of your file catalog/checkout_process.php

 

Changes have been made in file catalog/checkout_process.php

 

// load selected payment module

require(DIR_WS_CLASSES . 'payment.php');

$payment_modules = new payment($payment);

 

// Need to be included before Authorizenet ADC Direct Connection

require(DIR_WS_CLASSES . 'order.php');

$order = new order;

 

//************************************************************

// Authorizenet ADC Direct Connection

// Make sure the /catalog/includes/class/order.php is included

// and $order object is created before this!!!

if(MODULE_PAYMENT_AUTHORIZENET_STATUS) {

include(DIR_WS_MODULES . 'authorizenet_direct.php');

}

//************************************************************

 

// load the before_process function from the payment modules

$payment_modules->before_process();

 

require(DIR_WS_CLASSES . 'order_total.php');

$order_total_modules = new order_total;

 

$order_totals = $order_total_modules->process();

 

 

Step3: In your OsCommerce Admin

- Enable your authorizenet module by clicking on the green button.

Click on the 'Edit' button and you will be asked with the following questions.

 

Allow Authorize.net

Do you want to accept Authorize.net payments?

1

 

Authorize.net Login

Login used for Authorize.net payments

My_LogID

 

Authorize.net Test Mode

Test mode for Authorize.net payments

0

 

Authorize.net E-Mail Client

Should Authorize.Net e-mail the customer too? 0=NO, 1=YES

0

 

Authorize.net E-Mail Merchant

Should Authorize.Net e-mail you? 0=NO, 1=YES

1

 

Authorize.net Method

This should be either CC or ECHECK

CC

 

 

Step4: In your Authorize.net Admin

- Your authorizenet account must be in password required mode.

'Setting' --> 'Password-Required Mode' --> Check that box and click on the 'Submit' button.

 

- With ADC Direct Connection, you you don't need to add add any url.

Delete all of them because ADC Direct Connection is not based on referrer url, but it connects directly to Authorizenet system.

 

'Settings' --> 'WebLink' --> 'Referrer URLs' --> Remove all url that you have in there. Look at the 'Transaction Submission' section!!!

 

If you don't see WebLink, did you disable weblink ??? You need to make sure that you removed all 'Referrer URL' before you disable Weblink. You might need to contact Authorize.Net Technical Support to remove that Referrer URLs if you forgot to remove them before you disable Weblink. Once you disable Weblink, it will no longer accessible in your Authorize.net admin. I suggest not to disable Weblink.

 

Please remove all URLs if you have any in the following:

'Settings' --> Response/Receipt URLs

'Settings' --> Receipt Page --> Receipt Page --> Receipt Method

'Settings' --> Relay Response

 

If you don't remove the Urls as instructed above, you will receive the following error from Authorize.net

0: The referrer, relay response or receipt link URL is invalid.

 

- 'Settings' --> 'Test Mode' --> Click on the 'Turn Test On' button

// Switch back to 'Live Mode' when you are done with this testing.

 

Regards,

Bn

[Guest]

This is wierd

 

On checkout the authorize.net module is working and processes the order but instead of saying "Credit Card Owner:" it says

MODULE_PAYMENT_AUTHORIZENET_TEXT_CREDIT_CARD_OWNER

 

Maybe a fix is something simple??

 

Thanks in advance!

[crock]

I've found 1 small bug with the ADC system and one major one.

 

The Country is not being sent to Authorizenet the way it should be. It's send as "Array" because this line...

 

x_Ship_To_Country => "{$order->delivery['country']}",

 

Should be...

 

x_Ship_To_Country => "{$order->delivery['country']['title']}",

 

Also, the credit card number is not stored when I use the ADC method. This is important now since Authorizenet no longer displays or allows downloads of the full credit card number.

 

Any help with storing the credit card number would be appreciated. In the mean time I've switched back to manual processing.