topic Re: Validate SIM Response on Test Accounts in Integration and Testing

Validate SIM Response on Test Accounts

gnpatterson — Wed, 16 Jan 2013 14:26:16 GMT

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.

Re: Validate SIM Response on Test Accounts

teledirek1 — Wed, 16 Jan 2013 17:54:36 GMT

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

Re: Validate SIM Response on Test Accounts

teledirek1 — Wed, 16 Jan 2013 18:04:30 GMT

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....

Re: Validate SIM Response on Test Accounts

RaynorC1emen7 — Wed, 16 Jan 2013 18:53:44 GMT

Or you could just login to the account and change it to whatever you want.

Re: Validate SIM Response on Test Accounts

teledirek1 — Wed, 16 Jan 2013 19:28:46 GMT

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 ;-(

Re: Validate SIM Response on Test Accounts

RaynorC1emen7 — Wed, 16 Jan 2013 23:33:11 GMT

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.

Re: Validate SIM Response on Test Accounts

gnpatterson — Fri, 18 Jan 2013 19:19:02 GMT

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.