--- title: "Retry an Identity Verification" method: POST path: "/identity_verification/retry" tags: ["plaid"] --- # Retry an Identity Verification `POST /identity_verification/retry` Allow a customer to retry their Identity Verification ## Request body - IdentityVerificationRetryRequest — Request input for retrying an identity verification attempt - `client_user_id` string, required — A unique ID that identifies the end user in your system. Either a `user_id` or the `client_user_id` must be provided. This ID can also be used to associate user-specific data from other Plaid products. Financial Account Matching requires this field and the `/link/token/create` `client_user_id` to be consistent. Personally identifiable information, such as an email address or phone number, should not be used in the `client_user_id`. - `template_id` string, required — ID of the associated Identity Verification template. Like all Plaid identifiers, this is case-sensitive. - `strategy` 'reset' | 'incomplete' | 'infer' | 'custom', required — An instruction specifying what steps the new Identity Verification attempt should require the user to complete: `reset` - Restart the user at the beginning of the session, regardless of whether they successfully completed part of their previous session. `incomplete` - Start the new session at the step that the user failed in the previous session, skipping steps that have already been successfully completed. `infer` - If the most recent Identity Verification attempt associated with the given `client_user_id` has a status of `failed` or `expired`, retry using the `incomplete` strategy. Otherwise, use the `reset` strategy. `custom` - Start the new session with a custom configuration, specified by the value of the `steps` field Note: The `incomplete` strategy cannot be applied if the session's failing step is `watchlist_screening` or `risk_check`. The `infer` strategy cannot be applied if the session's status is still `active` - `user` IdentityVerificationRequestUser, nullable — User information collected outside of Link, most likely via your own onboarding process. Each of the following identity fields are optional: `email_address` `phone_number` `date_of_birth` `name` `address` `id_number` Specifically, these fields are optional in that they can either be fully provided (satisfying every required field in their subschema) or omitted from the request entirely by not providing the key or value. Providing these fields via the API will result in Link skipping the data collection process for the associated user. All verification steps enabled in the associated Identity Verification Template will still be run. Verification steps will either be run immediately, or once the user completes the `accept_tos` step, depending on the value provided to the `gave_consent` field. - `email_address` string, email — A valid email address. Must not have leading or trailing spaces and address must be RFC compliant. For more information, see [RFC 3696](https://datatracker.ietf.org/doc/html/rfc3696). - `phone_number` string, nullable — A valid phone number in E.164 format. - `date_of_birth` string, date — A date in the format YYYY-MM-DD (RFC 3339 Section 5.6). - `name` IdentityVerificationRequestUserName, nullable — You can use this field to pre-populate the user's legal name; if it is provided here, they will not be prompted to enter their name in the identity verification attempt. - `given_name` string, required — A string with at least one non-whitespace character, with a max length of 100 characters. - `family_name` string, required — A string with at least one non-whitespace character, with a max length of 100 characters. - `address` UserAddress, nullable — Home address for the user. Supported values are: not provided, address with only country code or full address. For more context on this field, see [Input Validation by Country](https://plaid.com/docs/identity-verification/hybrid-input-validation/#input-validation-by-country). - `street` string, nullable — The primary street portion of an address. If an address is provided, this field will always be filled. A string with at least one non-whitespace alphabetical character, with a max length of 80 characters. - `street2` string, nullable — Extra street information, like an apartment or suite number. If provided, a string with at least one non-whitespace character, with a max length of 50 characters. - `city` string, nullable — City from the address. A string with at least one non-whitespace alphabetical character, with a max length of 100 characters. - `region` string, nullable — A subdivision code. "Subdivision" is a generic term for "state", "province", "prefecture", "zone", etc. For the list of valid codes, see [country subdivision codes](https://plaid.com/documents/country_subdivision_codes.json). Country prefixes are omitted, since they are inferred from the `country` field. - `postal_code` string, nullable — The postal code for the associated address. Between 2 and 10 alphanumeric characters. For US-based addresses this must be 5 numeric digits. - `country` string, required — Valid, capitalized, two-letter ISO code representing the country of this object. Must be in ISO 3166-1 alpha-2 form. - `id_number` UserIDNumber, nullable — ID number submitted by the user, currently used only for the Identity Verification product. If the user has not submitted this data yet, this field will be `null`. Otherwise, both fields are guaranteed to be filled. - `value` string, required — Value of the identity document typed in by the user. Alpha-numeric, with all formatting characters stripped. For specific format requirements by ID type, see [Input Validation Rules](https://plaid.com/docs/identity-verification/hybrid-input-validation/#id-numbers). - `type` 'ar_dni' | 'au_drivers_license' | 'au_passport' | 'br_cpf' | 'ca_sin' | 'cl_run' | 'cn_resident_card' | 'co_nit' | 'dk_cpr' | 'eg_national_id' | 'es_dni' | 'es_nie' | 'hk_hkid' | 'in_pan' | 'in_epic' | 'it_cf' | 'jo_civil_id' | 'jp_my_number' | 'ke_huduma_namba' | 'kw_civil_id' | 'mx_curp' | 'mx_rfc' | 'my_nric' | 'ng_nin' | 'nz_drivers_license' | 'om_civil_id' | 'ph_psn' | 'pl_pesel' | 'ro_cnp' | 'sa_national_id' | 'se_pin' | 'sg_nric' | 'tr_tc_kimlik' | 'us_ssn' | 'us_ssn_last_4' | 'za_smart_id', required — A globally unique and human readable ID type, specific to the country and document category. For more context on this field, see [Input Validation Rules](https://plaid.com/docs/identity-verification/hybrid-input-validation/#id-numbers). - `steps` IdentityVerificationRetryRequestStepsObject, nullable — Instructions for the `custom` retry strategy specifying which steps should be required or skipped. Note: This field must be provided when the retry strategy is `custom` and must be omitted otherwise. Custom retries override settings in your Plaid Template. For example, if your Plaid Template has `verify_sms` disabled, a custom retry with `verify_sms` enabled will still require the step. The `selfie_check` step is currently not supported on the sandbox server. Sandbox requests will silently disable the `selfie_check` step when provided. - `verify_sms` boolean, required — A boolean field specifying whether the new session should require or skip the `verify_sms` step. - `kyc_check` boolean, required — A boolean field specifying whether the new session should require or skip the `kyc_check` (Data Source Verification) step. - `documentary_verification` boolean, required — A boolean field specifying whether the new session should require or skip the `documentary_verification` step. - `selfie_check` boolean, required — A boolean field specifying whether the new session should require or skip the `selfie_check` step. If a previous session has already passed the `selfie_check` step, the new selfie check will be a Selfie Reauthentication check, in which the selfie is tested for liveness and for consistency with the previous selfie. - `is_shareable` boolean, nullable — A flag specifying whether you would like Plaid to expose a shareable URL for the verification being retried. If a value for this flag is not specified, the `is_shareable` setting from the original verification attempt will be used. - `client_id` string — Your Plaid API `client_id`. The `client_id` is required and may be provided either in the `PLAID-CLIENT-ID` header or as part of a request body. - `secret` string — Your Plaid API `secret`. The `secret` is required and may be provided either in the `PLAID-SECRET` header or as part of a request body. ## Response `200` OK - IdentityVerificationRetryResponse — An identity verification attempt represents a customer's attempt to verify their identity, reflecting the required steps for completing the session, the results for each step, and information collected in the process. - `id` string, required — ID of the associated Identity Verification attempt. - `client_user_id` string, required — A unique ID that identifies the end user in your system. Either a `user_id` or the `client_user_id` must be provided. This ID can also be used to associate user-specific data from other Plaid products. Financial Account Matching requires this field and the `/link/token/create` `client_user_id` to be consistent. Personally identifiable information, such as an email address or phone number, should not be used in the `client_user_id`. - `created_at` string, date-time, required — An ISO8601 formatted timestamp. - `completed_at` string, date-time, nullable, required — An ISO8601 formatted timestamp. - `previous_attempt_id` string, nullable, required — The ID for the Identity Verification preceding this session. This field will only be filled if the current Identity Verification is a retry of a previous attempt. - `shareable_url` string, nullable, required — A shareable URL that can be sent directly to the user to complete verification - `template` IdentityVerificationTemplateReference, required — The resource ID and version number of the template configuring the behavior of a given Identity Verification. - `id` string, required — ID of the associated Identity Verification template. Like all Plaid identifiers, this is case-sensitive. - `version` integer, required — Version of the associated Identity Verification template. - `user` IdentityVerificationUserData, required — The identity data that was either collected from the user or provided via API in order to perform an Identity Verification. - `phone_number` string, nullable — A valid phone number in E.164 format. - `date_of_birth` string, date, nullable, required — A date in the format YYYY-MM-DD (RFC 3339 Section 5.6). - `ip_address` string, nullable, required — An IPv4 or IPv6 address. - `email_address` string, email, nullable, required — A valid email address. Must not have leading or trailing spaces and address must be RFC compliant. For more information, see [RFC 3696](https://datatracker.ietf.org/doc/html/rfc3696). - `name` IdentityVerificationResponseUserName, nullable, required — The full name provided by the user. If the user has not submitted their name, this field will be null. Otherwise, both fields are guaranteed to be filled. - `given_name` string, required — A string with at least one non-whitespace character, with a max length of 100 characters. - `family_name` string, required — A string with at least one non-whitespace character, with a max length of 100 characters. - `address` IdentityVerificationUserAddress, nullable, required — Even if an address has been collected, some fields may be null depending on the region's addressing system. For example: Addresses from the United Kingdom will not include a region Addresses from Hong Kong will not include postal code - `street` string, nullable, required — The primary street portion of an address. If an address is provided, this field will always be filled. A string with at least one non-whitespace alphabetical character, with a max length of 80 characters. - `street2` string, nullable, required — Extra street information, like an apartment or suite number. If provided, a string with at least one non-whitespace character, with a max length of 50 characters. - `city` string, nullable, required — City from the address. A string with at least one non-whitespace alphabetical character, with a max length of 100 characters. - `region` string, nullable, required — A subdivision code. "Subdivision" is a generic term for "state", "province", "prefecture", "zone", etc. For the list of valid codes, see [country subdivision codes](https://plaid.com/documents/country_subdivision_codes.json). Country prefixes are omitted, since they are inferred from the `country` field. - `postal_code` string, nullable, required — The postal code for the associated address. Between 2 and 10 alphanumeric characters. For US-based addresses this must be 5 numeric digits. - `country` string, required — Valid, capitalized, two-letter ISO code representing the country of this object. Must be in ISO 3166-1 alpha-2 form. - `id_number` UserIDNumber, nullable, required — ID number submitted by the user, currently used only for the Identity Verification product. If the user has not submitted this data yet, this field will be `null`. Otherwise, both fields are guaranteed to be filled. - `value` string, required — Value of the identity document typed in by the user. Alpha-numeric, with all formatting characters stripped. For specific format requirements by ID type, see [Input Validation Rules](https://plaid.com/docs/identity-verification/hybrid-input-validation/#id-numbers). - `type` 'ar_dni' | 'au_drivers_license' | 'au_passport' | 'br_cpf' | 'ca_sin' | 'cl_run' | 'cn_resident_card' | 'co_nit' | 'dk_cpr' | 'eg_national_id' | 'es_dni' | 'es_nie' | 'hk_hkid' | 'in_pan' | 'in_epic' | 'it_cf' | 'jo_civil_id' | 'jp_my_number' | 'ke_huduma_namba' | 'kw_civil_id' | 'mx_curp' | 'mx_rfc' | 'my_nric' | 'ng_nin' | 'nz_drivers_license' | 'om_civil_id' | 'ph_psn' | 'pl_pesel' | 'ro_cnp' | 'sa_national_id' | 'se_pin' | 'sg_nric' | 'tr_tc_kimlik' | 'us_ssn' | 'us_ssn_last_4' | 'za_smart_id', required — A globally unique and human readable ID type, specific to the country and document category. For more context on this field, see [Input Validation Rules](https://plaid.com/docs/identity-verification/hybrid-input-validation/#id-numbers). - `status` 'active' | 'success' | 'failed' | 'expired' | 'canceled' | 'pending_review', required — The status of this Identity Verification attempt. `active` - The Identity Verification attempt is incomplete. The user may have completed part of the session, but has neither failed nor passed. `success` - The Identity Verification attempt has completed, passing all steps defined to the associated Identity Verification template. `failed` - The user failed one or more steps in the session and was told to contact support. `expired` - The Identity Verification attempt was active for a long period of time without being completed and was automatically marked as expired. Note that sessions currently do not expire. Automatic expiration is expected to be enabled in the future. `canceled` - The Identity Verification attempt was canceled, either via the dashboard by a user, or via API. The user may have completed part of the session, but has neither failed nor passed. `pending_review` - The Identity Verification attempt template was configured to perform a screening that had one or more hits needing review. - `steps` IdentityVerificationStepSummary, required — Each step will be one of the following values: `active` - This step is the user's current step. They are either in the process of completing this step, or they recently closed their Identity Verification attempt while in the middle of this step. Only one step will be marked as `active` at any given point. `success` - The Identity Verification attempt has completed this step. `failed` - The user failed this step. This can either cause the user to fail the session as a whole, or cause them to fall back to another step depending on how the Identity Verification template is configured. A failed step does not imply a failed session. `waiting_for_prerequisite` - The user needs to complete another step first, before they progress to this step. This step may never run, depending on if the user fails an earlier step or if the step is only run as a fallback. `not_applicable` - This step will not be run for this session. `skipped` - The retry instructions that created this Identity Verification attempt specified that this step should be skipped. `expired` - This step had not yet been completed when the Identity Verification attempt as a whole expired. `canceled` - The Identity Verification attempt was canceled before the user completed this step. `pending_review` - The Identity Verification attempt template was configured to perform a screening that had one or more hits needing review. `manually_approved` - The step was manually overridden to pass by a team member in the dashboard. `manually_rejected` - The step was manually overridden to fail by a team member in the dashboard. - `accept_tos` 'success' | 'active' | 'failed' | 'waiting_for_prerequisite' | 'not_applicable' | 'skipped' | 'expired' | 'canceled' | 'pending_review' | 'manually_approved' | 'manually_rejected', required — The status of a step in the Identity Verification process. - `verify_sms` 'success' | 'active' | 'failed' | 'waiting_for_prerequisite' | 'not_applicable' | 'skipped' | 'expired' | 'canceled' | 'pending_review' | 'manually_approved' | 'manually_rejected', required — The status of a step in the Identity Verification process. - `kyc_check` 'success' | 'active' | 'failed' | 'waiting_for_prerequisite' | 'not_applicable' | 'skipped' | 'expired' | 'canceled' | 'pending_review' | 'manually_approved' | 'manually_rejected', required — The status of a step in the Identity Verification process. - `documentary_verification` 'success' | 'active' | 'failed' | 'waiting_for_prerequisite' | 'not_applicable' | 'skipped' | 'expired' | 'canceled' | 'pending_review' | 'manually_approved' | 'manually_rejected', required — The status of a step in the Identity Verification process. - `selfie_check` 'success' | 'active' | 'failed' | 'waiting_for_prerequisite' | 'not_applicable' | 'skipped' | 'expired' | 'canceled' | 'pending_review' | 'manually_approved' | 'manually_rejected', required — The status of a step in the Identity Verification process. - `watchlist_screening` 'success' | 'active' | 'failed' | 'waiting_for_prerequisite' | 'not_applicable' | 'skipped' | 'expired' | 'canceled' | 'pending_review' | 'manually_approved' | 'manually_rejected', required — The status of a step in the Identity Verification process. - `risk_check` 'success' | 'active' | 'failed' | 'waiting_for_prerequisite' | 'not_applicable' | 'skipped' | 'expired' | 'canceled' | 'pending_review' | 'manually_approved' | 'manually_rejected', required — The status of a step in the Identity Verification process. - `documentary_verification` DocumentaryVerification, nullable, required — Data, images, analysis, and results from the `documentary_verification` step. This field will be `null` unless `steps.documentary_verification` has reached a terminal state of either `success` or `failed`. - `status` string, required — The outcome status for the associated Identity Verification attempt's `documentary_verification` step. This field will always have the same value as `steps.documentary_verification`. - `documents` DocumentaryVerificationDocument[], required — An array of documents submitted to the `documentary_verification` step. Each entry represents one user submission, where each submission will contain both a front and back image, or just a front image, depending on the document type. Note: Plaid will automatically let a user submit a new set of document images up to three times if we detect that a previous attempt might have failed due to user error. For example, if the first set of document images are blurry or obscured by glare, the user will be asked to capture their documents again, resulting in at least two separate entries within `documents`. If the overall `documentary_verification` is `failed`, the user has exhausted their retry attempts. - `status` 'success' | 'failed' | 'manually_approved', required — An outcome status for this specific document submission. Distinct from the overall `documentary_verification.status` that summarizes the verification outcome from one or more documents. - `attempt` integer, required — The `attempt` field begins with 1 and increments with each subsequent document upload. - `images` PhysicalDocumentImages, required — URLs for downloading original and cropped images for this document submission. The URLs are designed to only allow downloading, not hot linking, so the URL will only serve the document image for 60 seconds before expiring. The expiration time is 60 seconds after the `GET` request for the associated Identity Verification attempt. A new expiring URL is generated with each request, so you can always rerequest the Identity Verification attempt if one of your URLs expires. - `original_front` string, nullable, required — Temporary URL that expires after 60 seconds for downloading the uncropped original image of the front of the document. - `original_back` string, nullable, required — Temporary URL that expires after 60 seconds for downloading the original image of the back of the document. Might be null if the back of the document was not collected. - `cropped_front` string, nullable, required — Temporary URL that expires after 60 seconds for downloading a cropped image containing just the front of the document. - `cropped_back` string, nullable, required — Temporary URL that expires after 60 seconds for downloading a cropped image containing just the back of the document. Might be null if the back of the document was not collected. - `face` string, nullable, required — Temporary URL that expires after 60 seconds for downloading a crop of just the user's face from the document image. Might be null if the document does not contain a face photo. - `extracted_data` PhysicalDocumentExtractedData, nullable, required — Data extracted from a user-submitted document. - `id_number` string, nullable, required — Alpha-numeric ID number extracted via OCR from the user's document image. - `category` 'drivers_license' | 'id_card' | 'passport' | 'residence_permit_card' | 'resident_card' | 'visa', required — The type of identity document detected in the images provided. Will always be one of the following values: `drivers_license` - A driver's license issued by the associated country, establishing identity without any guarantee as to citizenship, and granting driving privileges `id_card` - A general national identification card, distinct from driver's licenses as it only establishes identity `passport` - A travel passport issued by the associated country for one of its citizens `residence_permit_card` - An identity document issued by the associated country permitting a foreign citizen to temporarily reside there `resident_card` - An identity document issued by the associated country permitting a foreign citizen to permanently reside there `visa` - An identity document issued by the associated country permitting a foreign citizen entry for a short duration and for a specific purpose, typically no longer than 6 months Note: This value may be different from the ID type that the user selects within Link. For example, if they select "Driver's License" but then submit a picture of a passport, this field will say `passport` - `expiration_date` string, date, nullable, required — The expiration date of the document in the format YYYY-MM-DD (RFC 3339 Section 5.6). - `issue_date` string, date, nullable, required — The issue date of the document in the format YYYY-MM-DD (RFC 3339 Section 5.6). - `issuing_country` string, required — Valid, capitalized, two-letter ISO code representing the country of this object. Must be in ISO 3166-1 alpha-2 form. - `issuing_region` string, nullable, required — A subdivision code. "Subdivision" is a generic term for "state", "province", "prefecture", "zone", etc. For the list of valid codes, see [country subdivision codes](https://plaid.com/documents/country_subdivision_codes.json). Country prefixes are omitted, since they are inferred from the `country` field. - `date_of_birth` string, date, nullable, required — A date extracted from the document in the format YYYY-MM-DD (RFC 3339 Section 5.6). - `address` IdentityVerificationDocumentAddressResponse, nullable, required — The address extracted from the document. The address must at least contain the following fields to be a valid address: `street`, `city`, `country`. If any are missing or unable to be extracted, the address will be null. `region`, and `postal_code` may be null based on the addressing system. For example: Addresses from the United Kingdom will not include a region Addresses from Hong Kong will not include postal code Note: Optical Character Recognition (OCR) technology may sometimes extract incorrect data from a document. - `street` string, required — The full street address extracted from the document. - `city` string, required — City extracted from the document. - `region` string, nullable, required — A subdivision code extracted from the document. Related terms would be "state", "province", "prefecture", "zone", "subdivision", etc. For a full list of valid codes, see [country subdivision codes](https://plaid.com/documents/country_subdivision_codes.json). Country prefixes are omitted, since they can be inferred from the `country` field. - `postal_code` string, nullable, required — The postal code extracted from the document. Between 2 and 10 alphanumeric characters. For US-based addresses this must be 5 numeric digits. - `country` string, required — Valid, capitalized, two-letter ISO code representing the country extracted from the document. Must be in ISO 3166-1 alpha-2 form. - `name` IdentityVerificationDocumentNameResponse, nullable — The individual's name extracted from the document. - `given_name` string, required — A string with at least one non-whitespace character, with a max length of 100 characters. - `family_name` string, required — A string with at least one non-whitespace character, with a max length of 100 characters. - `analysis` DocumentAnalysis, required — High level descriptions of how the associated document was processed. If a document fails verification, the details in the `analysis` object should help clarify why the document was rejected. - `authenticity` 'match' | 'partial_match' | 'no_match' | 'no_data', required — High level summary of whether the document in the provided image matches the formatting rules and security checks for the associated jurisdiction. For example, most identity documents have formatting rules like the following: The image of the person's face must have a certain contrast in order to highlight skin tone The subject in the document's image must remove eye glasses and pose in a certain way The informational fields (name, date of birth, ID number, etc.) must be colored and aligned according to specific rules Security features like watermarks and background patterns must be present So a `match` status for this field indicates that the document in the provided image seems to conform to the various formatting and security rules associated with the detected document. - `image_quality` 'high' | 'medium' | 'low', required — A high level description of the quality of the image the user submitted. For example, an image that is blurry, distorted by glare from a nearby light source, or improperly framed might be marked as low or medium quality. Poor quality images are more likely to fail OCR and/or template conformity checks. Note: By default, Plaid will let a user recapture document images twice before failing the entire session if we attribute the failure to low image quality. - `extracted_data` PhysicalDocumentExtractedDataAnalysis, nullable, required — Analysis of the data extracted from the submitted document. - `name` 'match' | 'partial_match' | 'no_match' | 'no_data', required — A match summary describing the cross comparison between the subject's name, extracted from the document image, and the name they separately provided to the identity verification attempt. - `date_of_birth` 'match' | 'partial_match' | 'no_match' | 'no_data', required — A match summary describing the cross comparison between the subject's date of birth, extracted from the document image, and the date of birth they separately provided to the identity verification attempt. - `expiration_date` 'not_expired' | 'expired' | 'no_data', required — A description of whether the associated document was expired when the verification was performed. Note: In the case where an expiration date is not present on the document or failed to be extracted, this value will be `no_data`. - `issuing_country` 'match' | 'no_match', required — A binary match indicator specifying whether the country that issued the provided document matches the country that the user separately provided to Plaid. Note: You can configure whether a `no_match` on `issuing_country` fails the `documentary_verification` by editing your Plaid Template. - `fraud_analysis_details` FraudAnalysisDetails, nullable, required — Details about the fraud analysis performed on the document. - `type_supported` 'success' | 'failed', required — The outcome of the fraud check. `success` - The check passed. `failed` - The check did not pass. - `portrait_presence_check` 'success' | 'failed', required — The outcome of the fraud check. `success` - The check passed. `failed` - The check did not pass. - `portrait_details_check` 'success' | 'failed', required — The outcome of the fraud check. `success` - The check passed. `failed` - The check did not pass. - `image_composition_check` 'success' | 'failed', required — The outcome of the fraud check. `success` - The check passed. `failed` - The check did not pass. - `integrity_check` 'success' | 'failed', required — The outcome of the fraud check. `success` - The check passed. `failed` - The check did not pass. - `detail_check` 'success' | 'failed', required — The outcome of the fraud check. `success` - The check passed. `failed` - The check did not pass. - `issue_date_check` 'success' | 'failed' | 'no_data', required — The outcome of the fraud check. `success` - The check passed. `failed` - The check did not pass. `no_data` - The check could not be performed due to insufficient data. - `image_quality_details` ImageQualityDetails, nullable, required — Details about the image quality of the document. - `glare_check` 'success' | 'failed', required — The outcome of the image quality check. `success` - The check passed. `failed` - The check did not pass. - `dimensions_check` 'success' | 'failed', required — The outcome of the image quality check. `success` - The check passed. `failed` - The check did not pass. - `blur_check` 'success' | 'failed', required — The outcome of the image quality check. `success` - The check passed. `failed` - The check did not pass. - `human_review` HumanReview, nullable — Details about the human review check, which refers to a check that is performed by a document specialist. - `status` 'success' | 'failed' | 'no_data', required — The outcome of the human review check, when available. The following values are possible: `success` - The document passed the check. `failed` - The document failed the check. `no_data` - The document was submitted, but the document specialist review was not completed in time. - `aamva_verification` AAMVAAnalysis, nullable, required — Analyzed AAMVA data for the associated hit. Note: This field is only available for U.S. driver's licenses issued by participating states. - `is_verified` boolean, required — The overall outcome of checking the associated hit against the issuing state database. - `id_number` 'match' | 'no_match' | 'no_data', required — The outcome of checking the particular field against state databases. `match` - The field is an exact match with the state database. `no_match` - The field is not an exact match with the state database. `no_data` - The field was unable to be checked against state databases. - `id_issue_date` 'match' | 'no_match' | 'no_data', required — The outcome of checking the particular field against state databases. `match` - The field is an exact match with the state database. `no_match` - The field is not an exact match with the state database. `no_data` - The field was unable to be checked against state databases. - `id_expiration_date` 'match' | 'no_match' | 'no_data', required — The outcome of checking the particular field against state databases. `match` - The field is an exact match with the state database. `no_match` - The field is not an exact match with the state database. `no_data` - The field was unable to be checked against state databases. - `street` 'match' | 'partial_match' | 'no_match' | 'no_data', required — The outcome of checking the associated hit against state databases. `match` - The field is an exact match with the state database. `partial_match` - The field is a partial match with the state database. `no_match` - The field is not an exact match with the state database. `no_data` - The field was unable to be checked against state databases. - `city` 'match' | 'no_match' | 'no_data', required — The outcome of checking the particular field against state databases. `match` - The field is an exact match with the state database. `no_match` - The field is not an exact match with the state database. `no_data` - The field was unable to be checked against state databases. - `postal_code` 'match' | 'partial_match' | 'no_match' | 'no_data', required — The outcome of checking the associated hit against state databases. `match` - The field is an exact match with the state database. `partial_match` - The field is a partial match with the state database. `no_match` - The field is not an exact match with the state database. `no_data` - The field was unable to be checked against state databases. - `date_of_birth` 'match' | 'no_match' | 'no_data', required — The outcome of checking the particular field against state databases. `match` - The field is an exact match with the state database. `no_match` - The field is not an exact match with the state database. `no_data` - The field was unable to be checked against state databases. - `gender` 'match' | 'no_match' | 'no_data', required — The outcome of checking the particular field against state databases. `match` - The field is an exact match with the state database. `no_match` - The field is not an exact match with the state database. `no_data` - The field was unable to be checked against state databases. - `height` 'match' | 'no_match' | 'no_data', required — The outcome of checking the particular field against state databases. `match` - The field is an exact match with the state database. `no_match` - The field is not an exact match with the state database. `no_data` - The field was unable to be checked against state databases. - `eye_color` 'match' | 'no_match' | 'no_data', required — The outcome of checking the particular field against state databases. `match` - The field is an exact match with the state database. `no_match` - The field is not an exact match with the state database. `no_data` - The field was unable to be checked against state databases. - `first_name` 'match' | 'partial_match' | 'no_match' | 'no_data', required — The outcome of checking the associated hit against state databases. `match` - The field is an exact match with the state database. `partial_match` - The field is a partial match with the state database. `no_match` - The field is not an exact match with the state database. `no_data` - The field was unable to be checked against state databases. - `middle_name` 'match' | 'partial_match' | 'no_match' | 'no_data', required — The outcome of checking the associated hit against state databases. `match` - The field is an exact match with the state database. `partial_match` - The field is a partial match with the state database. `no_match` - The field is not an exact match with the state database. `no_data` - The field was unable to be checked against state databases. - `last_name` 'match' | 'partial_match' | 'no_match' | 'no_data', required — The outcome of checking the associated hit against state databases. `match` - The field is an exact match with the state database. `partial_match` - The field is a partial match with the state database. `no_match` - The field is not an exact match with the state database. `no_data` - The field was unable to be checked against state databases. - `redacted_at` string, date-time, nullable, required — An ISO8601 formatted timestamp. - `selfie_check` SelfieCheck, nullable, required — Additional information for the `selfie_check` step. This field will be `null` unless `steps.selfie_check` has reached a terminal state of either `success` or `failed`. - `status` 'success' | 'failed', required — The outcome status for the associated Identity Verification attempt's `selfie_check` step. This field will always have the same value as `steps.selfie_check`. - `selfies` SelfieCheckSelfie[], required — An array of selfies submitted to the `selfie_check` step. Each entry represents one user submission. - `status` 'success' | 'failed', required — An outcome status for this specific selfie. Distinct from the overall `selfie_check.status` that summarizes the verification outcome from one or more selfies. - `attempt` integer, required — The `attempt` field begins with 1 and increments with each subsequent selfie upload. - `capture` SelfieCapture, required — The image or video capture of a selfie. Only one of `image_url` or `video_url` will be populated per selfie. In the vast majority of sessions Plaid records a short video of the user, so `video_url` is populated and `image_url` is `null`. `image_url` is only populated in the rare passive-liveness fallback case, where the user's device could not complete the standard video liveness capture (for example, a camera or streaming error) and submitted a single still image instead. - `image_url` string, nullable, required — Temporary URL for downloading a still-image selfie capture. This field is only populated when the session fell back to passive (image-based) liveness. For the majority of selfie checks this field is `null` and `video_url` is populated instead. - `video_url` string, nullable, required — Temporary URL for downloading a video selfie capture. This is the standard selfie capture for Identity Verification. Plaid records a short video of the user during the Selfie Check liveness step, so this field is populated for the vast majority of selfie checks. - `analysis` SelfieAnalysis, required — High level descriptions of how the associated selfie was processed. If a selfie fails verification, the details in the `analysis` object should help clarify why the selfie was rejected. - `document_comparison` 'match' | 'no_match' | 'no_input', required — Information about the comparison between the selfie and the document (if documentary verification also ran). - `liveness_check` 'success' | 'failed', required — Assessment of whether the selfie capture is of a real human being, as opposed to a picture of a human on a screen, a picture of a paper cut out, someone wearing a mask, or a deepfake. - `age_check` SelfieAgeCheck, nullable — Age-estimation results from the selfie capture. This field is `null` when an age range could not be estimated from the selfie capture. - `status` 'match' | 'warning' | 'no_match' | 'no_data', required — An enum indicating whether the reported age aligns with the estimated selfie capture age range. `match` indicates that the reported age falls within the estimated selfie capture age range. `warning` indicates that the reported age falls outside the estimated selfie capture age range, but is close enough that the result should be reviewed. `no_match` indicates that the reported age falls far outside the estimated selfie capture age range. `no_data` indicates that there was not enough data available at age-estimation time to compare the reported age against the estimated selfie capture age range. - `reported_age` integer, nullable, required — The user's age at the time of the selfie capture, calculated from the date of birth submitted during Identity Verification. If multiple date of birth sources are available, the date of birth submitted in the flow session takes priority over the document date of birth. This field is `null` when the date of birth is unavailable. - `age_estimate_lower_bound` integer, required — Lower bound of the estimated age range from the selfie capture. - `age_estimate_upper_bound` integer, required — Upper bound of the estimated age range from the selfie capture. - `facial_analysis` SelfieAnalysisFacialAnalysis, nullable — Analysis of the facial features of the selfie when compared to the face in the uploaded document, if one is present. - `left_eye` 'success' | 'failed', required — Outcome of the facial analysis for a specific facial feature. - `right_eye` 'success' | 'failed', required — Outcome of the facial analysis for a specific facial feature. - `left_brow` 'success' | 'failed', required — Outcome of the facial analysis for a specific facial feature. - `right_brow` 'success' | 'failed', required — Outcome of the facial analysis for a specific facial feature. - `forehead` 'success' | 'failed', required — Outcome of the facial analysis for a specific facial feature. - `middle_forehead` 'success' | 'failed', required — Outcome of the facial analysis for a specific facial feature. - `nose` 'success' | 'failed', required — Outcome of the facial analysis for a specific facial feature. - `philtrum` 'success' | 'failed', required — Outcome of the facial analysis for a specific facial feature. - `mouth` 'success' | 'failed', required — Outcome of the facial analysis for a specific facial feature. - `jaw` 'success' | 'failed', required — Outcome of the facial analysis for a specific facial feature. - `left_cheek` 'success' | 'failed', required — Outcome of the facial analysis for a specific facial feature. - `right_cheek` 'success' | 'failed', required — Outcome of the facial analysis for a specific facial feature. - `kyc_check` KYCCheckDetails, nullable, required — Additional information for the `kyc_check` (Data Source Verification) step. This field will be `null` unless `steps.kyc_check` has reached a terminal state of either `success` or `failed`. - `status` string, required — The outcome status for the associated Identity Verification attempt's `kyc_check` step. This field will always have the same value as `steps.kyc_check`. - `address` KYCCheckAddressSummary, required — Result summary object specifying how the `address` field matched. - `summary` 'match' | 'partial_match' | 'no_match' | 'no_data' | 'no_input', required — An enum indicating the match type between data provided by user and data checked against an external data source. `match` indicates that the provided input data was a strong match against external data. `partial_match` indicates the data approximately matched against external data. For example, "Knope" vs. "Knope-Wyatt" for last name. `no_match` indicates that Plaid was able to perform a check against an external data source and it did not match the provided input data. `no_data` indicates that Plaid was unable to find external data to compare against the provided input data. `no_input` indicates that Plaid was unable to perform a check because no information was provided for this field by the end user. - `po_box` 'yes' | 'no' | 'no_data', required — Field describing whether the associated address is a post office box. Will be `yes` when a P.O. box is detected, `no` when Plaid confirmed the address is not a P.O. box, and `no_data` when Plaid was not able to determine if the address is a P.O. box. - `type` 'residential' | 'commercial' | 'no_data', required — Field describing whether the associated address is being used for commercial or residential purposes. Note: This value will be `no_data` when Plaid does not have sufficient data to determine the address's use. - `street` 'match' | 'partial_match' | 'no_match' | 'no_data' | 'no_input' — An enum indicating the match type between data provided by user and data checked against an external data source. `match` indicates that the provided input data was a strong match against external data. `partial_match` indicates the data approximately matched against external data. For example, "Knope" vs. "Knope-Wyatt" for last name. `no_match` indicates that Plaid was able to perform a check against an external data source and it did not match the provided input data. `no_data` indicates that Plaid was unable to find external data to compare against the provided input data. `no_input` indicates that Plaid was unable to perform a check because no information was provided for this field by the end user. - `city` 'match' | 'partial_match' | 'no_match' | 'no_data' | 'no_input' — An enum indicating the match type between data provided by user and data checked against an external data source. `match` indicates that the provided input data was a strong match against external data. `partial_match` indicates the data approximately matched against external data. For example, "Knope" vs. "Knope-Wyatt" for last name. `no_match` indicates that Plaid was able to perform a check against an external data source and it did not match the provided input data. `no_data` indicates that Plaid was unable to find external data to compare against the provided input data. `no_input` indicates that Plaid was unable to perform a check because no information was provided for this field by the end user. - `region` 'match' | 'partial_match' | 'no_match' | 'no_data' | 'no_input' — An enum indicating the match type between data provided by user and data checked against an external data source. `match` indicates that the provided input data was a strong match against external data. `partial_match` indicates the data approximately matched against external data. For example, "Knope" vs. "Knope-Wyatt" for last name. `no_match` indicates that Plaid was able to perform a check against an external data source and it did not match the provided input data. `no_data` indicates that Plaid was unable to find external data to compare against the provided input data. `no_input` indicates that Plaid was unable to perform a check because no information was provided for this field by the end user. - `postal_code` 'match' | 'partial_match' | 'no_match' | 'no_data' | 'no_input' — An enum indicating the match type between data provided by user and data checked against an external data source. `match` indicates that the provided input data was a strong match against external data. `partial_match` indicates the data approximately matched against external data. For example, "Knope" vs. "Knope-Wyatt" for last name. `no_match` indicates that Plaid was able to perform a check against an external data source and it did not match the provided input data. `no_data` indicates that Plaid was unable to find external data to compare against the provided input data. `no_input` indicates that Plaid was unable to perform a check because no information was provided for this field by the end user. - `international_details` KYCCheckDetailsInternationalAddress, nullable — Result summary object specifying how the `address` field matched for fields that are only present on an international KYC check. - `building` 'match' | 'partial_match' | 'no_match' | 'no_data' | 'no_input', required — An enum indicating the match type between data provided by user and data checked against an external data source. `match` indicates that the provided input data was a strong match against external data. `partial_match` indicates the data approximately matched against external data. For example, "Knope" vs. "Knope-Wyatt" for last name. `no_match` indicates that Plaid was able to perform a check against an external data source and it did not match the provided input data. `no_data` indicates that Plaid was unable to find external data to compare against the provided input data. `no_input` indicates that Plaid was unable to perform a check because no information was provided for this field by the end user. - `county` 'match' | 'partial_match' | 'no_match' | 'no_data' | 'no_input', required — An enum indicating the match type between data provided by user and data checked against an external data source. `match` indicates that the provided input data was a strong match against external data. `partial_match` indicates the data approximately matched against external data. For example, "Knope" vs. "Knope-Wyatt" for last name. `no_match` indicates that Plaid was able to perform a check against an external data source and it did not match the provided input data. `no_data` indicates that Plaid was unable to find external data to compare against the provided input data. `no_input` indicates that Plaid was unable to perform a check because no information was provided for this field by the end user. - `district` 'match' | 'partial_match' | 'no_match' | 'no_data' | 'no_input', required — An enum indicating the match type between data provided by user and data checked against an external data source. `match` indicates that the provided input data was a strong match against external data. `partial_match` indicates the data approximately matched against external data. For example, "Knope" vs. "Knope-Wyatt" for last name. `no_match` indicates that Plaid was able to perform a check against an external data source and it did not match the provided input data. `no_data` indicates that Plaid was unable to find external data to compare against the provided input data. `no_input` indicates that Plaid was unable to perform a check because no information was provided for this field by the end user. - `house_number` 'match' | 'partial_match' | 'no_match' | 'no_data' | 'no_input', required — An enum indicating the match type between data provided by user and data checked against an external data source. `match` indicates that the provided input data was a strong match against external data. `partial_match` indicates the data approximately matched against external data. For example, "Knope" vs. "Knope-Wyatt" for last name. `no_match` indicates that Plaid was able to perform a check against an external data source and it did not match the provided input data. `no_data` indicates that Plaid was unable to find external data to compare against the provided input data. `no_input` indicates that Plaid was unable to perform a check because no information was provided for this field by the end user. - `subpremise` 'match' | 'partial_match' | 'no_match' | 'no_data' | 'no_input', required — An enum indicating the match type between data provided by user and data checked against an external data source. `match` indicates that the provided input data was a strong match against external data. `partial_match` indicates the data approximately matched against external data. For example, "Knope" vs. "Knope-Wyatt" for last name. `no_match` indicates that Plaid was able to perform a check against an external data source and it did not match the provided input data. `no_data` indicates that Plaid was unable to find external data to compare against the provided input data. `no_input` indicates that Plaid was unable to perform a check because no information was provided for this field by the end user. - `thoroughfare` 'match' | 'partial_match' | 'no_match' | 'no_data' | 'no_input', required — An enum indicating the match type between data provided by user and data checked against an external data source. `match` indicates that the provided input data was a strong match against external data. `partial_match` indicates the data approximately matched against external data. For example, "Knope" vs. "Knope-Wyatt" for last name. `no_match` indicates that Plaid was able to perform a check against an external data source and it did not match the provided input data. `no_data` indicates that Plaid was unable to find external data to compare against the provided input data. `no_input` indicates that Plaid was unable to perform a check because no information was provided for this field by the end user. - `name` KYCCheckNameSummary, required — Result summary object specifying how the `name` field matched. - `summary` 'match' | 'partial_match' | 'no_match' | 'no_data' | 'no_input', required — An enum indicating the match type between data provided by user and data checked against an external data source. `match` indicates that the provided input data was a strong match against external data. `partial_match` indicates the data approximately matched against external data. For example, "Knope" vs. "Knope-Wyatt" for last name. `no_match` indicates that Plaid was able to perform a check against an external data source and it did not match the provided input data. `no_data` indicates that Plaid was unable to find external data to compare against the provided input data. `no_input` indicates that Plaid was unable to perform a check because no information was provided for this field by the end user. - `given_name` 'match' | 'partial_match' | 'no_match' | 'no_data' | 'no_input' — An enum indicating the match type between data provided by user and data checked against an external data source. `match` indicates that the provided input data was a strong match against external data. `partial_match` indicates the data approximately matched against external data. For example, "Knope" vs. "Knope-Wyatt" for last name. `no_match` indicates that Plaid was able to perform a check against an external data source and it did not match the provided input data. `no_data` indicates that Plaid was unable to find external data to compare against the provided input data. `no_input` indicates that Plaid was unable to perform a check because no information was provided for this field by the end user. - `family_name` 'match' | 'partial_match' | 'no_match' | 'no_data' | 'no_input' — An enum indicating the match type between data provided by user and data checked against an external data source. `match` indicates that the provided input data was a strong match against external data. `partial_match` indicates the data approximately matched against external data. For example, "Knope" vs. "Knope-Wyatt" for last name. `no_match` indicates that Plaid was able to perform a check against an external data source and it did not match the provided input data. `no_data` indicates that Plaid was unable to find external data to compare against the provided input data. `no_input` indicates that Plaid was unable to perform a check because no information was provided for this field by the end user. - `date_of_birth` KYCCheckDateOfBirthSummary, required — Result summary object specifying how the `date_of_birth` field matched. - `summary` 'match' | 'partial_match' | 'no_match' | 'no_data' | 'no_input', required — An enum indicating the match type between data provided by user and data checked against an external data source. `match` indicates that the provided input data was a strong match against external data. `partial_match` indicates the data approximately matched against external data. For example, "Knope" vs. "Knope-Wyatt" for last name. `no_match` indicates that Plaid was able to perform a check against an external data source and it did not match the provided input data. `no_data` indicates that Plaid was unable to find external data to compare against the provided input data. `no_input` indicates that Plaid was unable to perform a check because no information was provided for this field by the end user. - `day` 'match' | 'partial_match' | 'no_match' | 'no_data' | 'no_input' — An enum indicating the match type between data provided by user and data checked against an external data source. `match` indicates that the provided input data was a strong match against external data. `partial_match` indicates the data approximately matched against external data. For example, "Knope" vs. "Knope-Wyatt" for last name. `no_match` indicates that Plaid was able to perform a check against an external data source and it did not match the provided input data. `no_data` indicates that Plaid was unable to find external data to compare against the provided input data. `no_input` indicates that Plaid was unable to perform a check because no information was provided for this field by the end user. - `month` 'match' | 'partial_match' | 'no_match' | 'no_data' | 'no_input' — An enum indicating the match type between data provided by user and data checked against an external data source. `match` indicates that the provided input data was a strong match against external data. `partial_match` indicates the data approximately matched against external data. For example, "Knope" vs. "Knope-Wyatt" for last name. `no_match` indicates that Plaid was able to perform a check against an external data source and it did not match the provided input data. `no_data` indicates that Plaid was unable to find external data to compare against the provided input data. `no_input` indicates that Plaid was unable to perform a check because no information was provided for this field by the end user. - `year` 'match' | 'partial_match' | 'no_match' | 'no_data' | 'no_input' — An enum indicating the match type between data provided by user and data checked against an external data source. `match` indicates that the provided input data was a strong match against external data. `partial_match` indicates the data approximately matched against external data. For example, "Knope" vs. "Knope-Wyatt" for last name. `no_match` indicates that Plaid was able to perform a check against an external data source and it did not match the provided input data. `no_data` indicates that Plaid was unable to find external data to compare against the provided input data. `no_input` indicates that Plaid was unable to perform a check because no information was provided for this field by the end user. - `id_number` KYCCheckIDNumberSummary, required — Result summary object specifying how the `id_number` field matched. - `summary` 'match' | 'partial_match' | 'no_match' | 'no_data' | 'no_input', required — An enum indicating the match type between data provided by user and data checked against an external data source. `match` indicates that the provided input data was a strong match against external data. `partial_match` indicates the data approximately matched against external data. For example, "Knope" vs. "Knope-Wyatt" for last name. `no_match` indicates that Plaid was able to perform a check against an external data source and it did not match the provided input data. `no_data` indicates that Plaid was unable to find external data to compare against the provided input data. `no_input` indicates that Plaid was unable to perform a check because no information was provided for this field by the end user. - `phone_number` KYCCheckPhoneSummary, required — Result summary object specifying how the `phone` field matched. - `summary` 'match' | 'partial_match' | 'no_match' | 'no_data' | 'no_input', required — An enum indicating the match type between data provided by user and data checked against an external data source. `match` indicates that the provided input data was a strong match against external data. `partial_match` indicates the data approximately matched against external data. For example, "Knope" vs. "Knope-Wyatt" for last name. `no_match` indicates that Plaid was able to perform a check against an external data source and it did not match the provided input data. `no_data` indicates that Plaid was unable to find external data to compare against the provided input data. `no_input` indicates that Plaid was unable to perform a check because no information was provided for this field by the end user. - `area_code` 'match' | 'partial_match' | 'no_match' | 'no_data' | 'no_input', required — An enum indicating the match type between data provided by user and data checked against an external data source. `match` indicates that the provided input data was a strong match against external data. `partial_match` indicates the data approximately matched against external data. For example, "Knope" vs. "Knope-Wyatt" for last name. `no_match` indicates that Plaid was able to perform a check against an external data source and it did not match the provided input data. `no_data` indicates that Plaid was unable to find external data to compare against the provided input data. `no_input` indicates that Plaid was unable to perform a check because no information was provided for this field by the end user. - `risk_check` RiskCheckDetails, nullable, required — Additional information for the `risk_check` step. - `status` 'success' | 'active' | 'failed' | 'waiting_for_prerequisite' | 'not_applicable' | 'skipped' | 'expired' | 'canceled' | 'pending_review' | 'manually_approved' | 'manually_rejected', required — The status of a step in the Identity Verification process. - `behavior` RiskCheckBehavior, nullable, required — Result summary object specifying values for `behavior` attributes of risk check, when available. - `user_interactions` 'genuine' | 'neutral' | 'risky' | 'no_data', required — Field describing the overall user interaction signals of a behavior risk check. This value represents how familiar the user is with the personal data they provide, based on a number of signals that are collected during their session. `genuine` indicates the user has high familiarity with the data they are providing, and that fraud is unlikely. `neutral` indicates some signals are present in between `risky` and `genuine`, but there are not enough clear signals to determine an outcome. `risky` indicates the user has low familiarity with the data they are providing, and that fraud is likely. `no_data` indicates there is not sufficient information to give an accurate signal. - `fraud_ring_detected` 'yes' | 'no' | 'no_data', required — Field describing the outcome of a fraud ring behavior risk check. `yes` indicates that fraud ring activity was detected. `no` indicates that fraud ring activity was not detected. `no_data` indicates there was not enough information available to give an accurate signal. - `bot_detected` 'yes' | 'no' | 'no_data', required — Field describing the outcome of a bot detection behavior risk check. `yes` indicates that automated activity was detected. `no` indicates that automated activity was not detected. `no_data` indicates there was not enough information available to give an accurate signal. - `risk_level` 'low' | 'medium' | 'high' | 'no_data' — Risk level for the given risk check type, when available. - `email` RiskCheckEmail, nullable, required — Result summary object specifying values for `email` attributes of risk check. - `is_deliverable` 'yes' | 'no' | 'no_data', required — SMTP-MX check to confirm the email address exists if known. - `breach_count` integer, nullable, required — Count of all known breaches of this email address if known. - `first_breached_at` string, date, nullable, required — A date in the format YYYY-MM-DD (RFC 3339 Section 5.6). - `last_breached_at` string, date, nullable, required — A date in the format YYYY-MM-DD (RFC 3339 Section 5.6). - `domain_registered_at` string, date, nullable, required — A date in the format YYYY-MM-DD (RFC 3339 Section 5.6). - `domain_is_free_provider` 'yes' | 'no' | 'no_data', required — Indicates whether the email address domain is a free provider such as Gmail or Hotmail if known. - `domain_is_custom` 'yes' | 'no' | 'no_data', required — Indicates whether the email address domain is custom if known, i.e. a company domain and not free or disposable. - `domain_is_disposable` 'yes' | 'no' | 'no_data', required — Indicates whether the email domain is listed as disposable if known. Disposable domains are often used to create email addresses that are part of a fake set of user details. - `top_level_domain_is_suspicious` 'yes' | 'no' | 'no_data', required — Indicates whether the email address top level domain, which is the last part of the domain, is fraudulent or risky if known. In most cases, a suspicious top level domain is also associated with a disposable or high-risk domain. - `is_edu` 'yes' | 'no' | 'no_data', required — Indicates whether the email address domain is an educational institution domain if known. - `includes_date_of_birth` 'yes' | 'no' | 'no_data', required — Indicates whether the email address includes the date of birth or year of birth if known. - `name` 'no_input' | 'indeterminate' | 'no_match' | 'partial_match' | 'match' | 'no_data', required — Indicates whether the provided name matches the email address according to the KYC name-matches-email inference result if known. `match` - "The email's name identifiers match the user's name." `partial_match` - "The email's name identifiers partially match the user's name." `no_match` - "The email's name identifiers do not match the user's name." `indeterminate` - "The email does not contain any name identifiers, and a match could not be determined." `no_input` - "The user's profile does not contain the required user inputs to determine a match." `no_data` - "Field could not be verified against available sources." - `linked_services` RiskCheckLinkedService[], required — A list of online services where this email address has been detected to have accounts or other activity. - `risk_level` 'low' | 'medium' | 'high' — Risk level for the given risk check type. - `factors` string[] — List of factors, when available, that contribute towards the risk level of the given risk check type. - `phone` RiskCheckPhone, nullable, required — Result summary object specifying values for `phone` attributes of risk check. - `linked_services` RiskCheckLinkedService[], required — A list of online services where this phone number has been detected to have accounts or other activity. - `risk_level` 'low' | 'medium' | 'high' — Risk level for the given risk check type. - `factors` string[] — List of factors, when available, that contribute towards the risk level of the given risk check type. - `devices` RiskCheckDevice[], required — Array of result summary objects specifying values for `device` attributes of risk check. - `ip_proxy_type` 'none_detected' | 'tor' | 'vpn' | 'web_proxy' | 'public_proxy', nullable, required — An enum indicating whether a network proxy is present and if so what type it is. `none_detected` indicates the user is not on a detectable proxy network. `tor` indicates the user was using a Tor browser, which sends encrypted traffic on a decentralized network and is somewhat similar to a VPN (Virtual Private Network). `vpn` indicates the user is on a VPN (Virtual Private Network) `web_proxy` indicates the user is on a web proxy server, which may allow them to conceal information such as their IP address or other identifying information. `public_proxy` indicates the user is on a public web proxy server, which is similar to a web proxy but can be shared by multiple users. This may allow multiple users to appear as if they have the same IP address for instance. - `ip_spam_list_count` integer, nullable, required — Count of spam lists the IP address is associated with if known. - `ip_timezone_offset` string, nullable, required — UTC offset of the timezone associated with the IP address. - `risk_level` 'low' | 'medium' | 'high' — Risk level for the given risk check type. - `factors` string[] — List of factors, when available, that contribute towards the risk level of the given risk check type. - `identity_abuse_signals` RiskCheckIdentityAbuseSignals, nullable, required — Result summary object capturing abuse signals related to `identity abuse`, e.g. stolen and synthetic identity fraud. These attributes are only available for US identities and some signals may not be available depending on what information was collected. - `synthetic_identity` RiskCheckSyntheticIdentity, nullable, required — Field containing the data used in determining the outcome of the synthetic identity risk check. Contains the following fields: `score` - A score from 0 to 100 indicating the likelihood that the user is a synthetic identity. - `score` integer, required — A score from 0 to 100 indicating the likelihood that the user is a synthetic identity. - `risk_level` 'low' | 'medium' | 'high' — Risk level for the given risk check type. - `first_party_synthetic_fraud` SyntheticFraud, nullable — Field containing the data used in determining the outcome of a synthetic fraud risk check. - `risk_level` 'low' | 'medium' | 'high', required — Risk level for the given risk check type. - `third_party_synthetic_fraud` SyntheticFraud, nullable — Field containing the data used in determining the outcome of a synthetic fraud risk check. - `risk_level` 'low' | 'medium' | 'high', required — Risk level for the given risk check type. - `stolen_identity` RiskCheckStolenIdentity, nullable, required — Field containing the data used in determining the outcome of the stolen identity risk check. Contains the following fields: `score` - A score from 0 to 100 indicating the likelihood that the user is a stolen identity. - `score` integer, required — A score from 0 to 100 indicating the likelihood that the user is a stolen identity. - `risk_level` 'low' | 'medium' | 'high' — Risk level for the given risk check type. - `network` RiskCheckNetwork, nullable — Result summary object specifying values for network attributes of risk check. - `risk_level` 'low' | 'medium' | 'high', required — Risk level for the given risk check type. - `factors` string[], required — List of factors, when available, that contribute towards the risk level of the given risk check type. - `facial_duplicates` RiskCheckFacialDuplicate[], required — The attributes related to the facial duplicates captured in risk check. - `id` string, required — ID of the associated Identity Verification attempt. - `similarity` integer, required — Similarity score of the match. Ranges from 0 to 100. - `matched_after_completed` boolean, required — Whether this match occurred after the session was complete. For example, this would be `true` if a later session ended up matching this one. - `trust_index_score` integer, nullable, required — The trust index score for the `risk_check` step. - `verify_sms` VerifySMSDetails, nullable, required — Additional information for the `verify_sms` step. - `status` 'success' | 'failed', required — The outcome status for the associated Identity Verification attempt's `verify_sms` step. This field will always have the same value as `steps.verify_sms`. - `verifications` SMSVerification[], required — An array where each entry represents a verification attempt for the `verify_sms` step. Each entry represents one user-submitted phone number. Phone number edits, and in some cases error handling due to edge cases like rate limiting, may generate additional verifications. - `status` 'pending' | 'success' | 'failed' | 'canceled', required — The outcome status for the individual SMS verification. - `attempt` integer, required — The attempt field begins with 1 and increments with each subsequent SMS verification. - `phone_number` string, nullable, required — A phone number in E.164 format. - `delivery_attempt_count` integer, required — The number of delivery attempts made within the verification to send the SMS code to the user. Each delivery attempt represents the user taking action from the front end UI to request creation and delivery of a new SMS verification code, or to resend an existing SMS verification code. There is a limit of 3 delivery attempts per verification. - `solve_attempt_count` integer, required — The number of attempts made by the user within the verification to verify the SMS code by entering it into the front end UI. There is a limit of 3 solve attempts per verification. - `initially_sent_at` string, date-time, nullable, required — An ISO8601 formatted timestamp. - `last_sent_at` string, date-time, nullable, required — An ISO8601 formatted timestamp. - `redacted_at` string, date-time, nullable, required — An ISO8601 formatted timestamp. - `watchlist_screening_id` string, nullable, required — ID of the associated screening. - `beacon_user_id` string, nullable, required — Beacon is deprecated in favor of Plaid Protect. This field is only populated for users of the deprecated Beacon product. - `user_id` string, nullable, required — Unique user identifier, created by calling `/user/create`. Either a `user_id` or the `client_user_id` must be provided. The `user_id` may only be used instead of the `client_user_id` if you were not a pre-existing user of `/user/create` as of December 10, 2025, or if you have since [migrated to the new User APIs](https://plaid.com/docs/api/users/migrate-to-new-user-apis); for more details, see [New User APIs](https://plaid.com/docs/api/users/user-apis). If both this field and a `client_user_id` are present in a request, the `user_id` must have been created from the provided `client_user_id`. - `redacted_at` string, date-time, nullable, required — An ISO8601 formatted timestamp. - `latest_scored_protect_event` IDVProtectEvent, nullable — Information about a Protect event including Trust Index score and fraud attributes. - `event_id` string, required — The event ID. - `timestamp` string, date-time, required — The timestamp of the event, in [ISO 8601](https://wikipedia.org/wiki/ISO_8601) format, e.g. `"2017-09-14T14:42:19.350Z"` - `trust_index` TrustIndex, nullable, required — Represents a calculated Trust Index Score. - `score` integer, required — The overall trust index score. - `model` string, required — The versioned name of the Trust Index model used for scoring. - `subscores` TrustIndexSubscores, nullable, required — Contains sub-score metadata. - `device_and_connection` TrustIndexSubscore, nullable — Represents Trust Index Subscore. - `score` integer, required — The subscore score. - `bank_account_insights` TrustIndexSubscore, nullable — Represents Trust Index Subscore. - `score` integer, required — The subscore score. - `fraud_attributes` FraudAttributes, nullable, required — Event fraud attributes as an arbitrary set of key-value pairs. The set of attributes returned varies by model. - `request_id` string, required — A unique identifier for the request, which can be used for troubleshooting. This identifier, like all Plaid identifiers, is case sensitive. --- [API](https://skmtc.net/plaid/apis/the-plaid-api.md) · [All operations](https://skmtc.net/plaid/apis/the-plaid-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/plaid/the-plaid-api/versions/64c4514ea59b/schema)