Authorize.net Technical Updates

I was just wondering if there will be another release coming to address changes that Auth.net is making to their systems. We received a notification from them yesterday (4/20/16) about some changes but I'm not sure if any of them affect the use of this module.

I don't want to assume that you received the same email from Auth.net so I'll include it here:

Over the next few months, we are making several updates to our systems that you need to be aware of. They are all technical in nature and may require the assistance of your web developer or shopping cart/payment solution provider.

Akamai SureRoute Reminder
Authorize.Net is now using Akamai to optimize our Internet traffic routing, which includes your transaction requests. Akamai helps safeguard against interruptions caused by issues beyond Authorize.Net's direct control, such as Internet congestion, fiber cable cuts and other similar issues. Using Akamai is currently optional, but will be mandatory starting June 30th.

Upgrade your website or payment solution today to take immediate advantage of Akamai's benefits. If your solution uses a firewall, please read the Akamai FAQs to determine what steps to take before June 30th to avoid disruptions to transaction processing.

RC4 Cipher Disablement
In an effort to ensure that all server-to-server communications with the Authorize.Net platform (both transactional and otherwise) maintain the highest levels of security, we will be disabling the RC4 cipher suite in the sandbox on April 29, 2016, and in the production environment on May 31, 2016.

If you have a solution that relies on RC4 to communicate with our servers, please update it to a current, high-security cipher as soon as possible. Please review our API best practices blog post for more information.

Transaction and Batch ID Reminder
In the coming weeks, due to system updates, it will be possible to receive Authorize.Net IDs (Transaction ID, Batch ID, etc.) that are not in sequential order.

For example, currently, if you receive a Transaction ID of "1000," you could expect that the next Transaction ID would not be less than 1000. However, after the updates, it will be possible to receive a Transaction ID less than the one previously received.

If your system has any functionality that expects Authorize.Net-generated IDs to be sequential, please update it immediately so that you will not see any disruptions.

Additionally, please make sure that your solution does not restrict any Authorize.Net ID field to 10 characters. If you are required to define a character limit when storing any of our IDs, the limit should be no less than 20 characters.

Sincerely,
Authorize.Net