# Fraud Manager

Fraud Manager is Konnektive's whitelabel of Kount fraud screening. If you are experiencing fraudulent traffic on your site, enabling fraud manager will screen your customers prior to their payment being attempted against the gateway - preventing any refunds or chargebacks against those fraudulent customers. Enabling Fraud Manager will allow you to immediately start screening your customers.\
\
The Fraud Manager plugin is found by navigating to Admin → Plugins → Fraud Services.

Click on the Fraud Mananger plugin, then click the green Activate button. After you choose your risk tolerance level and enable any other options that you want to enable, click Connect.
\
Clicking Connect will auto-enable the Fraud Manager on all of your campaigns. This can be toggled within the campaign’s General Details \ <br>

<figure><img src="https://1103784913-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiAC0G99SjXjSv2GM5PAE%2Fuploads%2FU0B6D3yDdk9eN8HhKOvA%2Fimage.png?alt=media&#x26;token=1223d1ae-5743-4cee-ad0c-36c711f82f97" alt="" width="458"><figcaption></figcaption></figure>

Fraud Manager has a cost of $0.10 per screening. The screening only occurs on the initial sale for the customer. You have the option to screen Recurring Purchases and Upsell Purchases with Fraud Manager, allowing full use of RDR services with Kount.

\
**There are 3 additional options:**
\
**useTestServer** - Enable this option while you are testing your funnels to prevent your test data from being captured by Kount's production enviornment
\
**screenRepeatCustomers** - This option will screen a customer returning to purchase again.
\
**screenUpsells** - This option will screen upsells

### Risk Values

Below are the differences between the rules for each risk value. If any of these rules are true for a transaction, then Fraud Manager will return a decline. If a value is not selected then Fraud Manager will default to the Medium setting.

#### Low:

* Network chargeback > 3
* Merchant chargeback > 0
* More than 3 orders in 14 days
* Omniscore of < 15

#### Medium:

* Network chargeback > 5
* Merchant chargeback > 0
* More than 5 orders in 14 days
* Omniscore of < 25

#### High:

* Network chargeback > 7
* Merchant chargeback > 0
* More than 7 orders in 14 days
* Omniscore of < 35

<h4 align="center">Criteria in all Risk Values:</h4>

| Criteria                                                  | Action  |
| --------------------------------------------------------- | ------- |
| Visionworx Decline Billing Address Error (Unknown Street) | Decline |
| Bin Country <> Billing Country (Visa/MC)                  | Decline |
| Bin Country <> Device Country (Visa/MC)                   | Review  |
| VIP Approve / Email Whitelist                             | Approve |
| VIP Decline                                               | Decline |
| Device Location = High Risk Country                       | Decline |

### Campaign Setup

You now have the option to screen transactions with the Fraud Manager!

* In the **Edit Campaign** screen under the **Other Options** section of the campaign’s **General Details** you will see a new “Screen with Fraud Manager” option.
  * This is where you can choose which custom ruleset should be used for Fraud Manager.
* Please remember to click the **Update** button when you are done configuring the Fraud Manager settings in your campaign.
* If you are using Direct API, you will need to add the Device Data Collection pixel on your lander. Please review this article on how configure [**Fraud Manager with API**](https://help.konnektive.com/konnektive-crm/admin-setup/plugins/fraud-services/device-data-collector-pixel-ddc-pixel). **If you are using Konnektive form code, re-download the form code package to ensure the Fraud Manager plug-in is automatically integrated**.

&#x20;

**Reporting**

Now with Fraud Manager enabled, your Dashboard will have a new Fraud Manager button. You can click this to bring you to the reporting for Fraud Manager.

<figure><img src="https://1103784913-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiAC0G99SjXjSv2GM5PAE%2Fuploads%2FcgW0Kl05VbJBqyx6WX24%2Fimage.png?alt=media&#x26;token=3350880a-155e-4950-81d1-04835be08b02" alt=""><figcaption></figcaption></figure>

The reporting will show how many transactions were screened within your chosen date range and will break down the declines by rulesets and their rules.\
\ <br>

In addition, the Transaction Details report will now have a Fraud Manager Status filter to view all Approved, Pending, and Declined Transactions.

* If the transaction is declined, you can click the View Rules button under the transaction’s response to see which rules were triggered causing the decline

<figure><img src="https://1103784913-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiAC0G99SjXjSv2GM5PAE%2Fuploads%2FznulGbpUpKbGEVQxqNwu%2Fimage.png?alt=media&#x26;token=a29dcbba-9749-4905-9d4b-78b89617c82d" alt=""><figcaption></figcaption></figure>

\
You also have the ability to pull transactions screened by Fraud Manager on our [Transaction Query API](https://apidocs.konnektive.com/?version=latest#e9a7caf1-825c-485a-b7c4-b3cae30384f3) by using the parameter: fraudPlugin=FRAUDMANAGER

{% hint style="warning" %}
If using Direct API - BE SURE to place the [Device Data Collection Pixel](https://help.konnektive.com/konnektive-crm/admin-setup/plugins/fraud-services/device-data-collector-pixel-ddc-pixel) onto your landing pages so Fraud Manager can send more data to Kount for screening.
{% endhint %}

{% hint style="warning" %}
If using Konnektive form-code -

Be sure to redownload the SDK and deploy the new config file. This will enable the Device Data Collection Pixel
{% endhint %}

***

### Additional Notes

**Enable option for “Fire Pixels on QA Approval” to fire affilaite pixels for orders that went into Qualtity Assurance and were later approved.**

<figure><img src="https://1103784913-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiAC0G99SjXjSv2GM5PAE%2Fuploads%2FCJzsl2wo0OWo9kmJ8uus%2Fimage.png?alt=media&#x26;token=b2f3b9e2-f20d-4c24-8602-7a0ebca820f3" alt=""><figcaption></figcaption></figure>