Authorize.net Error

[z3n]

Hi,

I've searched and found some other threads about this, but can't find a clear answer to resolve it. I have Authorize.net AIM installed and configured properly, using the hash setting as well, I have SSL & cURL installed on the server. When I try to process a transaction (in test or production mode) I get the following errors:

WARNING: Security hash problem. Please contact store-owner immediately. Your order has *not* been fully authorized.

This transaction cannot be accepted. - Your credit card could not be authorized for this reason. Please correct the information and try again or contact us for further assistance.

I've talked to Authorize.net support on two occasions about this, neither person was able to help me.

Any help or direction would be great. Thanks!

[DrByte]

AIM Setup Instructions are here: https://www.zen-cart.com/tutorials/i...hp?article=373

The MD5 Hash code that you enter must be a word/phrase of maximum 20 characters length, and you must enter the SAME word/phrase in both your authnet account profile and your zen cart admin. Do not attempt to md5-encode it yourself -- just key in the same phrase in both places.

[z3n]

OK, I am no longer getting the hash error, but I am getting this:

This transaction cannot be accepted. - Your credit card could not be authorized for this reason. Please correct the information and try again or contact us for further assistance.

I am in LIVE mode on both Authorize.net & ZC, I have triple checked every setting, I can't figure this out. A.NET support keeps telling me it is a ZC issue.

I have my SSL working, cURL is installed... I am clueless at this point and frustrated.

[DrByte]

What's in the debug logs?

[z3n]

What's in the debug logs?

I've censored the sensitive info..

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] => 0.01
[x_currency_code] => USD
[x_card_num] => XXXXXXXXXXXXXXXX4580
[x_exp_date] => 0911
[x_card_code] => ****
[x_email_customer] => TRUE
[x_email_merchant] => TRUE
[x_cust_id] => 9
[x_invoice_num] => 1-5ErsXe
[x_first_name] => Joe
[x_last_name] => Customer
[x_company] =>
[x_address] => 123 Fake St.
[x_city] => Springfield
[x_state] => MO
[x_zip] => 54899
[x_country] => United States
[x_phone] => 123456789
[x_email] => [email protected]
[x_ship_to_first_name] => Joe
[x_ship_to_last_name] => Customer
[x_ship_to_address] => 123 Fake St.
[x_ship_to_city] => Springfield
[x_ship_to_state] => MO
[x_ship_to_zip] => 54899
[x_ship_to_country] => United States
[x_description] => Cheap test product (qty: 1)
[x_recurring_billing] => NO
[x_customer_ip] => 123.456.789
[x_po_num] => Sep-04-2008 02:11:06
[x_freight] => 0.00
[x_tax_exempt] => FALSE
[x_tax] => 0.00
[x_duty] => 0
[Date] => September 4, 2008, 2:11 pm
[IP] => 123.456.789
[Session] => b51dc2f0435fe636a934c326bdc2ea5d
[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] => 0.01
[11] => CC
[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] => 9894BCC34fBBC663AE18F4E22ADA0CB8
[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] => September 4, 2008, 2:11 pm
[70] => 123.456.789
[71] => b51dd32f0d43fec66a90c326bdc2ea5d
[Expected-MD5-Hash] => 9894BC5d66BBC2663AE8F4E221DA0CB8
[HashMatchStatus] => PASS
)


CURL communication info: Array
(
[url] => https://secure.authorize.net/gateway/transact.dll
[content_type] => text/html
[http_code] => 200
[header_size] => 237
[request_size] => 1153
[filetime] => -1
[ssl_verify_result] => 0
[redirect_count] => 0
[total_time] => 5.571621
[namelookup_time] => 5.025457
[connect_time] => 5.109632
[pretransfer_time] => 5.29631
[size_upload] => 1002
[size_download] => 376
[speed_download] => 67
[speed_upload] => 179
[download_content_length] => 376
[upload_content_length] => 0
[starttransfer_time] => 5.571497
[redirect_time] => 0
)


RAW data received:
*3*|*1*|*103*|*This transaction cannot be accepted.*|**|*P*|*0*|**|**|*0.01*|*CC*|*auth_capture*|**|**|**|**|**|**|**|**|* *|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|*9894BCC6BBC2663AE18F4E221ADA0 CB8*|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**| **|**|**|**|**|*September 4, 2008, 2:11 pm*|*132.456.789*|*b51dc2f0435fec636a90c326bdc2ea5d*

[DrByte]

[3] => 103
[4] => This transaction cannot be accepted.

Error code 103 means you've supplied an incorrect transaction key.
If you're absolutely convinced you've supplied the right transaction key, contact Authnet support for specific assistance.