Thread: Authorize.net Fraud Holds

How does ASPDotNetStoreFront handle orders that get held by Authorize.net?

We are working on setting up some filters via Authorize.net to authorize the order but hold it for review if there is suspected fraud. Do these orders get saved in the storefront somewhere that when we approve it in authorize.net they get processed?

Thanks!

Prior to forwarding the order transactions to your gateway, the software already kept a record of it in the DB. A transaction can have either of these Statuses: AUTH, CAPTURED, DECLINED. This will be determined after your merchant gateway verifies the CC of the customer together with the Appconfig: TransactionMode setting in AspDotNetStorefront. I believe, the TransactionMode= AUTH is what you're looking at, this setting will only instruct the software to verify funds with the merchant gateway, but not actually collect the funds yet (so, merchants can have time to verify, etc). Then, store admins will have to manually click the 'Capture' button for each order under Orders → View/Manage Orders to CAPTURE the funds.

Thanks Alfred, 2 Questions Here:

We have specific settings on Authorize.net to filter out fraud orders. For example: Customer visits our checkout and tries to pay with a credit card that could possibly be fraud. On the customer end on our website (aspdnsf), it will appear that their order went through. However, on authorize.net's end, it will hold the order and charge until we validate the order on authorize.net. If we update the order successfully in authorize.net, will an order then go through automatically in ASPDNSF?

This setting that you are referring to TransactionMode set at AUTH. Will this only affect orders that are being held in Authorize.net (gateway) or will it set ALL credit card transactions from the website (aspdnsf) on AUTH and we will have to check ALL orders and manually CAPTURE them?

Thanks.

If you set TransactionMode to 'AUTH' only, then all orders are held and have to be manually captured (it's just a button click). There's nothing built in to handle orders that Auth.net authorizes but puts a hold on, as far as the cart can tell the order went through normally. You'll have to either mark the order as captured or voided depending on how you handle it on the Auth.net end.

we have an issue that is recurring and causing serious customer service issues. Our ASP store front is putting orders in a Pending status, but instantly putting them in a failed transaction status. We use Shipworks to process shipping and have that linked for tendering the orders out of our POS 2010 system. We seldom go to the storefront to check on orders and we find pending then declined orders in the declined status, but we have the orders still pending in Authorize.net.