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

7.0.0

• Breaking 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.
• 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 Processor enum.

v7.0.0-beta.1

• Breaking Updated TransactionReport to make the ipAddress parameter
  optional. Now the tag and at least one of the following paramters must be
  supplied: ipAddress, maxmindId, minfraudId, transactionId.
• Added support for the new risk reasons outputs in minFraud Factors.

6.1.0

• Added PxpFinancial and Trustpay to the 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, [email protected] will become
  [email protected].
• Fastmail alias subdomain email addresses are now normalized when
  hashAddress is used. For example, [email protected] will become
  [email protected].
• Additional yahoo.com email addresses now have aliases removed from
  their local part when hashAddress 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
  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, the domain part of an email address is now
  normalized to NFC.
• When hashAddress is used, the local part of an email address is now
  normalized to NFC.

v6.0.0

• Breaking Drop Node 16 support
• Add host parameter to Client constructor to allow for use of the Sandbox environment.
• Updated @maxmind/geoip2-node to version that includes the isAnycast attribute on response.ipAddress.traits. This attribute is true if the IP address belongs to an anycast network. This is available in minFraud Insights and Factors.

v5.0.0

• Drop Node 14 support

v4.7.0

• Added GooglePay to the Processor enum.
• Added Placetopay to the Processor enum.
• Set minimum version of GeoIP2-node to v3.5.0.
• Remove camelcase-keys dependency.

4.6.0

• Added ShopifyPayments to the Processor enum.
• Fix creditCard.was3DSecureSuccessful snakecase conversion.

4.5.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 the
  /credit_card/issuer_id_number if you do not wish to pass partial
  account numbers or if your payment processor does not provide them. You
  may provide this by providing country to CreditCard.

v4.4.0

• Added the following new values to the Processor enum:
  • Boacompra
  • Boku
  • Coregateway
  • Fiserv
  • Neopay
  • Neosurf
  • Openbucks
  • Paysera
  • Payvision
  • Trustly
  • Windcave
• Updated dependencies.
• Added 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.
• creditCard.last4digits has been deprecated in favor of creditCard.lastDigits
  and will be removed in a future release. lastDigits/last4digits also now
  supports two digit values in addition to the previous four digit values.
• Eight digit creditCard.issuerIdNumber inputs are now supported in addition to
  the previously accepted six digit issuerIdNumber. In most cases, you should
  send the last four digits for creditCard.lastDigits. If you send a
  issuerIdNumber 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
  lastDigits:
  • Discover
  • JCB
  • Mastercard
  • UnionPay
  • Visa