minFraud Release Notes

Updates to geolocation confidence factors

Mon, 23 Mar 2026 16:00:00 +0000

Starting tomorrow, Tuesday, March 24 2026, we’re deploying updates to our geolocation confidence factors to make them more accurate.

For networks located outside of the United States, we will be adjusting country level confidence to be higher in circumstances where those networks are used exclusively in a single country.

For all networks, we will be improving the accuracy of our subdivision, city, and postal confidence. These will be minor changes. Most significantly, some subdivision confidence values of 99 will be reduced to 95.

The following products and services will be improved:

minFraud Insights web services
minFraud Factors web services
GeoIP Insights web service
GeoIP Enterprise database

Updates to user count data

Wed, 04 Mar 2026 16:00:00 +0000

Between Tuesday March 3 and Friday, March 6, 2026 (and possibly longer), we are making daily updates to the user count data to more often return a value of 0 or 1 for residential proxies.

Previously, approximately 50% of residential proxy IPs on single household IPs had a user count value of at least 2, and 50% had a value of 0 or 1. This update will make it easier to flag a high volume of customer profiles on a residential proxy as anomalous in relation to a lower user count value of 0 or 1.

Please see an explanation of user counts below:

User count	Description
0	IP assigned to a single end-user at a time (household, person, or small business), or not in use.
1	IP assigned to a single end-user with possibility of multiple end-users.
2	IP shared with multiple end-users.
>5	IP shared with many end-users.

Learn more about user counts on our Knowledge Base.

Number of minFraud custom inputs increased to 100

Tue, 17 Feb 2026 16:00:00 +0000

You are now able to add up to 100 custom inputs in minFraud.

Custom inputs allow you to pass data that is relevant to your business and fine-tune minFraud custom rules to help identify suspicious transactions and reduce fraud.

Custom inputs are available to users of all minFraud service tiers: Score, Insights, and Factors.

Learn how to use custom inputs on our Knowledge Base.

Updates to autonomous_system_organization, ISP, and organization data

Wed, 28 Jan 2026 16:00:00 +0000

On January 21, 2026, we released data with significant changes to autonomous_system_organization and less significant changes to isp and organization data.

Customers can expect to see in many cases improved, more readable versions of autonomous_system_organization and, in some cases, small changes to isp and organization data.

This change is reflected in the following products and services:

minFraud Insights web service
minFraud Factors web service
GeoLite ASN database
GeoLite City web service
GeoIP ISP database
GeoIP Enterprise database
GeoIP City Plus web service
GeoIP Insights web service

New email domain outputs in the Insights and Factors web services

Thu, 18 Dec 2025 16:00:00 +0000

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.

new output	description
`email/domain/classification`	A classification of the domain such as business or education. Read the API specifications for domain classification on our developer portal.
`email/domain/risk`	Contains the risk associated with the domain. Read the API specifications for domain risk on our developer portal.
`email/domain/volume`	Indicates how much activity we see on an email domain across the minFraud network, expressed in sightings per million. Read the API specifications for domain volume on our developer portal.
`email/domain/first_seen`	When an email domain was first seen on the minFraud Network. Read the API specifications for domain tenure tracking on our developer portal.
`email/domain/visit`	A sub-object of `email/domain` that contains information about an automated visit to the email domain such as whether a website on the domain is live. Read the API specifications for domain visit on our developer portal.

Client APIs have been updated to reflect this change.

Expanded event type inputs, and new payment method and event party inputs

Thu, 18 Dec 2025 16:00:00 +0000

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

new input	description
`payment/method`	The payment method associated with the transaction. View possible values on our developer portal.
`event/party`	The party submitting the transaction. Either `agent` or `customer`. This input can help reduce false positive potential in cases where an agent is submitting transactions on behalf of customers. Learn more on our developer portal.

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

additional input	description
`credit_application`	The transactor is attempting to submit an application for credit.
`fund_transfer`	The transactor is attempting to transfer funds from one account to another.
`sim_swap`	For mobile network operators. A new SIM card or eSIM is being issued to activate service on a customer’s existing phone number.

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.

Subdivision, city, and postal fields blanked in additional countries

Wed, 17 Dec 2025 16:00:00 +0000

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

Subdivision, city, and postal fields blanked in additional countries

Fri, 28 Nov 2025 16:00:00 +0000

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

IP risk snapshot output added to traits object in the Insights web services

Thu, 20 Nov 2025 16:00:00 +0000

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.

New anonymizer data added to web services

Wed, 19 Nov 2025 16:00:00 +0000

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:

new data	description
`anonymizer/confidence`	A score ranging from 1 to 99 that represents our percent confidence that the network is currently part of an actively used VPN service.
`anonymizer/network_last_seen`	The last day that the network was sighted in our analysis of anonymized networks. This is in the ISO 8601 date format (YYYY-MM-DD).
`anonymizer/provider_name`	The name of the VPN provider (e.g., `nordvpn`, `surfshark`) associated with the network.

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

minFraud Insights
minFraud Factors
GeoIP Insights

Subdivision, city, and postal fields blanked in selected cities and countries

Tue, 18 Nov 2025 16:00:00 +0000

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

Subdivision, city, and postal fields blanked in selected large cities

Thu, 06 Nov 2025 16:00:00 +0000

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

Subdivision, city, and postal fields blanked in Tokyo metro area in some cases

Thu, 06 Nov 2025 16:00:00 +0000

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

EMAIL_DOMAIN_CREATION_DATE risk score reason added

Mon, 16 Jun 2025 16:00:00 +0000

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.

Resolved - Postal code validation bug

Mon, 05 May 2025 16:00:00 +0000

We have resolved the bug that resulted in a number of incorrect and invalid values for postal codes.

Postal code validation bug

Thu, 01 May 2025 16:00:00 +0000

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 out of beta

Mon, 24 Feb 2025 16:00:00 +0000

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.

No longer returning A1 country code in minFraud legacy web services

Mon, 10 Feb 2025 16:00:00 +0000

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.

Several Spectrum Business networks reclassified

Tue, 03 Dec 2024 16:00:00 +0000

In data released today, Tuesday, December 3, 2024, we are updating a large number of Spectrum Business networks to be classified as Spectrum residential networks. For these networks, the ISP name will change from Spectrum Business to Spectrum. This change has been reviewed, and is accurate.

This change will be reflected in the following products and services:

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

Updates to Risk Score Reasons (beta)

Tue, 12 Nov 2024 16:00:00 +0000

On November 13, 2024, we will release a number of updates to risk score reasons:

All reasons will be updated to say [reason] raised the overall risk score or [reason] lowered the overall risk score to more clearly indicate the effect of a reason.
The EMAIL_ADDRESS_NEW reason code will be removed and replaced with three distinct and more specific codes and reasons:
- EMAIL_FIRST_SEEN
- EMAIL_TENURE
- EMAIL_TENURE_NO_ACTIVITY
The CUSTOMER_ID reason code will be renamed to CUSTOMER_ID_ACTIVITY to better fit its reason description.

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

Deprecation of risk factor scores/subscores

Tue, 22 Oct 2024 16:00:00 +0000

On Monday, November 4, 2024, we will be deprecating the risk factor scores/ subscores data in the minFraud Factors service. Risk factor scores/subscores will be removed from the API response in March, 2025.

Risk factor scores have been replaced by risk score reasons, to help you more deeply understand your risk patterns and make more informed decisions. Please review the risk score reasons for specific and understandable insights into why a risk score is high or low. Learn more about risk score reasons on our Knowledge Base.

Submit a support ticket request if you have questions or concerns.

Upcoming improvements to user count data

Wed, 09 Oct 2024 16:00:00 +0000

On Tuesday, October 22, 2024, we will release an improvement to our user count data to better detect IPs with multiple end users.

Many IP addresses with multiple end users that previously had a user count value of 0 or 1 will now have a value of 2.

If you have applications of the data that rely on user count values with a threshold of 0, 1, or 2, you may want to increase the thresholds by 1. For example, if you currently consider user count values of greater than 1 to be high volume, you may wish to consider user count values of greater than 2 to be high volume when this update goes live.

The following services will be impacted:

minFraud Insights web service
minFraud Factors web service

Learn more about user count data on our Knowledge Base.

Submit a support ticket request if you have questions or concerns.

Increase in slightly elevated IP risk and proxy scores and remediation

Thu, 12 Sep 2024 16:00:00 +0000

On September 10, 2024 we pushed a model update to IP risk scoring that increased a large volume of IP risk scores (also referred to as proxy score for legacy services) at the lower end of the scale (between 0.01 and 1).

While these IP risk scores remained low (less than 1), this shifted the score distribution and may have impacted your systems depending on your score thresholds.

On September 12, 2024, we implemented an update that will decrease most of these low IP risk scores again. To remediate this sort of issue in the future, we will be increasing the sensitivity of our monitoring for scores on the lower end of the distribution before releasing model updates.

Introducing Risk Score Reasons beta for minFraud Factors customers

Tue, 27 Aug 2024 16:00:00 +0000

Today, we have released a new beta feature that will help minFraud Factors customers more deeply understand risk patterns and make more informed decisions.

Risk score reasons are a set of data that provide users with specific and understandable reasons for why a risk score is high or low. This data is exclusive to the minFraud Factors service.

Watch this 2-minute video to learn more.

For full details, including how to access and test this feature, check out the Risk Score Reasons knowledge base article.

To provide feedback on Risk Score Reasons, please email customersuccess@maxmind.com to schedule a feedback session.

MaxMind minFraud alert emails now include instant feedback links

Thu, 15 Aug 2024 16:00:00 +0000

MaxMind minFraud alert emails now include links that allow you to provide instant feedback on each request. Providing transaction feedback helps improve the risk scoring for your account.

You can mark a request as risky and we will raise the risk for similar requests.

Or, you can mark a request as not risky and we will lower the risk for similar requests.

Here is an example of the links in the minFraud alerts email body.

Please continue to report chargebacks and fraud on your account portal or via API.

Additional filtering options now available for minFraud transactions

Thu, 08 Aug 2024 16:00:00 +0000

The transactions screen in your MaxMind account portal now has expanded filtering options, giving you added ability to discover trends in your transactions and adjust risk strategies.

You can now filter transactions by:

Risk score range: the likelihood that a transaction is fraudulent, scored between a minimum of 0.01 and a maximum of 99
IP risk score range: the riskiness of an IP address, scored between a minimum of 0.01 and a maximum of 99
ISP: the internet service provider of the end-user who initiated the transaction
IP Country: the country for the IP address associated with the transaction

New phone outputs released for minFraud® Insights and minFraud Factors

Tue, 09 Jul 2024 16:00:00 +0000

We have released additional outputs for our minFraud Insights and minFraud Factors web services. Insights and Factors customers that pass phone numbers can now make use of the following additional outputs:

/shipping_phone/country – A two-character ISO 3166-1 country code for the country associated with the shipping phone number.
/shipping_phone/is_voip – This is true if the shipping phone number is a Voice over Internet Protocol (VoIP) number allocated by a regulator. It is false if the shipping phone number is not a VoIP number allocated by a regulator. The key is only present when a valid shipping phone number has been provided and we have data for it.
/shipping_phone/network_operator – The name of the original network operator associated with the shipping phone number. This field does not reflect phone numbers that have been ported from the original operator to another, nor does it identify mobile virtual network operators.
/shipping_phone/number_type – Indicates whether the phone number is mobile or fixed.
/billing_phone/country – A two-character ISO 3166-1 country code for the country associated with the billing phone number.
/billing_phone/is_voip – This is true if the billing phone number is a Voice over Internet Protocol (VoIP) number allocated by a regulator. It is false if the billing phone number is not a VoIP number allocated by a regulator. The key is only present when a valid billing phone number has been provided and we have data for it.
/billing_phone/network_operator – The name of the original network operator associated with the billing phone number. This field does not reflect phone numbers that have been ported from the original operator to another, nor does it identify mobile virtual network operators.
/billing_phone/number_type – Indicates whether the phone number is mobile or fixed.

These values are particularly helpful to identify mismatches between data points, such as a mismatch between the billing country as indicated by the IP address and the country as indicated by the billing phone number. Another strong signal for fraud is a phone carrier that does not operate in the country indicated by the IP address.

Our client APIs have been updated to support these outputs so you may need to refresh yours if you are not interfacing directly with our REST API.

Email first seen can be used as a parameter for custom rules

Mon, 08 Apr 2024 16:00:00 +0000

minFraud Insights and Factors customers can now use the /email/first_seen output in minFraud custom rules.

The minFraud service retains a record of when an email address or email domain was first seen on the minFraud Network. An email address that has been conducting transactions for a long time across the minFraud Network may be more trustworthy than a new email address created within the last 30 days.

You can select the email first seen output as a parameter in custom rules by selecting minFraud outputs > Email first seen when defining a new condition for a custom rule.

Upcoming changes to our TLS certificates may impact customers with unusual server configuration

Mon, 08 Apr 2024 16:00:00 +0000

Starting in May, Let’s Encrypt will no longer use a cross-signed root certificate, and the primary TLS certificate handling the *.maxmind.com domains will be impacted by this change.

Most customers will see no impact from this change.

This change should only be of concern if the servers interacting with MaxMind domains are running a very old or out of date operating system, or if you manage your own local Certificate Authority store.

API policies are now permanently enforced

Wed, 13 Mar 2024 16:00:00 +0000

To improve our server infrastructure and allow for better performance and efficiency, our API policies are now being permanently enforced as of March 13, 2024.

What are the policies?

MaxMind only accepts API and database download requests sent with the more secure HTTPS protocol.
MaxMind only accepts API and database download requests that are sent to the appropriate hostname as documented in the integration instructions on our Developer Portal (see direct links below).

What do I need to do? Ensure that you are using the correct hostname for your API requests, and that you are using HTTPS. Failure to do so will result in web service or database download requests failing.

You can view the appropriate URIs for minFraud services on our Developer Portal using the links below:

Please note: This enforcement will also affect GeoIP web service and database download requests. If you are also a GeoIP user, see our GeoIP release note on this issue.

API policies - temporary enforcement on February 7, 2024

Thu, 25 Jan 2024 16:00:00 +0000

To improve our server infrastructure and allow for better performance and efficiency, MaxMind will begin enforcing our policies around our API and database download requests on March 13, 2024. To help customers get ready for this change, we will have a planned, temporary enforcement of these policies on February 7, 2024.

What are the policies?

MaxMind will only accept API and database download requests sent with the more secure HTTPS protocol.
MaxMind will only accept API and database download requests that are sent to the appropriate hostname as documented in the integration instructions on our Developer Portal (see direct links below).

If you have not made the requested changes before Wednesday, February 7, 2024, you might experience a period where web service or database download requests fail.

You can view the appropriate URIs for minFraud services on our Developer Portal using the links below:

Please note: This enforcement also affects GeoIP API requests. If you are also a GeoIP user, see our GeoIP release note on this issue.

minFraud no longer accepts event times more than one year in the past

Mon, 22 Jan 2024 16:00:00 +0000

Starting tomorrow, January 23, 2024, minFraud will no longer accept /event/time inputs with values more than one year in the past. Most customers do not need to send the /event/time input and will not be impacted by this change. Learn more about this input and how to use it to score historical transactions on our Knowledge Base.

If you send the /event/time inputs with values more than one year in the past, minFraud will:

replace the event time with the current time
score the transaction and return a score
return an INPUT_INVALID warning with its response

Session age input can be used as a parameter for custom rules

Mon, 11 Dec 2023 16:00:00 +0000

You can now use the /device/session_age input in minFraud custom rules. Session age can be used to detect patterns of device usage across multiple sessions to help determine risk. For example, short sessions may be a higher indicator of risk.

You can select the session age input as a parameter in custom rules by selecting minFraud inputs > Session age when defining a new condition for a custom rule.

ISP output can be used as a parameter for custom rules

Mon, 04 Dec 2023 16:00:00 +0000

You can now use the /ip_address/traits/isp output in minFraud custom rules, with the following operators: matches, does not match, contains, does not contain.

Filtering transactions by ISP can be especially helpful if you notice certain ISPs are more likely to be associated with fraudulent behavior.

You can select the ISP output as a parameter in custom rules by selecting minFraud outputs > ISP when defining a new condition for a custom rule.

Learn more about setting custom rule conditions on our Knowledge Base.

Updated static IP scoring for IPv6 addresses

Wed, 29 Nov 2023 16:00:00 +0000

We are releasing a bug fix to our static IP scoring system today.

Previously we were returning higher static IP scores for cellular IPv6 addresses when the networks were actually more dynamic.

minFraud Insights and Factors customers will see the static IP score for cellular IPv6 addresses reduce. This should also result in improved risk scoring for these networks for all minFraud customers.

Learn more about static IP scores in minFraud on our Knowledge Base.

Free email output can be used as a parameter for custom rules

Thu, 16 Nov 2023 16:00:00 +0000

You can now use the /email/is_free output in minFraud custom rules. This output is available for transactions submitted through minFraud Insights and minFraud Factors when you pass the /email/address input as plaintext, or when you pass an MD5 hash of the /email/address and the plaintext /email/domain input.

Use of free email providers (e.g. Gmail, Yahoo, Outlook, etc.) by consumers is the norm, so filtering transactions on this data point is often useful only in business-to-business contexts where you expect transactions to be conducted using a business email domain.

You can select the free email output as a parameter in custom rules by selecting minFraud outputs > Is free email when defining a new condition for a custom rule.

Create stored lists of email addresses to use in minFraud custom rules

Wed, 15 Nov 2023 16:00:00 +0000

You can now add up to 2000 emails to a stored list and use it within minFraud custom rules to automatically apply a disposition to all matching transactions. Previously, you would have to create a custom rule for each separate email address.

Learn more about stored lists on our Knowledge Base.

Improvements to IP risk score

Fri, 29 Sep 2023 16:00:00 +0000

We have made some improvements to the IP risk score, and minFraud customers may see an average increase of 1.5% in their risk scores beginning Monday, October 2. These changes to risk scoring should improve the accuracy of risk scoring. This change will apply to the following data:

Overall risk score (available in all current and Legacy minFraud services)
IP risk score (available in minFraud Score, Insights, and Factors)
Proxy score (available in our Legacy Proxy detection web service)

Group and join up to 20 conditions in minFraud custom rules

Tue, 26 Sep 2023 16:00:00 +0000

When using minFraud’s custom rules, you can now group and join up to 20 conditions. The previous limit was 4 conditions.

Learn more about custom rules on our Knowledge Base.

More Virtual Payment Cards Flagged in minFraud

Wed, 30 Aug 2023 16:00:00 +0000

Effective September 1, 2023 we will be flagging more virtual payment cards from select digital banks in minFraud. In transactions where the IIN is submitted, the minFraud services will be able to accurately tag more payment cards as virtual. Virtual cards do not have a physical card associated with the card number. Customers may use virtual cards for added security, though they are also popular with resellers who use them to attempt to bypass order limits.

To benefit from increased virtual payment card detection, you must pass the IIN or BIN (credit_card/issuer_id_number) of the payment card:

Users of the minFraud Insights and Factors services will be able to see whether a submitted payment card is virtual using the credit_card/is_virtual output:

API policies - temporary enforcement on October 17, 2023

Thu, 17 Aug 2023 16:00:00 +0000

To improve our server infrastructure and allow for better performance and efficiency, MaxMind will begin enforcing our policies around our API and database download requests in March 2024. To help customers get ready for this change, we will have a planned, temporary enforcement of these policies on October 17, 2023.

What are the policies?

MaxMind will only accept API and database download requests sent with the more secure HTTPS protocol.
MaxMind will only accept API and database download requests that are sent to the appropriate hostname as documented in the integration instructions on our Developer Portal (see direct links below).

What do I need to do? To ensure that your MaxMind service is not interrupted, please ensure that you are using the correct hostname for your API requests, and that you are using HTTPS, prior to October 17, 2023. You can view the appropriate URIs for minFraud services on our Developer Portal using the links below:

Please note: This enforcement will also affect GeoIP API requests. If you are also a GeoIP user, see our GeoIP release note on this issue.

Expanded filtering options in minFraud Interactive

Thu, 20 Jul 2023 16:00:00 +0000

Within minFraud Interactive, the interface provided in your account portal for searching, filtering, reviewing, and submitting minFraud transactions, you can now click to filter on more transaction data.

From the log of your minFraud transactions you can click on a number of transaction inputs and immediately get a filtered log of your transactions with matching data. For example, if you have a transaction with a billing phone number of +1 123 555 7698, you could click on that transaction’s billing phone number and immediately see a list of all transactions submitted with the same billing phone number over the past four months.

You can click to filter on the following transaction inputs (newly filterable inputs with this release are marked with an asterisk):

Device ID
IP address
Credit card - Issuer Identification Number (IIN)*
Credit card - IIN + Last 4 digits*
Email address or domain
Shipping address*
Billing phone number*

You can learn more about minFraud Interactive’s log of your transactions on our Knowledge Base.

Data retention increased for minFraud Interactive

Mon, 17 Jul 2023 16:00:00 +0000

Effective immediately, we will begin to retain data in minFraud Interactive for up to 5 months. Although this change is already in place, you will not notice the increased retention period until early August.

Previously, we retained data in minFraud Interactive for up to 4 months.

minFraud Interactive is the interface for searching, filtering, and viewing minFraud transactions through your account portal. Learn more about minFraud Interactive on our Knowledge Base.

Correction regarding London boroughs in our geolocation data

Mon, 12 Jun 2023 16:00:00 +0000

On June 6, we announced that more networks would be mapped to London boroughs beginning on Friday, June 9.

This change has been delayed. It should be present in our products and services beginning on Friday, June 16.

In addition, for networks in the greater London area we will be returning the name of the town for city-level name data instead of the borough. The borough will be populated in the second level subdivision.

For example, a network that maps to the Walthamstow town will return Walthamstow for the city_name, and Walthamstow Forest for the second level subdivision.

More networks mapped to London boroughs

Tue, 06 Jun 2023 16:00:00 +0000

When a network geolocates to London, we will often return the borough for the city, rather than returning London. Beginning this Friday, June 9, we will be mapping more networks to London boroughs.

This change will apply to all products and services with city-level geolocation data:

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

minFraud Transactions searchable by email domain

Tue, 30 May 2023 16:00:00 +0000

We have updated the minFraud Transactions interface in the account portal to allow users to search for and filter transactions by email domain.

Learn how to search and filter minFraud Transactions through the account portal on our Knowledge Base.

minFraud Alerts will be restored

Mon, 15 May 2023 16:00:00 +0000

We are aware of an issue in which some minFraud Alerts were not being sent or were delayed.

We expect to restore full functionality to minFraud Alerts by the end of the day.

Improvements to minFraud Interactive

Wed, 29 Mar 2023 16:00:00 +0000

We have made a number of improvements to the user interface for minFraud Interactive, the interface used to view minFraud transactions through your account portal.

The functionality of the interface is not changed, but some of the features now appear in a different place on the screen, and the transaction information is now displayed differently.

Learn how to navigate the new interface on our Knowledge Base.

Velocity Checking on User ID

Tue, 21 Mar 2023 16:00:00 +0000

We have enabled velocity tracking on the account/user_id input for all minFraud customers.

If you send a user ID associated with your transactions, minFraud will now factor the velocity of the user’s transactions into the risk score.

The account/user_id input allows you to pass a unique identifier for each of your users so that the minFraud service can group transactions by user in order to identify fraud signals attached to specific users.

Learn more about the account/user_id input on our Developer Portal.

Learn more about velocity tracking on our Knowledge Base.

New License Key Format

Thu, 16 Mar 2023 16:00:00 +0000

We have updated the format of our license keys. New license keys will be longer, with a six character prefix.

The new license keys can be used in all current versions of our Client APIs and in version 3.1.1 and higher of our GeoIP Update program.

No action is required for minFraud users. Existing license keys will still be valid and will continue to function normally.

New license keys will have the following changes:

The character set is changing from [a-zA-Z0-9] to [a-zA-Z0-9_].
The length of the license key will now be 40 characters.
License keys will have a _mmk suffix.

Please note that the length of license keys may be increased in the future.