Latest News: (loading..)
Sign in to follow this  
Followers 0
janicen

Authorization Required - Authorize.net

12 posts in this topic

I got this error:

 

Authorization Required

This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.

 

The test mode is ON because I want to test the website first before going live.

Does any of you have the same experience as I do ? If so, did you fix it successfully ? And please, how do you do that?

 

Thanks!

Janice

Share this post


Link to post
Share on other sites

generate a new transaction key.

take it out of test mode, create a product for $1.00 and then purchase it.

see what happens. test mode doesnt always work right.

Edited by Mibble

Share this post


Link to post
Share on other sites

I already did request for a new transaction key and inserted in the Authorize.net module. If I remove the test mode, will it work?

 

thanks.

Share this post


Link to post
Share on other sites

depends, doesnt hurt to try it and you can always refund yourself the $1.00

Share this post


Link to post
Share on other sites

The error is still there even though the mode is LIVE. Why does the error still there with the Authorization Required ? What did I miss ? :(

Share this post


Link to post
Share on other sites

Nobody have experience with Authorize.Net on the osCommerce ? There must be hundreds of web programmers experienced with Authorize.net on the osCommerce but where are they? <_<

 

My client is waiting for the website to go LIVE....but can't do that without the error being cleared first !!

Share this post


Link to post
Share on other sites

Ok, ok. It sounds like nobody had experienced a similar problem with Authorize.net on osCommerce. Do you recommend any other gateway for credit card processing on osCommerce other than Authorize.net ? Thanks.

Share this post


Link to post
Share on other sites

Fixed the problem. It was a .htaccess file protecting the catalog so I had to remove the .htaccess file from the catalog. :D

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0