Magento Maintenance Services; getting caught by the safety net

Yesterday Authorize.net deployed an unannounced change to their API. This change caused the native Authorize.net integration within Magento 1 to throw exception errors during order creation. Transactions were processed, without returning a success message. Customer service agents became inundated with questions and concerns that trickled back to us.

When our clients spoke with Authorize.net, their representatives provided them with either of these responses; “The issue was within Magento” or “Magento should have been aware of this upcoming change and adjusted accordingly”. We usually receive a notification concerning changes in plenty of time to react before the rollout date. Just recently they announced the deprecation of the MD5 Hash, which we have already addressed for our clients, so this API change came as a big surprise.

Luckily for our clients, we have a fantastic Magento Maintenance & Support Plan that allows us to jump into the issue and provide a solution.

After confirming the API change was the root cause (a change made regarding the support of the delimiter character from any string to only a single character) we reviewed the native integration and quickly created an extension to override Magento’s core and provide support for this change. We have publicly released the fix in hopes that it would help others in this time of chaos. https://github.com/vonnda/Vonnda_AuthorizePatch/

We have received word that Authorize.net has rolled back the change to their API, but we have not seen an official announcement, only comments from their support team. You can find the original mention of the change on Authorize.net’s community news here.

If you’d like to learn more about how Vonnda can help take the worry out of maintaining your Magento store give us a ring (415) 282-9400 or leave us a message on our contact form.

Like the sound of success?

Let's talk.