Hi Kenyatta

We support several different Authorize.net products (AIM, SIM, CIM and Accept.js)

Can you please confirm which product you're using?

Thank you

We don't modify, translate or change the IP address we pass to AIM. The IP address is what is being captured by the server and pass to Authorize.net via the "x_customer_ip" field.

Can you please confirm or find out from Authorize.net which IP address is being flagged? 

Thank you

Good morning,

Here are some of the IP addresses from this week. 172.31.37.169, 172.31.43.222, 172.31.7.161.

Thanks,

Kenyatta

Ok. I believe the 172 is a private IP network, possibly from Cloudflare. This can mean the pages are being served by some proxy. Please note the Storefront merely reads the IP address of the incoming request and pass along to Authorize.net. It won't know that it's coming from a proxy or a real client.

Normal requests looks like this:

SERVER <=> END USER

Using a proxy in between:

SERVER <=> PROXY <=> END USER

Can you check with your hosting provider if they are somehow using a proxy to serve out the pages because that is the IP address read by the Web server from the incoming request? You can share those IP address with them and see if they recognize it. I think they may be using CDN (Content Delivery Network) like Cloudflare that reads your pages, caches them and serves the cached version to the end user. If that is the case, you can ask them to try disable the cache on the document, but only cache the static resources like images, etc.

Thank you