Authorize.net turning off MD5 hash

[jmelson]

Authorize.net advises that they are turning off support for the MD5 hash, and will be moving to the SHA-256 at some time in the near future.
Does anybody know what is involved in supporting that? I'm guessing that it is at least a few lines in the Authorize.net payment module.

Thanks for any suggestions.

Jon

[jmelson]

Just to add more info, this is an osCmax 2.5.4 system, the module is Authorize.net Credit Card SIM
They don't say when they will actually turn off the ability to take payment through this hash function, but
when they do, I will lose my credit card processor.

Thanks much in advance for any help on this.

Jon

[Pr0ject]

Just to add more info, this is an osCmax 2.5.4 system, the module is Authorize.net Credit Card SIM
They don't say when they will actually turn off the ability to take payment through this hash function, but
when they do, I will lose my credit card processor.

Thanks much in advance for any help on this.

Jon

me 2; is there a new module? or update?

[ridexbuilder]

Have you seen updates for it at osCommerce? That should provide a template for any required changes.

[JRR]

Until a fix is found you may want to consider using the PayPal module as it allows credit card processing.

[ridexbuilder]

I have at least one client that uses Authorize.net but haven't found time to investigate.

[jmelson]

Until a fix is found you may want to consider using the PayPal module as it allows credit card processing.

I ALSO offer PayPal, but some countries and some people are not able to use PayPal, for a variety of reasons.

So, I want to have an alternative for them.

Thanks,

Jon

[JRR]

Authorize.net does have an update for developers here:

Upgrade Guide

And some discussion on this on osCommerce:

AIM Module - MD5 Hash Is Going Away. Is there an update? - Authorize.net - osCommerce Support Forum

Hope that helps,

John ;-#)#

[jmelson]

UGH, even worse! They are deprecating SIM, and will eventually discontinue that feature. Yes, they want us all to move to AIM (or other), so that they no longer have to deal with the card security issues, it will be OUR problem! That is why I WENT to SIM, was to get out of the card security issues when your own server processes the card data. Before I got SIM working, I was using AIM, and had to go through incredible handstands to pretend that I was compliant. I'll spare you the details unless you want them, but it was awful, made me feel like a MAJOR criminal, and always waiting for the big hack!

If I am to continue using Authorize.net, I need some kind of interface to their APIs that works.

Thanks,

Jon

Jon

[jmelson]

Anybody want to go in together to hire a freelancer or similar to make us up a module for this?

Jon