I received a notice Jan 9 2019 that Authorize.Net will be removing it's MD5 Hash element at the END OF JANUARY.
Unfortunately, our installation does not work without populating this field, so our store WILL break at the end of Jan.
Does anyone know if newer versions of Magento "fix" this?.. meaning, is the MD5 Hash field required in Authorize.Net installations in newer versions of Magento? Is there a better place to bring this to the attention of the Magento Programmers?
Hopefully this will get some attention very soon.
Just an FYI, on further looking, it appears that only the field at the AuthNet portal (to create a hash) will disappear at the end of Jan.
Thus, it appears that, if you have an MD5 already set up, AuthNet will continue to serve it for an "undetermined" time after that.
So, stores may not stop processing payments at the end of Jan.
The "undetermined time" has been solidified.
Today we’re announcing final phase 2 dates when the gateway will stop populating the MD5 hash value.
· Phase 1 Complete
· Phase 2 - Stop sending the MD5 Hash data element in the API response. To continue verifying via hash, this will require applications to support the SHA-512 hash via signature key.
· Sandbox will be updated on March 7, 2019 to stop populating the MD5 Hash value, the field will still be present but empty.
· Production will be updated on March 14, 2019 to stop populating the MD5 Hash value, the field will still be present but empty.
We have updated documentation on our developer center, posted sample code on Github, and will have SDK updates completed by end of February.
Please refer to our support article: MD5 Hash End of Life & Signature Key Replacement for more details and information on this change.
Thank you for your attention to this matter.
I'm going to point everyone in these multiple alike threads to one thread, here:
The only reason being that guy has the best subject description.