Verify Identity

Overview

The Verify Identity API is a standalone service that verifies a user’s identity against authoritative databases when the chosen method of verification includes:

Passport
Government ID
Financial Account Ownership

By leveraging this API, businesses can authenticate user identities against trusted records, reducing fraud risk and ensuring regulatory compliance.

Prerequisites

Before using this API, ensure the following:

The user has successfully uploaded a Government ID, Passport, or linked a Financial Account either via API or through Medallion.
The User Object contains complete and accurate Personally Identifiable Information (PII).
This step is not needed if the user has successfully passed Verify Quiz.

How This API Works

The Verify Identity API cross-references user data with multiple authoritative data sources to confirm whether the provided information matches a known individual. These sources include, but are not limited to:

U.S. Government Databases
Credit Bureau Records
Commercial and Consumer Data Sources
Utility and Telecommunication Records
Proprietary and Other Trusted Sources

This ensures accurate identity validation, minimizing fraud risk and enhancing compliance.

Why This API is Essential

Successful identity verification is a prerequisite for certain dependent processes. If identity verification is incomplete, actions such as generating a criminal background report will fail, returning an error indicating that verification must be completed first.

Common Roadblocks & Resolutions

Data Consistency Check
- The Verify Identity process checks whether the name and DOB on the Government ID matches the full name and DOB in the User Object.
- If a user provides a name or DOB that differs from the one on the ID, verification will fail.
Resolution

✅ To override this, retrieve the scanned user details from the Get Test Result endpoint after a successful document submission and update the User Object using the Update User method before retrying.
Incomplete or incorrect data in Authoritative Databases

In rare cases, a user's information may be captured incorrectly in authoritative databases. This can occur due to the following reasons:
- Identity changes – Legal name changes, marriages, or other personal status updates not reflected in official records.
- Third-party reporting errors – Incorrect data submission by financial institutions, employers, or other reporting entities.
- Clerical errors – Mistakes made during manual data entry.
Resolution

To resolve such issues, try the following:

✅ Provide a full SSN – In some cases, a partial SSN may not be sufficient for verification.
✅ Add a long-term address – Using an address the user has maintained for a long time can help improve match accuracy.

If discrepancies persist, explore alternative verification methods or contact support for further assistance.

Next Steps

Once identity verification is successfully completed, users can proceed with dependent processes, such as generating background reports and other compliance-related actions.