You may have recently received several E-mails from Authorize.NET notifying you of upcoming integration changes that may impact your ability to accept and process payments. If you are using Instant SOLO Server Shared or Dedicated URL, no action is needed. If you are providing your own hosting for SOLO Server, action may be needed. Read on to determine what, if any action is needed to address these changes.
Over the coming months, Authorize.Net will be upgrading access to the Internet connections that serve their data centers. Instead of allowing direct connections, all Internet traffic will be routed through Akamai, a third-party cloud network service that routes and delivers Internet traffic. As part of this change, Authorize.Net strongly recommends updating your web site to use a new transaction URL hosted by Akamai.
Do I need to take any action?
Regardless of the version of SOLO Server you are running, action is optional. The existing transaction URL will continue to function. If you would like to start using the new URL:
On September 21, 2015, Authorize.NET is upgrading api.authorize.net to new security certificates, which are signed using Security Hash Algorithm 2 (SHA-2) and 2048-bit signatures.
Do I need to take any action?
No action is needed. SOLO Server does not use api.authorize.net.
In October of this year, due to system updates, it will be possible to receive Authorize.Net IDs (Transaction ID, Batch ID, etc.) that are not in sequential order. Additionally, Authorize.Net notes that any payment solutions should not restrict any Authorize.NET ID field to 10 characters.
Do I need to take any action?
No action is needed. SOLO Server does not rely on Authorize.NET Transaction IDs being in sequential order, and allots up to 25 characters for the Transaction ID, 5 more than the recommended limit of 20.
New PCI DSS requirements state that all payment systems must disable TLS 1.0 by June 30, 2016. To ensure that compliance ahead of that date, Authorize.NET will be disabling TLS 1.0 first in the sandbox environment and then in our production environments.
Do I need to take any action?
Please contact us with any questions.
Mike Wozniak is one of the co-founders of SoftwareKey.com and responsible for marketing, content and product strategy. When he isn't plotting new ways to help customers solve licensing and business automation challenges, he likes to travel and entertain guests who come to visit the Orlando area. He also writes most of the licensing tips here.
Maximizing email deliverability with SOLO Server Automation
SOLO Server 1.19.1.5 Released with New Support for Consumption-Based Licensing and More!
SOLO Server 1.19.1.3 – Improved Add License and Monthly Statements
SOLO Server 1.19.1.1 Released with New Integration User Accounts
What is Cloud-Controlled Network Floating Licensing?
Introducing API Transaction Fee Policy