2.12.0b1

• setuptools was incorrectly listed as a runtime dependency. This has
  been removed.
• Added support for the new risk reasons outputs in minFraud Factors. The risk
  reasons output codes and reasons are currently in beta and are subject to
  change. We recommend that you use these beta outputs with caution and avoid
  relying on them for critical applications.

2.11.0

• Updated the validation for the Report Transactions API to make the
  ip_address parameter optional. Now the tag and at least one of the
  following parameters must be supplied: ip_address, maxmind_id,
  minfraud_id, transaction_id.
• Added billing_phone and shipping_phone properties to the minFraud
  Insights and Factors response models. These contain objects with information
  about the respective phone numbers. Please see our developer site <https://dev.maxmind.com/minfraud/api-documentation/responses/>_ for
  more information.
• Added payconex to the /payment/processor validation.

2.10.0

• Added the following new values to the /payment/processor validation:

  • pxp_financial
  • trustpay

• Equivalent domain names are now normalized when hash_email is used.
  For example, googlemail.com will become gmail.com.

• Periods are now removed from gmail.com email address local parts when
  hash_email is used. For example, f.o.o@gmail.com will become
  foo@gmail.com.

• Fastmail alias subdomain email addresses are now normalized when
  hash_email is used. For example, alias@user.fastmail.com will
  become user@fastmail.com.

• Additional yahoo.com email addresses now have aliases removed from
  their local part when hash_email is used. For example,
  foo-bar@yahoo.com will become foo@yahoo.com for additional
  yahoo.com domains.

• Duplicate .com s are now removed from email domain names when
  hash_email is used. For example, example.com.com will become
  example.com.

• Certain TLD typos are now normalized when hash_email is used. For
  example, example.comcom will become example.com.

• Additional gmail.com domain names with leading digits are now
  normalized when hash_email is used. For example, 100gmail.com will
  become gmail.com.

• Additional gmail.com typos are now normalized when hash_email is
  used. For example, gmali.com will become gmail.com.

• When hash_email is used, the local part of an email address is now
  normalized to NFC.

2.9.0

• IMPORTANT: Python 3.8 or greater is required. If you are using an older
  version, please use an earlier release.
• Updated geoip2 to version that includes the is_anycast attribute on
  geoip2.record.Traits. This property is True if the IP address
  belongs to an anycast network <https://en.wikipedia.org/wiki/Anycast>_.
  This is available in minFraud Insights and Factors.

2.8.0

• IMPORTANT: Python 3.7 or greater is required. If you are using an older
  version, please use an earlier release.
• Added the following new values to the /payment/processor validation:
  • google_pay
  • placetopay
  • shopify_payments

2.7.2

• Updated code to correctly handle None Content-Type from minFraud
  web service. This should never happen, but if it does, the correct
  exception will now be thrown.

2.7.1

• Fixed KeyError when using the report() method. Reported by siang.
  GitHub #99.

2.7.0

• Added the input /credit_card/country. This is the country where the
  issuer of the card is located. This may be passed instead of
  /credit_card/issuer_id_number if you do not wish to pass partial
  account numbers or if your payment processor does not provide them.

2.6.0

• Upgraded geoip2 to 4.5.0. This adds mobile country code (MCC) and mobile
  network code (MNC) to minFraud Insights and Factors responses. These are
  available at response.ip_address.traits.mobile_country_code and
  response.ip_address.traits.mobile_network_code. We expect this data to be
  available by late January, 2022.
• Added the following new values to the /payment/processor validation:
  • boacompra
  • boku
  • coregateway
  • fiserv
  • neopay
  • neosurf
  • openbucks
  • paysera
  • payvision
  • trustly
  • windcave
• The /credit_card/last_4_digits input has been deprecated in favor of
  /credit_card/last_digits and will be removed in a future release.
  last_digits/last_4_digits also now supports two digit values in
  addition to the previous four digit values.
• Eight digit /credit_card/issuer_id_number inputs are now supported in
  addition to the previously accepted six digit issuer_id_number. In most
  cases, you should send the last four digits for last_digits. If you send
  an issuer_id_number that contains an eight digit IIN, and if the credit
  card brand is not one of the following, you should send the last two digits
  for last_digits:
  • Discover
  • JCB
  • Mastercard
  • UnionPay
  • Visa

2.5.0

• Previously, the py.typed file was not being added to the source
  distribution. It is now explicitly specified in the manifest.