Compare Nametag with Other ID Verification Tools

Basic Know-Your-Customer (KYC) flows at account opening and other regulated activities

Any employee or customer activity that requires strong, phishing-proof authentication

Collect data to inform existing fraud detection processes only

Auditable verification logs enable security and compliance teams to review all ID verifications performed through Nametag

Relies on manual flags

Patent-pending selfie chaining technology ensures one Nametag per person, stopping repeat offenders

Webcams capture photos and extract data, sometimes matching them to a template and sometimes cross-referencing against other data sources

Machine learning is often applied in the cloud or on-premises to extract data from ID documents

Smartphone cameras provide higher-fidelity image capture and security features that eliminate digital manipulation and focus on physical manipulation using rich 3D data and app attestation

On-device and cloud-based AI and machine vision enable structural and semantic analysis

‍Other platforms simply can’t do this so they need to use other data sources and templates

Either no liveness detection capabilities, or require users to take a short video for liveness

Reliable liveness detection performed via selfie captured with advanced depth maps via native smartphone cameras

Browser-based encryption with
varying levels of adherence to security and privacy standards

Hardware-backed cryptography on device and cloud. SOC 2 Type II audited, complaint with GDPR, CCPA/CPRA, and HIPAA

Cross platform and device type

Cross platform and device type

Involves multiple lengthy redirects between browser and mobile device, requires users to download an app to complete

iOS App Clips and Android Instant Apps deliver an on-device user flow through an interface users are already familiar with

Yes

No

Mostly white-labeled

Mostly white-labeled

User has to share everything on their ID document with the requesting company

Privacy masking prevents oversharing of data. Users share only share the minimum required data with their explicit consent

All collected PII is often required to be stored by the company 

No collected PII is required to be stored by the company

Varies

Serverless, multi-region, cloud-native architecture

Name, birthdate, sometimes address, sometimes SS, sometimes ID number

Name, birthdate, +18, +21, phone number, address, verified profile photo, personal or work email

Company handles requests 

End-user controls sharing of their data, can revoke access at any time on their own

General “check the box”

Explicit consent received from the user for every data request

User re-scans their ID every time

Selfie re-verification using patent-pending Selfie Chaining technology

Recoverable, patent-pending device-to-identity binding eliminates permanent lockouts when a device is lost or broken

Universal APIs and SDKs require lengthy integration work to use

Out-of-the-box agent console sets up in minutes; universal APIs and SDKs also available

Single-use, one-time

Extend from support or step-up use cases to complete Sign in with ID functionality

Varies

Full global coverage for over 10,000 document types

Fixed fee per verification

Unlimited verifications per user