minFraud Release Notes

May 14, 2020

Customers of minFraud Insights and minFraud Factors can now use the following Anonymous IP outputs as parameters to serve as the basis when creating a custom rule:

  • /ip_address/traits/is_anonymous
  • /ip_address/traits/is_anonymous_vpn
  • /ip_address/traits/is_hosting_provider
  • /ip_address/traits/is_public_proxy
  • /ip_address/traits/is_tor_exit_node

May 8, 2020

On May 8, 2020, we discontinued our legacy minFraud SOAP API in order to focus our development on our newer current APIs. We initially announced this retirement in April 2019.

Other client APIs for legacy minFraud services (not recommended) will continue to be supported. We recommend either integrating with the legacy minFraud service directly, or using our current minFraud services.

April 27, 2020

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:

  • /billing/address – The first line of the user’s billing address.
  • /billing/address_2 – The second line of the user’s billing address.
  • /email/is_disposable – This field is true if MaxMind believes that the email address is from a disposable email provider. It is false if the address is not from a known disposable email provider.

April 6, 2020
The /credit_card/is_business output is now available in minFraud Insights and Factors. This field is true if the issuer ID number is for a business card.
March 24, 2020

The /email/domain/first_seen output is now available in minFraud Insights and Factors. This output is a date string (e.g. 2020-03-24) indicating the date the email address domain was first seen by MaxMind. The earliest date that may be returned is January 1, 2019.

March 2, 2020

Users of the minFraud Score, Insights, and Factors services can now manually submit minFraud queries (with a subset of inputs) through the new minFraud Query Form [login required]. The results of the query are displayed in our minFraud Interactive user interface.

February 19, 2020

The /email/is_disposable output is now available in minFraud Insights and Factors. The output is a boolean indicating whether the email address is from a disposable email provider.

February 4, 2020

We’ve added the following outputs to the Transaction Details screen in minFraud Interactive to assist you with manual review of minFraud transactions:

  • Subdivision name
  • Registered country name
  • Represented country name
  • Represented country type
  • Country, city, and subdivision confidence
  • ISP
  • Organization
  • Domain
  • Anonymous IP flags
  • User count
  • Static IP score

You can find descriptions of these outputs here.

January 31, 2020

On January 31, 2020, we discontinued our legacy IIN (BIN) API in order to focus development and maintenance efforts on our core services. The affected endpoint is /app/bin_http.

We continue to support the IIN (BIN) manual look-up form on our website [login required].

January 29, 2020

minFraud service users can now tag transactions (e.g. chargeback, not fraud, spam/abuse, suspected fraud) directly from the Transaction Details screen for an individual transaction in minFraud Interactive.

Tagging transactions allows us to detect 10-50% more fraud for you. You may also tag transactions outside of minFraud Interactive by using this form.

December 23, 2019

Our web services, including GeoIP2 Precision web services and minFraud services, now return the error code ACCOUNT_ID_REQUIRED instead of USER_ID_REQUIRED when the account ID parameter is missing.

December 17, 2019

You can now filter by license key when viewing the query usage report [login required] in your account portal.

December 11, 2019

Account administrators can now enable or disable access to the minFraud Transactions page [login required], which is accessible from the account portal. You can manage account access to this feature here [login required].

The minFraud Transactions page is used for review, dispositioning, tagging, and exporting transactions. See our guide for more info.

December 10, 2019

Effective December 16, 2019, we will return 1 as the last digit for all 7 digit postal codes in Japan. The last digit refers to street-level resolution and should not be relied upon for IP geolocation.

November 8, 2019

Effective November 12, 2019, we will return -001 as the last 3 digits for all 7 digit postal codes in Lisbon, Portugal. Our postal code resolution in Portugal is accurate for the first 4 digits and we include the -001 at the end for backwards compatibility for customers to join the data with 7 digit Portuguese postal code databases. We may extend this convention to other large Portuguese cities in the future.