Authorize.net has emailed users about a pending architecture change that will impact the URLs used for its API.

Akamai Network Technology

Over the coming months, Authorize.Net will be upgrading access to the Internet connections that serve our 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.
Using Akamai network technology will help decrease latency and improve the reliability of our payment gateway. It will also help safeguard against interruptions caused by issues beyond Authorize.Net‘s direct control, such as Internet congestion, fiber cable cuts and other similar issues. Additionally, come October, merchants connected to Akamai should no longer be affected by planned downtimes.

Implementation Plan And Timeline

We are implementing Akamai’s technology into our network in two phases.

• Phase One (Now through June 2016) — We have created three new URLs for transaction processing that are hosted by Akamai. You can update your website or payment solution to point to the new transaction URLs today, which will provide you with the immediate benefits detailed above. Come October, you should no longer be affected by planned downtimes.
• Phase Two (June 2016) — We will automatically direct all of our existing transaction processing URLs to connect through Akamai in June of 2016. After this change, all transaction URLs will connect to Authorize.Net through Akamai.

IMPORTANT: To take advantage of the uptime benefits Akamai offers, we recommend you proactively update your website or payment solution during Phase One rather than waiting to be automatically updated during Phase Two.

Updating Your Solution

The new Akamai transaction URLs that are available now are:

• https://api2.authorize.net/xml/v1/request.api
• https://api2.authorize.net/soap/v1/Service.asmx
• https://secure2.authorize.net/gateway/transact.dll

Please contact your web developer or solution provider for assistance in updating to one of these new Akamai URLs.

Firewall And IP Address Considerations

If you do not use a firewall or do not connect directly via an IP address, then you can disregard this section. If you are unsure, please contact your web developer or solution provider. Click here if you need help finding a developer.
Using Akamai technology, Authorize.Net‘s IP addresses will become dynamic rather than static. If your website or payment solution uses a firewall that has whitelisted Authorize.Net‘s IP address or connects to Authorize.Net directly via an IP address, you will need to make additional changes.

• Firewall Considerations — If your solution uses a firewall to filter outbound connections, make sure that the firewall is set to permit outbound traffic to flow to the Akamai cloud by configuring your outbound firewall to “ANY.” If you do not update your firewall ahead of June 2016, you will be unable to process transactions after Phase Two is implemented.
• IP Address Considerations — If your solution connects to Authorize.Net directly via an IP address, you will need to update it to connect by domain name. Continuing to connect directly via an IP address is strongly discouraged as you will not receive the benefits of routing through Akamai, and you could suffer a loss of service if transactions are re-routed among our various data centers.

Akamai is available for testing now in our sandbox environment. We strongly encourage you to test your solution prior to making any production change to ensure that you will not experience any disruptions to your transaction processing.

Questions?

If you have any questions about the Akamai upgrade, please refer to our Akamai FAQs or submit an eTicket by logging into the Merchant Interface and clicking Contact Us from the upper right corner of any page.
Thank you for your attention to this important email. We appreciate your ongoing partnership and are excited to bring you the benefits and reliability that this enhanced service provides.
Sincerely, Authorize.Net

As indicated if you use an API then you need to check the API and change the URLs accordingly,