Jump to content
Latest News: (loading..)

bill138

Members
  • Content count

    1
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Authorize sent this via email today. Apparently there is a bit more time to address this than might originally have been thought. Authorize.Net is phasing out the MD5 hash, an older method used by shopping carts, payment modules and plugins to verify that transaction responses are genuine and from Authorize.Net. We have identified that you have this feature configured and may be relying on this older method. Please contact your web developer or solutions provider and confirm if you are using an MD5-based hash. If so, you should begin plans for moving to SHA-512 hash via Signature Key. The MD5 Hash will phase out in two phases: Phase 1 - Starting later this month to early February 2019, we will remove ability to configure or update MD5 Hash setting in the Merchant Interface. There are no changes to the existing API response. Phase 2 - Stop sending the MD5 Hash data element in the API response. This change will require that applications support the SHA-512 hash via signature key. Dates for phase 2 will be announced later but is expected in the next 2-3 months. 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 and for being an Authorize.Net merchant. Sincerely, Authorize.Net
×