|
We are using Magento CE 1.7.0.2 integrated with Authorize.net via Direct Post method using Magento’s native integration for this service. We are using Authorize.net’s Transactional IP Velocity Filter that is a part of their Advanced Fraud Detection Suite (AFDS). With this Transactional IP Velocity Filter, Magento transmits the customer’s IP address to Authorize.net and Authorize.net blocks too many transactions from the same IP address at a velocity that we set.
The issue is that Magento will often capture both the customer’s private as well as public IP, but transmit to Authorize.net just the private IP. Because so many private IPs are similar (presumably they are created by a customer’s home router), we have cases of different customers being blocked by this filter just because someone else using the same private IP at home but a different public IP made a purchase before them.
How do we get Magento to transmit just the customer’s public IP to Authorize.net and not the private IP? See sample excerpted from an Order Information screen below.
Placed from IP
10.248.94.199 (76.176.188.123)
Here, 10.248.94.199 is a common private IP and 76.176.188.123 is the public IP. However, Authorize.net seems to receive and record only
10.248.94.199 and not 76.176.188.123. Any ideas as to a fix?
|
