MD5 Hash Removal/Disablement June 27, 2019 (Updated 3X)

AdamT — Mon, 08 Apr 2019 18:29:27 GMT

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 (completed) to stop populating the MD5 Hash value, the field will still be present but empty.
- Production will be updated on ~~March 14, 2019~~ ~~March 28, 2019~~ ~~June 28, 2019~~ June 27, 2019 (Updated 3X) 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.

For more details, see MD5 Hash End of Life & Signature Key Replacement article. Sample codes have been added to Github and SKDs will be updated by end of February.

topic MD5 Hash Removal/Disablement June 27, 2019 (Updated 3X) in News and Announcements