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

v4.3.0

• Added support for the new test disposition action.
• Added support for the /disposition/rule_label output in Score, Insights and
  Factors. This is available at response.disposition.ruleLabel(), and is the
  label of the custom rule that was triggered by the transaction.
• Added support for the /credit_card/was_3d_secure_successful input in Score,
  Insights and Factors. The input should indicate whether or not the outcome of
  3D-Secure verification (e.g. Safekey, SecureCode, Verified by Visa) was
  successful. true if customer verification was successful, or false if the
  customer failed verification. If 3-D Secure verification was not used, was
  unavailable, or resulted in another outcome other than success or failure, do
  not include this field. Use the was3DSecureSuccessful property in a call to
  new minFraud.CreditCard() to set it.

v4.2.0

• Update yarn deps

v4.1.0

• Add Datacap to the Processor enum.
• Upgrade yarn modules

v4.0.1

• Fix: IP address response is optional. Issue 515

v4.0.0

• Breaking Drop Node 10 support
• Upgrade yarn dependencies

v3.4.0

• Add new payment processors eb59e03
• Upgrade yarn dependencies
• Update @maxmind/geoip2-node. The staticIpScore property was incorrectly spelled staticIPScore. This is now fixed.

v3.2.0...v3.4.0