Authorize.net has completed some important upgrades on the way online stores transfer payment information to their data centers. On a practical level, this means that their subdomain has changed from “secure” to “secure2.” At this point the change is optional but is highly recommended by Authorize.net as it will provide merchants with a superior level of processing reliability.
What will change?
Over the last months, Authorize.Net have been working on changes to increase security to merchants. Now, 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 the 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.
What do I have to do?
The migration to Akamai is voluntary, but remains highly recommended. Authorize.Net will not automatically direct their existing URLs to Akamai as they had previously communicated.
The new Akamai SureRoute 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
If your site 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 don’t know whether your solution uses a firewall or would like assistance to perform these changes, hire us today.