Moderator
Posts: 22
Registered: ‎09-25-2017
Authorize.Net API Integration IP Address Changes (Updated)
[ Edited ]

 

We are upgrading the way we manage our network infrastructure to be more responsive to events and business need. In order to support these changes, we are changing the IP addresses used by our API endpoints. Nothing else will change. The URLs and domains for all Authorize.Net websites and services will remain the same. 

 

Authorize.Net will make the below changes to the IP addresses used by our API endpoints:

 

  • New IP addresses are available now for testing and use.
  • On 01/16/2019 (completed) a test was completed switching over to our new ip addresses and domain name resolution to them and then later reversed.
  • On 02/13/201903/11/2019 (completed) a change was completed to update to our new ip addresses and domain name resolution. Merchants will need to use our new IP addresses for any firewall white listing. Legacy IP addresses are still in place but should not be used or connected to directly as only domain names should be used. At this time the legacy IP addresses may be removed at any time.

The impact will vary depending on how your website/solution is set up. Below are examples:

 

  1. If you do not whitelist our IP address on your firewall or proxy, you do not need to do anything.
  2. If you use a firewall/proxy that supports domain name whitelisting, you do not need to do anything.
  3. If you use a firewall/proxy that only support IP addresses whitelisting, you will need to work with your developer or web host to add the new IP addresses to your whitelist. Once we have switched permanently to the new IP addresses, you may remove the old IP addresses.

For more details, see our support article, Authorize.Net Domains and IP Addresses.

Who Me Too'd this topic