From 2dc2bbf905a2136f3f203a0c8908a420e84983fd Mon Sep 17 00:00:00 2001 From: William Storey Date: Tue, 3 Nov 2026 21:16:07 +0000 Subject: [PATCH 1/4] Do not report pending verifications as failed The verification result rows did not say what to send while a verification is pending. A merchant could send false for a link that the user has not clicked yet, and minFraud would see a failed check. Define the result as that of the most recent completed verification. A pending, abandoned, or expired verification is not complete and is not a failure. If no verification is complete, leave out the field. The phone method rows described the most recent verification attempt, which can be pending. Make them describe the same completed verification as the result rows, so that a merchant does not send a method from a pending attempt next to a result from an earlier one. Update the release note descriptions to match. Co-Authored-By: Claude Opus 5.5 --- content/minfraud/api-documentation/requests.md | 14 +++++++------- .../2026-10-15-new-phone-verification-inputs.md | 16 ++++++++-------- .../2026-10-26-new-email-verification-inputs.md | 8 ++++---- 3 files changed, 19 insertions(+), 19 deletions(-) diff --git a/content/minfraud/api-documentation/requests.md b/content/minfraud/api-documentation/requests.md index 4e2747be1..75a003a20 100644 --- a/content/minfraud/api-documentation/requests.md +++ b/content/minfraud/api-documentation/requests.md @@ -384,7 +384,7 @@ the end-user who initiated the event. {{}} {{< 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). `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 valid values are: | Method | Description | | ---------------- | --------------------------------------------------------------------------- | @@ -478,14 +478,14 @@ 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`. `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) {{}} @@ -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 valid values are: | Method | Description | | ---------------- | --------------------------------------------------------------------------- | @@ -586,14 +586,14 @@ 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`. `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) {{}} 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..7f640ff7a 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 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 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 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) | 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..dae5d63b1 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 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 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) | From 7d5e79759151b5c5d9641368927ad8d8f3d7157a Mon Sep 17 00:00:00 2001 From: William Storey Date: Tue, 3 Nov 2026 21:16:15 +0000 Subject: [PATCH 2/4] Define verification time as the time of the result "The most recent date and time a verification was attempted" could mean the time the merchant sent the link or code, or the time the user used it. For email, these times can be days apart. Define the time as the time the most recent completed verification succeeded or failed. A pending verification is neutral, so the time a link or code was sent is not a result time. Update the release note descriptions to match. Co-Authored-By: Claude Opus 5.5 --- content/minfraud/api-documentation/requests.md | 6 +++--- .../2026-10-15-new-phone-verification-inputs.md | 4 ++-- .../2026-10-26-new-email-verification-inputs.md | 2 +- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/content/minfraud/api-documentation/requests.md b/content/minfraud/api-documentation/requests.md index 75a003a20..907e491a4 100644 --- a/content/minfraud/api-documentation/requests.md +++ b/content/minfraud/api-documentation/requests.md @@ -378,7 +378,7 @@ 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. Use the time the verification succeeded or failed, for example the time the user clicked the link, not the time you sent the link. 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) {{}} @@ -491,7 +491,7 @@ information provided by the end-user who initiated the event. {{}} {{< 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. Use the time the verification succeeded or failed, for example the time the user entered the code, not the time you sent the code. 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) {{}} @@ -599,7 +599,7 @@ information provided by the end-user who initiated the event. {{}} {{< 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. Use the time the verification succeeded or failed, for example the time the user entered the code, not the time you sent the code. 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 7f640ff7a..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 @@ -11,7 +11,7 @@ describe the most recent verification of the billing or shipping phone number. | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `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 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) | +| `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 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) | +| `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 dae5d63b1..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 @@ -9,5 +9,5 @@ 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/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) | From 9d5875ec343eaa7b9b89ba2ca5dd13e2849845cd Mon Sep 17 00:00:00 2001 From: William Storey Date: Tue, 3 Nov 2026 21:16:23 +0000 Subject: [PATCH 3/4] Describe verification state as of the event time You can score a stored event later with /event/time. The verification rows did not say whether to send the state at the time of the event or at the time of the request. If a merchant sends the current state, the model sees information from after the event. Say that the email and phone verification rows must reflect the state as of the time of the event. Co-Authored-By: Claude Opus 5.5 --- content/minfraud/api-documentation/requests.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/content/minfraud/api-documentation/requests.md b/content/minfraud/api-documentation/requests.md index 907e491a4..e231df85f 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 date and time of the most recent completed verification of the email address, if known. Use the time the verification succeeded or failed, for example the time the user clicked the link, not the time you sent the link. 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. 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 completed 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. 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. + 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 completed verification 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 | | ---------------- | --------------------------------------------------------------------------- | @@ -485,13 +485,13 @@ information provided by the end-user who initiated the event. {{}} {{< minfraud-schema-row key="phone_was_verification_successful" type="request" valueType="boolean" >}} - 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`. `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. + 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 date and time of the most recent completed verification of the billing phone number, if known. Use the time the verification succeeded or failed, for example the time the user entered the code, not the time you sent the code. 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. 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 completed verification 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 | | ---------------- | --------------------------------------------------------------------------- | @@ -593,13 +593,13 @@ information provided by the end-user who initiated the event. {{}} {{< minfraud-schema-row key="phone_was_verification_successful" type="request" valueType="boolean" >}} - 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`. `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. + 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 date and time of the most recent completed verification of the shipping phone number, if known. Use the time the verification succeeded or failed, for example the time the user entered the code, not the time you sent the code. 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. 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) {{}} From 56d0839735a39c3ba87825ee03876ce7507eb131 Mon Sep 17 00:00:00 2001 From: William Storey Date: Tue, 3 Nov 2026 21:16:28 +0000 Subject: [PATCH 4/4] Leave out the verification time if there is none The time rows did not say to leave out the field when no verification was attempted. An integration that always sends a value could send a placeholder such as 1970-01-01T00:00:00Z. The web service accepts it and records a verification that did not occur. Say to leave out the time if no verification was attempted or no verification is complete. Co-Authored-By: Claude Opus 5.5 --- content/minfraud/api-documentation/requests.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/minfraud/api-documentation/requests.md b/content/minfraud/api-documentation/requests.md index e231df85f..8be5ea803 100644 --- a/content/minfraud/api-documentation/requests.md +++ b/content/minfraud/api-documentation/requests.md @@ -378,7 +378,7 @@ the end-user who initiated the event. {{}} {{< minfraud-schema-row key="verification_time" type="request" valueType="string" >}} - 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. 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) {{}} @@ -491,7 +491,7 @@ information provided by the end-user who initiated the event. {{}} {{< minfraud-schema-row key="phone_verification_time" type="request" valueType="string" >}} - 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. 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) {{}} @@ -599,7 +599,7 @@ information provided by the end-user who initiated the event. {{}} {{< minfraud-schema-row key="phone_verification_time" type="request" valueType="string" >}} - 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. 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) {{}}