diff --git a/content/minfraud/api-documentation/requests.md b/content/minfraud/api-documentation/requests.md index 4e2747be1..8be5ea803 100644 --- a/content/minfraud/api-documentation/requests.md +++ b/content/minfraud/api-documentation/requests.md @@ -378,13 +378,13 @@ the end-user who initiated the event. {{}} {{< minfraud-schema-row key="verification_time" type="request" valueType="string" >}} - The most recent date and time a verification of the email address was attempted, if known. The string must be in the [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339) date-time format. The time must not be before 1970-01-01T00:00:00Z or more than two days in the future. For a time outside this range, MaxMind ignores the input and returns a warning. + The date and time of the most recent completed verification of the email address, if known. The value must reflect the verification state as of the time of the event. Use the time the verification succeeded or failed, for example the time the user clicked the link, not the time you sent the link. Do not include this field if no verification was attempted or no verification is complete. The string must be in the [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339) date-time format. The time must not be before 1970-01-01T00:00:00Z or more than two days in the future. For a time outside this range, MaxMind ignores the input and returns a warning. [Learn more about the /email/verification\_time input on our Knowledge Base.](https://support.maxmind.com/knowledge-base/articles/passing-email-inputs-minfraud) {{}} {{< minfraud-schema-row key="was_verification_successful" type="request" valueType="boolean" >}} - Whether the most recent verification that the end user controls this email address was successful (e.g. by confirming a link sent to the email address). `true` if the email verification was successful, or `false` if the user failed email verification. Do not include this field if you have not performed this check. + Whether the most recent completed verification that the end user controls this email address was successful (e.g. by confirming a link sent to the email address). The value must reflect the verification state as of the time of the event. `true` if the email verification was successful, or `false` if the user failed email verification. A pending, abandoned, or expired verification is not complete and is not a failure. If no verification is complete, for example because the user has not clicked the link yet, do not include this field. Do not include this field if you have not performed this check. [Learn more about the /email/was\_verification\_successful input on our Knowledge Base.](https://support.maxmind.com/knowledge-base/articles/passing-email-inputs-minfraud) {{}} @@ -470,7 +470,7 @@ information provided by the end-user who initiated the event. {{< minfraud-schema-row key="phone_verification_method" type="request" valueType="string" valueTypeNote="format: enum" >}} - The method used for the most recent verification attempt of the billing phone number. The valid values are: + The method used for the most recent completed verification of the billing phone number. The value must reflect the verification state as of the time of the event. The valid values are: | Method | Description | | ---------------- | --------------------------------------------------------------------------- | @@ -478,20 +478,20 @@ information provided by the end-user who initiated the event. | `delivered_code` | A one-time code delivered to the phone number by SMS, an automated voice call, or an over-the-top messaging channel such as WhatsApp or RCS, and entered by the user. | | `other` | A method not listed above, such as flash or missed call verification, or a method you do not know because a third party performed the check. | - If you send a value that is not in this list, the service returns an `INPUT_INVALID` warning. Do not include this field if no verification was attempted. + If you send a value that is not in this list, the service returns an `INPUT_INVALID` warning. Do not include this field if no verification was attempted or no verification is complete. [Learn more about the /billing/phone\_verification\_method input on our Knowledge Base.](https://support.maxmind.com/knowledge-base/articles/billing-and-shipping-inputs-minfraud#billing-address) {{}} {{< minfraud-schema-row key="phone_was_verification_successful" type="request" valueType="boolean" >}} - Whether the most recent verification that the end user controls this billing phone number was successful, using the method named in `phone_verification_method`. `true` if the phone verification was successful, or `false` if the user failed phone verification. Do not include this field if you have not performed this check. + Whether the most recent completed verification that the end user controls this billing phone number was successful, using the method named in `phone_verification_method`. The value must reflect the verification state as of the time of the event. `true` if the phone verification was successful, or `false` if the user failed phone verification. A pending, abandoned, or expired verification is not complete and is not a failure. If no verification is complete, for example because the user has not entered the code yet, do not include this field. Do not include this field if you have not performed this check. [Learn more about the /billing/phone\_was\_verification\_successful input on our Knowledge Base.](https://support.maxmind.com/knowledge-base/articles/billing-and-shipping-inputs-minfraud#billing-address) {{}} {{< minfraud-schema-row key="phone_verification_time" type="request" valueType="string" >}} - The most recent date and time a verification of the billing phone number was attempted, if known. The string must be in the [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339) date-time format. The time must not be before 1970-01-01T00:00:00Z or more than two days in the future. For a time outside this range, MaxMind ignores the input and returns a warning. + The date and time of the most recent completed verification of the billing phone number, if known. The value must reflect the verification state as of the time of the event. Use the time the verification succeeded or failed, for example the time the user entered the code, not the time you sent the code. Do not include this field if no verification was attempted or no verification is complete. The string must be in the [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339) date-time format. The time must not be before 1970-01-01T00:00:00Z or more than two days in the future. For a time outside this range, MaxMind ignores the input and returns a warning. [Learn more about the /billing/phone\_verification\_time input on our Knowledge Base.](https://support.maxmind.com/knowledge-base/articles/billing-and-shipping-inputs-minfraud#billing-address) {{}} @@ -578,7 +578,7 @@ information provided by the end-user who initiated the event. {{< minfraud-schema-row key="phone_verification_method" type="request" valueType="string" valueTypeNote="format: enum" >}} - The method used for the most recent verification attempt of the shipping phone number. The valid values are: + The method used for the most recent completed verification of the shipping phone number. The value must reflect the verification state as of the time of the event. The valid values are: | Method | Description | | ---------------- | --------------------------------------------------------------------------- | @@ -586,20 +586,20 @@ information provided by the end-user who initiated the event. | `delivered_code` | A one-time code delivered to the phone number by SMS, an automated voice call, or an over-the-top messaging channel such as WhatsApp or RCS, and entered by the user. | | `other` | A method not listed above, such as flash or missed call verification, or a method you do not know because a third party performed the check. | - If you send a value that is not in this list, the service returns an `INPUT_INVALID` warning. Do not include this field if no verification was attempted. + If you send a value that is not in this list, the service returns an `INPUT_INVALID` warning. Do not include this field if no verification was attempted or no verification is complete. [Learn more about the /shipping/phone\_verification\_method input on our Knowledge Base.](https://support.maxmind.com/knowledge-base/articles/billing-and-shipping-inputs-minfraud#shipping-address) {{}} {{< minfraud-schema-row key="phone_was_verification_successful" type="request" valueType="boolean" >}} - Whether the most recent verification that the end user controls this shipping phone number was successful, using the method named in `phone_verification_method`. `true` if the phone verification was successful, or `false` if the user failed phone verification. Do not include this field if you have not performed this check. + Whether the most recent completed verification that the end user controls this shipping phone number was successful, using the method named in `phone_verification_method`. The value must reflect the verification state as of the time of the event. `true` if the phone verification was successful, or `false` if the user failed phone verification. A pending, abandoned, or expired verification is not complete and is not a failure. If no verification is complete, for example because the user has not entered the code yet, do not include this field. Do not include this field if you have not performed this check. [Learn more about the /shipping/phone\_was\_verification\_successful input on our Knowledge Base.](https://support.maxmind.com/knowledge-base/articles/billing-and-shipping-inputs-minfraud#shipping-address) {{}} {{< minfraud-schema-row key="phone_verification_time" type="request" valueType="string" >}} - The most recent date and time a verification of the shipping phone number was attempted, if known. The string must be in the [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339) date-time format. The time must not be before 1970-01-01T00:00:00Z or more than two days in the future. For a time outside this range, MaxMind ignores the input and returns a warning. + The date and time of the most recent completed verification of the shipping phone number, if known. The value must reflect the verification state as of the time of the event. Use the time the verification succeeded or failed, for example the time the user entered the code, not the time you sent the code. Do not include this field if no verification was attempted or no verification is complete. The string must be in the [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339) date-time format. The time must not be before 1970-01-01T00:00:00Z or more than two days in the future. For a time outside this range, MaxMind ignores the input and returns a warning. [Learn more about the /shipping/phone\_verification\_time input on our Knowledge Base.](https://support.maxmind.com/knowledge-base/articles/billing-and-shipping-inputs-minfraud#shipping-address) {{}} diff --git a/content/minfraud/release-notes/2026-10-15-new-phone-verification-inputs.md b/content/minfraud/release-notes/2026-10-15-new-phone-verification-inputs.md index 9f0794da8..0fd8031ad 100644 --- a/content/minfraud/release-notes/2026-10-15-new-phone-verification-inputs.md +++ b/content/minfraud/release-notes/2026-10-15-new-phone-verification-inputs.md @@ -7,11 +7,11 @@ draft = false We have released new inputs for all minFraud web service customers. They describe the most recent verification of the billing or shipping phone number. -| new input | description | -| -------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `billing/phone_verification_method` | The method used for the most recent verification attempt of the billing phone number: `network`, `delivered_code`, or `other`. [Learn more on our developer portal.](/minfraud/api-documentation/requests/#schema--request--billing__phone_verification_method) | -| `billing/phone_was_verification_successful` | Whether the most recent verification that the end user controls this billing phone number was successful. [Learn more on our developer portal.](/minfraud/api-documentation/requests/#schema--request--billing__phone_was_verification_successful) | -| `billing/phone_verification_time` | The most recent date and time a verification of the billing phone number was attempted, if known. [Learn more on our developer portal.](/minfraud/api-documentation/requests/#schema--request--billing__phone_verification_time) | -| `shipping/phone_verification_method` | The method used for the most recent verification attempt of the shipping phone number: `network`, `delivered_code`, or `other`. [Learn more on our developer portal.](/minfraud/api-documentation/requests/#schema--request--shipping__phone_verification_method) | -| `shipping/phone_was_verification_successful` | Whether the most recent verification that the end user controls this shipping phone number was successful. [Learn more on our developer portal.](/minfraud/api-documentation/requests/#schema--request--shipping__phone_was_verification_successful) | -| `shipping/phone_verification_time` | The most recent date and time a verification of the shipping phone number was attempted, if known. [Learn more on our developer portal.](/minfraud/api-documentation/requests/#schema--request--shipping__phone_verification_time) | +| new input | description | +| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `billing/phone_verification_method` | The method used for the most recent completed verification of the billing phone number: `network`, `delivered_code`, or `other`. [Learn more on our developer portal.](/minfraud/api-documentation/requests/#schema--request--billing__phone_verification_method) | +| `billing/phone_was_verification_successful` | Whether the most recent completed verification that the end user controls this billing phone number was successful. [Learn more on our developer portal.](/minfraud/api-documentation/requests/#schema--request--billing__phone_was_verification_successful) | +| `billing/phone_verification_time` | The date and time of the most recent completed verification of the billing phone number, if known. [Learn more on our developer portal.](/minfraud/api-documentation/requests/#schema--request--billing__phone_verification_time) | +| `shipping/phone_verification_method` | The method used for the most recent completed verification of the shipping phone number: `network`, `delivered_code`, or `other`. [Learn more on our developer portal.](/minfraud/api-documentation/requests/#schema--request--shipping__phone_verification_method) | +| `shipping/phone_was_verification_successful` | Whether the most recent completed verification that the end user controls this shipping phone number was successful. [Learn more on our developer portal.](/minfraud/api-documentation/requests/#schema--request--shipping__phone_was_verification_successful) | +| `shipping/phone_verification_time` | The date and time of the most recent completed verification of the shipping phone number, if known. [Learn more on our developer portal.](/minfraud/api-documentation/requests/#schema--request--shipping__phone_verification_time) | diff --git a/content/minfraud/release-notes/2026-10-26-new-email-verification-inputs.md b/content/minfraud/release-notes/2026-10-26-new-email-verification-inputs.md index 7afa134b6..2258393dc 100644 --- a/content/minfraud/release-notes/2026-10-26-new-email-verification-inputs.md +++ b/content/minfraud/release-notes/2026-10-26-new-email-verification-inputs.md @@ -7,7 +7,7 @@ draft = false We have released new inputs for all minFraud web service customers. They describe the most recent verification of the email address. -| new input | description | -| ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `email/verification_time` | The most recent date and time a verification of the email address was attempted, if known. [Learn more on our developer portal.](/minfraud/api-documentation/requests/#schema--request--email__verification_time) | -| `email/was_verification_successful` | Whether the most recent verification that the end user controls this email address was successful. [Learn more on our developer portal.](/minfraud/api-documentation/requests/#schema--request--email__was_verification_successful) | +| new input | description | +| ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `email/verification_time` | The date and time of the most recent completed verification of the email address, if known. [Learn more on our developer portal.](/minfraud/api-documentation/requests/#schema--request--email__verification_time) | +| `email/was_verification_successful` | Whether the most recent completed verification that the end user controls this email address was successful. [Learn more on our developer portal.](/minfraud/api-documentation/requests/#schema--request--email__was_verification_successful) |