Merchant Login ID or Password Invalid For Authorize.net

[Wonder95]

When I try to run my contribution page in test mode, I get the following error message:

Payment Processor Error message:
2:13 (TESTMODE) The merchant login ID or password is invalid or the account is inactive.

I have a valid Authorize.net account set up, and I have my API Login ID and Payment Key values set in Global Settings.  Is there something else missing?  I saw another post that said it might be something with the SMTP settings.  If so, what should they be?  Shouldn't CiviCRM just use whatever is set in PHP.INI on the server for SMTP settings?

Thanks.

[Dave Greenberg]

That error sounds like a Payment Processor configuration issue (not SMTP). Have you reviewed the configuration info for Auth.net / CiviCRM here:
http://wiki.civicrm.org/confluence/display/CRMDOC/Authorize.net+Configuration ?

I haven't played with this for a while, but it seems like you need to configure your merchant account to be in "Test Mode" on the Auth.net side if you're doing test-drive transactions. You should also verify the Test Payments Site URL and login info in that section of your Payment Processor settings form.

As a side note, you do need to configure the SMTP server to be used by CiviCRM from Administer CiviCRM >> Global Settings >> Outbound Mail (SMTP).

[Wonder95]

Yes, I have read that page many times.  But I couldn't figure out if Authorize.net had to be in test mode because it doesn't say.  It just says "If your Merchant Account is set to run in Test Mode, then you must use the following test server in your Payment Processor Settings for Site URL" which is https://test.authorize.net/gateway/transact.dll.

In the Payment Processor setup, there are two sets of configuration data: one for live transactions, and one for test transactions.  I assumed that if I was doing my form as a test drive, it would use the test data, which is https://test.authorize.net/gateway/transact.dll.  Is that not correct?

Another problem is that the Authorize.net account is being used live to sell other products.  Are you saying that I can't do test transactions using test.authorize.net - and therefore even test my membership registration page - unless I put the Authorize.net account in test mode?

Thanks.

[Dave Greenberg]

I've shared the extent of my knowledge on this :-( Perhaps others with live experience with Auth.net will be able to shed more light.

[Wonder95]

I just chatted with Authorize.net. and was told that in order to use the test server (i.e. test.authorize.net), you must have a test account set up with them (at developer.authorize.net/test).  If you are using the live server, you must put your account in test mode to run test transactions.

I still have one CiviCRM question that I'm hoping you can answer, Dave.  Since there is test and live configuration info set up in the Payment Processor setup screen, is it safe to assume that when I do a Test drive with my contribution form that it is using the test data, and if I use the live page, then I am using the live data?

Thanks.

[Dave Greenberg]

Yes - that's correct. Test-drive uses "Test Payments" configuration section values, Live transactions use "Live Payments".

[Wonder95]

OK, I got the test account set up at Authorize.net, but when I submit a test page, I get this error:

Code: [Select]

Array
(
    [callback] => Array
        (
            [0] => CRM_Core_Error
            [1] => handle
        )

    [code] =>
    [message] => Invalid response code received from server
    [mode] => 16
    [debug_info] =>
    [type] => PEAR_Error
    [user_info] =>
    [to_string] => [pear_error: message="Invalid response code received from server" code=0 mode=callback callback=CRM_Core_Error::handle prefix="" info=""]
)
This doesn't really give me a lot of info.  Is there a way get more detail on what the invalid code is?[/code]

[Kurund Jalmi]

Quick forum search for above error:

http://forum.civicrm.org/index.php/topic,1309.0.html

kurund

[flug]

I just chatted with Authorize.net. and was told that in order to use the test server (i.e. test.authorize.net), you must have a test account set up with them (at developer.authorize.net/test).  If you are using the live server, you must put your account in test mode to run test transactions.

I still have one CiviCRM question that I'm hoping you can answer, Dave.  Since there is test and live configuration info set up in the Payment Processor setup screen, is it safe to assume that when I do a Test drive with my contribution form that it is using the test data, and if I use the live page, then I am using the live data?

Thanks.

A little more info from the authorize.net help files:

Response Reason Text: The merchant Login ID is invalid or the account is inactive.

This error indicates you are either posting the incorrect API Login ID within your script, connecting to a server that does not recognize your account, or using an account which is inactive. Please follow these steps to ensure that your software is connecting correctly:

• If you are posting your transaction requests to the gateway URLs https://test.authorize.net/gateway/transact.dll or https://certification.authorize.net/gateway/transact.dll and you are using an account given to you by an Authorize.Net Reseller or from Authorize.Net Sales, you may encounter this error. The gateway URLs mentioned above only work with specific test accounts, available upon request by completing the form at http://developer.authorize.net/testaccount/

Try posting your transaction request to https://secure.authorize.net/gateway/transact.dll instead. If you need to submit a test transaction, you may do so by setting the field x_test_request to "TRUE". You may then remove x_test_request or set it to "FALSE" when you have completed your testing.

Note: If you are integrating your website with Advanced Integration Method (AIM) using PHP, please be aware that the gateway URL is listed twice--once in the cURL configuration, and once again in the main body of the code. Using the test gateway URL in the cURL section of the code will create an Error 13 as cURL would connect to the incorrect server.

  From: http://www.fuzeqna.com/authorize.net/consumer/kbdetail.asp?kbid=364&p=t

In short, it looks like to use CiviCRM's default testing setup for Authorize.net you need a special developers/testing account.  However it could be set up to simply set the special x_test_request field when testing instead.

[Donald Lobo]

actually the civicrm auth.net code (which is a contributed payment processor) does that. You just need to give the same account setting for the live vs test mode

lobo