Authorize.net Problem (AIM)

[cycochuck]

I am having a problem AIM expecting a MD5 hash from the merchant account when one isn't set.

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

I have no md5 hash set in either zen admin or the merchant account, but it looks like zen is creating one and expecting it from the merchant account. Any ideas on how to fix this?

[DrByte]

Back up a bit. What happened to lead you to research and think your problem is MD5-related?

[cycochuck]

I am having a problem AIM expecting a MD5 hash from the merchant account when one isn't set.



I have no md5 hash set in either zen admin or the merchant account, but it looks like zen is creating one and expecting it from the merchant account. Any ideas on how to fix this?

Sorry, posted the wrong error.

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

The previous error is from me trying to bypass this error.

[DrByte]

So, you're getting basically no results back.
What about the details being *sent*?

Again I ask ... there's a reason why you started looking into this. What was it? Did you see an error message on your site? Did you see a ghost in a dream that told you something is wrong with your MD5 hash?

[cycochuck]

So, you're getting basically no results back.
What about the details being *sent*?

Again I ask ... there's a reason why you started looking into this. What was it? Did you see an error message on your site? Did you see a ghost in a dream that told you something is wrong with your MD5 hash?

Sorry, should of posted more info. I've been using the NaviGate for credit card processing from merchantplus.com. Their system is compatible with AIM settings as long as you can change the url that the software points to to process cards. They do provide a zen cart aim module that works except for the little fact that is there is any error message (such as a mistyped number) the customer is left with a blank screen. After having to do a few phone orders (with another piece of software with a modified AIM module) I went to try to modify the current zen AIM module to work for me so that I can have error messages.

I modified the module so that the url points to the correct server and set it up in zen and thats where the problems begin.

On the customer side I am getting

Communications Error - Please notify webmaster. - Your credit card could not be authorized for this reason. Please correct the information and try again or contact us for further assistance.

On the server I am getting an AIM error message in the cache directory.

Nov-26-2010 10:57:59
=================================

Comm results: 6 name lookup timed 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] => 7.82
[x_currency_code] => USD
[x_card_num] => XXXXXXXXXXXXXXXXXXX3208
[x_exp_date] => 0712
[x_card_code] => ****
[x_email_customer] => FALSE
[x_email_merchant] => FALSE
[x_cust_id] => 1
[x_invoice_num] => 1479-RGgaCd
[x_first_name] => xxxxxxx
[x_last_name] => xxxxxxx
[x_company] =>
[x_address] => xxxxxxxx
[x_city] => xxxxxxxx
[x_state] => xxxxxxx
[x_zip] => xxxxxx
[x_country] => United States
[x_phone] => xxxxxxxxxx
[x_email] => xxxxxxxxxxx
[x_ship_to_first_name] => xxxxxxxx
[x_ship_to_last_name] => xxxxxxx
[x_ship_to_address] => xxxxxxxxx
[x_ship_to_city] => xxxxxxxx
[x_ship_to_state] => xxxxxxxx
[x_ship_to_zip] => xxxxxxxxxxxx
[x_ship_to_country] => United States
[x_description] => Flavorwood Alder Cans (qty: 2)
[x_recurring_billing] => NO
[x_customer_ip] => xxxxxxxxx
[x_po_num] => Nov-26-2010 10:57:44
[x_freight] => 7.00
[x_tax_exempt] => FALSE
[x_tax] => 0.06
[x_duty] => 0
[x_allow_partial_Auth] => FALSE
[Date] => November 26, 2010, 10:57 am
[IP] => xxxxxxxxxxxx
[Session] => 2lnin8h09r91u6l9vraj4ea3o7
[url] => https://gateway.merchantplus.com/cgi-bin/PAWebClient.cgi
)


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


CURL communication info: Array
(
[url] => https://gateway.merchantplus.com/cgi-bin/PAWebClient.cgi
[content_type] =>
[http_code] => 0
[header_size] => 0
[request_size] => 0
[filetime] => -1
[ssl_verify_result] => 0
[redirect_count] => 0
[total_time] => 0
[namelookup_time] => 14.992
[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:

To me it looks like zen is looking for a md5 hash when there isn't one set on either zen or the merchant account.

[DrByte]

On the server I am getting an AIM error message in the cache directory.

6 name lookup timed out

To me it looks like zen is looking for a md5 hash when there isn't one set on either zen or the merchant account.

No, actually your problem is with the actual error message you quoted. It has nothing to do with MD5 hash calculations at all.

Error #6 "name lookup timed out" tells me that your server's CURL client is unable to do a name lookup to attempt to connect to the gateway's URL.
This is a typical problem when the server is misconfigured.
It could be bad resolv.cnf entries, which only the server administrator can fix.
It could be bad SSL configuration (SSL not compiled into CURL when compiled into PHP), which is also something the server administrator must fix for you.

[cycochuck]

Thank you for the help! That explains why the other modified AIM modules for other software works and this one didn't. They all were using javascript to send the info to the merchant account. After some digging on google I've found the solution to my problem (damn Godaddy!) and now up and running. Hopefully I can now get through the holidays without anymore calls from people having trouble ordering.