You can pass information about the device that your end user or customer used to initiate the transaction. The minFraud services accept the following inputs about the transacting device:
- the IP address the device is using,
- the user agent and language of the device’s browser, and
- the length of time the device has been on your website, and a unique ID that can be used to identify the device’s visit.
In addition to these inputs, you can also set up device tracking through the minFraud services for better risk scoring about devices, and additional risk data about devices when using the minFraud Insights or Factors services. Learn how to set up device tracking.
IP Address
You can pass the public IP address of the transacting device (for example, your customer or user’s device) to the minFraud service. The IP address is one of the recommended high value inputs to pass to the minFraud service when it is available.
To get accurate risk scoring, ensure that you are actually passing the IP address of the end user or customer where it is available:
- If you use a load balancer, reverse proxy, or content delivery network you may have to check your documentation to find out how to access the IP address of the end users to your website or applications.
- If your customers or end users are using anonymizers, it will not be possible to discover the IP address of the end user. However, if you pass the IP address of the anonymizer being used, the minFraud services will attempt to identify the type of anonymizer and adjust the risk score accordingly. You can learn more about different kinds of anonymizers and consumer privacy networks.
- There may be other situations where it is difficult to associate an IP address with an end user. You can learn more about how IP addresses are assigned and used on our blog.
When you pass the IP address input, you should get the following effect based on the minFraud service that you are using. Click on the links below to learn more about how this input is used to help generate risk scores and risk data:
| minFraud Score, Insights, and Factors | minFraud Insights and Factors |
|---|---|
|
|
You can read the full API specification for the IP address input on our developer portal:
Browser Information
You can capture certain information from the web browser of your customers or end users and pass it to the minFraud services for scoring. The user agent and language of the browser can be used to identify riskier patterns of device usage, for example if a fraudster is using a particular browser setup to perpetuate fraud.
When you pass browser information inputs, you should get the following effect based on the minFraud service that you are using. Click on the links below to learn more about how these inputs are used to help generate risk scores and risk data:
| minFraud Score, Insights, and Factors | minFraud Insights and Factors | minFraud Factors |
|---|---|---|
|
If you have device tracking enabled:
|
|
You can read the full API specification for the browser inputs on our developer portal:
Session Information
You can pass a unique ID that identifies the session of the transaction, the specific visit by a device to your website or application in which the transaction occurred. You can also pass the length of time that the session has lasted. This information can be used to detect patterns of device usage across multiple sessions to help determine risk. For example, short sessions may be a higher indicator of risk.
When you pass session data inputs, you should get the following effect based on the minFraud service that you are using. Click on the links below to learn more about how this input is used to help generate risk scores and risk data:
| minFraud Score, Insights, and Factors |
|---|
|
You can read the full API specification for the session inputs on our developer portal:
This page was last updated on .