Woocommerce Auth.net AIM - New SHA512 Requirements

[rfree190]

I'm stuck...

We are using BlueHost with a VPS.  When Auth.net advised they were moving away from MD5 and upgrading to SHA512, I contacted BlueHost support to find out what I need to do.

I was told our VPS was using MD5 as the password hash.  And, they wouldn't help me move from MD5 to SHA512 as we aren't on a "Managed Server".

Being that I'm using the Latest WooCommerce on Wordpress, and using the lastest WooCommerce developed Auth.net AIM Payment Gateway, what do I need to do to be compliant with the new standards set by Auth.net?

Thanks!

Rick

[Renaissance]

@bikecod

If you are using AIM plugin and the orders are going through then you have no real concern. As long as the correct updates are happening on your end. To use sha512 you need to generate a signature key. This is a separate credential from your login and Transkey that you likely haven’t used until now. If and when you have the most up to date version of the plugin, you want to paste that signature key into the plugin.

With AIM you do not need sha512 or md5 to submit transactions. The main function for you is to aid in validating transaction responses. Usually what happens is based on the transaction response updates are made on your records. If your records are getting updated even when sha512 fails then it’s of no consequence. The above, however, will get rid of that message.