Authorize.net AIM
Posted: Tue Nov 04, 2008 8:59 am
Is AbleCommerce 7.0 using AIM for it's Authorize.net payment method? If so I have a question about AC7 and the Auth.net Fraud Detection Suite.
One filter in the Auth.net Fraud Detection Suite is Authorized AIM IP Addresses – If you submit transactions exclusively via Advanced Integration Method (AIM), you may maintain a list of server IP addresses that are authorized to submit transactions. Any transactions received by your payment gateway account from an IP address NOT on the list are rejected.
This sounds great, and I would definately like to use this, however there is a note in the documenation that says, if you are using Advanced Integration Method (AIM), you will need to pass the Customer IP Address (x_customer_ip) in order to use the IP Address Blocking tool. For more information, talk your Web developer or the person who performed your integration.
In my own AIM integration this is no problem, but does AC7.0 do this behind the scenes? Is AC7.0 using AIM and if so is it passing the Customer IP Address (x_customer_ip)?
One filter in the Auth.net Fraud Detection Suite is Authorized AIM IP Addresses – If you submit transactions exclusively via Advanced Integration Method (AIM), you may maintain a list of server IP addresses that are authorized to submit transactions. Any transactions received by your payment gateway account from an IP address NOT on the list are rejected.
This sounds great, and I would definately like to use this, however there is a note in the documenation that says, if you are using Advanced Integration Method (AIM), you will need to pass the Customer IP Address (x_customer_ip) in order to use the IP Address Blocking tool. For more information, talk your Web developer or the person who performed your integration.
In my own AIM integration this is no problem, but does AC7.0 do this behind the scenes? Is AC7.0 using AIM and if so is it passing the Customer IP Address (x_customer_ip)?