Prefer authorize.net certified developer
Need assistance with authorize.net updated security below
1. Akamai SureRoute Reminder
They referenced a fire wall, I do not believe we have one.
2.Transaction and Batch ID Reminder
a. 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.
b.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
3.RC4 Cipher Disablement
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.
4. Early 2017 TLS Remediation for PCI DSS Compliance
1. PCI DSS requirements state that all payment systems must disable TLS 1.0, 1.1,
2.Recommend using TLS 1.2 for API integrations.