topic transHashSha2 is not in the API transaction response in Integration and Testing

transHashSha2 is not in the API transaction response

blackwood821 — Thu, 31 Jan 2019 02:48:26 GMT

Hi,

I received the notification about transHash being replaced by transHashSha2. I updated to the latest SDK (1.9.9) but I still don't get a value in the transHashSha2 field. I am calling

CreateTransactionRequest

against the sandbox and the transaction response contains a value for transHash but the transHashSha2 field value is an empty string. I have double checked and I already have generated a signature key in the sandbox. What am I missing?

Re: transHashSha2 is not in the API transaction response

JenHaga — Thu, 31 Jan 2019 18:12:54 GMT

Has anyone using the API figured out how to get the amount from the response? The upgrade guide text is posted below. Can someone tell me how to grab the information in the third bullet point? I can successfully pull the transId element from the createTransactionResponse using response.transactionResponse.transId , but when I use response.transactionResponse.amount I get the error, "Public member 'amount' on type 'createTransactionResponse' not found". What is the syntax for extracting the amount from the createTransactionResponse ?

Step 3. Create a message string that starts with a caret ("^"), followed by the following three fields delimited by carets, and terminated with another caret:
• The API Login ID that you send in createTransactionRequest in the name element.
• The transaction ID that we send in createTransactionResponse in the transId element.
• The transaction amount that we send in createTransactionResponse in the amount element.

Re: transHashSha2 is not in the API transaction response

Renaissance — Thu, 31 Jan 2019 18:20:43 GMT

You will not get an amount in the response object. You want to use the amount of the transaction hard coded in, rather than pulling it from the response.

Re: transHashSha2 is not in the API transaction response

JenHaga — Thu, 31 Jan 2019 18:24:14 GMT

So their upgrade guide is incorrect? It cleary says to use "The transaction amount that we send in createTransactionResponse in the amount element."

https://developer.authorize.net/support/hash_upgrade/

So just use the amount I'm sending to them?

Re: transHashSha2 is not in the API transaction response

Renaissance — Thu, 31 Jan 2019 18:41:21 GMT

Yep it’s wrong. So if your app has a variable called amount that you pass in the transaction, you just plop that variable into your string. I’ve had mine tested and working for 2 or 3 weeks.

Re: transHashSha2 is not in the API transaction response

Renaissance — Thu, 31 Jan 2019 18:43:51 GMT

@blackwood821,

Are you by chance using the sandbox in test mode? Not sure what else would cause that.

Re: transHashSha2 is not in the API transaction response

blackwood821 — Sat, 09 Feb 2019 20:41:23 GMT

@Renaissance no, my sandbox is in live mode.

Re: transHashSha2 is not in the API transaction response

blackwood821 — Sat, 09 Feb 2019 20:42:08 GMT

@JenHaga your question should've probably been a separate post as it's not related to my issue.

Re: transHashSha2 is not in the API transaction response

Renaissance — Sun, 10 Feb 2019 21:47:34 GMT

@blackwood821,

What language and integration method are you using?

Re: transHashSha2 is not in the API transaction response

blackwood821 — Sun, 10 Feb 2019 22:04:00 GMT

@Renaissance I am calling

createTransactionResponse

in Java using the anet-java-sdk version 1.9.9.

Re: transHashSha2 is not in the API transaction response

Renaissance — Mon, 11 Feb 2019 01:06:51 GMT

Ok in your above post I believe you said you were calling createTransactionRequest. Did I miss something?

Re: transHashSha2 is not in the API transaction response

blackwood821 — Mon, 11 Feb 2019 05:24:45 GMT

Oops, I meant createTransactionRequest. I was looking at the API docs to verify that it was documented to be included in the response and accidentally copied the response name.

Re: transHashSha2 is not in the API transaction response

Renaissance — Mon, 11 Feb 2019 15:13:47 GMT

Yeah that is strange. I am not sure what it would be. You created your signature key from the same place you created your transaction key, correct? You answered the question with Simon? I am sure you did because you would be getting back a null value rather than an empty string. You would have a transaction key, login, signature key, and (if you use accept.js) a public client key. So 4 api credentials total. A consolation prize if you can’t figure this out is that the modern integration methods don’t get as much benefit from this as the old ones. You can do without it, I think.