- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
no data in x_SHA2_Hash when using Silent Post
I've created a Signature Key but there is no data in x_SHA2_Hash when using Silent Post.
What is required to get the x_SHA2_Hash field to be populated?
โ02-01-2019 10:48 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Were you able to figure this out? I'm experiencing the same issue, and support was unable to help with this.
โ02-25-2019 07:34 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm having a very similar issue (different API) here:
So far, no useful response.
โ02-26-2019 04:06 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I too am trying to test using sandbox silent post and am finding that field empty. To add to the fun the md5 process we've used for decades doesn't match the sandbox's returned X_MD5_HASH value either.
โ02-26-2019 06:17 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @MinneSnowtain @desiminr61 @gh
What type of transaction are you submitting that is not returning an SHA2 hash in the response?
Richard
โ02-26-2019 08:49 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm requesting a silent post from authorize.net sandbox back to our testing site. (signed into sandbox account>Account>Under 'Transaction Format Settings'>Silent Post URL>entered a url to our site
โ02-26-2019 09:15 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @MinneSnowtain
Thanks for the reply. Which API specifically are you calling to create a transaction? We would like to duplicate if possible so as much detail as possible is appreciated.
Richard
โ02-26-2019 09:19 AM - edited โ02-26-2019 09:20 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
no api, just post data to https://secure.authorize.net/gateway/transact.dll and after processing payment it is suppose to silent post back to us so we can record the payment results. (and that post url has been changed to https://test.authorize.net/gateway/transact.dll for sandbox testing)
โ02-26-2019 09:25 AM - edited โ02-26-2019 09:29 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It appears you're using our older AIM method. Could you provide a sample transaction request with any sensitive information removed? Please also include your sandbox API Login but not your transaction key.
Richard
โ02-26-2019 09:28 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Absolutely but why? Can't you guys just populate that returned field with the correct hashed string instead of leaving it empty? or fix the X_MD5_HASH returned value.
โ02-26-2019 09:58 AM

