minFraud scoring is based on an analysis of inputs related to the transaction being scored. The more input fields you pass to the minFraud service, the more accurate the risk score will be. Learn more about the risk score.
Continue reading to see more about:
- Our recommended minimum inputs for the minFraud service, and
- a list of outputs you may receive, based on the inputs you provide.
Recommended minimum inputs
When possible, we recommend passing at least the following inputs:
| Input | Description | API Specification (Link to Developer Portal) |
|---|---|---|
| IP | The IP address of the customer or end-user initiating the transaction. Learn more about the IP address input. | /device/ip_address |
| Billing Country | The country of the billing address provided by the customer or end-user initiating the transaction. Learn more about the billing address input. | /billing/country |
| Billing City | The city of the billing address provided by the customer or end-user initiating the transaction. Learn more about the billing address input. | /billing/city |
| Billing Postal | The postal code of the billing address provided by the customer or end-user initiating the transaction. Learn more about the billing address input. | /billing/postal |
| IIN | The issuer ID number (IIN) of the credit card used in the transaction. Learn more about the credit card IIN input. | /credit_card/issuer_id_number |
| The email address provided by the customer or end-user initiating the transaction. Learn more about the email address inputs. | /email/address |
|
| User Agent | The User-Agent header of the browser used by the customer or end-user initiating the transaction. This helps minFraud services to identify and track devices that are conducting fraud across the minFraud Network. Learn more about device tracking and the browser inputs. | /device/user_agent |
| Browser Language | The Accept-Language header of the browser used by the customer or end-user initiating the transaction. This input is used in conjunction with location indicators to see if the language being used in the browser is very unusual for the location of the transaction. Learn more about browser inputs. | /device/accept_language |
You can review all of the minFraud inputs we accept in our developer documentation.
Payment processor inputs
If you perform AVS and CVV checks through your payment processor prior to querying the minFraud service, we recommend passing the codes for these checks to minFraud as part of your query. Learn more about payment processor inputs.
You can also consult the API specifications for these inputs on our developer portal:
Risk scoring and risk data based on inputs
In addition to making scoring more accurate, the minFraud services will return different outputs depending on which inputs are received. For example, the minFraud services cannot return the IP risk score for transactions that do not have an IP address. Similarly, minFraud Insights and minFraud Factors cannot return IP geolocation information about the transaction if there is no IP address associated with it. minFraud Insights and minFraud Factors can return risk data and risk scoring related to email addresses, billing and shipping addresses, credit cards, and more, but only when the relevant inputs are provided.
You can see what kind of risk data may be returned based on which inputs you send to the minFraud Insights or minFraud Factors service (click on the links below for documentation on the input and risk data.
In addition, the minFraud Factors service will return the risk score reasons that change the risk score significantly for a given transaction. Learn more about risk score reasons.
| Input Sent | Risk Data Returned | Risk Scores Returned |
|---|---|---|
| IP |
|
|
| IP and Device Tracking |
|
-- |
| Device Data | -- | |
| Billing Address | -- | |
| IIN (Issuer ID Number) | -- | |
| -- | ||
| Shipping Address | -- |
This page was last updated on .