minFraud Release Notes

June 14, 2019
We have added Node.js as a MaxMind Supported minFraud API (NPM, GitHub). It provides an API for the minFraud Score, Insights, and Factors services.
April 18, 2019
In order to ensure your data is as safe and secure as possible, we will be retiring support for TLS v1.0 and 1.1, unencrypted HTTP requests to our legacy minFraud services, and our legacy minFraud SOAP API in the coming months. Please see our blog for more info.
April 8, 2019
To enhance the security of your MaxMind account, Chrome users can enable two-factor authentication (2FA). You can now add and require a (FIDO U2F) security key on top of your account credentials for a more secure log-in. See our support center user guide for information on how to set up 2FA.
September 21, 2018
On Monday, October 1st, we will be changing a large amount of our U.S. coordinate (latitude & longitude) data* to use GeoNames coordinates for postal codes. This change will ensure greater consistency during our build processes. Around 95% of US coordinates will change with most moving about 1 mile. About 5 to 10% of US coordinates will move by more than 10 miles.

* Coordinate data is approximate and is not precise. It should not be used to identify a particular street address or household as it refers to a larger geographical area instead of a precise location.
July 17, 2018
We have released additional input parameters for use with custom rules. Customers of minFraud Score, minFraud Insights, and minFraud Factors can now use the following inputs to serve as the basis when creating a custom rule:

  • IIN: /credit_card/issuer_id_number – The issuer ID number for the credit card. This is the first 6 digits of the credit card number. It identifies the issuing bank.
  • Accept Language: /device/accept_language – The HTTP “Accept-Language” header of the device used in the transaction.
  • IP (CIDR block): /device/ip_address – A network CIDR block
May 25, 2018
Effective May 29, 2018, we will be adding Åland Islands, Martinique, Mayotte, Guadeloupe, French Guiana, Réunion, and Saint Martin to the list of European Union locations identified by minFraud Insights and minFraud Factors responses.
May 18, 2018

The HTTP request made by the Device Tracking Add-on now always uses HTTPS. Previously it used HTTP if your document was served over HTTP. This reduces compatibility with certain older versions of Internet Explorer, but will not cause errors.

We also recommend that you use an HTTPS URL when including the add-on in your site. We’ve updated the example code in our documentation to show how to do this.

April 10, 2018

We’ve added two new output fields to the minFraud Insights and Factors services. The outputs are:

  • Credit card is_virtual: /credit_card/is_virtual – A flag that is true if the credit card is a virtual card.
  • Device local_time: /device/local_time – A date-time indicating the local date and time of the transaction in the time zone of the device.

We’ve also added a new event type to the /event/type field for all minFraud requests: payout_change.

February 13, 2018
We have added additional outputs to the minFraud Insights and minFraud Factors services. The outputs are:

  • EU Country: /country/is_in_european_union – Country of the location of the IP address in an EU member state
  • EU Registered Country: /registered_country/is_in_european_union – Country registered by the ISP or organization is an EU member state

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: Input Parameters: /device/session_id, /device/session_age. Output Parameter: /email/first_seen.

June 23, 2017
Our Account Portal has been updated to include the ability for our customers to create and manage multiple license keys.