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.
Recommended minimum inputs
When possible, we recommend passing at least the following inputs:
| Input | Description | API Specification (Link to Dev Documentation) |
|---|---|---|
| IP | The IP address of the customer or end-user initiating the transaction. | /device/ip_address |
| Billing Country | The country of the billing address provided by the customer or end-user initiating the transaction. | /billing/country |
| Billing City | The city of the billing address provided by the customer or end-user initiating the transaction. | /billing/city |
| Billing Postal | The postal code of the billing address provided by the customer or end-user initiating the transaction. | /billing/postal |
| IIN | The issuer ID number (IIN) of the credit card used in the transaction. Read more about credit card IINs on Wikipedia. | /credit_card/issuer_id_number |
| The email address provided by the customer or end-user initiating the transaction. | /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. | /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. | /device/accept_language |
You can review all of the minFraud inputs we accept in our developer documentation.
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 and risk scores will be returned based on which inputs you send to the minFraud Insights or minFraud Factors service:
| Input Sent | Risk Data Returned | Risk Scores Returned |
|---|---|---|
| IP |
|
|
| IP and Chargebacks Learn more about reporting chargebacks. |
-- | |
| IP and Device Tracking Learn more about device tracking. |
|
|
| Device Data | -- | |
| Billing Address | ||
| IIN (Issuer ID Number) | ||
| Shipping Address |
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. The API specifications for these inputs are documented on the dev site under /credit_card/avs_result and /credit_card/cvv_result.
This page was last updated on .