minFraud Release Notes - 2020 Archive

We have released an additional output for our web services. GeoIP2 Insights, minFraud Insights, and minFraud Factors customers can now see whether an IP address is likely a residential proxy:

• /traits/is_residential_proxy – This is true if the IP address is on a suspected anonymizing network and belongs to a residential ISP. Otherwise, the key is not included in the traits object.

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

We have released an additional input parameter for use with custom rules. Customers of minFraud Score, minFraud Insights, and minFraud Factors can now use email address to serve as the basis when creating a custom rule:

• Email address: /email/address/ – a valid email address or an MD5 of the lowercased email used in the transaction.

For more information on implementing custom rules, see the Custom Rules Guide on our Support Center.

We have released three additional risk-factor outputs. Customers of minFraud Factors can now access the following risk factors:

• /subscores/device – Risk associated with the device.
• /subscores/email_local_part – Risk associated with the part of the email before the @ symbol.
• /subscores/shipping_address – Risk associated with the shipping address.

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

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

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.

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.

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.

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].

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.