- This topic has 3 replies, 2 voices, and was last updated 8 years, 8 months ago by
.
-
Posts
-
We received an email from Authorize.net stating that the above will be implemented over the next few months. It seems like there is nothing on our end to prepare for this – will there be an update to WPeS for this – or is your product not affected by these changes?
Dear Authorize.Net Merchant:
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
As we get further into 2016, we want to remind you of our previously announced Akamai SureRoute implementation plan and timelines(https://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Important-Authorize-Net-Networking-Change/ba-p/51272). Using Akamai’s technology will help safeguard against interruptions caused by issues beyond our direct control, such as Internet congestion, fiber cable cuts and other similar issues.
If you have not already, please review the announcement and the Akamai FAQs ( http://www.authorize.net/support/akamaifaqs/ ) to make sure you avoid any disruptions to your transaction processing.
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.
RC4 Cipher Disablement
In an effort to ensure that all of your 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 during the first half of 2016. A follow-up notification will be sent out once specific dates for the disablement are ready for the sandbox and production environments.
For now, 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 ( https://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Request-for-Comments-API-Best-Practices/ba-p/53668 ) for more information.
Sincerely,
Authorize.Net
- You must be logged in to reply to this topic.