9.0.0

• Breaking Dropped support for Node.js 18 and 20. The minimum supported version is
  now 22.
• Breaking Dropped commonjs support. The package is now only available as an ES module.
• Breaking Errors from the web service client are now thrown as
  WebServiceError instances, which extend Error, rather than as plain
  objects. The code, error, status, and url properties are preserved,
  so existing field access continues to work, but the thrown value is now an
  Error. The original error is now preserved as the standard cause
  property (for example, the network error behind a FETCH_ERROR). The
  WebServiceError and ArgumentError classes and the WebServiceClientError
  type are now exported from the package.
• Breaking The WebServiceClient constructor now takes an options object as
  its third argument ({ timeout, host, fetcher }) instead of positional
  timeout and host arguments. For backward compatibility a number may still
  be passed and is treated as the timeout; callers that passed host
  positionally must change to { host }, and passing a fourth positional
  argument now throws an ArgumentError rather than being silently ignored. The
  new fetcher option accepts a custom fetch implementation, useful for
  routing requests through a proxy or custom dispatcher, or for testing. The
  WebServiceClientOptions type is exported from the package.
• The code property on WebServiceError and the WebServiceClientError
  interface is now typed as WebServiceErrorCode
  (ClientErrorCode | (string & {})) instead of string, providing
  autocompletion for the client-generated codes while still accepting any code
  returned by the web service. The ClientErrorCode and WebServiceErrorCode
  types are exported from the package.
• ArgumentError now accepts an optional cause and forwards it to Error.
• customInputs on Transaction may now be provided as a plain object mapping
  keys to values, in addition to an array of CustomInput instances.
• Removed the validator dependency. Email and domain validation now use
  built-in regex helpers, and the order referrer URI is validated with the
  URL constructor (restricted to http/https). Validation of a few
  uncommon email edge cases may differ slightly.
• Fixed a bug where serializing a Transaction (e.g. when sending a request)
  mutated the Billing, Shipping, CreditCard, and Order objects passed
  to it.
• Added the input /device/tracking_token. This is the token generated by
  the Device Tracking Add-on
  for explicit device linking. You may provide this by providing
  trackingToken to Device.
• Added FatZebra to the Processor enum.
• Added CLEAR to the Tag enum for use with the Report Transaction API.

8.3.0

• Added Banquest, SummitPayments, and Yaadpay to the Processor enum.
• Added anonymizer property to the IpAddress interface. This contains
  information about whether the IP address is an anonymous network, including
  confidence score, VPN provider name, and various anonymizer type flags.

8.2.1

• First release via Trusted Publishing.

8.2.0

• Added Securepay to the Processor enum.
• Added CreditApplication, FundTransfer, and SimSwap to the EventType
  enum.
• Added the input /event/party. This is the party submitting the
  transaction. You may provide this by providing party to Event.
• Added the input /payment/method. This is the payment method associated
  with the transaction. You may provide this by providing method to
  Payment.
• Added new response.email.domain outputs:
  • classification - The domain type (business, education, government,
    isp_email).
  • risk - A risk score from 0.01 to 99 associated with the email domain.
  • volume - Activity level for the domain across the minFraud network,
    expressed in sightings per million.
• Added new response.email.domain.visit outputs for low-volume domains:
  • status - Domain status from automated visit (live, dns_error,
    network_error, http_error, parked, pre_development).
  • lastVisitedOn - The date the automated visit was completed.
  • hasRedirect - Whether the domain redirects to another URL.
• Added the status property to WebServiceClientError. This property
  contains the HTTP status code when the error is the result of an HTTP
  response error. Network errors (timeouts, fetch errors) will not have a
  status code.
• Updated @maxmind/geoip2-node to 6.3.0, which includes new anonymizer
  and IP risk outputs.

8.1.0

8.1.0

• Added support for the /billing_phone/matches_postal and
  /shipping_phone/matches_postal outputs. These are available as the
  matchesPostal attributes on response.billingPhone and
  response.shippingPhone.
• Added Cryptomus to the Processor enum.

8.0.0

• Breaking Internal webservice calls now use Node's built-in fetch instead of http. This
  will affect users who are on unsupported versions of Node, specifically Node 17 and below.
• Two new error codes have been added: NETWORK_TIMEOUT and FETCH_ERROR, second of which is returned
  when there's a fetch related error that could not be handled by other errors.
• The minFraud Factors subscores have been deprecated. They will be removed
  in March 2025. Please see our release notes
  for more information.
• Added Epayco to the Processor enum.

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