topic Re: AIM / NVP & MD5 Removal in Integration and Testing

AIM / NVP & MD5 Removal

billynoah — Sat, 12 Jan 2019 01:05:01 GMT

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

Re: AIM / NVP & MD5 Removal

ciroalvarez1 — Tue, 29 Jan 2019 22:12:01 GMT

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.

Re: AIM / NVP & MD5 Removal

RichardH — Wed, 30 Jan 2019 01:12:24 GMT

@ciroalvarez1 @billynoah

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

Richard

Re: AIM / NVP & MD5 Removal

billynoah — Wed, 30 Jan 2019 02:20:12 GMT

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.