2.0.0

• Java 11 or greater is now required.
• Apache HttpClient has been replaced with java.net.http.HttpClient.
• The close() method on WebServiceClient is now deprecated. It
  no longer does anything.
• On WebServiceClient.Builder:
  • connectTimeout(int) has been deprecated in favor of
    connectTimeout(Duration).
  • readTimeout(int) has been deprecated in favor of
    requestTimeout(Duration).
  • proxy(Proxy) has been deprecated in favor of proxy(ProxySelector).
• On HttpException and InvalidRequestException, getUrl() has been
  deprecated in favor of getUri(). Constructors that took a URL have
  been replaced with the equivalent taking a URI.
• Deprecated constructors on model classes were removed.
• Removed deprecated response methods:
  • Email.getAddressMd5()
  • Subscores.getEmailTenure()
  • Subscores.getIpTenure()
• Removed GeoIp2Country and its associated isHighRisk() method.
  IpAddress.getCountry() now returns a com.maxmind.geoip2.record.Country.
• Removed deprecated Payment.Processor.VERAPAY enum value. Use VEREPAY
  instead.
• Email.getDomain() will now return an empty object rather than null if
  there is no domain data. This is match other response model class getters.
• Upgraded the geoip2 dependency to 2.16.1. This adds mobile country code
  (MCC) and mobile network code (MNC) to minFraud Insights and Factors
  responses. These are available at
  response.getIpAddress.getTraits.getMobileCountryCode() and
  response.getIpAddress.getTraits.getMobileNetworkCode(). We expect this
  data to be available by late January 2022.
• The following payment processors were added to the Payment.Processor enum:
  • BOACOMPRA
  • BOKU
  • COREGATEWAY
  • FISERV
  • NEOPAY
  • NEOSURF
  • OPENBUCKS
  • PAYSERA
  • PAYVISION
  • TRUSTLY
  • WINDCAVE
• com.maxmind.minfraud.request.CreditCard.last4Digits has been deprecated in
  favor of 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 com.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
  com.maxmind.minfraud.request.CreditCard.last4Digits. 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
• Apache Commons Codec is no longer used for generating MD5s.

1.18.0

• The following payment processors were added to the Payment.Processor enum:
  • CARDKNOX
  • CREDITGUARD
  • CREDORAX
  • DATACAP
  • DLOCAL
  • ONPAY
  • SAFECHARGE
• Documented the new test disposition action.
• Added support for the /disposition/rule_label output in Score, Insights and
  Factors. This is available at response.getDisposition().getRuleLabel(), 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
  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(Boolean) method on
  com.maxmind.minfraud.request.CreditCard.Builder to set it.

1.17.0

• The following payment processors were added to the Payment.Processor enum:
  • APPLE_PAY
  • APS_PAYMENTS
• Added additional normalizing of the email address if hashAddress is
  enabled.
• Added support for the IP address risk reasons in the minFraud Insights and
  Factors responses. This is available at response.getIpAddress().getRiskReasons().
  It is a list of IpRiskReason objects.

1.16.0

• The HTTP client now allows up to 20 connections to be active at once.
  Previously the limit was 2. Reported by mjancewicz. GitHub #110.
• TSYS was added to the Payment.Processor enum.
• The device IP address is no longer a required input.

1.15.0

• The following payment processors were added to the Payment.Processor enum:
  • CASHFREE
  • FIRST_ATLANTIC_COMMERCE
  • KOMOJU
  • PAYTM
  • RAZORPAY
  • SYSTEMPAY
• Added support for three new Factors outputs: /subscores/device (the risk
  associated with the device), /subscores/email_local_part (the risk
  associated with the part of the email address before the @ symbol) and
  /subscores/shipping_address (the risk associated with the shipping
  address).

1.14.0

• Added support for Report Transaction API. Report Transaction requests can be
  created via TransactionReport.Builder().
• Updated Jackson dependencies to 2.11.0.

1.13.0

• Added support for the new credit card output /credit_card/is_business.
  This indicates whether the card is a business card. It may be accessed via
  response.getCreditCard().isBusiness() on the minFraud Insights and Factors
  response objects.

1.12.0

• Added support for the new email output /email/domain/first_seen This can
  be accessed via response.getEmail().getDomain().getFirstSeen().
• Added Device.getLastSeenDateTime(), Device.getLocalDateTime(),
  Email.getFirstSeenDate(), and GeoIp2Location.getLocalDateTime() methods
  that return java.time objects rather than strings.
• The request event time is now stored internally as a ZonedDateTime. An
  Event.Builder.time(ZonedDateTime) method was also added to the event
  builder.
• The following payment processors were added to the Payment.Processor enum:
  • CARDPAY
  • EPX

1.11.0

• Added support for the new email output /email/is_disposable. This can
  be accessed via the isDisposable() method on the Email response
  object.

1.10.0

• IMPORTANT: Java 8 is now required. If you need Java 7 support, please
  continue using 1.9.0.
• Added constructor to com.maxmind.minfraud.request.Email.Builder that
  allows validation to be disabled.
• The client-side validation for numeric custom inputs has been updated to
  match the server-side validation. The valid range is -9,999,999,999,999
  to 9,999,999,999,999. Previously, larger numbers were allowed.
• Responses with chunked encoding are now handled correctly.
• The following payment processors were added to the Payment.Processor enum:
  • AFFIRM
  • AFTERPAY
  • CETELEM
  • DATACASH
  • DOTPAY
  • ECOMMPAY
  • G2A_PAY
  • GOCARDLESS
  • INTERAC
  • KLARNA
  • MERCANET
  • PAYEEZY
  • PAYLIKE
  • PAYMENT_EXPRESS
  • PAYSAFECARD
  • SMARTDEBIT
  • SYNAPSEFI
  • VEREPAY
• Deprecated VERAPAY in the Payment.Processor enum. This was a misspelling
  of VEREPAY.
• Deprecated getEmailTenure() and getIpTenure() methods of
  com.maxmind.minfraud.response.Subscores.
• Deprecated the isHighRisk() method of com.maxmind.minfraud.response.GeoIP2Country.