Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

AUTHORIZENET Module Problems


pedram

Recommended Posts

I have recently signed up for an Authorize.Net merchant account, and I have setup the module in PerpetualSilver.com with all the information necessary. I have also put the module in Production mode, which is the one other than test mode. I have tried buying a few products with my credit card, and a few others, which are all usable. Instead of going through, I get an error of :

 

There has been an error processing your credit card. Please try again.

 

This appears in red, right under the logo of my store, and above the rest of the information. The URL in the browser is also set to :

 

https://secure.authorize.net/gateway/transact.dll

 

So I know, that it is actually reaching the authorize.net, or trying to reach the authorize.net gateway. I have checked through the source code, in read-only mode and figured out that this is an error code of #3. I have called Authorize.Net and they have told me that the error code #3 is the first part of the error code, and you need the second part of the error code to exactly know what is wrong with the processes. If someone has had some experience, or knows what the problem could be. Please give me a helping hand :D

Link to comment
Share on other sites

Same problem here. Authorize.net works fine with other software but with OScommerce I just get the message: "There has been an error processing your credit card. Please try again." How can I find out what the error was? Does OScommerce keep any sort of log or have a debug mode?

Link to comment
Share on other sites

I ran into this same problem (error code #3) "Merchant login ID or password is invalid....."

 

I found a solution in the forum here, but unfortunately I didn't remember to record just exactly where I found it. I'll highlight the solution here with additional information that I ran across.

 

I'm assuming your using the Authorizenet_ADC_Direct_Connection_November_10_2002 contrib:

 

The post that I found related to a fix in the file

{domain-path}/catalog/includes/modules/authorizenet_direct.php

 

in the line:

 

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

 

Remove the " that preceed and follow the $data variable.

 

This fixed the problem as you have described it on one of our servers, but appears to be specific to what versions of software are available on your server. Another server that we have with a more recent version of RedHat, Apache and PHP had to have the line kept as it originally was to work properly.

 

Again, this solution was posted elsewhere in the forums -- I'm not trying to claim any credit for the information -- just passing it along...<g>

Link to comment
Share on other sites

If you are using the Authorize.net payment module that comes with osC, edit the catalog/includes/modules/payment/authorizenet.php file.

 

In the before_process() member function, edit

      // Code 3 is an error - but anything else is an error too (IMHO)

     tep_redirect(tep_href_link(FILENAME_CHECKOUT_PAYMENT, 'error_message=' . urlencode(MODULE_PAYMENT_AUTHORIZENET_TEXT_ERROR_MESSAGE), 'SSL', true, false));

to be

      // Code 3 is an error - but anything else is an error too (IMHO)

     tep_redirect(tep_href_link(FILENAME_CHECKOUT_PAYMENT, 'error_message=' . urlencode($_POST['x_response_reason_code'] . ' - ' . $_POST['x_response_reason_text']), 'SSL', true, false));

and that should give you the code and text for why the transaction was declined.

"Great spirits have always found violent opposition from mediocre minds. The latter cannot understand it when a man does not thoughtlessly submit to hereditary prejudices but honestly and courageously uses his intelligence." - A. Einstein

Link to comment
Share on other sites

the problem for me was the time on my server was wrong, i was getting a X_RESON_RESPONSE of 97 im guessing its a common problem that people over loook its either that the SIM script that authorize is using has the wrong time or your time of either over 5 min fast or over 15 min slow from there time. the solution can be found at

 

http://www.sluggis.com/fptest.htm it tells you if that is the problem. i hope this helps someone i know how frustrating it is trying to figure this out

Link to comment
Share on other sites

  • 1 year later...

Thanks for the info. I had the same situation. Once I got the error code (97) I just called up Authorize.net and made sure my system time was the same as theirs and viola... everything worked fine again.

 

m@

Link to comment
Share on other sites

  • 1 year later...
  • 4 months later...
  • 3 weeks later...

me too.

 

we are getting a few clients with this error - 97 and so it would good if someone can answer the above question.

 

how to get the output of x_fp_timestamp?

Link to comment
Share on other sites

  • 5 weeks later...

I am having the same problem but I don't know how often. Is there a way to see an error log? I only noticed I was having a problem because of the who is feature and it shows the page the customer was on.

 

Thanks!

Link to comment
Share on other sites

You can't see an error log. All you can see is the error code if you make the code change mentioned above.

 

Amazingly, both our customers had server time errors. So easiest way is to check the server time with your hosting company if you can't get it any other way.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...