Document verification

Overview

Physical document verification is an identity verification technique that allows brands to be very sure the person registering an account is who they say they are. If configured, users are asked during registration to scan a drivers license, passport, or other government issued identity document to prove their identity. This information is passed to a third-party service where various risk and fraud checks can be performed before a new account is created.

Document verification is available globally, in over 200 countries.

Approach

Physical document verification is a configurable step in our Identity Verification policy. When enabled, a physical document verification step will occur as part of an identity verification workflow.

Prospective customers can claim their identities online by presenting an identity document they hold, such as a driver’s license or passport. Once they scan their document, the verification flow will do various levels of fraud checks to make sure:

  • the presented document is real and it’s not a counterfeit nor has been tampered with (Authenticity/Credibility)
  • the person is the actual owner of the identification document presented (Possession)
  • the person signing up for the account is genuinely present in the process (Liveness check)

You can store information collected from a physical document as part of the user’s account information. And, of course, this is all available via our no-code components so your brand is reflected in the customer workflow automatically.

Capabilities

  • Require a user to perform an physical document check before account opening
  • Supports drivers license, passports, and other government issued documents in over 200 countries
  • Workflow supports ID capture (front and back), data extraction, selfie capture, and verification that a document in genuine
  • Data extracted from documents can be stored in the user's account
  • 99% + accuracy in detecting the most sophisticated fraudulent documents
  • EXIF data analysis of images to detect fraud
  • Biometric liveness detection and face match detection

Compliance

Compliance badges

As part of our Information Security Management Program (ISMP), Strivacity includes compliance, testing, and certification wherever possible. Our document verification process complies with the following security standards:

NIST 800-63A IAL 2 compliance

Document verification is equipped to protect sensitive and regulated data, such as financial and healthcare records from unauthorized access and fraudulent activities in accordance with NIST 800-63A’s Identity Assurance Level 2 standards. Our verification method provides a high level of confidence in user identities accessing sensitive data and services.

NIST non-bias decisioning

Our document verification service earned the highest ranking for impartial race and gender decisioning. Rate 1 by NIST ensures objective, non-biased decisioning when an identity’s authenticity is verified. Our service can handle 35 million identity verification transactions in a single day and over a whopping 1 billion in a month.

Liveness check

Our built-in liveness detection fulfills Level 2 iBeta Presentation Attack Detection (PAD) requirements. This assures that document verification rejects fake representations or “spoofs” of biometric samples and only accepts genuine biometric data for verification.

GDPR compliance

We’ve taken the necessary steps to ensure the processing of personal data for document verification is in line with the General Data Protection Regulation (GDPR) to protect the rights of your EU customers.

CCPA compliance

We’ve also made sure our document verification process complies with the California Consumer Privacy Act (CCPA) to protect your US customers' rights to privacy.

Data retention

You can adjust data retention rules for document verification to stay compliant with the data protection regulations relevant to your organization. You can define how customer data collected during the verification process should be stored, retained, and deleted.