I have the Fraud Detection Suite (FDS) enabled with Authorize.net and with this option when transaction are "Authorized and hold for review" or are processed but trigger a suspicious transaction alert, the customer is not issued a receipt and an order status is not given to the customer. I want to set these orders as Pending, but still issue the customer a receipt. How can I fix this?
Also is there a way to resend a receipt if a customer did not get it?
Has anyone figured this one out? My client is also using Fraud Detection Suite (FDS) and while it holds the transactions for approval, it doesn't seem to send the orders back to OC or OC doesn't know that orders are supposed to come back? After approving the transaction with Authorize.net the orders "disappear" - are there some settings on either side dealing with batch transfers or something we are missing?
the fraud detection suite has lots more response codes to factor in
would be cool though if the authorize.net module on the cart side could customize cart behavior on a per-customer basis using the fraud detection system responses
what i mean is that say you set the Amount Filter in FDS to $2,500.00 and set it to hold this amount for review
however, what if you have a few customers who normally place orders larger than $2,500.00 but have a long history doing this, thus these customers are more trusted
when auth.net sends back the suspicious code for those particular customers, the order would just come through normally, but for other customers, they would receive an email or order status of 'pending review' or something
in other words, there could be switches for each customer that could tailor how the fds settings would be handled on the cart side for specific customers to help keep legit orders flowing that otherwise fall into the default dfs settings
would be cool though if the authorize.net module on the cart side could customize cart behavior on a per-customer basis using the fraud detection system responses
what i mean is that say you set the Amount Filter in FDS to $2,500.00 and set it to hold this amount for review
however, what if you have a few customers who normally place orders larger than $2,500.00 but have a long history doing this, thus these customers are more trusted
when auth.net sends back the suspicious code for those particular customers, the order would just come through normally, but for other customers, they would receive an email or order status of 'pending review' or something
in other words, there could be switches for each customer that could tailor how the fds settings would be handled on the cart side for specific customers to help keep legit orders flowing that otherwise fall into the default dfs settings
This could drive people away from using opencart. I assumed FDS was taken into consideration until I got a large order that failed because I was using the fraud detection suite and the customer had a apartment # on their shipping address and not on their billing. I had FDS set to 'Authorized and hold for review' for mismatched shipping & billing address. I would definitely love a fix for this!
does opencart recognize all of the FDS response codes?yachzo wrote:I had FDS set to 'Authorized and hold for review' for mismatched shipping & billing address. I would definitely love a fix for this!
would love to have the option to not-authorize-but-hold-for-review cuz an auth.net rep told me that you can later enable that transaction if you want to (goes through normal authorization then)
thanks
Nope. I had to turn off my FDS settings so that orders with slight address mismatches would go through although I know that will end up biting me in the end.
I tried changing this on line 136:
to:
thinking that would allow "authorized but held for review" orders go through, but unfortunately I don't know what the hell I am doing
A table of AFDS Response Reason Codes is listed below:
250 - AFDS blocked IP address
251 - AFDS filter triggered; transaction declined per filter settings
252 - AFDS filter triggered; transaction held for merchant review
253 - AFDS filter triggered; transaction was authorized but is held for merchant review
254 - Transaction declined after manual review of AFDS filters
anyone?
I tried changing this on line 136:
Code: Select all
if ($response_info[1] == '1' ) {
Code: Select all
if ($response_info[1] == '1' || $response_info[253] == '1') {
A table of AFDS Response Reason Codes is listed below:
250 - AFDS blocked IP address
251 - AFDS filter triggered; transaction declined per filter settings
252 - AFDS filter triggered; transaction held for merchant review
253 - AFDS filter triggered; transaction was authorized but is held for merchant review
254 - Transaction declined after manual review of AFDS filters
anyone?
Due to increase fraud activity on my website I decided to enable Authorize.net FDS only to realize that when an FDS transaction filter is triggered the customer never reaches the "success" page, no email confirmation is sent out, and in the admin area, the order is held "missing orders" status.
The whole idea with FDS filters is that the merchant has a chance to review the transaction behind the scene and decide to either process or cancel. If the customer is not moved to the success page, and if no email confirmation is sent (with the standard pending status), the customer is bound to assume that her transaction was never accepted and go shop elsewhere.
The filter actions AU.net allow us to choose a response from this list:
Can this be achieved by modifying the AU module within opencart? I believe yachzo suggested something to that effect but did not get an answer.
Two years later, this is still a problem both on 1.5.6 and 2.0.3.1 -- please help
The whole idea with FDS filters is that the merchant has a chance to review the transaction behind the scene and decide to either process or cancel. If the customer is not moved to the success page, and if no email confirmation is sent (with the standard pending status), the customer is bound to assume that her transaction was never accepted and go shop elsewhere.
The filter actions AU.net allow us to choose a response from this list:
- Process as normal and report filter(s) triggered.
Authorize and hold for review.
Do not authorize, but hold for review.
Decline the transaction.
Can this be achieved by modifying the AU module within opencart? I believe yachzo suggested something to that effect but did not get an answer.
Two years later, this is still a problem both on 1.5.6 and 2.0.3.1 -- please help
Who is online
Users browsing this forum: No registered users and 69 guests