minFraud Release Notes

We have added new fields to the email/domain sub-object in our minFraud Insights and Factors web services. This enhancement provides you with more granular data for risk modeling and workflows, which is especially useful in B2B account opening/onboarding use cases.

These data points will only be returned when you pass the domain or the unhashed email address as an input to the minFraud Insights and Factors web services. Learn more about domain risk data on our knowledge base.

Client APIs have been updated to reflect this change.

We have released additional inputs and possible input values for all minFraud web service customers.

event/type now supports the additional values below. View the full list of possible values for event/type on our developer portal.

Passing the additional inputs above can help us improve our risk scoring accuracy for you by increasing the context available to our machine learning models and heuristics.

Our client APIs have been updated to support these inputs so you may need to refresh yours to submit them in your minFraud requests if you are not interfacing directly with our REST API.

Effective tomorrow, Thursday, December 18, 2025, we will be blanking out the subdivision, city, and postal fields more often in the following countries. This change will result in fewer resolutions in:

• Amman, Jordan
• Budapest, Hungary
• Reykjavik, Iceland
• All cities in Austria
• All cities in South Africa
• All cities in Vietnam

We will also be blanking out city and postal fields more often for cell networks in:

• India
• Mexico
• United States

This change is to reduce false positives when the end users of a network are dispersed all over the country.

The update will be reflected in the following products and services:

• minFraud Factors web service
• minFraud Insights web service
• GeoIP City database
• GeoIP Enterprise database
• GeoIP City Plus web service
• GeoIP Insights web service

Effective Monday, December 1, 2025, we will be blanking out the subdivision, city, and postal fields more often in the following countries. This change will result in fewer resolutions in:

• Belgium
• Israel
• Italy
• The Netherlands
• Portugal
• Sweden
• Ukraine

We will also be blanking out city and postal fields more often for cell networks in:

• Canada
• United States

This change is to reduce false positives when the end users of a network are dispersed all over the country. Many of the networks affected by this change are cell networks, which are often allocated across a wide area spanning one or more subdivisions.

The update will be reflected in the following products and services:

• minFraud Factors web service
• minFraud Insights web service
• GeoIP City database
• GeoIP Enterprise database
• GeoIP City Plus web service
• GeoIP Insights web service

We have added the ip_risk_snapshot to the traits object in our GeoIP Insights web service and our minFraud Insights and Factors web services. This field contains the risk associated with the IP address. The value ranges from 0.01 to 99. A higher score indicates a higher risk.

The IP risk snapshot is not a replacement for the minFraud IP risk score (ip_address/risk).

The IP risk snapshot is based on an analysis of historical risk on the IP address, while the minFraud IP risk score is a responsive data field that generates an IP risk score in real time based on the transactions you send and activity from across the minFraud network.

minFraud customers may find the IP risk snapshot output useful to determine whether an IP address is risky based on historical activity versus a current, emerging issue. A lower traits/ip_risk_snapshot score combined with a higher minFraud ip_address/risk score would mean that the IP address is becoming risky in real time based on the traffic on your and other customers’ networks. A high score in both ip_risk_snapshot and minFraud IP risk score would mean that the IP address has been risky for a longer time.

Client APIs have been updated to reflect this change.

We have added an anonymizer object to our web services. This object contains the anonymizer data previously found in the traits object together with new outputs.

Anonymizer data in the traits object is being marked as deprecated. However, for backwards compatibility, anonymizer data in the traits object will continue to be populated and the functionality remains the same. This will not be a breaking change.

We recommend updating your integrations to use the new anonymizer object, which contains data points not found in the traits object:

Client APIs have been updated to reflect this change, which applies to the following web services:

• minFraud Insights
• minFraud Factors
• GeoIP Insights

Effective tomorrow, Wednesday, November 19, 2025, we will be blanking out the subdivision, city, and postal fields more often in the following cities and countries. This change will result in fewer resolutions in:

• Bangkok, Thailand
• Istanbul, Turkey
• All cities in Argentina
• All cities in France
• All cities in Germany
• All cities in Ireland
• All cities in Poland
• All cities in South Korea
• All cities in Switzerland
• All cities in Taiwan
• All cities in the United Kingdom
• All cities in Uruguay

This change is to reduce false positives when the end users of a network are dispersed all over the country.

The update will be reflected in the following products and services:

• minFraud Factors web service
• minFraud Insights web service
• GeoIP City database
• GeoIP Enterprise database
• GeoIP City Plus web service
• GeoIP Insights web service

Effective Monday, November 10, 2025, we will be blanking out the subdivision, city, and postal fields more often in Austria, Denmark, Greece, Ireland, Norway, Spain, and Sweden where the end users are actually dispersed all over the country.

This change will result in fewer resolutions to the following cities:

• Vienna, Austria
• Copenhagen, Denmark
• Athens, Greece
• Dublin, Ireland
• Oslo, Norway
• All cities in Spain
• Stockholm, Sweden

The update will be reflected in the following products and services:

• minFraud Factors web service
• minFraud Insights web service
• GeoIP City database
• GeoIP Enterprise database
• GeoIP City Plus web service
• GeoIP Insights web service

As of Tuesday, November 4, 2025, we are blanking out the subdivision, city, and postal fields in cases where the subdivision was previously mapped to Tokyo but end users are dispersed throughout Japan.

This change will result in fewer resolutions to the Tokyo subdivision and will be reflected in the following products and services:

• minFraud Factors web service
• minFraud Insights web service
• GeoIP City database
• GeoIP Enterprise database
• GeoIP City Plus web service
• GeoIP Insights web service

We have added EMAIL_DOMAIN_CREATION_DATE as a new risk score reason.

The EMAIL_DOMAIN_CREATION_DATE risk reason will be returned as either EMAIL_DOMAIN_CREATION_DATE raised the overall risk score or EMAIL_DOMAIN_CREATION_DATE lowered the overall risk score to clearly indicate the effect the reason has on the score.

Please email product@maxmind.com if you have any questions.

We have identified a bug with postal code validation in our database build process.

This bug is resulting in a number of incorrect and invalid values for postal codes. We are working on a fix.

The following products and services are impacted:

• minFraud Insights
• minFraud Factors
• minfraud Legacy
• GeoIP Insights web service
• GeoIP City Plus web service
• GeoIP City database
• GeoIP Enterprise database

Risk score reasons have been officially introduced and out of beta as of February 19, 2025.

Available for all minFraud service tiers for individual transactions on the Transaction Details page and also via API for the minFraud Factors service, risk score reasons provide specific and understandable reasons for why a risk score is high or low, helping to uncover risk patterns for individual transactions and the overall transaction stream, both at a point in time and over time.

Read our blog post to learn about the ‘why’ behind risk score reasons, and how you can use the data they provide to enhance your fraud strategy.

For minFraud legacy web services, we will no longer return A1 as a country code.

This change is due to the removal of long-deprecated fields in our GeoIP databases. See our GeoIP release note for more information.