Another Authorize.net Hash Problem thread

[prodigious]

Hello everyone -

I have gone through just about every Hash thread in these forums and I still can't seem to find a solution for what's going on with my cart. Here are the details:

* Hosting company: Lunarpages
* cURL enabled: Yes
* Authorize.net AIM: Yes
* Did I check that the Hash was correct on both Auth.net and Zen: Yes, many times
* Is it under 20 characters: Yes
* Is my SSL setup correctly: Yes
* Is my API login and Transaction key correctly typed in: Yes
* Is my Auth.net account active: Yes
* Did I read the Zen Cart AIM tutorial: Yes


I get the dreaded "Security Hash Problem. Please contact store owner..." message after submitting any kind of payment.

Are there any other ideas we can try? I have included my logfile for review below. Also, does anyone know how to remove the hash entirely from Auth.net? It seems that once you put one in, you can only change it to another one thereafter.

Thanks in advance!
Mike



Logfile:

Oct-11-2008 10:13:46
=================================

Response Code: 3.
Response Text: This transaction cannot be accepted.

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_ONLY
    [x_method] => CC
    [x_amount] => 1.00
    [x_currency_code] => USD
    [x_card_num] => XXXXXXXXXXXXXXXXX0027
    [x_exp_date] => 0109
    [x_card_code] => ****
    [x_email_customer] => FALSE
    [x_email_merchant] => FALSE
    [x_cust_id] => 3
    [x_invoice_num] => 1-BZxioy
    [x_first_name] => mike
    [x_last_name] => lastname
    [x_company] => company
    [x_address] => street_address
    [x_city] => city
    [x_state] => Alabama
    [x_zip] => postcode
    [x_country] => United States
    [x_phone] => telephone
    [x_email] => [email protected]
    [x_ship_to_first_name] => mike
    [x_ship_to_last_name] => lastname
    [x_ship_to_address] => street_address
    [x_ship_to_city] => city
    [x_ship_to_state] => Alabama
    [x_ship_to_zip] => postcode
    [x_ship_to_country] => United States
    [x_description] => test (qty: 1) 
    [x_recurring_billing] => NO
    [x_customer_ip] => 70.222.222.222
    [x_po_num] => Oct-11-2008 10:13:46
    [x_freight] => 0.00
    [x_tax_exempt] => FALSE
    [x_tax] => 0.00
    [x_duty] => 0
    [Date] => October 11, 2008, 10:13 am
    [IP] => 70.222.222.222
    [Session] => 992b171168c7a9204c9d461816dba748
    [url] => https://secure.authorize.net/gateway/transact.dll
)


Results Received back from Authorizenet: Array
(
    [0] => Response from gateway
    [1] => 3
    [2] => 1
    [3] => 103
    [4] => This transaction cannot be accepted.
    [5] => 
    [6] => P
    [7] => 0
    [8] => 
    [9] => 
    [10] => 1.00
    [11] => CC
    [12] => auth_only
    [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] => B19034035861764E5F8F8A1C8F6A535B
    [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] => October 11, 2008, 10:13 am
    [70] => 70.222.222.222
    [71] => 992b171168c7a9204c9d461816dba748
    [Expected-MD5-Hash] => FC5AA18D9DA72B6691E12DE44909F382
    [HashMatchStatus] => FAIL
)


CURL communication info: Array
(
    [url] => https://secure.authorize.net/gateway/transact.dll
    [content_type] => text/html
    [http_code] => 200
    [header_size] => 237
    [request_size] => 1132
    [filetime] => -1
    [ssl_verify_result] => 0
    [redirect_count] => 0
    [total_time] => 0.153989
    [namelookup_time] => 0.002886
    [connect_time] => 0.033031
    [pretransfer_time] => 0.109908
    [size_upload] => 982
    [size_download] => 370
    [speed_download] => 2402
    [speed_upload] => 6377
    [download_content_length] => 370
    [upload_content_length] => 0
    [starttransfer_time] => 0.153859
    [redirect_time] => 0
)


RAW data received: 
*3*|*1*|*103*|*This transaction cannot be
accepted.*|**|*P*|*0*|**|**|*1.00*|*CC*|*auth_only*|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|*B19034035861764E5F8F8A1C8F6A535B*|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|*October
11, 2008, 10:13 am*|*70.112.1.6*|*992b171168c7a9204c9d461816dba748*

[DrByte]

Oct-11-2008 10:13:46
=================================

Response Code: 3.
Response Text: This transaction cannot be accepted.

...

Results Received back from Authorizenet: Array
(
    [0] => Response from gateway
    [1] => 3
    [2] => 1
    [3] => 103
    [4] => This transaction cannot be accepted.

Code 103 means you've got invalid security credentials ... typically this is a result of an invalid Transaction Key.
Maybe you need to have your key regenerated, and then re-enter it again?

[prodigious]

Ok! I think we are making progress. I still get the Hash error, but my logfile notes a different response from the gateway, it says the transaction has been declined.

Note that I am using the test Visa card # provided in the SIM module. I assume it also works in the AIM module.

Oct-11-2008 11:36:44
=================================

Response Code: 2.
Response Text: This transaction has been declined.

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] => 1.00
    [x_currency_code] => USD
    [x_card_num] => XXXXXXXXXXXXXXXXX0027
    [x_exp_date] => 0109
    [x_card_code] => ****
    [x_email_customer] => FALSE
    [x_email_merchant] => FALSE
    [x_cust_id] => 3
    [x_invoice_num] => 1-iHLd1j
    [x_first_name] => mike
    [x_last_name] => lastname
    [x_company] => company
    [x_address] => street_address
    [x_city] => city
    [x_state] => Alabama
    [x_zip] => postcode
    [x_country] => United States
    [x_phone] => telephone
    [x_email] => [email protected]
    [x_ship_to_first_name] => mike
    [x_ship_to_last_name] => lastname
    [x_ship_to_address] => street_address
    [x_ship_to_city] => city
    [x_ship_to_state] => Alabama
    [x_ship_to_zip] => postcode
    [x_ship_to_country] => United States
    [x_description] => test (qty: 1) 
    [x_recurring_billing] => NO
    [x_customer_ip] => 
    [x_po_num] => Oct-11-2008 11:36:43
    [x_freight] => 0.00
    [x_tax_exempt] => FALSE
    [x_tax] => 0.00
    [x_duty] => 0
    [Date] => October 11, 2008, 11:36 am
    [IP] => 
    [Session] => 2f746af245c52f99ab3f17e1acb62eb4
    [url] => https://secure.authorize.net/gateway/transact.dll
)


Results Received back from Authorizenet: Array
(
    [0] => Response from gateway
    [1] => 2
    [2] => 1
    [3] => 2
    [4] => This transaction has been declined.
    [5] => 
    [6] => U
    [7] => 2021477099
    [8] => 1-iHLd1j
    [9] => test (qty: 1)
    [10] => 1.00
    [11] => CC
    [12] => auth_capture
    [13] => 3
    [14] => mike
    [15] => lastname
    [16] => company
    [17] => street_address
    [18] => city
    [19] => Alabama
    [20] => postcode
    [21] => United States
    [22] => telephone
    [23] => 
    [24] => [email protected]
    [25] => mike
    [26] => lastname
    [27] => 
    [28] => street_address
    [29] => city
    [30] => Alabama
    [31] => postcode
    [32] => United States
    [33] => 0.0000
    [34] => 0.0000
    [35] => 0.0000
    [36] => FALSE
    [37] => Oct-11-2008 11:36:43
    [38] => C150DAFE43BCD408BBC699AB00505CB8
    [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] => October 11, 2008, 11:36 am
    [70] => 
    [71] => 2f746af245c52f99ab3f17e1acb62eb4
    [Expected-MD5-Hash] => 0154AA678D2B9B3CE08307DE18CBBB8A
    [HashMatchStatus] => FAIL
)


CURL communication info: Array
(
    [url] => https://secure.authorize.net/gateway/transact.dll
    [content_type] => text/html
    [http_code] => 200
    [header_size] => 237
    [request_size] => 1135
    [filetime] => -1
    [ssl_verify_result] => 0
    [redirect_count] => 0
    [total_time] => 0.985553
    [namelookup_time] => 0.057674
    [connect_time] => 0.087741
    [pretransfer_time] => 0.203458
    [size_upload] => 985
    [size_download] => 591
    [speed_download] => 599
    [speed_upload] => 999
    [download_content_length] => 591
    [upload_content_length] => 0
    [starttransfer_time] => 0.985406
    [redirect_time] => 0
)


RAW data received: 
*2*|*1*|*2*|*This transaction has been
declined.*|**|*U*|*2021477099*|*1-iHLd1j*|*test (qty:
1)*|*1.00*|*CC*|*auth_capture*|*3*|*mike*|*lastname*|*company*|*street_address*|*city*|*Alabama*|*postcode*|*United
States*|*telephone*|**|*[email protected]*|*mike*|*lastname*|**|*street_address*|*city*|*Alabama*|*postcode*|*United
States*|*0.0000*|*0.0000*|*0.0000*|*FALSE*|*Oct-11-2008
11:36:43*|*C150DAFE43BCD408BBC699AB00505CB8*|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|*October
11, 2008, 11:36 am*|*222.222.222.222*|*2f746af245c52f99ab3f17e1acb62eb4*

[DrByte]

The test card number will always give you a decline when the account is in production mode.

If you're getting a "FAIL" on the hash, I suspect you've still got a typo on it. Remember, the same word is entered on both ends, identically. No translations. No MD5-hashing of it. The MD5 part is done by the software, not by you.

[prodigious]

Hi Dr Byte,

First off - thanks so much for your quick replies.

I figured as much for the decline, and that makes sense. As far as the continuing hash problem, I went and typed the same phrase in, one more time, in both the AIM admin area in my Zen Cart and in the settings area in my Auth.net account.

It still gives me the error.

Do you think there is any lagtime between applying the hash value in Auth.net? I presume once you put it in Zen, it is instantaneously applied and active.

Otherwise, I'm at a loss here.

[DrByte]

What's the latest log content?

[prodigious]

This is from the most recent test, using the test card (I assume even though it declines, the hash problem would be present regardless).

Oct-11-2008 12:09:23
=================================

Response Code: 2.
Response Text: This transaction has been declined.

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] => 1.00
    [x_currency_code] => USD
    [x_card_num] => XXXXXXXXXXXXXXXXX0027
    [x_exp_date] => 0110
    [x_card_code] => ****
    [x_email_customer] => FALSE
    [x_email_merchant] => FALSE
    [x_cust_id] => 3
    [x_invoice_num] => 1-RBkJTl
    [x_first_name] => mike
    [x_last_name] => lastname
    [x_company] => company
    [x_address] => street_address
    [x_city] => city
    [x_state] => Alabama
    [x_zip] => postcode
    [x_country] => United States
    [x_phone] => telephone
    [x_email] => [email protected]
    [x_ship_to_first_name] => mike
    [x_ship_to_last_name] => lastname
    [x_ship_to_address] => street_address
    [x_ship_to_city] => city
    [x_ship_to_state] => Alabama
    [x_ship_to_zip] => postcode
    [x_ship_to_country] => United States
    [x_description] => test (qty: 1) 
    [x_recurring_billing] => NO
    [x_customer_ip] => x.x.x.x
    [x_po_num] => Oct-11-2008 12:09:21
    [x_freight] => 0.00
    [x_tax_exempt] => FALSE
    [x_tax] => 0.00
    [x_duty] => 0
    [Date] => October 11, 2008, 12:09 pm
    [IP] => x.x.x.x
    [Session] => f3d3f613f85c01568124329b78cf23b1
    [url] => https://secure.authorize.net/gateway/transact.dll
)


Results Received back from Authorizenet: Array
(
    [0] => Response from gateway
    [1] => 2
    [2] => 1
    [3] => 2
    [4] => This transaction has been declined.
    [5] => 
    [6] => U
    [7] => 2021501262
    [8] => 1-RBkJTl
    [9] => test (qty: 1)
    [10] => 1.00
    [11] => CC
    [12] => auth_capture
    [13] => 3
    [14] => mike
    [15] => lastname
    [16] => company
    [17] => street_address
    [18] => city
    [19] => Alabama
    [20] => postcode
    [21] => United States
    [22] => telephone
    [23] => 
    [24] => [email protected]
    [25] => mike
    [26] => lastname
    [27] => 
    [28] => street_address
    [29] => city
    [30] => Alabama
    [31] => postcode
    [32] => United States
    [33] => 0.0000
    [34] => 0.0000
    [35] => 0.0000
    [36] => FALSE
    [37] => Oct-11-2008 12:09:21
    [38] => 131BF9FBACB5CF72D3EEB9BF943B10AD
    [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] => October 11, 2008, 12:09 pm
    [70] => x.x.x.x
    [71] => f3d3f613f85c01568124329b78cf23b1
    [Expected-MD5-Hash] => BE01166E3304460DAC6412EF0FEC521B
    [HashMatchStatus] => FAIL
)


CURL communication info: Array
(
    [url] => https://secure.authorize.net/gateway/transact.dll
    [content_type] => text/html
    [http_code] => 200
    [header_size] => 237
    [request_size] => 1135
    [filetime] => -1
    [ssl_verify_result] => 0
    [redirect_count] => 0
    [total_time] => 1.41826
    [namelookup_time] => 0.003075
    [connect_time] => 0.039556
    [pretransfer_time] => 0.126097
    [size_upload] => 985
    [size_download] => 591
    [speed_download] => 416
    [speed_upload] => 694
    [download_content_length] => 591
    [upload_content_length] => 0
    [starttransfer_time] => 1.418092
    [redirect_time] => 0
)


RAW data received: 
*2*|*1*|*2*|*This transaction has been
declined.*|**|*U*|*2021501262*|*1-RBkJTl*|*test (qty:
1)*|*1.00*|*CC*|*auth_capture*|*3*|*mike*|*lastname*|*company*|*street_address*|*city*|*Alabama*|*postcode*|*United
States*|*telephone*|**|*[email protected]*|*mike*|*lastname*|**|*street_address*|*city*|*Alabama*|*postcode*|*United
States*|*0.0000*|*0.0000*|*0.0000*|*FALSE*|*Oct-11-2008
12:09:21*|*131BF9FBACB5CF72D3EEB9BF943B10AD*|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|*October
11, 2008, 12:09 pm*|*x.x.x.x*|*f3d3f613f85c01568124329b78cf23b1*

[DrByte]

And what happens if you try a "real" card?

[prodigious]

Unfortunately, the same thing happens with a real card.

Response Code: 2.
Response Text: This transaction has been declined.


Results Received back from Authorizenet: Array
(
    [0] => Response from gateway
    [1] => 2
    [2] => 2
    [3] => 44
    [4] => This transaction has been declined.
    [5] => 
    [6] => Y


    [68] => 
    [69] => October 12, 2008, 5:02 am
    [70] => x.x.x.x
    [71] => eb241ee4646f721a95f317ec69b7a204
    [Expected-MD5-Hash] => 82A3E4CCBE02EF3BF6F126CA94740495
    [HashMatchStatus] => FAIL
)

[DrByte]

Error code 44 means you have a "Card Code filter set in the Merchant Interface and the transaction received an error code from the processor that matched the rejection criteria set by the merchant."
Basically, it means your authnet account has some restrictions set up in it which are preventing that transaction from going through. You'll have to sort that out by calling your authnet account rep.