Blog

Updated Monday, February 25th

Authorize.Net recently announced plans to phase out MD5 based hashes used for transaction response verification. Phase 1 of that plan is now complete, and as such merchants are no longer able to configure or update their MD5 Hash settings in the Merchant Interface. Phase 2 will be complete March 14th, and at that time Authorize.Net will stop populating the MD5 Hash Value altogether. This will have severe impacts on merchants who use Authorize.Net Direct Post method in Magento, as they will no longer be able to process payments.

ParadoxLabs Authorize.Net CIM extensions for Magento 1 and Magento 2 are reliable alternatives to Direct Post and are not impacted by the recently announced MD5 Hash changes.

---

What is Authorize.Net Direct Post?

Authorize.Net Direct Post is a payment processing method that is built in to Magento 1 and Magento 2 and requires no payment extension to set up.

Why isn’t Authorize.Net Direct Post working?

To use the Direct Post Method in Magento, you need to have a Merchant MD5 Hash that is supplied by Authorize.Net. As of February 1st, 2019, new accounts were no longer able to obtain a Merchant MD5 Hash. As of March 14th, 2019, MD5 Hash values will cease to be supplied at all. In short, any Magento stores that want to use Authorize.Net and their top-notch fraud protection systems will no longer be able to do so with Direct Post Method, and will need an extension to process payments.

Are there Alternatives to Authorize.Net Direct Post?

Yes. ParadoxLabs Authorize.Net CIM extensions for Magento 1 and Magento 2 are excellent alternatives to Authorize.Net Direct Post. Our extensions, which processed over $2.6B in 2018, use TLS encryption and Authorize.Net’s proprietary Accept.js API to securely process payments without credit card numbers touching your web server. Additionally, these extensions bring Authorize.Net’s Customer Information Manager (CIM) service to Magento, allowing returning customers the convenience of stored credit cards and rapid checkout without breaking PCI compliance.

While ParadoxLabs Authorize.Net CIM extensions for Magento 1 and Magento 2 record the MD5 hash values Authorize.Net is changing, they do not otherwise use them. As a result, the changes implemented by Authorize.Net on March 14th, 2019 will not impact the operability of our extensions in any way.

Existing users of Paradoxlabs extensions on both Magento 1 and Magento 2 are not required to take any action.

ParadoxLabs Authorize.Net CIM extensions are proven solutions, and are used on thousands of Magento stores. We know what we’re doing, and we’ve been doing it a long time. Payment is a fundamental part of your business, and it’s a fundamental part of ours too. We help you make sure situations like this never become a problem for you.

ParadoxLabs Authorize.Net CIM Extension Purchase Options

Our extensions have been vetted and approved by Magento for the Magento Marketplace.

AUTHORIZE.NET CIM FOR MAGENTO 1

AUTHORIZE.NET CIM FOR MAGENTO 2

If you would like to install our extensions via composer, you will have to purchase through Magento Marketplace. After purchase please refer to the Marketplace-specific installation instructions in the extension user manual.

AUTHORIZE.NET CIM FOR MAGENTO 2 – COMPOSER INSTALLATION