Ruby example for calculate_TransHashSha512() is not functional #69

Activity

1. robertwahler commented on Mar 1, 2019

   

   robertwahler

   on Mar 1, 2019

   Author

   More actions

   I've located the proper fields to hash in the deprecated SIM documentation and updated the SDK. I will not issue a pull request as this is not complete SIM API support. https://github.com/robertwahler/sdk-ruby/tree/SIM_lifeline
2. gnongsie commented on Mar 6, 2019

   

   gnongsie

   on Mar 6, 2019

   Contributor

   More actions

   Hi,
   Thanks for bringing this to our notice. There were some minor issues with the sample which I have fixed.

   However, the SIM module has been deprecated in the latest version of the SDK. Server side support for the transHash value returned in SIM will also be discontinued and will return a null value moving forward. Please refer to the following links for MD5 based hash getting discontinued.

   • MD5 Hash End of Life & Signature Key Replacement
   • Authorize.Net Support : MD5 Hash End of Life & Signature Key Replacement
   • Transaction Hash Upgrade Guide

   The new field being sent for verification is transHashSHA2, for which the sample code you referred to is valid and functional.
3. gnongsie

   added

   awaiting-replyAwaiting a response from the developerAwaiting a response from the developer

   on Mar 6, 2019
4. robertwahler commented on Mar 6, 2019

   

   robertwahler

   on Mar 6, 2019

   Last edited by robertwahler

   Author

   More actions

   Hi, thanks for the response. There is no transHashSHA2 returned from test.authorize.net/gateway/transact.dll. but there is a SHA2_Hash that is populated with a hash of 30 different return parameter fields (see the referenced fork above). I understand SIM is deprecated but it is not obsolete yet so I hope that your gateway will continue to return SHA2_Hash. Could you verify?
5. gnongsie commented on Mar 13, 2019

   

   gnongsie

   on Mar 13, 2019

   Contributor

   More actions

   Hi Robert,
   Yes, x_SHA2_Hash is the SIM equivalent for transHashSHA2.

   Kindly refer to this document for any further doubts.

   Also, may I suggest that you consider migrating to our new APIs for your integration? Please refer to this document for suggestions on how to upgrade.