Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

[CONTRIBUTION] Authorize Net AIM module


Vger

Recommended Posts

I installed the prepackaged Authorize.net module, and configured it, yet it did not show up as a payment option when I proceded to checkout. I started searching the forums to find a solution (I found none) and realized that I really wanted the Authorize.net AIM contribution. I downloaded, installed, and configured it, and once again, it doesn't show up as a payment option. I have an Authorize.net account. I aquired a transaction key. The only thing I was hazy about was whether I should be logging in with my Authorize.net username or my API login that came with my transaction key, but I tried both and still nothing. Is there something really obvious that I'm missing? Do I have to activate something through Authorize.net, beyond aquiring an account and an API login/transaction key? Any help would be appreciated.

Link to comment
Share on other sites

I'm having trouble with our shopping cart and the AIM module as well. I have the March 18 2006 version installed (and have tried other modules) and each time I try to process a card it kicks me back to the checkout_payment.php page with a general error in the URL and nothing else.

 

Here is the error I recieve:

 

checkout_payment.php?payment_error=authorizenet_cc_aim&error=general

 

I have checked configuration settings in the module and on Authorize.net. It is possible that I have missed something, but I'm honestly hoping it's something simple I'm overlooking.

 

I recompiled the server with curl today to make sure that wasn't the problem and I'm still getting the same results. I can use the standard Authorize.net module that comes with osCommerce (Milestone 2.2) and it will process the card and reject it because there is no CCV (and module doesn't give the option).

 

I'm sorry if there question has been answered in this post, but I honestly don't have time to wade through 40 pages of forum posts and my searches haven't yielded anything helpful. If someone has an answer or link to a fix for this issue I would be very grateful.

 

I have this problem exactly. Everything is installed properly as best I can tell. I only get this error message which doesn't help diagnose the problem whatsoever. If anyone has a solve for this I would greatly appreciate it.

 

Thanks!

Link to comment
Share on other sites

I installed the prepackaged Authorize.net module, and configured it, yet it did not show up as a payment option when I proceded to checkout. I started searching the forums to find a solution (I found none) and realized that I really wanted the Authorize.net AIM contribution. I downloaded, installed, and configured it, and once again, it doesn't show up as a payment option. I have an Authorize.net account. I aquired a transaction key. The only thing I was hazy about was whether I should be logging in with my Authorize.net username or my API login that came with my transaction key, but I tried both and still nothing. Is there something really obvious that I'm missing? Do I have to activate something through Authorize.net, beyond aquiring an account and an API login/transaction key? Any help would be appreciated.

I still need help on this issue. Any help is appreciated.

Link to comment
Share on other sites

Hi all,

Back in November 2007 Authorize.net came out with CIM, customer information manager, see release info below.

It's $20 a month, but seems well worth it as a PCI issue can put you out of business overnight if your not careful. Not to mention possible lawsuits. How do other solutions compare to this? It sounds good but maybe there are better options for PCI compliance. I like the fact that we won't be storing credit card info on the server. If anyone is using this, is there code out there for this? Thanks for your help!

 

Steve

 

Customer Information Manager Now Available

 

We are excited to announce the release of our newest payment gateway feature, the Customer Information Manager (CIM). CIM allows you to store your customers' sensitive payment information on our secure servers, simplifying payments for returning customers as well as recurring transactions. It can also help you comply with the Payment Card Industry (PCI) Data Security Standard, since customer data is no longer stored locally.

 

By providing quick access to stored information, CIM is an ideal tool for companies that:

 

* Process recurring transactions where the date and/or amount is different each month (e.g. utility companies)

* Process usage charges - where you only bill when the service is used. (e.g. pay-as-you-go cell phones)

* Are concerned with PCI compliance

* Want to provide returning customers with the convenience of not re-entering personal data

 

Your Web site integrates to CIM via an Application Programming Interface (API). For additional information on CIM and how it works, please review the CIM product page on our Web site at http://www.authorize.net/cim. You can also review the CIM help files by clicking Help from the homepage, then Tools and then Customer Information Manager.

 

Note: At this time, only Card Not Present merchants who integrate to the payment gateway using Advanced Integration Method (AIM) can use CIM.

 

Whether your goal is to simplify your PCI compliance by storing your customer data on our servers, or you need a more flexible solution for recurring transactions and repeat customers, Customer Information Manager is the answer for you.

 

To sign up for CIM:

 

1. Click Customer Information Manager from the main menu on the left

2. Review your pricing and follow the instructions for signing up

 

We hope the CIM service will be beneficial to your business and help you increase customer loyalty while assisting you with PCI compliance. We wish you all the best in this holiday season!

Link to comment
Share on other sites

Hi all,

Back in November 2007 Authorize.net came out with CIM, customer information manager, see release info below.

It's $20 a month, but seems well worth it as a PCI issue can put you out of business overnight if your not careful. Not to mention possible lawsuits. How do other solutions compare to this? It sounds good but maybe there are better options for PCI compliance. I like the fact that we won't be storing credit card info on the server. If anyone is using this, is there code out there for this? Thanks for your help!

 

Steve

 

I am looking into coding something for this, but outside of osCommerce. Remember that even with the AIM module you should be safe from PCI-related issues as it should not store credit card details. Just make sure the module you use (there are a few) is one that does not store them, or amend the one you use. You should also make it clear to your customers that you do not store their details.

 

Unless you have a server security guru/genius on staff, you don't want to messing with PCI. The AIM module is the best of both worlds.

 

KB

Network Webcams - The IP Camera Specialists

Link to comment
Share on other sites

I am looking into coding something for this, but outside of osCommerce. Remember that even with the AIM module you should be safe from PCI-related issues as it should not store credit card details. Just make sure the module you use (there are a few) is one that does not store them, or amend the one you use. You should also make it clear to your customers that you do not store their details.

 

Unless you have a server security guru/genius on staff, you don't want to messing with PCI. The AIM module is the best of both worlds.

 

KB

 

Thanks Kevin for the quick reply. Yikes, the one I am using does store the cc info still. I installed a manual way to zero the cc info out, but this is not ideal.

Is the best one to use the AIM module contribution by Harald Ponce de Leon? I figured it might as I just saw his today while searching through them. I installed the "other" one.

Link to comment
Share on other sites

Installed this contrib and set the appropriate info for the module.

 

When I put in the CC info in on the payment info page and hit continue it kicks back to the same page and says "Please select a payment method for your order."

 

Payment method is selected!

 

I tried removing all other payment methods and get the same response.

 

Any clues?

Link to comment
Share on other sites

I've got version MS2 and I've got the contribution working and it's great. I went to turn on the CVV and noticed that my admin panel doesn't have that option. Do I need to update my version of OsC or am I being an idiot here? (Mine doesn't say request cvv number, its just username, transaction key, etc) Thanks for the help.

Link to comment
Share on other sites

I actually had luck with THIS mod, the one this thread is about... the new one that comes with RC2a simply does not work.

 

I had the same problem with both mods - the error as above. However, the problem was eventually tracked down to a combination of incorrect test url (should be https://certification.authorize.net/gateway/transact.dll if you don't have an A.net developer account), transaction ID and MD5 hash. The MD5 hash entry field in A.net account manager is shorter than most MD5 hash generators create, so I, at least, had a mismatch in the string i'd input into the contribution and the string A.net was looking for. It was off by about 8 chars.

 

Double check your data and url in the first instance. The RC2a version now works fine with my MS2.2 store.

 

KB

Network Webcams - The IP Camera Specialists

Link to comment
Share on other sites

A while back, I posted this, but didn't get any response:

 

I installed the prepackaged Authorize.net module, and configured it, yet it did not show up as a payment option when I proceded to checkout. I started searching the forums to find a solution (I found none) and realized that I really wanted the Authorize.net AIM contribution. I downloaded, installed, and configured it, and once again, it doesn't show up as a payment option. I have an Authorize.net account. I aquired a transaction key. The only thing I was hazy about was whether I should be logging in with my Authorize.net username or my API login that came with my transaction key, but I tried both and still nothing. Is there something really obvious that I'm missing? Do I have to activate something through Authorize.net, beyond aquiring an account and an API login/transaction key? Any help would be appreciated.

 

I discovered that my "separate pricing per customer" contribution required me to enable the payment modules for each of my separate customer groups. There I was able to enable the prepackaged module, but the AIM module was nowhere to be found. Has anyone here had success with installing this with the sppc contrib? I posted in that forum, and the response was that it was in this module not sppc. Any help would be appreciated.

Link to comment
Share on other sites

A while back, I posted this, but didn't get any response:

I discovered that my "separate pricing per customer" contribution required me to enable the payment modules for each of my separate customer groups. There I was able to enable the prepackaged module, but the AIM module was nowhere to be found. Has anyone here had success with installing this with the sppc contrib? I posted in that forum, and the response was that it was in this module not sppc. Any help would be appreciated.

From the sppc forum:

The fact that it doesn't show up in SPPC indicates it is not an installed module. Check your database with phpMyAdmin, table configuration and look for configuration_key:

MODULE_PAYMENT_INSTALLED (List of payment module filenames separated by a semi-colon. This is automatically updated. No need to edit. (Example: cc.php;cod.php;paypal.php))

 

I did this, and Authorize.net AIM is not listed as an installed module, but according to my OSC admin pannel, it is. What do I do about this?

Link to comment
Share on other sites

I'm having trouble with our shopping cart and the AIM module as well. I have the March 18 2006 version installed (and have tried other modules) and each time I try to process a card it kicks me back to the checkout_payment.php page with a general error in the URL and nothing else.

 

Here is the error I recieve:

 

checkout_payment.php?payment_error=authorizenet_cc_aim&error=general

 

I have checked configuration settings in the module and on Authorize.net. It is possible that I have missed something, but I'm honestly hoping it's something simple I'm overlooking.

 

I recompiled the server with curl today to make sure that wasn't the problem and I'm still getting the same results. I can use the standard Authorize.net module that comes with osCommerce (Milestone 2.2) and it will process the card and reject it because there is no CCV (and module doesn't give the option).

 

I'm sorry if there question has been answered in this post, but I honestly don't have time to wade through 40 pages of forum posts and my searches haven't yielded anything helpful. If someone has an answer or link to a fix for this issue I would be very grateful.

 

I am receiving the same message as above. I have exchanged emails with Authorize.net and they indicated the following:

 

Because this is a generic error and your shopping cart is not programmed correctly to output the actual reason response error codes that our server generates when there is a problem assuming the cart is connecting to the gateway we cannot troubleshoot this problem without someone making modifications to your cart so it includes the following field
x_reason_code
which will write out the actual error code.

 

That doesn't really help me configure osCommerce properly. So, I here are my questions:

  1. How do I configure the AIM module to output this code in the URL?
  2. How can I tell what has changed in the checkout_confirmation.php page (that came with the contribution archive)?
  3. Is there any other documentation other than what has been placed in the guide.txt?

 

** Here's some info on what's been done:

My settings in the module are...

  • API & Transaction Key: (pointing to a test account Authorize.net provided me)
  • MD5 Hash: left blank (Authorize.net indicated that this is optional)
  • Transaction Server & Mode: Test (I also made sure test url paths were uncommented in orders.php and authorizenet_aim.php)
  • Payment Zone: (none selected)
  • Curl Path: (path verified)

Lastly, I've added the authorize_data table to my database.

 

Thanks in advance for your help!

Link to comment
Share on other sites

Thanks for the contribution Vger, works great...

 

If anyone is curious about a *quick-fix* for the Invoice Number, here's what I did (without sleep). Remember to BACKUP your file first... I pretty much used the same logic as Jason's "Authorize.net Invoice Number Fix - for OSC MS2.2" but replaced some syntax in Vger's module:

 

Around Line #228 find this:

// Calculate the next expected order id
  $last_order_id = tep_db_query("select * from " . TABLE_ORDERS . " order by orders_id desc limit 1");
  $new_order_id = $last_order_id->fields['orders_id'];
  $new_order_id = ($new_order_id + 1);

 

Comment the above line out and/or replace with this:

// BOF: Authorize Net AIM Invoice Number Fix
// Calculate the next expected order id to pass as x_Invoice_Num
  $new_order_id = '';
  $inv_id = tep_db_query("select orders_id from " . TABLE_ORDERS . " order by orders_id DESC limit 1");
  $last_order_id = tep_db_fetch_array($inv_id);
  $new_order_id = $last_order_id['orders_id']+1;
// EOF: Authorize Net AIM Invoice Number Fix

 

Works for me so far. It's late. Post back here if it works for you too. You should probably rely on Vger to verify this addition if it's solid. Hope it helps! :thumbsup: -Tada

 

 

THIS WORKS GREAT FOR ME!!! THE INVOICE NUMBER MATCHES MY ORDER NUM IN ADMIN.....THANKS

Link to comment
Share on other sites

I am receiving the same message as above. I have exchanged emails with Authorize.net and they indicated the following:

 

Because this is a generic error and your shopping cart is not programmed correctly to output the actual reason response error codes that our server generates when there is a problem assuming the cart is connecting to the gateway we cannot troubleshoot this problem without someone making modifications to your cart so it includes the following field
x_reason_code
which will write out the actual error code.

 

That doesn't really help me configure osCommerce properly. So, I here are my questions:

  1. How do I configure the AIM module to output this code in the URL?
  2. How can I tell what has changed in the checkout_confirmation.php page (that came with the contribution archive)?
  3. Is there any other documentation other than what has been placed in the guide.txt?

** Here's some info on what's been done:

My settings in the module are...

  • API & Transaction Key: (pointing to a test account Authorize.net provided me)
  • MD5 Hash: left blank (Authorize.net indicated that this is optional)
  • Transaction Server & Mode: Test (I also made sure test url paths were uncommented in orders.php and authorizenet_aim.php)
  • Payment Zone: (none selected)
  • Curl Path: (path verified)

Lastly, I've added the authorize_data table to my database.

 

Thanks in advance for your help!

 

 

I was having very similar problems. Here is how I fixed mine.

 

I worked on the issue for two days. I finally called Authorize.Net. While the rep was not very helpful regarding OSC, she did confirm that by using the AIM features of Authorize.net... I DO NOT need to turn on any referrer URL's or receipt pages. She insisted that everything should just work as long as my log-in name and transaction ID were in the system.

 

I went back to the accounts panel in ANet and made sure that all of the URL settings were removed from everywhere I could find them. (Note that you need to go back into the accounts panel of ANet and click on the delete link after you have erased them from the line you were just editing.) I did all this and still was getting errors.

 

I went back and checked my Log-In and Transaction Key in OSC (for about the 10th time).... Wait... Look real careful... is that... A TYPO!!!

 

Bottom line.... carefully check your Log-In and Transaction ID. It worked for me!

Link to comment
Share on other sites

ok here's the latest...

 

My client tested this with her visa and works great.

 

She also tested with amex and gets the same error as I do with my mastercard.

 

I just got a later version of the cc_validation.php file and changed it over and now mastercard is working.

 

 

can you post the lastest version of the cc_validation file code for us people with the same problem. thank you so much!!!

Link to comment
Share on other sites

Ok, so I just read 41 pages of support thread; done EVERYTHING suggested here and am having problems with this module.

 

I have a brand new authorize.net account setup in TEST.

 

Am trying to use Authorize.net Advanced Integration Method v1.0, dated 11 Jan 2008.

 

My osCommerce is setup with the correct Login ID, Transaction Key, and MD5 Hash and setup for the test server and test transaction (modified the module to use the proper test server).

 

A.net has been configured Delimited Response: NO, Field Encapsulation Character: BLANK, Transaction Version: 3.1, and Relay Response is set to: my website's secure checkout_process.php page. cURL is compiled in PHP and I have a valid SSL certificate (have been running SSL for years and processing with another company).

 

Whenever I try to process a credit card via this module I get:

There has been an error processing your credit card

Please try again and if problems persist, please try another payment method.

 

The POST reply contains:

checkout_payment.php?payment_error=authorizenet_cc_aim&error=general

 

This seems to be what others have encountered, but I don't see any fix information in this thread.

Link to comment
Share on other sites

ljpenton,

 

Change delimited to YES (I personally use a pipe and have my OScomm AN module changed to write pipes)

also use both sides (AN and OSCOMM) production mode instead of test, which doesn't work and run a real transaction with a real CC number with a small amount. THIS IS THE ONLY GUARANTEE IT WORKS.

 

 

here is my authorizenet_aim.php file:

 

http://www.pixclinic.com/_code_parts/authorizenet_aim.txt

 

with the x_delim character set to a pipe

 

hope this helps!

Edited by pixclinic
Link to comment
Share on other sites

ljpenton,

 

Change delimited to YES (I personally use a pipe and have my OScomm AN module changed to write pipes)

also use both sides (AN and OSCOMM) production mode instead of test, which doesn't work and run a real transaction with a real CC number with a small amount. THIS IS THE ONLY GUARANTEE IT WORKS.

here is my authorizenet_aim.php file:

 

http://www.pixclinic.com/_code_parts/authorizenet_aim.txt

 

with the x_delim character set to a pipe

 

hope this helps!

 

Thank you for the help pixclinic.

 

Didn't fix the problem so I'm starting the troubleshooting from square 1. Have dropped my hosting company an email making sure that cURL is indeed installed where their docs state (that seems like a very likely culprit).

Link to comment
Share on other sites

I was having very similar problems. Here is how I fixed mine.

 

I worked on the issue for two days. I finally called Authorize.Net. While the rep was not very helpful regarding OSC, she did confirm that by using the AIM features of Authorize.net... I DO NOT need to turn on any referrer URL's or receipt pages. She insisted that everything should just work as long as my log-in name and transaction ID were in the system.

 

I went back to the accounts panel in ANet and made sure that all of the URL settings were removed from everywhere I could find them. (Note that you need to go back into the accounts panel of ANet and click on the delete link after you have erased them from the line you were just editing.) I did all this and still was getting errors.

 

I went back and checked my Log-In and Transaction Key in OSC (for about the 10th time).... Wait... Look real careful... is that... A TYPO!!!

 

Bottom line.... carefully check your Log-In and Transaction ID. It worked for me!

 

I never setup any of the referrer URLs or receipt pages, so that is in check. I reissued my Transaction ID and entered it into OSC and I am still having the same issue.

 

Thanks for your response.

 

I am still dead in the water, so does anyone else know how to code the x_reason_code into OSC?

Link to comment
Share on other sites

Thank you for the help pixclinic.

 

Didn't fix the problem so I'm starting the troubleshooting from square 1. Have dropped my hosting company an email making sure that cURL is indeed installed where their docs state (that seems like a very likely culprit).

 

Just an update.

 

Have spent 5 days on this now, without success. Downloaded the latest version of osCommerce (with the a net module embedded in it), and still get the "general error" failure. In a total act of desperation, downloaded and installed another shopping cart program, configured its a net module in exactly the same manner as for osC and it worked on the first try.

 

I don't see any functionality for putting this module in debug so I can properly troubleshoot the installation, so am giving up and decided not to use authorize.net for my cc processing.

Link to comment
Share on other sites

I never setup any of the referrer URLs or receipt pages, so that is in check. I reissued my Transaction ID and entered it into OSC and I am still having the same issue.

 

Thanks for your response.

 

I am still dead in the water, so does anyone else know how to code the x_reason_code into OSC?

 

So I found two posts that deal with this issue, but it dates back to 2004 (the old AIM module)...

 

http://www.oscommerce.com/forums/index.php?sho...l=x_reason_code

http://www.oscommerce.com/forums/index.php?sho...l=x_reason_code

 

Can the author (Vger?) please provide an update to the changes needed to display the reason code?

 

Thanks in advance!

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...