Plaid logo
Docs
ALL DOCS

Identity Verification

  • Introduction to Identity Verification
  • Webhooks
  • Link callbacks
  • Testing in Sandbox
  • Input validation rules
  • Risk checks
  • Managing failed verifications
  • Metrics and reporting
Plaid logo
Docs
Close search modal
Ask Bill!
Ask Bill!
Hi! I'm Bill! You can ask me all about the Plaid API. Try asking questions like:
    Note: Bill isn't perfect. He's just a robot platypus that reads our docs for fun. You should treat his answers with the same healthy skepticism you might treat any other answer on the internet. This chat may be logged for quality and training purposes. Please don't send Bill any PII -- he's scared of intimacy. All chats with Bill are subject to Plaid's Privacy Policy.
    Plaid.com
    Log in
    Get API Keys
    Open nav

    Operational guide

    Operational guidance for Identity Verification, including how to manage failed verifications

    Overview

    The most common reason for Identity Verification failures is bad actors and attempted fraud. However, sometimes a genuine user may fail a check due to various reasons, such as accidentally entering incorrect information, a lack of records available to confirm their identity, or issues with their identity documents. This page discusses common reasons why legitimate users may fail checks and how you can handle these issues.

    Common causes for Data Source Verification failures

    No match

    Causes include:

    • Recent personal information changes, such as a change of address or a legal name change
    • If you are providing any user information via the API rather than Link, it must use the correct format. For example, if you send DOB as month/day/year rather than in ISO format, it will cause date of birth mismatches. See Hybrid input validation.
    No data

    Causes include:

    • Phone number appears less consistently in data sources than other fields, and is most likely to result in "no data"
    • Recent immigrants and younger end users are less likely to have data on file
    • Countries other than the US have less complete records and are less likely to have data source matches

    Common causes for Documentary Verification failures

    • Expired documents will fail Documentary Verification, even if they are genuine
    • Documents that do not match the name and date of birth entered will fail

    Common causes for Risk Check failures

    See Risk Checks for more information.

    Common causes for Selfie Check failures

    Causes generally involve low-quality images, which can be caused by:

    • Poor quality camera, such as one found on a very old, low-end device
    • Insufficient lighting
    • Improper framing (head cut off or not facing camera)
    • Excessive glare from glasses
    • Motion blur while taking photo

    Plaid provides guidance in Link to help users take appropriate selfies.

    Managing failures

    If you have reason to believe that the end user's information is correct, you can override a failure via the Dashboard by clicking the Override Result button on the verification detail page in the Dashboard.

    To allow a user to retry a verification, you can issue a retry. For instructions on the process, see Retries.

    Reporting issues

    If at any point you believe that the Identity Verification result was incorrect, you can use the Report a Problem button in the Identity Verification Dashboard to inform Plaid. If you require a response, file a ticket via the Dashboard instead.

    Developer community
    GitHub
    GitHub
    Stack Overflow
    Stack Overflow
    YouTube
    YouTube
    Discord
    Discord