RE: AIM Filter Integration Problems (Error Code 250)

[JUsch2015]

I am running a few test transaction in my new gateway. Without the AIM IP Address Filter, I get successful transaction :-) When I enable that filter and added my server IP for whitelist, it gives:

<errorCode>250</errorCode><errorText>This transaction has been declined.</errorText>

Currently, I am using SOAP UI to test Authorize.Net APIs. I have also used native calls (java directly) to submit transaction to check whether SOAP UI is causing the IP problem. 

The URL I'm using that's triggering the error is:

https://api.authorize.net/xml/v1/request.api

Auth.Net cutomer support supplied the folowing URL which resulted in a successful transaction: 

https://secure.authorize.net/gateway/transact.dll?

Since they are both technically AIM, I thought they should behave the same with the AFDS AIM IP filter.

I used a Advanced REST Client Plugin from Chrome Browser and it is also giving the same error "250". Both the tools (a) SOAP UI and (b) Advanced Rest Client in Chrome is giving this error. Typically these tools are used to avoid any user error. 

Any advice would be greatly appreciated. Thanks in advance

[RaynorC1emen7]

So you did pass the customerIP? One problem I see it that it doesn' support IPv6

http://developer.authorize.net/api/reference/

customerIP

IP address of customer initiating the transaction. If this value is not passed, it will default to 255.255.255.255. Required only when the merchant is using customer IP based AFDS filters.

Up to 15 characters (no letters). For example, 255.255.255.255

[MuthuUVA]

Anyone using XML payload to send transactions to Authorize.Net?

Also, anyone using AIM Filter in their environment where XML payload is used with AIM method to integrate?

Appreciate your input.

Thank you.