3.8.0

• commons-validator has been removed as a dependency. This module now does
  its own email and domain name validation. This was done to reduce the number
  of dependencies and any security vulnerabilities in them. The new email
  validation of the local part is somewhat more lax than the previous
  validation.

3.7.2

• First release using Central Portal instead of Legacy OSSRH.
• Update geoip2 dependency.

3.7.1

• Updated pom.xml to fix issue with javadoc generation during the release
  process.

3.7.0

• Added support for the /billing_phone/matches_postal and
  /shipping_phone/matches_postal outputs. These are available as the
  matchesPostal method on com.maxmind.minfraud.response.Phone.
• Added CRYPTOMUS to the Payment.Processor enum.

3.6.0

• The minFraud Factors subscores have been deprecated. They will be removed
  in March 2025. Please see our release notes
  for more information.
• Added EPAYCO to the Payment.Processor enum.

3.6.0-beta.1

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

3.5.0

• Updated TransactionReport to make the ipAddress parameter optional. Now
  the tag and at least one of the following parameters must be supplied:
  ipAddress, maxmindId, minfraudId, transactionId.
• The TransactionReport.Builder(INetAddress, Tag) constructor has been
  deprecated in favor of the new TransactionReport.Builder(Tag) constructor.
• Added getBillingPhone and getShippingPhone methods to the minFraud
  Insights and Factors response models. These contain objects with information
  about the respective phone numbers. Please see our developer
  site for
  more information.
• Added PAYCONEX to the Payment.Processor enum.

3.4.0

• Added PXP_FINANCIAL and TRUSTPAY to the Payment.Processor enum.
• Equivalent domain names are now normalized when hashAddress is used.
  For example, googlemail.com will become gmail.com.
• Periods are now removed from gmail.com email address local parts when
  hashAddress is used. For example, f.o.o@gmail.com will become
  foo@gmail.com.
• Fastmail alias subdomain email addresses are now normalized when
  hashAddress 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 hashAddress is used. For example,
  foo-bar@yahoo.com will become foo@yahoo.com for additional
  yahoo.com domains.
• Duplicate .coms are now removed from email domain names when
  hashAddress is used. For example, example.com.com will become
  example.com.
• Certain TLD typos are now normalized when hashAddress is used. For
  example, example.comcom will become example.com.
• Additional gmail.com domain names with leading digits are now
  normalized when hashAddress is used. For example, 100gmail.com will
  become gmail.com.
• Additional gmail.com typos are now normalized when hashAddress is
  used. For example, gmali.com will become gmail.com.
• When hashAddress is used, all trailing periods are now removed from an
  email address domain. Previously only a single period was removed.
• When hashAddress is used, the local part of an email address is now
  normalized to NFC.

3.3.0

• Updated geoip2 dependency to version that includes the isAnycast method
  on com.maxmind.geoip2.record.Traits. This returns true if the IP
  address belongs to an anycast network.
  This is available in minFraud Insights and Factors.

1.19.0

• Updated model classes with non-breaking changes from the 3.2.0
  release.
• Updated Jackson and geoip2 dependencies.