Authorize.net AIM problem

[DrByte]

These values are supposed to match, which is why it's saying "FAIL":

[38] => A08B59825EA507824F997F3B32EC0ADA
[Expected-MD5-Hash] => 870352236DDF2E9DB7CBCE687ADD389A
[HashMatchStatus] => FAIL
)

[billt]

I'm having the same problem. It started this afternoon. The site has been working fine for months doing 500 or more orders a day. I have uninstalled and reinstalled authorize.net aim, put in a new hash and still have the problem. Here is a copy of one of the error logs

Jul-29-2008 04:14:10
=================================

Comm results: 28 Connection time-out

Response Code: .
Response Text:

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] => 22.99
[x_currency_code] => USD
[x_card_num] => XXXXXXXXXXXXXXXX7490
[x_exp_date] => 0211
[x_card_code] => ****
[x_email_customer] => FALSE
[x_email_merchant] => TRUE
[x_cust_id] => 70461
[x_invoice_num] => 63436-j3rFOv
[x_first_name] => Alexis
[x_last_name] => Martin
[x_company] =>
[x_address] => 6827 Meadow Ridge Ln.
[x_city] => Lake Charles
[x_state] => Louisiana
[x_zip] => 70605
[x_country] => United States
[x_phone] => 1-337-240-1424
[x_email] => [email protected]
[x_ship_to_first_name] => Alexis
[x_ship_to_last_name] => Martin
[x_ship_to_address] => 6827 Meadow Ridge Ln.
[x_ship_to_city] => Lake Charles
[x_ship_to_state] => Louisiana
[x_ship_to_zip] => 70605
[x_ship_to_country] => United States
[x_description] => Pre-Order New CDVU+ - "A Little Bit Longer" (qty: 1)
[x_recurring_billing] => NO
[x_customer_ip] => 74.193.133.170
[x_po_num] => Jul-29-2008 04:13:55
[x_freight] => 5.00
[x_tax_exempt] => FALSE
[x_tax] => 0.00
[x_duty] => 0
[Date] => July 29, 2008, 4:13 pm
[IP] => 74.193.133.170
[Session] => 69ca75d04e2bdec7ef2b94cae7c517ba
[url] => https://secure.authorize.net/gateway/transact.dll
)


Results Received back from Authorizenet: Array (
[0] => Response from gateway
[1] =>
[Expected-MD5-Hash] => 99042B82DB65EBFBF5EDBFCEAE57B826
[HashMatchStatus] => FAIL
)


CURL communication info: Array
(
[url] => https://secure.authorize.net/gateway/transact.dll
[http_code] => 0
[header_size] => 0
[request_size] => 0
[filetime] => -1
[ssl_verify_result] => 0
[redirect_count] => 0
[total_time] => 0
[namelookup_time] => 15.141388
[connect_time] => 0
[pretransfer_time] => 0
[size_upload] => 0
[size_download] => 0
[speed_download] => 0
[speed_upload] => 0
[download_content_length] => 0
[upload_content_length] => 0
[starttransfer_time] => 0
[redirect_time] => 0
)


RAW data received:


PLEASE HELP!!

Thanks,
Billt

[crocodilehunter]

I was having the EXACT same error message. I checked and rechecked my MD5 Hash code. Still couldn't get the error message to go away, so I checked my Authorize.net log in with my Authorize.net account, and noticed that my API Login had some CASE sensitive letters, so I copied the login from Authorize.net into Zen Cart, and the error message disappeared!!

Advice: If your MD5 hash code is correct, try checking your Authorize.net login and paste it EXACTLY into your Authorize.net (AIM)

It worked for me!!!

[DrByte]

I'm having the same problem. It started this afternoon. The site has been working fine for months doing 500 or more orders a day. I have uninstalled and reinstalled authorize.net aim, put in a new hash and still have the problem. Here is a copy of one of the error logs

Jul-29-2008 04:14:10
=================================

Comm results: 28 Connection time-out

A "Connection time-out" message means that when your server attempted to talk to the Authorize.net server ... a timeout occurred ... ie: it couldn't connect within a reasonable time.
That can be caused by the Authnet servers being down/unreachable/excessively-busy.
It could also be caused by a problem on your hosting company's servers and/or connection to the internet and/or their firewall and/or CURL issues.

Given that "it started happening today", you might want to ask both parties what's been happening with their systems.

There is NO benefit to changing transaction keys or MD5 hash values if there are communication problems. If things "were" working but stopped, find out why ... don't just go changing settings.