Reply
Highlighted
Member
Posts: 4
Registered: ‎07-11-2013

Silent Post being removed any time soon?

I recently had a client call me stating that they had contacted Authorize.net support and were told that Silent Post was no longer supported (in favor of Accept.js and Webhooks).

 

However, I cannot find any documentation online or in the forums about Silent Post being deprecated or removed.

 

Does anyone know if Silent Post is in-fact being deprected and if so, by when?

Trusted Contributor
Posts: 335
Registered: ‎11-05-2018

Re: Silent Post being removed any time soon?

I'm thinking they're done for. I started on my first integration in 2017. Silent post was already marked for upcoming deprecation at that time. The webhooks documentation states that webhooks replace the silent post method. Doesn't say "will replace at XZY date" or "we recommend upgrading to this" like the other docs about deprecated services.  The fact you search and can't find anything whatsoever about silent post anywhere on the website suggests strongly that they are no longer supported, period.

 

I'm not an employee of this company, but if I were to give you advice I would say start using webhooks ASAP and drop silent post, no matter the current status. If it's not deprecated completely, I would say that it's on the chopping block and the axe is in midswing at this point.

 

 

Posts: 327
Kudos: 55
Solutions: 35
Registered: ‎03-13-2017

Re: Silent Post being removed any time soon?

Hi @cartpauj

 

Yes silent post is deprecated  and for any new integration you should be using Webhooks integration . 

 

For more details on Webhooks please visit 

 

https://developer.authorize.net/api/reference/features/webhooks.html

 

https://github.com/AuthorizeNet/webhooks-sample-app

 

Thanks

Anurag





Send feedback at developer_feedback@authorize.net
Member
Posts: 1
Registered: ‎01-14-2019

Re: Silent Post being removed any time soon?

Hi @Anurag,

 

I am a developer on this project. Our plan is to migrate to webhooks in the very near future, but we have a hard deadline of the end of Jan to move from supporting the MD5 hash to the SHA2 hash for silent post data. We have thousands of clients currently using our plugin and need to allow for a transition. 

 

Here is where I have run into issues. I have followed the guide here: https://developer.authorize.net/support/hash_upgrade/. I have generated a signature key and am using that to hash the data string "^{API Login ID}^{transId}^{amount}^". However I cannot get the x_SHA2_Hash to match from the silent post. Is that the correct data and format for the silent post hash? Or does it hash the entire body like the webooks?

 

We will be moving to webhooks this month, but need to support silent posts until all clients have moved over. So we will also need to verify the silent posts via the SHA2_Hash until they have updated.