Posted: May 30, 2016 at 12:44 pm
Authorize.net has recently issued the below notice regarding changes concerning a number of items with relation to Authorize.net integrations.
Can you please confirm your recommendation if our version (4.4.8p) of EE is compatible with these changes. How is EE affected by the Akamai SureRoute, the RC4 Cipher Disablement, and the changes to the Transaction and Batch ID Reminder. What steps do we need to take knowing the above?
Please let me know if you need additional information or clarification
Dear Authorize.Net Merchant:
Please read this email carefully, and if you need to find a web developer to help you, please check out our Certified Developer Directory at http://www.authorize.net/cdd.
Using Akamai is currently optional, but will be mandatory starting June 30th when we direct our existing transaction URLs on our end to connect through Akamai SureRoute. Upgrade your website or payment solution today, however, 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.
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.
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.
Hello, earlier this year we released an updated version of Event Espresso 4 that has an option to test your site with the Akamai server URLs.
You can see changes since your version here:
Thank you for getting back to us Lorenzo,
Can you confirm if we were to upgrade to the latest Event Espresso 4 version, all of the above points that Authorize.net are covered?
Yes, you’ll have an option to switch in the current release.
I also want to mention that while we were proactive in making that option available, Authorize.net has sent an update (received yesterday) that it is now optional but recommended to switch to Akamai
Here is a screenshot of the of the email:
The support post ‘Authorize.net Changes and how they affect Event Espresso 4’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.