MD5 Hash Removal/Disablement from Authorize.Net
-
Today Morning I got an Email from the Authorize.Net regarding MD5 Hash Removal/Disablement. Here what exactly they stated.
Authorize.Net is phasing out the MD5 based transHash element in favor of the
SHA-256 based transHashSHA2. The setting in the Merchant Interface which
controls the MD5 Hash option will be removed by the end of January 2019, and
the transHash element will stop returning values at a later date to be
determined.Merchants utilizing this feature will need to work with their web developer
or solutions provider to verify if they are still utilizing MD5 based hash
and if still needed to move to SHA-256 hash via Signature Key.I checked plugin using Md5 hashing field in it’s setting. My question is, whether plugin is updated to support new feature from Authorize.Net or providing any other alternate solution.
Please look at this problem asap. Advice me any alternate solutions.
The page I need help with: [log in to see the link]
-
Hello,
Try following stepsTo generate your Signature Key:
1) Log into the Merchant Interface at https://account.authorize.net.
2) Click Account from the main toolbar.
3) Click Settings in the main left-side menu.
4) Click API Credentials & Keys.
Select New Signature Key.
To disable the old Signature Key, click the check box labeled Disable Old Signature Key Immediately.
If the Disable Old Signature Key check box is not selected, the old Signature Key will automatically expire in 24 hours. This will also impact any use of the Signature Key for transaction response validation for the SHA2 field. If the old Signature Key is not expired the previous key will continue to be used for the hash/response validation.
5) Click Submit to continue.
6) Request and enter PIN for verification.
7)Your new Signature Key is displayed.And put this key in your “Signature Key”
- The topic ‘MD5 Hash Removal/Disablement from Authorize.Net’ is closed to new replies.
