topic Re: Authorize.Net Relay Response Silent Post Whitelist IP Addresses in Integration and Testing

Authorize.Net Relay Response Silent Post Whitelist IP Addresses

RichardH — Thu, 07 Jul 2016 14:56:27 GMT

[Edit, 7/7/16: Updating this post with the current range of IP addresses.]

Recently Authorize.Net migrated to a new data center to further enhance the performance and security of our platform. As part of the new platform changes, Relay Response and Silent Post data will now originate at these IP addresses:

198.241.168.60
198.241.162.104

198.241.206.38

198.241.207.38

If you have a firewall that blocks inbound Internet traffic and use Relay Response or Silent Post, please add these IP addresses to your whitelist.

Re: Authorize.Net Whitelist IP Addresses

jruser — Tue, 28 Oct 2014 19:19:59 GMT

Are these for test, production, or both?

Re: Authorize.Net Whitelist IP Addresses

Lilith — Tue, 28 Oct 2014 21:16:15 GMT

I confirmed they are for both Production and Sandbox environments.

Re: Authorize.Net Relay Response Silent Post Whitelist IP Addresses

reahrum0r — Wed, 17 Feb 2016 20:11:33 GMT

Are the IP addresses current?

198.241.168.60
198.241.162.104

Re: Authorize.Net Relay Response Silent Post Whitelist IP Addresses

RichardH — Wed, 17 Feb 2016 21:17:31 GMT

Yes @reahrum0r, they are still accurate. If there are changes in the future, we'll update the original post so it's always accurate.

Richard

Re: Authorize.Net Relay Response Silent Post Whitelist IP Addresses

reahrum0r — Wed, 17 Feb 2016 20:51:47 GMT

Thanks

Re: Authorize.Net Relay Response Silent Post Whitelist IP Addresses

iamreb — Thu, 07 Jul 2016 06:00:53 GMT

@RichardH This is the IP address that was captured by our server during a silent post request: 198.241.206.38, after whitelisting this IP the silent post worked, but only whitelisting the two you've stated above did not help.

thank you

Re: Authorize.Net Relay Response Silent Post Whitelist IP Addresses

Lilith — Thu, 07 Jul 2016 14:47:55 GMT

This is a legacy post, but I'll refresh it shortly with more current IP addresses.

As Authorize.Net expands out its data centers, IP addresses are subject to change, but we'll strive to keep information about IP addresses up to date.

@iamreb -- there's actually four IP addresses you should whitelist: The two listed previously; the one you found, and one other. Check the post for the full IP address range. Thanks.

Re: Authorize.Net Relay Response Silent Post Whitelist IP Addresses

epibod01 — Thu, 19 Jan 2017 14:59:15 GMT

Been awhile, can you confirm this list is still up to date? We've started losing some transactions again since about the end of December and want to be sure its not this issue.

Re: Authorize.Net Relay Response Silent Post Whitelist IP Addresses

Lilith — Fri, 20 Jan 2017 16:02:48 GMT

We haven't changed these IP addresses since we posted them. We expect this list to remain stable for the foreseeable future. When we retire our legacy data centers, we'll drop two of the IP addresses, but that isn't going to happen for some time. The only additions were to support new data centers which we brought online, and we are using Network Address Translation, so even new servers should not change this list.

Again, this list should not change for some time, and when it does, it will be to retire IP addresses, not add new ones.

Re: Authorize.Net Relay Response Silent Post Whitelist IP Addresses

gothicsoftware — Tue, 31 Jan 2017 17:43:14 GMT

We are getting this error too.

Sorry, it seems that there are no available payment methods for your state. Please contact us if you require assistance or wish to make alternate arrangements

We think this may be the result of the configuration of out firewall. How to we test to see if this is the case. We allow any incoming http port 80 and not port 80 or port 443 outbound.

We added a rule to allow outbound port 80 on the ips listed above but still get the error.

Any suggestions?

~Paul

Re: Authorize.Net Relay Response Silent Post Whitelist IP Addresses

gothicsoftware — Tue, 31 Jan 2017 17:45:17 GMT

We are getting this error too.

Sorry, it seems that there are no available payment methods for your state. Please contact us if you require assistance or wish to make alternate arrangements

We think this may be the result of the configuration of out firewall. How to we test to see if this is the case. We allow any incoming http port 80 and not port 80 or port 443 outbound.

We added a rule to allow outbound port 80 on the ips listed above but still get the error.

Any suggestions?

~Paul