Merge pull request #1518 from maxmind/andram/minfraud-updates

minfraud release notes are posted

Author: mm-jpoole

content/minfraud/release-notes/2025.md

@@ -9,6 +9,47 @@ outputs: ['html', 'rss']
 [Sign up to be notified](https://comms.maxmind.com/minfraud-rss-release-notes)
 whenever a new minFraud release note is posted. {{</ alert >}}
 
+{{< release-note date="2025-12-18" title="New email domain outputs in the Insights and Factors web services">}}
+
+We have added new fields to the [`email/domain` sub-object](https://dev.maxmind.com/minfraud/api-documentation/responses/#email--domain) in our minFraud Insights and Factors web services. This enhancement provides you with more granular data for risk modeling and workflows, which is especially useful in B2B account opening/onboarding use cases.
+
+These data points will only be returned when you pass the domain or the unhashed email address as an input to the minFraud Insights and Factors web services. [Learn more about domain risk data on our knowledge base.](https://support.maxmind.com/knowledge-base/minfraud-domain-risk-data)
+
+| new output | description |
+| -------------------------------- | -------------------------------- |
+| `email/domain/classification`                       | A classification of the domain such as business or education. [Read the API specifications for domain classification on our developer portal.](https://dev.maxmind.com/minfraud/api-documentation/responses/#schema--response--email--domain__classification) | 
+| `email/domain/risk`                | Contains the risk associated with the domain. [Read the API specifications for domain risk on our developer portal.](https://dev.maxmind.com/minfraud/api-documentation/responses/#schema--response--email--domain__risk) |
+| `email/domain/volume`                | Indicates how much activity we see on an email domain across the minFraud network, expressed in sightings per million. [Read the API specifications for domain volume on our developer portal.](https://dev.maxmind.com/minfraud/api-documentation/responses/#schema--response--email--domain__volume) |
+| `email/domain/first_seen`                | When an email domain was first seen on the minFraud Network. [Read the API specifications for domain tenure tracking on our developer portal.](https://dev.maxmind.com/minfraud/api-documentation/responses#schema--response--email--domain__first_seen) |
+| `email/domain/visit`                | A sub-object of `email/domain` that contains information about an automated visit to the email domain such as whether a website on the domain is live. [Read the API specifications for domain visit on our developer portal.](https://dev.maxmind.com/minfraud/api-documentation/responses/#email--domain--visit) |
+
+[Client APIs](https://dev.maxmind.com/minfraud/evaluate-a-transaction#links-to-maxmind-client-apis) have been updated to reflect this change. 
+
+{{</ release-note >}}
+
+{{< release-note date="2025-12-18" title="Expanded event type inputs, and new payment method and event party inputs">}}
+
+We have released additional inputs and possible input values for all minFraud web service customers. 
+
+| new input | description |
+| -------------------------------- | -------------------------------- |
+| `payment/method`                       | The payment method associated with the transaction. [View possible values on our developer portal.](https://dev.maxmind.com/minfraud/api-documentation/requests/#schema--request--payment__method) | 
+| `event/party`                | The party submitting the transaction. Either `agent` or `customer`. This input can help reduce false positive potential in cases where an agent is submitting transactions on behalf of customers. [Learn more on our developer portal.](https://dev.maxmind.com/minfraud/api-documentation/requests/#schema--request--event__party) |
+
+`event/type` now supports the additional values below. [View the full list of possible values for `event/type` on our developer portal.](https://dev.maxmind.com/minfraud/api-documentation/requests/#schema--request--event__type)
+
+| additional input | description |
+| -------------------------------- | -------------------------------- |
+| `credit_application`                       | The transactor is attempting to submit an application for credit.| 
+| `fund_transfer`                | The transactor is attempting to transfer funds from one account to another. |
+| `sim_swap`                | For mobile network operators. A new SIM card or eSIM is being issued to activate service on a customer’s existing phone number. |
+
+Passing the additional inputs above can help us improve our risk scoring accuracy for you by increasing the context available to our machine learning models and heuristics.
+
+Our [client APIs](https://dev.maxmind.com/minfraud/evaluate-a-transaction#links-to-maxmind-client-apis) have been updated to support these inputs so you may need to refresh yours to submit them in your minFraud requests if you are not interfacing directly with our REST API.
+
+{{</ release-note >}}
+
 {{< release-note date="2025-12-17" title="Subdivision, city, and postal fields blanked in additional countries">}}
 
 Effective tomorrow, Thursday, December 18, 2025, we will be blanking out the subdivision, city, and postal fields more often in the following countries. This change will result in fewer resolutions in: