2

Read
https://support.magento.com/hc/en-us/articles/360024368392
Issue :

Magento implements the Authorize.Net Direct Post payment method, using Authorize.Net's AIM (Advanced Integration Method) and DPM (Direct Post method) APIs, which use MD5 based hash.

Authorize.net will stop supporting MD5 based hash usage on March 14, 2019. Starting from this date, Magento Open Source, Magento Commerce and Magento Cloud merchants will not be able to process payments using Authorize.Net Direct Post payment method. To be able to continue successfully process payments using these methods, merchants need to apply the patch provided by Magento and replace the existing MD5 hash with a Signature Key in the Magento Admin configuration settings.

3

Now Apply Patch directly in vendor folder
This patch is applicable on all Magento 2.x and 1.x versions.

Alternatively you can use patched files from following address and replace them in your vendor folder.

https://github.com/MeetanshiInc/Magento-Authorize-Net-Direct-Post-Patch-for-M1-M2

If Need Run php bin/magento setup:upgrade; php bin/magento setup:static-content:deploy -f;

After apply patch you will see Signature Key enter image description here

  • You don't need to run upgrade script and re-deploy static content. – joni jones Mar 7 at 21:43
  • I needed to flush cache after that changes were reflected. – wakar Ahamad Apr 5 at 14:54
0

I found this from github which explains the detail; https://gist.github.com/robolmos/7a3bf336516b18f8e0bd48a13d93e1ef

Basically, you have to change from the original patch file here;

Index: vendor/magento/module-authorizenet/Model/Directpost.php

+++ vendor/magento/module-authorizenet/Model/Directpost.php    (revision a0dade4d8bc15b651d8b1ea0e7e4e3580fb1d3ae)
--- vendor/magento/module-authorizenet/Model/Directpost.php    (revision 01fbfeba9bd743266199e30260376a9c1b95fbf5)

and they become this;

Index: Model/Directpost.php
+++ Model/Directpost.php   (revision a0dade4d8bc15b651d8b1ea0e7e4e3580fb1d3ae)
--- Model/Directpost.php   (revision 01fbfeba9bd743266199e30260376a9c1b95fbf5)

after the text replacement.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.