AIM / NVP & MD5 Removal

[billynoah]

How will the upcoming MD5 Hash Removal/Disablement affect integrations using the legacy AIM / NVP (with .dll endpoint) API?

[ciroalvarez1]

No replies yet from authorize.net? I have the same question. I don't think that the MD5 hash removal will affect the legacy NVP integrations (.dll) but I want to be 100% sure too.

[RichardH]

@ciroalvarez1 @billynoah

You can read more at https://support.authorize.net/s/article/MD5-Hash-End-of-Life-Signature-Key-Replacement

This change applies to applications using the MD5 hash to verify transaction responses.  It does not affect how transactions are submitted.

Richard

[billynoah]

Thanks Richard.  The article you linked seems to indicate that the MD5 hash in the AIM method will be replaced with an SHA2 hash.  It also mentions upcoming revisions to that documentation.  I'll check back once this has been ironed out.  We appreciate the information.