Authorize.net AIM problem

[earmsby]

Hi all,

I successfully upgrade my client's store over the weekend and thought everything was fine. However, when I just tested a credit card purchase using the Authorize.net AIM payment module, I get this yellow warning across the screen:

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

I don't see any Hash setting in the module settings in admin. It does seem like the credit card goes through to authorize.net ok so I'm not sure what's up with this message.

It definitely only appeared right after the upgrade - no other changes made since then.

Thanks for any wisdom!

[BlessIsaacola]

Hi all,

I successfully upgrade my client's store over the weekend and thought everything was fine. However, when I just tested a credit card purchase using the Authorize.net AIM payment module, I get this yellow warning across the screen:

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

I don't see any Hash setting in the module settings in admin. It does seem like the credit card goes through to authorize.net ok so I'm not sure what's up with this message.

It definitely only appeared right after the upgrade - no other changes made since then.

Thanks for any wisdom!

Assuming that everything is installed correctly, uninstall Authorize.net Aim from Module/Payments and reinstall it. You will have the new feature to add your MD5 Hash value. It's always a good idea after upgrade to reinstall payment and shipping modules to get all the new features.

[earmsby]

Thanks for your speedy reply. I was just thinking perhaps I should uninstall and then reinstall so thanks for confirming my suspicion.

[earmsby]

Ok, that made the warning go away but now because I do not have any MD5 hash text, no credit cards are being approved.

Is the hash required? We never had anything like that before. On the other hand perhaps it is something my client set up (he's the one who logs into Authorize.net to process the cc transactions).

[BlessIsaacola]

Ok, that made the warning go away but now because I do not have any MD5 hash text, no credit cards are being approved.

Is the hash required? We never had anything like that before. On the other hand perhaps it is something my client set up (he's the one who logs into Authorize.net to process the cc transactions).

You need to have your client login to Authorize.net to enter the value and then whatever value is entered needs to be entered on the Zen Cart Admin side. Alternatively, you can enter a value on the Zen Cart admin side and provide that to your client to enter on the authorize.net side so they both match.

[earmsby]

Thanks again for your help. I got the log in info from my client and added the same MD5 hash string to both Authorize.net and Zencart but the CC is still being turned down.

I even made a new transaction key in case that was part of the problem.

I'm really stumped.

[earmsby]

Never mind. After a few minutes I tried again and it worked. Perhaps it took some time for the hash to get logged into Authorize.net's system.

[lushdawn]

I did all the same things as you and still have that warning:
WARNING: Security hash problem. Please contact store-owner immediately. Your order has *not* been fully authorized.
I have deleted and reinstalled the module...I have changed the MD5 HASH several times in both Authorize.net...then matched it in Zen cart...nothing is working...HELP!!! This error started to occur a few months ago but has NOT been a problem since the initial installation of ZEN.

[DrByte]

The hash code that you use needs to be 20 characters or less. If you're using something longer than that, you're going to have problems.

[lushdawn]

My MD5 Hash is only 12 characters long. I have double checked the values on both ends numerous times. Here is the debug mode log file...this is done in test mode:
Jul-16-2008 03:26:15
=================================

Response Code: 1.
Response Text: (TESTMODE) This transaction has been approved.

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] => 18.95
[x_currency_code] => USD
[x_card_num] => XXXXXXXXXXXXXXXX7914
[x_exp_date] => 0709
[x_card_code] => ****
[x_email_customer] => TRUE
[x_email_merchant] => TRUE
[x_cust_id] => 257
[x_invoice_num] => 1000196-ICHtE3
[x_first_name] => Dawn
[x_last_name] => Ross
[x_company] =>
[x_address] => blah blah st
[x_city] => west chazy
[x_state] => New York
[x_zip] => 12992
[x_country] => United States
[x_phone] => 888-888-2258
[x_email] => [email protected]
[x_ship_to_first_name] => Dawn
[x_ship_to_last_name] => Ross
[x_ship_to_address] => blah blah st
[x_ship_to_city] => west chazy
[x_ship_to_state] => New York
[x_ship_to_zip] => 12992
[x_ship_to_country] => United States
[x_description] => Ariel Swirl BooJee Beads Lanyard (qty: 1)
[x_recurring_billing] => NO
[x_customer_ip] => 75.68.173.239
[x_po_num] => Jul-16-2008 03:26:13
[x_freight] => 6.95
[x_tax_exempt] => FALSE
[x_tax] => 0.00
[x_duty] => 0
[Date] => July 16, 2008, 3:26 am
[IP] => 75.68.173.239
[Session] => 4foscndfetvqicged08m2e0nh1
[url] => https://secure.authorize.net/gateway/transact.dll
)


Results Received back from Authorizenet: Array
(
[0] => Response from gateway
[1] => 1
[2] => 1
[3] => 1
[4] => (TESTMODE) This transaction has been approved.
[5] => 000000
[6] => P
[7] => 0
[8] => 1000196-ICHtE3
[9] => Ariel Swirl BooJee Beads Lanyard (qty: 1)
[10] => 18.95
[11] => CC
[12] => auth_capture
[13] => 257
[14] => Dawn
[15] => Ross
[16] =>
[17] => blah blah st
[18] => west chazy
[19] => New York
[20] => 12992
[21] => United States
[22] => 888-888-2258
[23] =>
[24] => [email protected]
[25] => Dawn
[26] => Ross
[27] =>
[28] => blah blah st
[29] => west chazy
[30] => New York
[31] => 12992
[32] => United States
[33] => 0.0000
[34] => 0.0000
[35] => 6.9500
[36] => FALSE
[37] => Jul-16-2008 03:26:13
[38] => A08B59825EA507824F997F3B32EC0ADA
[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] => July 16, 2008, 3:26 am
[70] => 75.68.173.239
[71] => 4foscndfetvqicged08m2e0nh1
[Expected-MD5-Hash] => 870352236DDF2E9DB7CBCE687ADD389A
[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] => 1165
[filetime] => -1
[ssl_verify_result] => 20
[redirect_count] => 0
[total_time] => 2.75
[namelookup_time] => 0
[connect_time] => 0.047
[pretransfer_time] => 2.578
[size_upload] => 0
[size_download] => 624
[speed_download] => 226
[speed_upload] => 0
[download_content_length] => 624
[upload_content_length] => 0
[starttransfer_time] => 2.75
[redirect_time] => 0
)

Using CURL Proxy: [] with Proxy Tunnel: On

RAW data received:
*1*|*1*|*1*|*(TESTMODE) This transaction has been
approved.*|*000000*|*P*|*0*|*1000196-ICHtE3*|*Ariel Swirl BooJee Beads
Lanyard (qty: 1)*|*18.95*|*CC*|*auth_capture*|*257*|*Dawn*|*Ross*|**|*blah
blah st*|*west chazy*|*New York*|*12992*|*United
States*|*888-888-2258*|**|*[email protected]*|*Dawn*|*Ross*|**|*blah blah
st*|*west chazy*|*New York*|*12992*|*United
States*|*0.0000*|*0.0000*|*6.9500*|*FALSE*|*Jul-16-2008
03:26:13*|*A08B59825EA507824F997F3B32EC0ADA*|**|**|**|**|**|**|**|**|**|**|**|** |**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|**|*July
16, 2008, 3:26 am*|*75.68.173.239*|*4foscndfetvqicged08m2e0nh1*




Do you see anything wrong? Thanks