Sort of related to a previous post of mine HERE, I was curious if any Miva users utilize Auth.NET for their payment gateway while on the Cloudflare CDN.
Auth.NET is in the stone age - still only using IPv4 for their fraud detection which we use to prevent out-of-country ordering.
The default Auth.NET velocity filter would ding every minute if using Cloudflare as normal since traffic thru CF's servers come in as an the IPv4 of that specific location. We can get around CF's server IP and use the true IP of the end-user, but with [insert current] percentage of modern traffic using IPv6, those would be at risk of validation erros on Auth.NET's side.
Has anyone found a good balance to keep Auth.NET functioning well (preventing fraud, velocity, no false-positives, etc) while also having Cloudflare enabled?
Auth.NET is in the stone age - still only using IPv4 for their fraud detection which we use to prevent out-of-country ordering.
The default Auth.NET velocity filter would ding every minute if using Cloudflare as normal since traffic thru CF's servers come in as an the IPv4 of that specific location. We can get around CF's server IP and use the true IP of the end-user, but with [insert current] percentage of modern traffic using IPv6, those would be at risk of validation erros on Auth.NET's side.
Has anyone found a good balance to keep Auth.NET functioning well (preventing fraud, velocity, no false-positives, etc) while also having Cloudflare enabled?
Comment