• Resolved mincioni

    (@mincioni)


    All of our transactions at Authorize.Net are showing our server IP as the Customer IP. Is there a way to pass the true customer’s IP to Authorize.Net instead? Then we could better utilize the Fraud Detection Suite IP filters.

    • This topic was modified 6 years, 9 months ago by mincioni.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author cardpaysolutions

    (@cardpaysolutions)

    Hello. We just pushed an update (v 2.0.8) that passes the customer IP address to Authorize.net.

    Thread Starter mincioni

    (@mincioni)

    Thank you. Version 2.0.8 works fine for IPv4, however it is truncating IPv6 in the AuthNet transactions.

    For example, customer IP in the WC order is:
    2607:fb90:7dae:c586:b01f:8ea4:980a:8903
    Customer IP in the corresponding AuthNet transaction is truncated:
    2607:fb90:7dae:

    Can this be corrected? Thanks in advance.

    Plugin Author cardpaysolutions

    (@cardpaysolutions)

    I think that issue is on Authorize.Net’s end. We are sending the full IPv6 and I think they are truncating it.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Customer IP -> Authorize.Net’ is closed to new replies.