01-16-2013 06:26 AM
For test accounts, the documentation says that the default value of MD5 Hash Value (set on the Account page and used to validate the MD5 Hash sent from Authorize.Net after a transaction) is the empty string; however it is actually the AuthorizeNet Account LoginID.
Solved! Go to Solution.
01-16-2013 09:54 AM
I thought I tried that and got the failure....actually one doc says leave it blank and another doc says leave it as it.... I will try again....and report... thanks
01-16-2013 10:04 AM
Just tried both the api login id and my login id; same result. You'd thought they'd had a definitive guide on how to resolve the issue. Given that I have been trying for the last 3 days, there is no way I would recommend this lousy support model...when I chatted with the people they were as clueless and referred me to the developers' forum, I thought I would find the solution to the problem in no time...sorely mistaken....
01-16-2013 11:28 AM
Yeah, I have changed it to a numbers of things like a single character, a few characters like 1234 to no avail. I believe as with the relay_reponse.jsp issue there needs to be a document that captures all the scenarios that could cause this problem....elementary watson ;-(
01-16-2013 03:32 PM - edited 01-16-2013 03:33 PM
If you don't think the problem is the MD5, you could change it to just display what is in the request.getParameterMap() so you can see what is being return.
01-18-2013 11:19 AM
The documentation that I found said that test accounts share the same MD5 Hash value and thus it could not be changed on test accounts. I didn't even try setting it to something. Thanks for the heads up.