Previously, when using the DIRECT API to process CCs, the IP address of the transaction was saved. Now that we are using the HOSTED solution, this information is not. Why? The IFRAME should retain the customer's browsers IP, and auth.net should store it. Without this, we are unable to use much of the advanced fraud protection features.
Please see here: https://developer.authorize.net/api/reference/#accept-suite-get-an-accept-payment-page On this page, under "Request Field Description" for the "GetHostedPaymentPageRequest", there are no options to input the Customer IP. The only option for adding in a Customer IP seems to be under the "createTransactionRequest" (https://developer.authorize.net/api/reference/#payment-transactions-charge-a-credit-card), which is not used for the Hosted Payment Page, but for direct order processing through the Authorize.net server. How and why is there not an option to pass the Customer IP through the Hosted Payment Page Request or any of the Customer Profile requests, either?
โ06-18-2019 10:54 AM
I'm also investigating fraud prevention with the hosted payment page. Have you found a solution on this issue?
Thanks,
Troy
โ03-29-2021 12:27 PM