• Toll-free  888-665-8637
  • International  +1 717-220-0012
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

lcasey
#1 Posted : Thursday, August 7, 2014 9:10:39 AM(UTC)
lcasey

Rank: Member

Joined: 4/22/2004(UTC)
Posts: 280

Is there an authorize.net plugin that works with the advanced fraud detection suite?
Aaron
#2 Posted : Thursday, August 7, 2014 9:54:03 AM(UTC)
Aaron

Rank: Administration

Joined: 4/2/2004(UTC)
Posts: 2,393
United States
Location: Hummelstown, PA

Thanks: 6 times
Was thanked: 163 time(s) in 158 post(s)
Originally Posted by: lcasey Go to Quoted Post
Is there an authorize.net plugin that works with the advanced fraud detection suite?

BV Commerce 2013 has the necessary integration for AFDS.
Aaron Sherrick
BV Commerce
Toll-free 888-665-8637 - Int'l +1 717-220-0012
lcasey
#3 Posted : Thursday, August 7, 2014 10:02:08 AM(UTC)
lcasey

Rank: Member

Joined: 4/22/2004(UTC)
Posts: 280

Great news!
But my client's live site is not working correctly, so it must not have been updated correctly.
There are 2 authorize.net plugins in CreditCardGateways, Authorize.Net and BV AuthorizeDotNet, but only Authorize.Net is available in the admin.
Is BV AuthorizeDotNet the one that supports AFDS, and if so, what changes to we need to make to implement it?
Aaron
#4 Posted : Thursday, August 7, 2014 10:53:14 AM(UTC)
Aaron

Rank: Administration

Joined: 4/2/2004(UTC)
Posts: 2,393
United States
Location: Hummelstown, PA

Thanks: 6 times
Was thanked: 163 time(s) in 158 post(s)
Originally Posted by: lcasey Go to Quoted Post
But my client's live site is not working correctly, so it must not have been updated correctly.
There are 2 authorize.net plugins in CreditCardGateways, Authorize.Net and BV AuthorizeDotNet, but only Authorize.Net is available in the admin.

Correct. The "Authorize.Net" one is the current one. The other one was removed from BVC some time ago which is why it does not appear in the admin. We'll be sure to remove this remnant folder in the next release.

Originally Posted by: lcasey Go to Quoted Post
Is BV AuthorizeDotNet the one that supports AFDS, and if so, what changes to we need to make to implement it?

No. The "Authorize.Net" gateway is the correct one.

When you say that it doesn't work correctly, what do you mean?
Aaron Sherrick
BV Commerce
Toll-free 888-665-8637 - Int'l +1 717-220-0012
Aaron
#5 Posted : Thursday, August 7, 2014 11:01:24 AM(UTC)
Aaron

Rank: Administration

Joined: 4/2/2004(UTC)
Posts: 2,393
United States
Location: Hummelstown, PA

Thanks: 6 times
Was thanked: 163 time(s) in 158 post(s)
All of the setup happens on the Authorize.Net side of things; there's nothing to configure in BVC. AFDS declines are logged in the order private notes, like the other declines.
Aaron Sherrick
BV Commerce
Toll-free 888-665-8637 - Int'l +1 717-220-0012
lcasey
#6 Posted : Thursday, August 7, 2014 11:04:32 AM(UTC)
lcasey

Rank: Member

Joined: 4/22/2004(UTC)
Posts: 280

Authorizations that are held in authorize.net due to AFDS can be "captured" in BVC.
Capturing in BVC does not release them from the hold in authorize.net.
BVC reports successful capture in the private notes, but the transaction remains uncaptured & held in authorize.net.


Aaron
#7 Posted : Thursday, August 7, 2014 1:49:15 PM(UTC)
Aaron

Rank: Administration

Joined: 4/2/2004(UTC)
Posts: 2,393
United States
Location: Hummelstown, PA

Thanks: 6 times
Was thanked: 163 time(s) in 158 post(s)
Originally Posted by: lcasey Go to Quoted Post
Authorizations that are held in authorize.net due to AFDS can be "captured" in BVC.

Orders that AFDS holds have their payment status set to "Pending Payment". That's how you can pick them out in the admin compared to a regular order.

Originally Posted by: lcasey Go to Quoted Post
Capturing in BVC does not release them from the hold in authorize.net. BVC reports successful capture in the private notes, but the transaction remains uncaptured & held in authorize.net.

Can you check the private notes to see if there is an authorization code?



Aaron Sherrick
BV Commerce
Toll-free 888-665-8637 - Int'l +1 717-220-0012
lcasey
#8 Posted : Thursday, August 7, 2014 2:03:06 PM(UTC)
lcasey

Rank: Member

Joined: 4/22/2004(UTC)
Posts: 280

The "Authorize success" note includes a Transaction Reference Number and a Transaction Response Code.
lcasey
#9 Posted : Monday, August 11, 2014 12:07:27 PM(UTC)
lcasey

Rank: Member

Joined: 4/22/2004(UTC)
Posts: 280

These are marked as "Pending Payment". The plugin does not provide a way to approve AFDS held orders from the BVC admin. Correct?
Aaron
#10 Posted : Monday, August 11, 2014 4:43:04 PM(UTC)
Aaron

Rank: Administration

Joined: 4/2/2004(UTC)
Posts: 2,393
United States
Location: Hummelstown, PA

Thanks: 6 times
Was thanked: 163 time(s) in 158 post(s)
Originally Posted by: lcasey Go to Quoted Post
The plugin does not provide a way to approve AFDS held orders from the BVC admin. Correct?

Correct. However, I don't think this is even possible via their API. From talking with Authorize.Net support last week it sounds like making this work smoothly really comes down to how you configure AFDS. Put another way, if you don't want to use Authorize.Net's backend every time AFDS flags an order you probably need to adjust your AFDS filters. Here's some info that I found related to this:

A transaction held for review by the Advanced Fraud Detection Suite (AFDS) will be held for either 5 or 30 days depending upon the filter settings. If the AFDS filter is set to "Authorize and hold for review" the transaction will authorize as normal and you will have 30 days in which you can choose to approve it. If the AFDS filter is set to "Do not authorize and hold for review" it will be held for only 5 days. If the merchant does not approve or decline the transaction within that time, it will decline automatically.
Aaron Sherrick
BV Commerce
Toll-free 888-665-8637 - Int'l +1 717-220-0012
lcasey
#11 Posted : Monday, August 11, 2014 5:15:25 PM(UTC)
lcasey

Rank: Member

Joined: 4/22/2004(UTC)
Posts: 280

This is actually related to the AFDS Enhanced AVS filter only. For that filter, there's no "Do not authorize and hold for review". The 4 possibilities are Allow, Decline, Allow and Report Triggered Filter, Authorize and Hold for Review.

With "Authorize and Hold", the transaction can be authorized and held on the AVS result - in this case, it is reported as successful authorization in BVC and marked as Pending Payment (which is OK - though "On Hold" might be a better label unless it is automatically triggered for some other reason.) For Authorize and Hold, you have to enter Authorize.NET and Approve the transaction to release the hold. Only then, can funds can be captured.

So, with the AVS filter, the only way to avoid using Authorize.NET's backend is to "Allow", which bypasses AFDS/AVS altogether or "Allow and Report", which sends a Suspicious Transaction email but does not hold and there would be no flag in BVC.
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

©2024 Develisys. All rights reserved.
  • Toll-free  888-665-8637
  • International  +1 717-220-0012