Compare providers
Select a capability for its definition, or a status for provider details. Arrow keys move between statuses. 70 of 70 capabilities.
- Yes
- Optional
- Partner
- Related
- Not verified
- Outside scope
- Yes (Gov)
- Reported
- BAA-ready
- HIPAA stated
- Component tested
- Mobile only
- Hardware-dependent
- On request
- Scope to confirm
Colors apply equally to every provider: green = available; blue = available with stated conditions; gray = outside scope or not established.
- F01Document authenticityChecks a government-issued identity document for authenticity. Merely reading an ID is insufficient.
- F02ID data extractionExtracts structured identity fields through OCR, MRZ, barcode or another supported document-reading method.
- F03NFC chip verificationReads and validates the chip of a supported electronic identity document.
- F04Identity-data matchingCorroborates personal identity attributes against authoritative or trusted external records.
- F05Proof of addressVerifies address evidence or corroborates a person-address relationship. Address formatting alone is Related.
- F06Phone / email checksChecks ownership, validity or risk of a phone number or email. Yes can cover either channel, not necessarily both.
- F07ID-based age checksChecks age using a verified identity document or an attribute derived from that document.
- F08Facial age estimationEstimates an age or age range from a facial capture. This is distinct from identity or date-of-birth verification.
- F091:1 face matchCompares a face with one claimed identity reference.
- F10Real-time livenessChecks whether the capture represents a live human using the supported liveness process.
- F11Server-side face matchPerforms facial comparison in a server service, beyond a device-local unlock result.
- F12Repeat live identity matchSupports a new live face match to an established identity after enrollment. Yes does not mean mandatory in every product or session.
- F13Server-side face referenceMaintains a biometric reference for later server-side comparison. This is an architecture field, not a security score.
- F141:N face duplicate checksCompares a face against multiple enrolled references to detect duplicate enrollment. Device or record linking alone is Related.
- F15Account reverificationOffers identity reverification for account recovery, sensitive changes or another later account action.
- F16No retained face photosOffers a flow without ongoing retention of raw face photographs by the verification service. Templates are assessed separately.
- F17No retained ID imagesOffers a flow without ongoing retention of government-ID images after verification. Attributes and records may remain.
- F18Homomorphic template protectionDescribes homomorphic encryption for the biometric reference or matching process. Ordinary encryption is not equivalent.
- F19Biometric key rotationDescribes rotating encryption keys protecting the biometric reference. Rotating API keys does not qualify.
- F20Selective / result-only disclosureSupports sharing needed identity attributes or an eligibility result without routinely disclosing the underlying evidence.
- F21Reusable verified identityReuses established verified identity across later interactions or participating services. Yes does not imply cross-organization portability.
- F22Separate organization accountsCombines reusable verified identity with separate organization-controlled accounts and permissions, without required sharing of business records.
- F23Cross-device live verificationSupports later live biometric verification across devices without relying only on the original device-local enrollment.
- F24Exact-event bindingBinds an authorization or signature to the specified action or transaction details. This field does not require a live identity check.
- F25Single-use event authorizationProvides one-time, event-scoped authorization with replay enforcement. An expiring OTP or login session alone does not qualify.
- F26Live identity + event bindingCombines established verified identity, fresh presence and the specific event in one scoped authorization.
- F27Complete authorization evidenceProtects a record connecting the identified human, fresh presence, exact event and explicit authorization.
- F28Human authorization for AISupports fresh verified-human authorization scoped to a particular AI-agent action. Human sponsorship alone is Related.
- F29API integrationProvides programmatic integration for the reviewed identity or authorization offering.
- F30SDK integrationProvides a supported client or server SDK for the reviewed offering.
- F31Webhooks / event callbacksDocuments asynchronous verification events or callback delivery to the organization.
- F32Workflow configurationProvides configurable orchestration, verification journeys or manual-review operations.
- F33IAM integrationDocuments connection to enterprise/customer identity and access systems or federation. A generic API alone is insufficient.
- F34Private / on-premises optionDocuments private-hosted or on-premises server deployment of relevant components. Local device capture alone does not qualify.
- F35Device / network riskUses device, network, IP, geolocation or related signals to assess risk. These signals do not establish a verified human.
- F36Individual AML screeningScreens individuals against sanctions, PEP or related watchlists. Business screening is a separate field.
- F37Ongoing individual screeningMonitors an enrolled person for later sanctions, PEP or related screening changes.
- F38Packaged business verificationOffers a packaged company-verification workflow, beyond a standalone registry lookup. Scope may include ownership and officers.
- F39Native transaction monitoringOffers a dedicated transaction-risk monitoring product with rules, alerts or investigations. Authentication risk is not equivalent.
- F40Air-gapped operationRuns the relevant verification service inside an isolated network without a required connection to external services.
- F41Customer-managed signing keysLets the customer hold or manage keys used to sign identity or authorization records.
- F42Customer-owned evidenceAssigns ownership and governance of the authorization evidence to the customer, with the provider acting as processor.
- F43Revocable biometric referenceAllows an enrolled biometric reference to be disabled or purged so it cannot support future verification in that system.
- F44Non-exportable biometric referenceRestricts export of a usable biometric reference outside the designated deployment boundary.
- F45Independently verifiable evidenceProduces a signed identity, authorization or signing record that can be verified independently of the originating application.
- F46Two-person human authorizationRequires two distinct humans, each freshly verified, to authorize the same defined action.
- F47Scoped human delegation to AIBinds a verified human to a defined scope of authority delegated to an AI agent, with escalation when that scope is exceeded.
- F48Revocable AI delegationWithdraws a human-linked agent authorization so later actions requiring that authorization are prevented.
- F49Fallback policyLets the organization define escalation or an alternative path when a verification cannot complete, while preserving the outcome.
- F50CAC-linked human enrollmentEstablishes a reusable human biometric reference linked to a validated Common Access Card or equivalent government credential.
- F51Fingerprint verification pathProvides infrastructure-based fingerprint identity verification for settings where cameras cannot be used. A device-local unlock alone does not qualify.
- F52SOC 2 Type II attestationAn independent SOC 2 Type II report for the relevant entity and service, covering controls over a stated period.
- F53ISO/IEC 27001 certificationA certified information security management system with an identified entity, edition and scope.
- F54HIPAA / BAA supportDocumented healthcare safeguards and support for a Business Associate Agreement where applicable.
- F55Independent PAD Level 1 testIndependent presentation-attack testing at Level 1 against ISO/IEC 30107-3 for the named component/version.
- F56Independent PAD Level 2 testIndependent presentation-attack testing at Level 2 against ISO/IEC 30107-3 for the named component/version.
- F57Independent face-match evaluationA third-party evaluation of biometric matching performance for an identified algorithm/configuration.
- F58Independent penetration testingDocumented external adversarial testing of the relevant application, SDK, service or infrastructure.
- F59Mobile driver license verificationSupport for verifying compatible mobile driver license credentials, with applicable standards identified.
- F60Customer-managed encryption keysCustomer management of keys protecting retained platform data or biometric templates.
- F61Mobile runtime protectionRuntime application self-protection or documented equivalent capture-app integrity controls.
- F62Signed result callbacksAuthenticated verification-result delivery with documented signature validation.
- F63Separated service environmentsDocumented separation between production and nonproduction API/service environments.
- F64Optional FIDO2 supportFIDO2 authentication or device-binding support alongside the reviewed offering.
- F65Configurable verification thresholdsDocumented ability to tune biometric or liveness decision thresholds by deployment or policy.
- F66Passive liveness captureLiveness verification without requiring scripted user gestures such as head turns or blinking.
- F67HSM-backed identity operationsDocumented use of a hardware security module in relevant identity, key or evidence operations.
- F68Tamper-evident operational logsProtected logging across relevant verification and downstream integration events.
- F69Security evidence on requestSecurity documentation, audit evidence or testing materials available to qualified buyers.
- F70Multispectral document checksSupported document-security examination using compatible multispectral capture hardware.
Yes: Documented availability within the reviewed product scope. Does not mean mandatory by default, universally deployed, independently tested or equal performance.
Not verified: The reviewed material does not establish the specific capability. An evidence gap, not a Yes or No. Apply the same standard to every provider; unknowns are not scored as wins or losses.
Read status definitions and methodologyRead the comparison precisely
Available or configurable does not mean mandatory. Not verified is an evidence gap, not an absent feature.