Important Authorize.Net Networking Change

[Datagg]

Not sure if this effects us in anyway under the hood, but wanted to ask as this just landed in my box.

 At Authorize.Net, the reliability of our platform is our first priority. Your business depends on our services, and we understand how important that is. To that end, we are implementing a new networking solution that will provide you with a superior level of processing reliability.
Please read this email thoroughly.
Akamai Network TechnologyOver 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 TimelineWe are implementing Akamai's technology into our network in two phases.
[*=left]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.
[*=left]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 SolutionThe new Akamai transaction URLs that are available now are:
[*=left]https://api2.authorize.net/xml/v1/request.api
[*=left]https://api2.authorize.net/soap/v1/Service.asmx
[*=left]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. 

There's a bit more in the email which i left out for security purposes. Thanks guys!!

[ILoveHostasaurus]

Re: Important Authorize.Net Networking Change

You shouldn't need to change anything as they're going to point the current production URL through their new setup once they've completed testing.

[Datagg]

Re: Important Authorize.Net Networking Change

You shouldn't need to change anything as they're going to point the current production URL through their new setup once they've completed testing.

Thank you David.

[lesliekirk]

Re: Important Authorize.Net Networking Change

Does anything need to be done for this?

Firewall And IP Address Considerations

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.

[ILoveHostasaurus]

Re: Important Authorize.Net Networking Change

If your authnet module has a URL configured as the target, then you do not need to change anything.

[Eric S]

I received another email from Auth.net and they list 3 URL's and suggest that switching now is advisable. Are you saying the old URL will just forward
so don't bother changing it? The Auth.net notice I just received seems to indicate that a change is advisable. The last of the 3 URL's they list seems
to be almost identical to the one we use now except for the "2" after "secure" https://secure2.authorize.net/gateway/transact.dll
http://www.authorize.net/support/aka...s.html#newurls

[ILoveHostasaurus]

My understanding is the 'old' URL is simply going to become the same as the new URL with regard to pointing at Akamai instead of authnet directly, but they aren't going to implement that until June. I think the only reason they're using language to encourage its adoption now is to encourage people to switch in real time and test afterward so they will hopefully discover any unresolved issues with Akamai before they switch everyone to it. :-)

[afiumano]

An email was sent to our clients about this on June 20th. It says: JUNE 30TH MIGRATION TO AKAMAI IS NOW VOLUNTARY, BUT REMAINS HIGHLY RECOMMENDED.

So are we suppose to update the URL in the authorize.net module or leave as is and let authorize.net take care of it? I just want to make sure the payment gateway doesn't go down at all.

[Rick Wilson]

Just leave it as is AFAIK.