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, [email protected] will become
    [email protected].
  • Fastmail alias subdomain email addresses are now normalized when
    hashEmail is used. For example, [email protected] will become
    [email protected].
  • Additional yahoo.com email addresses now have aliases removed from
    their local part when hashEmail is used. For example,
    [email protected] will become [email protected] 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.

2.0.0

• IMPORTANT: PHP 8.1 or greater is now required.
• BREAKING: Read-only properties are now used for the model class rather than
  magic methods.
• BREAKING: The rawResponse property on model classess has been removed. Use
  the jsonSerialize method instead.
• BREAKING: The inheritance hierarchy on model classes has changed.
• Updated geoip2/geoip2 to version that includes the isAnycast property on
  GeoIp2\Record\Traits. This property is true if the IP address belongs to
  an anycast network. This is available
  in minFraud Insights and Factors.

1.23.0

• Fixed "creation of a dynamic property" deprecation warning on newer PHP
  versions. Reported by Andrey Lebedev. GitHub #145.
• Added google_pay to the payment processor validation.
• Added placetopay to the payment processor validation.

1.22.0

• The model class names are no longer constructed by concatenating strings.
  This change was made to improve support for tools like PHP-Scoper.
• Added shopify_payments to the payment processor validation.
• Box 4.0.1 is now used to generate the geoip2.phar file.

1.21.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.
• Fixed PHP 8.1 deprecation warning in internal validation classes.

1.20.0

• Upgraded geoip2/geoip2 to 2.12.0. This adds mobile country code (MCC)
  and mobile network code (MNC) to minFraud Insights and Factors responses.
  These are available at $response->ipAddress->traits->mobileCountryCode and
  $response->ipAddress->traits->mobileNetworkCode. We expect this data to be
  available by late January, 2022.
• minfraud.phar is now generated with Box 3.x.
• 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

1.19.0

• Added datacap to the payment processor validation.
• Added ruleLabel to minFraud output Disposition.
• Added was_3d_secure_successful to /credit_card validation.