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

5.0.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.
• 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 PaymentProcessor enum.
• Removed several obsolete constructors as well as the Last4Digits
  property on MaxMind.MinFraud.Request.CreditCard.

4.3.0

• Added PxpFinancial and Trustpay to the PaymentProcessor 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.

4.2.0

• .NET 5.0 has been removed as a target as it has reach its end of life.
  However, if you are using .NET 5.0, the .NET Standard 2.1 target should
  continue working for you.
• .NET 7.0 and .NET 8.0 have been added as a target.
• Added GooglePay, Placetopay, and ShopifyPayments to the
  PaymentProcessor enum.
• Added IWebServiceClient to facilitate mocking of WebServiceClient.
  Pull request by Ian Göbl. GitHub #152.
• Updated MaxMind.GeoIP2 dependency to version that includes the IsAnycast
  property on MaxMind.GeoIP2.Model.Traits. This is true if the IP address
  belongs to an anycast network.
  This is available in minFraud Insights and Factors.

4.1.0

• Added the Country property to MaxMind.MinFraud.Response.CreditCard.
  This is the country where the issuer of the card is located. This may be
  passed instead of IssuerIdNumber if you do not wish to pass partial
  account numbers or if your payment processor does not provide them.

4.0.0

• This library no longer targets .NET 4.6.1.
• .NET 6.0 was added as a target.
• Removed deprecated code, include:
  • The class MaxMind.MinFraud.Response.GeoIP2Country was removed. This was
    a subclass of MaxMind.GeoIP2.Model.Country that added an IsHighRisk
    property. This property was marked obsolete in 2019. Now
    MaxMind.GeoIP2.Model.Country is used directly.
  • In MaxMind.MinFraud.Response.Subscores, the properties EmailTenure
    and IPTenure were removed. These were deprecated in the web service
    and always return a fixed value.

3.3.0

• Upgraded MaxMind.GeoIP2 to 4.1.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.
• Added the following new values to the PaymentProcessor enum:
  • Boacompra
  • Boku
  • Coregateway
  • Fiserv
  • Neopay
  • Neosurf
  • Openbucks
  • Paysera
  • Payvision
  • Trustly
  • Windcave
• The last4Digits constructor parameter and and Last4Digits property of
  MaxMind.MinFraud.Request.CreditCard have been deprecated in favor of
  lastDigits / LastDigits respectively and will be removed in a future
  release. lastDigits / LastDigits also now supports two digit values in
  addition to the previous four digit values.
• Eight digit MaxMind.MinFraud.Request.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
  MaxMind.MinFraud.Request.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

3.2.0

• Added the following new values to the PaymentProcessor enum:
  • Cardknox
  • Creditguard
  • Credorax
  • Datacap
  • Dlocal
  • Onpay
  • Safecharge
• Documented the new "test" disposition.
• Added support for the /disposition/risk_label output in Score, Insights and
  Factors. This is the available as the RiskLabel property of
  MaxMind.MinFraud.Response.Disposition, 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. This input should indicate whether or not the outcome
  of 3-D 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.

3.1.0

• Added ApplePay and ApsPayments to the PaymentProcessor enum.
• Added additional normalizing of the request email address in
  MaxMind.MinFraud.Request.Email when hashAddress is set to true.
• Added support for the IP address risk reasons in the minFraud Insights and
  Factors responses. This is available at response.IPAddress.RiskReasons.
  It is a list of MaxMind.MinFraud.Response.IPRiskReason objects.

3.0.0

• This library now requires .NET Framework 4.6.1 or greater or .NET Standard
  2.0 or greater.
• .NET 5.0 was added as a target framework.
• System.Text.Json is now used for serializing and deserializing JSON.
  If you are serializing the objects yourself, the Newtonsoft.Json
  attributes have been removed and you will need to switch to
  System.Text.Json.
• When creating a Transaction object, you may now use init-only properties
  rather than constructor parameters.
• You may now create WebServiceClient as a typed client with
  IHttpClientFactory in .NET Core 2.1+.
• Exception objects now correctly implement ISerializable.
• The Warnings properties on the response models are now an
  IReadOnlyList<Warning> rather than an IList<Warning>.
• The Names properties on NamedEntity models are now
  IReadOnlyDictionary<string, string>.
• The Subdivisions property on MaxMind.MinFraud.Response.IPAddress is now
  an IReadOnlyList<Subdivision>.
• GeoNameId properties on NamedEntity models are now long? rather than
  int? to match the underlying database.