Device ID at Fraugster

The device your customers use to make a transaction is an excellent tool you can use in your risk management strategy. It is a source of additional data that helps validate the identity of the person making the purchase.

As a Fraud Management SaaS user, you can create rules to manage the risk coming from a specific device ID. Velocity attributes featuring a device ID are particularly useful if you want to detect and prevent fraud coming from the same device in quick succession.

Fraugster offers you several options to manage the device ID fraud:

1. You can send your own device ID to the Fraugster API in device_id and use this data during the rule creation. If you're using an external service provider for device fingerprinting, you can also send device_id_smart and device_id_exact and use them as desired.
2. You can opt in to use Fraugster device ID. It's represented by the hashed value of all device fingerprint datapoints concatenated with the Class B IP address. To generate the device fingerprint datapoints, you need to be using the fraugster.js script. Read more in Device fingerprinting with fraugster.js.

Important

There are two prerequisites for using Fraugster device ID. You have to:

• Install the fraugster.js script to generate the device fingerprint datapoints.
• Send the datapoint ip for each transaction that needs a device ID calculated. You send ip in your API request as any other datapoint, not as part of the device_fingerprint datapoint.

If you select to use Fraugster device ID in the configuration service but do not install the script or send the datapoint ip, device fingerprinting with Fraugster is not going to work.

Response example

The device ID is returned in the API response if you opted in to use one of the available options.

{
  "fraugster_approved": 0,
  "frg_trans_id": "abc01f6ccc8a5832a7871fdb14be1211",
  "is_liable": true,
  "frg_device_id": "ATHjII4ALRQySeFH1hmaC5svTtgg",
  "score": 0.92,
  "validation": {
    "ok": true
  }
}

Create rules with a device ID

Regardless of which option you choose in the configuration service, the final data you will be using for rule creation is located in the attribute device_id_mapped. This is the higher attribute that collects device ID information for you to use further. The configuration setting determines which source data is used for the rule engine attribute device_id_mapped:

• Either device_id you send through the API,
• Or device_fingerprint_ip_b_class_hash that is generated with the data produced by the fraugster.js script. It's the hashed value of all device fingerprint datapoints concatenated with the Class B IP address.

The following is a visual representation of how the higher level attribute is created:

Check a few more tips on creating rules with device ID in Rule recommendations.