Thread: Authorize.net FDS Configuration

Hi, we are using Authorize.net and we did enabld fraud detection suite. We configured the storefront based on the URL

http://manual.aspdotnetstorefront.co...t-gateway.aspx

In the authorize.net FDS we have configured as Authorize and Hold for review. So when an order is placed through shopping cart, the authorize.net decided to hold for review.

We logged into authorize.net and approved the transaction. The transaction didn't appear in our storefront. Also, the order was not created.

Seems to be a configuration issue. Is there any configuration involved in storefront or authorize.net?

Im just guessing here, but ... my guess is when auth.net marks it as questionable and marks it as hold for review it doesnt return a valid auth number .. it must return an error to the customer and therefore does not actually place an order. You logging in and approving it will do nothing to the storefront, there is nothing in place to take that request.

Bottom line, FDS probably wont work with ASPDNSF out of the box.

Ok. Just to note. I see this transaction in failed transactions. The response from Auth.net is "Your order has been received. Thank you for your business"

But this is not a denial. This is additional Fraud detection based on certain rules and the payment is on hold.

I have tried paypal before and used their FDS. Certain transactions can be on hold and when you approve that transaction from Paypal, they order will be created in our system.

Just wondering how auth.net works with this storefront.

If you see it in failed transactions, then as far as ASPDNSF is concerned it is a denial. I dont think FDS will work with authorize.net and ASPDNSF

Auth.net's fraud detection needs to be turned off to have our integration work properly. As has been stated in this thread, the software just isn't written to handle that. If you want additional fraud prevention services, I would recommend MaxMind, which we do integrate with (and use ourselves).