Authorize.net

Hey guys,
Where can i find changelog for payment add-on? We use payment add-on v1.1.9 and authorize.net. Last time I tried to update this add-on, payments quit working. So I reverted back.

Now I got this from authorize.net. So I’m wondering if we’re prepared.
Could you provide some insight?

thanks,
larry

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Dear Authorize.Net Partner:
Over the next couple of months, we are making several updates to our systems that you need to be aware of. Please read this email carefully.
Akamai SureRoute Reminder
Authorize.Net is now using Akamai SureRoute to optimize our Internet traffic routing, which includes your merchants’ 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.

Your merchants should upgrade their websites or payment solutions today to take immediate advantage of Akamai’s benefits. If their solution uses a firewall, please refer them to the Akamai FAQs to determine what steps to take before June 30th to avoid disruptions to transaction processing.
RC4 Cipher Disablement
We previously announced that we would be be disabling the RC4 cipher suite in the sandbox on April 29, 2016, and in the production environment on May 31, 2016. Unfortunately, those dates have been delayed. The new dates are May 10th for the sandbox and June 13th for production. We apologize for any confusion.

If your merchants have a solution that relies on RC4 to communicate with our servers, please have them 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 digits. If you are required to define a limit when storing any of our IDs, the limit should be an unsigned integer (up to 20 digits).

Sincerely,
Authorize.Net