You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/minfraud/release-notes/2025.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ We have released additional inputs and possible input values for all minFraud we
36
36
|`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)|
37
37
|`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)|
38
38
39
-
`event/type/` now supports the additional values below. [View the full list of possible values for `event/type` on our developer portal.](hhttps://dev.maxmind.com/minfraud/api-documentation/requests/#schema--request--event__type)
39
+
`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)
0 commit comments