Authorize.Net is one of the leading payment gateways available on the market. Over few next months Authorize.Net is going through important changes that shouldn’t be neglected.
Short summary of the upcoming changes:
1. Akamai SureRoute Implementation
Authorize.Net uses Akamai to optimize Internet traffic routing, which includes 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 for all merchants on June 30th.
2. Transaction and Batch ID Changes
In the coming months, it will be possible to receive Authorize.Net IDs (Transaction ID, Batch ID, etc.) that are not in sequential order. Also, it is necessary to make sure that your solution does not restrict any Authorize.Net ID field to 10 digits.
3. RC4 Cipher Disablement
Within an effort to upgrade to a higher level security Authorize.NET will be disabling the RC4 cipher suite during the first half of 2016.
4. TLS Remediation for PCI DSS Compliance
New PCI DSS requirements state that all payment systems must disable TLS 1.0 by 2018. It is recommended to upgrade TLS version to 1.2.
As an Authorize.net certified developer DevCom is starting a campaign aimed at upgrading your website or payment solution to adopt upcoming Authorize.NET changes. Contact us by June 15 and receive a 15% discount for the Akamai SureRoute implementation.
Contact us now to get your guaranteed discount.