"Authorizenet is in Testing mode"...please help!

Hi,

This is my first time with Zen Cart... so far it's been real easy to work with and I'm very pleased. I've recently just setup an account with Authorize.net and I'm using thier payment module (Authorize.net (AIM)) in the admin section of the shopping cart. I've turned off the "Test Mode" in my Authorize account and also turned on the "Production" mode in the payment module... but for some reason it says "Authorizenet is in testing mode". I've contacted them and they told me to do two more things:

Step 1: If you are passing x_test_request=true in your code, change to x_test_request=false

Step 2: Make sure you are posting to https://secure.authorize.net/gateway/transact.dll

Not sure what that means or where to find it. Can anyone please help me? I told the boss man the site will go live soon... :-/

in your zen cart admin look in modules-> payment -> authorize.net
there should be a switch in there for test or production.

Yeah I've switched it to production and gone back to the store but the message is still there for some reason... Is there any other place that has to be changed?

Do you have BOTH the Authorize.net (or Authorize.net SIM) ... AND the Authorize.net AIM modules installed?

If you are using AIM, then edit the non-AIM (ie: SIM) module and click Remove to de-install it.

Both modules check for "test" mode independently. If either is enabled and in test mode, the warning alert will show.

Thanks for helping me out with this... I do have the other Authorize.net (sim) installed but it is turned off... does that matter or do I need to go ahead and uninstall it like you said?

You need to uninstall any payment or shipping module that you are not using

You guys are great... that seemed to work! Thank you so much for your help.

How do I set the authorize.net transaction URL in zen cart?
Everytime I try to process an order it is not accepted because it is posting to the production URL. How do I change the transaction URL to https://test.authorize.net/gateway/transact.dll?
Also, in the admin tool I have the transaction mode set to TEST.
thanks!

The module is designed to work with production servers, not test servers.
The "test mode" switch in the admin sends "test" transactions ... to the production server ... which will send back the appropriate responses for test transactions.

Why do you think you need to send to the test server specifically?

I'm unable to complete the check out process. When I try to check out with the test credit card numbers I get this error:
"(TESTMODE) This transaction cannot be accepted. - Your credit card could not be authorized for this reason. Please correct any information and try again or contact us for further assistance."
I would like to be sure the order is completed correctly. I asked authorize.net why this was happening. Their reply was, because the transaction is being posted to the production URL. I don't know how to get Zen Cart to post the transaction to their test URL. Please advise.

Is your authorizenet account in Test mode or Production mode?
What happens if you put it in Production mode?

When I put authorize.net in production mode it returns the same error:
" This transaction cannot be accepted. - Your credit card could not be authorized for this reason. Please correct any information and try again or contact us for further assistance."

It seems the problem is that when it's in the test mode it's posting the transaction to the production URL. I need the test mode to post the transaction to the test URL, which is:
https://test.authorize.net/gateway/transact.dll

Is there any way to modify the URL so that it posts to the test URL?
Please let me know. Thanks!

I don't think you'll see anything better by posting to the test server. The production server is designed to handle test transactions as tests on live accounts.
The "test" server is specifically intended for use with test accounts for developers, not production accounts.

You can force it to use the test server by manually adding a new file called:
/includes/extra_datafiles/authnet_aim.php
containing:```

For debug purposes, you might be better advised to simply turn on debug logging within the module (available since v1.3.7) so you can see what problems it's encountering, and deal with those error messages specifically.

To change to Authorize.net test server URL, you need to specify it in the “includes/modules/payment/authorizenet_aim.php” file at or near line 360.
Replace $url = 'https://secure.authorize.net/gateway/transact.dll'; by the server URL provided to you by Authorize.net in their account confirmation e-mail message. Most probably it will be:
$url = 'https://test.authorize.net/gateway/transact.dll'; but double check from the e-mail message.
It seems that Authorize.net issues different kinds of temporary test accounts and some of them need to send the test transactions to the test server URL. My free temporary Authorize.net developer account is set up that way.

deBeaujeu

Thank you.
That worked! I really appreciate your help.
:D

Are you looking at an old version of AuthorizeNet? Zen Cart has this built into the AuthorizeNet AIM that comes with Zen Cart ...

You shouldn't need to touch the code for that test server ...

To take full advantage of Authorize.net “x_test_request” and the ZC Admin Test/Production switch feature, a connection has to be first established with the prod server (https://secure/authorize.net/gateway/transact.dll ). Unfortunately, Authorize.net does not permit Developer Test Accounts to connect to the prod server (confirm in writing by Authorize.net).

In the account confirmation e-mail message received from Authorize.net, it is specifically stated that the test transactions should be sent to the test server at URL: https://test.authorize.net/gateway/transact.dll . So, the Developer Test Account owner has no choice but to modify the hard-coded URL in the “includes/modules/payment/authorizenet_aim.php” payment program in order to send test transactions.

Authorize.net claims that the test server (https://test.authorize.net/gateway/transact.dll) supports the “x_test_request” feature, but I did not test it. After going through the trouble of modifying the server hard-coded URL, the “x_test_request” feature becomes less attractive.

The Developer Test Account is really meant for application Developer activities and not for Customer implementation of the ZC shopping cart. The ZC implementer should go directly to a live account (Merchant or Production account) and use the ZC Admin Test/Production switch.

deBeaujeu

Perhaps you explain in more detail why you think you need to use the test server?

There is no need to edit code.

To clarify:

1. deBeauJeu correctly states

The Developer Test Account is really meant for application Developer activities and not for Customer implementation of the ZC shopping cart. The ZC implementer should go directly to a live account (Merchant or Production account) and use the ZC Admin Test/Production switch.

2. For those who feel the need to test the module as a developer and not use a real live account, there is no need to change code to do this.
   Simply add this switch in a new file as explained (above and reposted here):

DrByte:

You can force it to use the test server by manually adding a new file called:
/includes/extra_datafiles/authnet_aim.php
containing:

> This will switch the URL to test.authorize.net ... which, again, requires that you have a developers account in order to submit transactions.

3. For those who are simply having difficulties in getting the module to work and wish to debug its operation, simply turn on the debug settings in the module via Admin->Modules->Payment->Authorizenet AIM->Edit->Debug Mode = Log to File or Log and Email.
The log files will appear in the /cache folder (wherever it's located, as long as it's chmod 777), as of v1.3.7.  This location will change in v1.4.x

----------------
There is no need to edit code to make this happen. 
If you are not using v1.3.7 or greater then you'll need to upgrade to take full advantage of these features, as well as the various bugfixes applied to this stage.