authorize.net AIM response code 13 since update from 1.3.9d to 1.3.9h

[billc108]

I recently updated a client form 1.3.9d to 1.3.9h, and suddenly his authorize.net AIM gateway isn't working.

api login looks correct and acct is active according to Auth.net, but I'm getting

[0] => Response from gateway
[1] => 3
[2] => 2
[3] => 13
[4] => The merchant login ID or password is invalid or the account is inactive.
[5] =>
[6] => P
[7] => 0
[8] =>
[9] =>
[10] => 9.21
[11] =>
[12] => auth_capture

Auth.net says talk to you...

I've already turned the module off and back on, as well as set to test mode. No difference either way.

I see there are a fair number of changes to the AIM module. Anything in particular I should check or try?

[haredo]

You're using invalid login ID and/or transaction key.
Look to see if a new one was not generated for you

[haredo]

Read this thread please:

http://www.zen-cart.com/forum/showthread.php?t=87443

[billc108]

Thanks for the quick reply.

Already checked the login ID, and as far as I can tell (and the Auth.net live chat guy can tell) it's correct. It hasn't been changed in years, anyway.

Already reset the transaction key, so that's not it.

I read the stuff in the other thread. We're not in test mode (though I did try that and got the same response).

Any other ideas?

[DrByte]

[0] => Response from gateway
[1] => 3
[2] => 2
[3] => 13
[4] => The merchant login ID or password is invalid or the account is inactive.

Regardless of your statement that "auth.net says talk to you", how do you expect *us* to fix an authentication problem that exists between the merchant and the auth.net servers?
Or maybe you can explain how "we" can fix a "merchant login ID or password is invalid" message magically for them?

Or maybe you've configured it to connect to the wrong server? The full log file content would help determine that, but you didn't share the whole thing.

[billc108]

Regardless of your statement that "auth.net says talk to you", how do you expect *us* to fix an authentication problem that exists between the merchant and the auth.net servers?
Or maybe you can explain how "we" can fix a "merchant login ID or password is invalid" message magically for them?

Certainly I don't expect you to fix a problem between the merchant and auth.net... except that the only change I'm aware of was the update from 1.3.9d to 1.3.9h. So I thought you might have a clue.

Or maybe you've configured it to connect to the wrong server? The full log file content would help determine that, but you didn't share the whole thing.

Ok, I was just trying to cut to the relevant details. Here's the full deal. I have more if you want to see 'em.

Apr-21-2011 04:54:05
=================================

Response Code: 3.
Response Text: The merchant login ID or password is invalid or the account is inactive.

Sending to Authorizenet: Array
(
[x_login] => *******
[x_tran_key] => *******
[x_relay_response] => FALSE
[x_delim_data] => TRUE
[x_delim_char] => |
[x_encap_char] => *
[x_version] => 3.1
[x_type] => AUTH_CAPTURE
[x_method] => CC
[x_amount] => 9.21
[x_currency_code] => USD
[x_card_num] => XXXXXXXXXXXXXXXX8653
[x_exp_date] => 0412
[x_card_code] => ****
[x_email_customer] => FALSE
[x_email_merchant] => FALSE
[x_cust_id] => 212
[x_invoice_num] => 2226-pVjgvU
[x_first_name] => bill
[x_last_name] => c testing
[x_company] =>
[x_address] => 4 crystal creek trail
[x_city] => austin
[x_state] => Texas
[x_zip] => 78737
[x_country] => United States
[x_phone] => 512-288-5223
[x_email] => [email protected]
[x_ship_to_first_name] => bill
[x_ship_to_last_name] => c testing
[x_ship_to_address] => 4 crystal creek trail
[x_ship_to_city] => austin
[x_ship_to_state] => Texas
[x_ship_to_zip] => 78737
[x_ship_to_country] => United States
[x_description] => test product (qty: 1)
[x_recurring_billing] => NO
[x_customer_ip] => 205.238.182.108
[x_po_num] => Apr-21-2011 04:54:04
[x_freight] => 9.20
[x_tax_exempt] => FALSE
[x_tax] => 0.00
[x_duty] => 0
[x_allow_partial_Auth] => FALSE
[Date] => April 21, 2011, 4:54 pm
[IP] => 205.238.182.108
[Session] => pbtlf9b3e3nit3jis0s4898797
[url] => https://secure.authorize.net/gateway/transact.dll
)


Results Received back from Authorizenet: Array
(
[0] => Response from gateway
[1] => 3
[2] => 2
[3] => 13
[4] => The merchant login ID or password is invalid or the account is inactive.
[5] =>
[6] => P
[7] => 0
[8] =>
[9] =>
[10] => 9.21
[11] =>
[12] => auth_capture
[13] =>
[14] =>
[15] =>
[16] =>
[17] =>
[18] =>
[19] =>
[20] =>
[21] =>
[22] =>
[23] =>
[24] =>
[25] =>
[26] =>
[27] =>
[28] =>
[29] =>
[30] =>
[31] =>
[32] =>
[33] =>
[34] =>
[35] =>
[36] =>
[37] =>
[38] => 0826F9FDC906EF0E78845E7E9764CA2F
[39] =>
[40] =>
[41] =>
[42] =>
[43] =>
[44] =>
[45] =>
[46] =>
[47] =>
[48] =>
[49] =>
[50] =>
[51] =>
[52] =>
[53] =>
[54] =>
[55] =>
[56] =>
[57] =>
[58] =>
[59] =>
[60] =>
[61] =>
[62] =>
[63] =>
[64] =>
[65] =>
[66] =>
[67] =>
[68] =>
[69] => April 21, 2011, 4:54 pm
[70] => 205.238.182.108
[71] => pbtlf9b3e3nit3jis0s4898797
[Expected-MD5-Hash] => 955CF63D7311EAA225F44BBC1079B4E9
[HashMatchStatus] => FAIL
)


CURL communication info: Array
(
[url] => https://secure.authorize.net/gateway/transact.dll
[content_type] => text/html
[http_code] => 200
[header_size] => 196
[request_size] => 208
[filetime] => -1
[ssl_verify_result] => 0
[redirect_count] => 0
[total_time] => 0.611187
[namelookup_time] => 0.104298
[connect_time] => 0.178459
[pretransfer_time] => 0.452612
[size_upload] => 1048
[size_download] => 402
[speed_download] => 657
[speed_upload] => 1714
[download_content_length] => 402
[upload_content_length] => 1048
[starttransfer_time] => 0.52704
[redirect_time] => 0
[certinfo] => Array
(
)

)


RAW data received:
*3*|*2*|*13*|*The merchant login ID or password is invalid or the account is inactive.*|**|*P*|*0*|**|**|*9.21*|**|*auth_capture*|**|**|**|**|**|**|**|**|**| **|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|*0826F9FDC906EF0E78845E7E9764CA2 F*|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|** |**|**|**|**|*April 21, 2011, 4:54 pm*|*205.238.182.108*|*pbtlf9b3e3nit3jis0s4898797*

[DrByte]

Looks to be nothing wrong with the submission content or destination. The error seems to be the best path to chase.
The account number and transaction key need to be valid. Might need to regenerate a transaction key in his account.
There's a setup tutorial FAQ on AIM configuration in the ZC Tutorials/FAQs area for further troubleshooting ideas.

[billc108]

Weird. After checking many other things, reverting back to version d, etc, I went back and reset the login ID and the transaction key again, and it worked. Strange since I did a copy/paste both times.

As usual, you were right about that being the actual problem even though everything checked out properly on a visual check.

[haredo]

Great you are up and running...
Persistence pays ...

[NumberSix]

I am nearing my wits end with this Merchant ID thing. Same problem as above poster.

Client updated the site on his own. (Which broke some custom code). I have fixed most of it. The only problem lies now with:

"The merchant login ID or password is invalid or the account is inactive."

Client is with Chase Paymentech. I keep re-generating the transaction key and updating Authorizenet (AIM) in ZenCart.

Every time, it fails with The merchant login ID or password is invalid or the account is inactive.

Even tried a fresh install of 1.3.9.h. with resets. Same problem. According to Chase, the Login is Active and was working prior to this update.

Both Zen and Chase are set to production when generating or entering login and keys. Not a test mode issue.

Log shows:

#######################################
Jun-05-2011 02:09:11
=================================

Response Code: 3.
Response Text: The merchant login ID or password is invalid or the account is inactive.

Sending to Authorizenet: Array
(
[x_login] => *******
[x_tran_key] => *******
[x_relay_response] => FALSE
[x_delim_data] => TRUE
[x_delim_char] => |
[x_encap_char] => *
[x_version] => 3.1
[x_type] => AUTH_CAPTURE
[x_method] => CC
[x_amount] => 75.70
[x_currency_code] => USD
[x_card_num] => XXXXXXXXXXXXXXXX1111
[x_exp_date] => 0613
[x_card_code] =>
[x_email_customer] => FALSE
[x_email_merchant] => TRUE
[x_cust_id] => 49
[x_invoice_num] => 85-MPPCwz
[x_first_name] => XXXXX
[x_last_name] => XXXXXXXX
[x_company] =>
[x_address] => XXXXXXXX Circle
[x_city] => Nepean
[x_state] => Ontario
[x_zip] => XXX XXX
[x_country] => Canada
[x_phone] =>
[x_email] => XXXXXXXXXXXXXXXXX
[x_ship_to_first_name] => XXXXXX
[x_ship_to_last_name] => XXXXXXX
[x_ship_to_address] => XXXXXXXXX
[x_ship_to_city] => Nepean
[x_ship_to_state] => Ontario
[x_ship_to_zip] => XXX XXX
[x_ship_to_country] => Canada
[x_description] => Add a Little Life (qty: 1)
[x_recurring_billing] => NO
[x_customer_ip] => 99.242.72.155
[x_po_num] => Jun-05-2011 02:09:10
[x_freight] => 7.00
[x_tax_exempt] => FALSE
[x_tax] => 8.71
[x_duty] => 0
[x_allow_partial_Auth] => FALSE
[Date] => June 5, 2011, 2:09 pm
[IP] => 99.242.72.155
[Session] => d14ce77653001cb84db37abd4942fa59
[url] => https://secure.authorize.net/gateway/transact.dll
)


Results Received back from Authorizenet: Array
(
[0] => Response from gateway
[1] => 3
[2] => 2
[3] => 13
[4] => The merchant login ID or password is invalid or the account is inactive.
[5] =>
[6] => P
[7] => 0
[8] =>
[9] =>
[10] => 75.70
[11] =>
[12] => auth_capture
[13] =>
[14] =>
[15] =>
[16] =>
[17] =>
[18] =>
[19] =>
[20] =>
[21] =>
[22] =>
[23] =>
[24] =>
[25] =>
[26] =>
[27] =>
[28] =>
[29] =>
[30] =>
[31] =>
[32] =>
[33] =>
[34] =>
[35] =>
[36] =>
[37] =>
[38] => 0558524998C3607AEB6A236E02EA3D3C
[39] =>
[40] =>
[41] =>
[42] =>
[43] =>
[44] =>
[45] =>
[46] =>
[47] =>
[48] =>
[49] =>
[50] =>
[51] =>
[52] =>
[53] =>
[54] =>
[55] =>
[56] =>
[57] =>
[58] =>
[59] =>
[60] =>
[61] =>
[62] =>
[63] =>
[64] =>
[65] =>
[66] =>
[67] =>
[68] =>
[69] => June 5, 2011, 2:09 pm
[70] => 99.242.72.155
[71] => d14ce77653001cb84db37abd4942fa59
[Expected-MD5-Hash] => 1233BAB25D32CEF4BA8A7F0144E7BCF3
[HashMatchStatus] => FAIL
)


CURL communication info: Array
(
[url] => https://secure.authorize.net/gateway/transact.dll
[content_type] => text/html
[http_code] => 200
[header_size] => 196
[request_size] => 210
[filetime] => -1
[ssl_verify_result] => 0
[redirect_count] => 0
[total_time] => 0.631289
[namelookup_time] => 0.185298
[connect_time] => 0.254108
[pretransfer_time] => 0.486927
[size_upload] => 1030
[size_download] => 405
[speed_download] => 641
[speed_upload] => 1631
[download_content_length] => 405
[upload_content_length] => 1030
[starttransfer_time] => 0.556704
[redirect_time] => 0
[certinfo] => Array
(
)

)


RAW data received:
*3*|*2*|*13*|*The merchant login ID or password is invalid or the account is inactive.*|**|*P*|*0*|**|**|*75.70*|**|*auth_capture*|**|**|**|**|**|**|**|**|** |**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|*0558524998C3607AEB6A236E02EA3D 3C*|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|* *|**|**|**|**|*June 5, 2011, 2:09 pm*|*99.242.72.155*|*d14ce77653001cb84db37abd4942fa59*