- November 2, 2017
minFraud Insights and Factors services now include anonymizer-type outputs. These outputs are:
/ip_address/traits/is_anonymous– whether the IP address belongs to any sort of anonymous network.
/ip_address/traits/is_anonymous_vpn– whether the IP address belongs to an anonymous VPN system.
/ip_address/traits/is_hosting_provider– whether the IP address belongs to a hosting provider.
/ip_address/traits/is_public_proxy– whether the IP address belongs to a public proxy.
/ip_address/traits/is_tor_exit_node– whether the IP address is a Tor exit node.
As these are included via GeoIP2 Precision Insights, please see our GeoIP2 Precision Web Services documentation for more information.
- July 24, 2017
- We have added a Dispositions API for use with Disposition setting from the Transaction Details page. Use this new API to integrate with your order management system, payment processor, or other internal system so that manual review decisions made in the MaxMind account portal are available within your own systems. More information Here.
- July 24, 2017
- We will be mapping additional mobile (cellular) networks to a region (subdivision) rather than city level. This change will only occur where the confidence in the city data is low due to the mobile provider allocating IPs over a wide area.
- July 13, 2017
- Customers now have the ability to create Custom Inputs for use with our minFraud services. Custom Inputs requires the use of minFraud Score, minFraud Insights, or minFraud Factors queries.
- July 13, 2017
We have added three new parameters to minFraud Score, Insights and Factors:
/device/session_age. Output Parameter:
- June 23, 2017
- Our Account Portal has been updated to include the ability for our customers to create and manage multiple license keys.
- March 17, 2017
The minFraud Transaction History page was replaced by the minFraud Transactions Screen in support of showing dispositions. In addition, it is now possible to set dispositions from the transaction details screen.
- December 5, 2016
shipCityPostalMatchoutputs are available for non-US locations.
- December 1, 2016
The responses for minFraud Score, Insights, and Factors may now include a
dispositionobject. This object contains information about custom rules that were applied to the request.
- November 17, 2016
We have added a new
/credit_card/tokeninput to the minFraud Score, minFraud Insights, and minFraud Factors request bodies. The token must uniquely identify the credit card and must be different from the account number.
- October 10, 2016
We have added two new event types to the
/event/typefield for all minFraud requests,
- September 6, 2016
We will be returning more proxyScores between 0 and 1.8 and 1.8 and 3. Such scores typically represent “medium” risk transactions which have some risk of fraud but may be legitimate. The higher the proxyScore, the riskier the transaction.
The proxyScore is a score from 0.00-4.00 indicating the likelihood that the user’s IP address is high risk.
This change has also been implemented for the IP Risk Score provided with minFraud Score, minFraud Insights, and minFraud Factors. The IP Risk Score is a score from 0.01 to 99 indicating the likelihood that the user’s IP address is high risk. We will return more positive IP Risk Scores between 0 and 45 and 45 and 75. Such scores typically represent “medium” risk transactions which have some risk of fraud but may be legitimate. The higher the IP Risk Score, the riskier the transaction.
- June 9, 2016
/device/last_seenhave been added to the minFraud Insights and minFraud Factors response. These fields are only available for customers using our Device Tracking Add-on. Please see our API documentation for more information.
- June 6, 2016
credits_remainingis deprecated in the minFraud Score, minFraud Insights, and minFraud Factors response. It will be removed before the final release. It has been replaced with
queries_remaining, which also returns the number of queries available. An additional field,
funds_remaining, containing the US dollar value of the funds remaining will be added before the final release.
- February 18, 2016
All minFraud services now include an updated machine learning algorithm that takes order amount into consideration when calculating the risk score.
Merchants may want to update their rules if the rule is a combination of risk score and order amount. For example, if a custom rule rejects transactions with a high order amount and a risk score above 10, the merchant may want to adjust the risk score to a higher number, as the high order amount itself may cause the risk score to increase.
In general, orders $500 or above may have a higher risk score than before.