cancel
Showing results for 
Search instead for 
Did you mean: 

transHash elimination questions

Regardng the impending elimination of the transHash (MD5) field from transaction responses in favor of transHashSHA2, we have several questions that don't appear to be answered anywhere in the existing communications:

 

1) We are using an AuthorizeNet .NET API DLL that we compiled from the GitHub source code back inAugust 2018.  This source code includes both the transHash and transHashSHA2 fields in its data structures, but it is not clear how or where these are actually being used in the rest of the source code.  Can you tell us whether or not there will be any problem with this version of the SDK source code once transHash is eliminated from transaction responses?  (We understand that at best it will be empty or null ... the question is whether the SDK will crash as a result of looking for a response field that will no longer be present.)

 

2) If the August 2018 SDK will indeed crash on the absence of transHash (as asked above), then has the current version of the SDK source code on GitHub already resolved any such issue, or is that yet to be resolved?

 

3) Are you intending to remove transHash from the transaction responses in the sandbox environmets prior to making this change in production, so that we would be able to test our code to determine if we are prepared for that production change before it happens?  (We certainly hope you are planning to do so, and with enough of a time window to allow us to build, test and distribute a new version of our software to our customer companies prior to the production change if need be.)

dsandberg
Contributor
0 REPLIES 0