3.6.0

• Added the anonymizer property to MaxMind\MinFraud\Model\IpAddress. This
  contains anonymizer data from the GeoIP2 Insights response, including VPN
  detection confidence, provider name, and network last seen date. This was
  previously available in the GeoIP2 library but not exposed in minFraud
  responses.
• Added banquest, summit_payments, and yaadpay to the payment processor
  validation.

3.5.0

• Added support for new /email/domain/ outputs in minFraud Insights and
  Factors responses:
  • /email/domain/classification - categorizes the email domain type
    (business, education, government, isp_email)
  • /email/domain/risk - risk score associated with the domain (0.01 to 99)
  • /email/domain/volume - activity level across the minFraud network
    (sightings per million)
  • /email/domain/visit/has_redirect - whether the domain redirects
  • /email/domain/visit/last_visited_on - date of last automated check
  • /email/domain/visit/status - domain status (live, dns_error,
    network_error, http_error, parked, pre_development)

3.4.0

• Added securepay to the payment processor validation.
• Added credit_application, fund_transfer, and sim_swap to event type
  validation.
• Added the input /event/party. This is the party submitting the
  transaction.
• Added the input /payment/method. This is the payment method associated
  with the transaction.
• Updated geoip2/geoip2 to 3.3.0, which includes new anonymizer and IP risk
  outputs.

3.3.0

• Added support for the /billing_phone/matches_postal and
  /shipping_phone/matches_postal outputs. These are available as the
  matchesPostal property on MaxMind\MinFraud\Model\Phone.
• Added cryptomus to the payment processor validation.
• \MaxMind\MinFraud now implements JsonSerializable. This returns an
  array containing the contents of the request in a sub-array as well as
  the value of the locales and hashEmail options. Pull request by Noé
  Fleury. GitHub #193.

3.2.0

• Added epayco to the payment processor validation.

3.2.0-beta.2

• The minFraud Factors subscores have been deprecated. They will be removed
  in March 2025. Please see our release notes
  for more information.
• The type hints in the PHPDocs have been improved.

3.2.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.1.0

• Updated MaxMind\MinFraud\ReportTransaction to make the ip_address
  parameter optional. Now the tag and at least one of the following
  parameters must be supplied: ipAddress, maxmindId, minfraudId,
  transactionId.
• Added billingPhone and shippingPhone properties 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 validation.

3.0.1

• When calling withDevice with an array, an exception was incorrectly
  thrown if user_agent was set but session_id was not set. Reported by
  Gregor Kuhlmann. GitHub #172.

3.0.0

• This library no longer uses Respect\Validation.
• The with* methods can now be used with named arguments instead of
  an array. This provides better editor completion, type checking,
  and documentation.
• Email normalization has been improved:
  • Equivalent domain names are now normalized when hashEmail is used.
    For example, googlemail.com will become gmail.com.
  • Periods are now removed from gmail.com email address local parts when
    hashEmail is used. For example, f.o.o@gmail.com will become
    foo@gmail.com.
  • Fastmail alias subdomain email addresses are now normalized when
    hashEmail 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 hashEmail 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
    hashEmail is used. For example, example.com.com will become
    example.com.
  • Certain TLD typos are now normalized when hashEmail is used. For
    example, example.comcom will become example.com.
  • Additional gmail.com domain names with leading digits are now
    normalized when hashEmail is used. For example, 100gmail.com will
    become gmail.com.
  • Additional gmail.com typos are now normalized when hashEmail is used.
    For example, gmali.com will become gmail.com.
  • When hashEmail is used, the local part of an email address is now
    normalized to NFC.
• Added pxp_financial and trustpay to the payment processor validation.