topic Re: How to programmatically test for Suspicious Transaction Filter in Integration and Testing

How to programmatically test for Suspicious Transaction Filter

davestevens — Thu, 26 Mar 2015 16:09:33 GMT

Is there a way to programmatically test for the Suspicious Transaction Filter in the fraud detection suite? I'm looking for a test credit card number I can use of a setting or something. Right now, the only way I know of to test that it works is to fire off a transaction (e.g. CreateCustomerProfileTransaction > profileTransAuthCapture) and then use the transaction id to fire off GetTransactionDetails and then check for the presence of the following. Is that correct? However, the test credit card numbers we are using never trigger this filter. Any way I can test this?

<FDSFilterAction>report</FDSFilterAction>
<FDSFilters>

<name>Suspicious Transaction Filter</name>

<action>report</action>

</FDSFilter>

</FDSFilters>

Re: How to programmatically test for Suspicious Transaction Filter

RaynorC1emen7 — Thu, 26 Mar 2015 16:38:08 GMT

Which filter? It is in one of these tiggers?

http://developer.authorize.net/tools/errorgenerationguide/

Re: How to programmatically test for Suspicious Transaction Filter

davestevens — Thu, 26 Mar 2015 16:50:56 GMT

Thanks for the link. But I think this only applies to the "Enhanced AVS Handling Filter" and the "Enhanced CCV Handling Filter" filters. I'm trying to test out the "Suspicious Transaction Filter".

Re: How to programmatically test for Suspicious Transaction Filter

Joy — Mon, 30 Mar 2015 16:36:46 GMT

Hi davestevens,

Not all filters will work on sandbox accounts, the ones that will not work are the following:

Shipping Address Verification Filter
IP-Shipping Address Mismatch Filter
Regional IP Address Filter
Suspicious Transaction Filter

Basically, they are the filters that rely on external services like the IP Address geolocation service and USPS address verification service used for the first 3 filters.

Thanks,

Joy

Re: How to programmatically test for Suspicious Transaction Filter

davestevens — Mon, 30 Mar 2015 20:23:11 GMT

Also, just wanted to post a how a programmer can detect if the suspicious transaction filter fires. Each CreateCustomerProfileTransaction call returns a transId, which can then be used to call GetTransactionDetails. Whenever the suspicious transaction filter the GetTransactionDetails will show an FDS section that looks like the following.

<soap:Body>

…

…

<FDSFilterAction>report</FDSFilterAction>

<name>Suspicious Transaction Filter</name>

<action>report</action>

</FDSFilter>

</FDSFilters>

Note, I have yet to verify this in a production environment. However, Joy did confirm that this is what the response will look like.