- April 6, 2020
/credit_card/is_businessoutput is now available in minFraud Insights and Factors. This field is
trueif the issuer ID number is for a business card.
- March 24, 2020
/email/domain/first_seenoutput 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
/email/is_disposableoutput 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
- 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
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
- 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
1as 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
-001as 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
-001at 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.
- October 16, 2019
We retired support for TLS v1.0/v1.1 and unencrypted HTTP requests to minFraud services today, as part of our commitment to securing and protecting your data. Please ensure you are using TLS v1.2+ to connect to MaxMind services.
- October 15, 2019
static_ip_score– An indicator of how static or dynamic an IP address is. The value ranges from 0 to 99.99 with higher values meaning a greater static association. For example, many IPs with a
cellularhave a score under one. Static Cable/DSL IPs typically have a score above thirty.
This indicator can be useful for deciding whether an IP address represents the same user over time.
static_ip_scoreoutput is present in the
- October 14, 2019
This is a reminder that we are retiring support for requests using TLS 1.0/1.1, and unencrypted HTTP requests to MaxMind minFraud services on October 16, 2019. After October 16, 2019, these types of requests will always fail with an error. Please update to TLS 1.2+ to avoid service disruption. You may need to upgrade your technology stack to a later version, or make code changes to do so.
Contact us for support or if you have questions.