Capability guide
Available or configurable does not mean mandatory.
Identity checks
Document authenticity
Checks a government-issued identity document for authenticity. Merely reading an ID is insufficient.
F02ID data extraction
Extracts structured identity fields through OCR, MRZ, barcode or another supported document-reading method.
F03NFC chip verification
Reads and validates the chip of a supported electronic identity document.
F04Identity-data matching
Corroborates personal identity attributes against authoritative or trusted external records.
F05Proof of address
Verifies address evidence or corroborates a person-address relationship. Address formatting alone is Related.
F06Phone / email checks
Checks ownership, validity or risk of a phone number or email. Yes can cover either channel, not necessarily both.
F07ID-based age checks
Checks age using a verified identity document or an attribute derived from that document.
F08Facial age estimation
Estimates an age or age range from a facial capture. This is distinct from identity or date-of-birth verification.
Human verification
1:1 face match
Compares a face with one claimed identity reference.
F10Real-time liveness
Checks whether the capture represents a live human using the supported liveness process.
F11Server-side face match
Performs facial comparison in a server service, beyond a device-local unlock result.
F12Repeat live identity match
Supports a new live face match to an established identity after enrollment. Yes does not mean mandatory in every product or session.
F13Server-side face reference
Maintains a biometric reference for later server-side comparison. This is an architecture field, not a security score.
F141:N face duplicate checks
Compares a face against multiple enrolled references to detect duplicate enrollment. Device or record linking alone is Related.
F15Account reverification
Offers identity reverification for account recovery, sensitive changes or another later account action.
Privacy & reuse
No retained face photos
Offers a flow without ongoing retention of raw face photographs by the verification service. Templates are assessed separately.
F17No retained ID images
Offers a flow without ongoing retention of government-ID images after verification. Attributes and records may remain.
F18Homomorphic template protection
Describes homomorphic encryption for the biometric reference or matching process. Ordinary encryption is not equivalent.
F19Biometric key rotation
Describes rotating encryption keys protecting the biometric reference. Rotating API keys does not qualify.
F20Selective / result-only disclosure
Supports sharing needed identity attributes or an eligibility result without routinely disclosing the underlying evidence.
F21Reusable verified identity
Reuses established verified identity across later interactions or participating services. Yes does not imply cross-organization portability.
F22Separate organization accounts
Combines reusable verified identity with separate organization-controlled accounts and permissions, without required sharing of business records.
F23Cross-device live verification
Supports later live biometric verification across devices without relying only on the original device-local enrollment.
Authorization
Exact-event binding
Binds an authorization or signature to the specified action or transaction details. This field does not require a live identity check.
F25Single-use event authorization
Provides one-time, event-scoped authorization with replay enforcement. An expiring OTP or login session alone does not qualify.
F26Live identity + event binding
Combines established verified identity, fresh presence and the specific event in one scoped authorization.
F27Complete authorization evidence
Protects a record connecting the identified human, fresh presence, exact event and explicit authorization.
F28Human authorization for AI
Supports fresh verified-human authorization scoped to a particular AI-agent action. Human sponsorship alone is Related.
Integration
API integration
Provides programmatic integration for the reviewed identity or authorization offering.
F30SDK integration
Provides a supported client or server SDK for the reviewed offering.
F31Webhooks / event callbacks
Documents asynchronous verification events or callback delivery to the organization.
F32Workflow configuration
Provides configurable orchestration, verification journeys or manual-review operations.
F33IAM integration
Documents connection to enterprise/customer identity and access systems or federation. A generic API alone is insufficient.
F34Private / on-premises option
Documents private-hosted or on-premises server deployment of relevant components. Local device capture alone does not qualify.
Risk & compliance
Device / network risk
Uses device, network, IP, geolocation or related signals to assess risk. These signals do not establish a verified human.
F36Individual AML screening
Screens individuals against sanctions, PEP or related watchlists. Business screening is a separate field.
F37Ongoing individual screening
Monitors an enrolled person for later sanctions, PEP or related screening changes.
F38Packaged business verification
Offers a packaged company-verification workflow, beyond a standalone registry lookup. Scope may include ownership and officers.
F39Native transaction monitoring
Offers a dedicated transaction-risk monitoring product with rules, alerts or investigations. Authentication risk is not equivalent.
Sovereign deployment & privacy
Air-gapped operation
Runs the relevant verification service inside an isolated network without a required connection to external services.
F41Customer-managed signing keys
Lets the customer hold or manage keys used to sign identity or authorization records.
F42Customer-owned evidence
Assigns ownership and governance of the authorization evidence to the customer, with the provider acting as processor.
F43Revocable biometric reference
Allows an enrolled biometric reference to be disabled or purged so it cannot support future verification in that system.
F44Non-exportable biometric reference
Restricts export of a usable biometric reference outside the designated deployment boundary.
Authorization governance
Independently verifiable evidence
Produces a signed identity, authorization or signing record that can be verified independently of the originating application.
F46Two-person human authorization
Requires two distinct humans, each freshly verified, to authorize the same defined action.
F47Scoped human delegation to AI
Binds a verified human to a defined scope of authority delegated to an AI agent, with escalation when that scope is exceeded.
F48Revocable AI delegation
Withdraws a human-linked agent authorization so later actions requiring that authorization are prevented.
F49Fallback policy
Lets the organization define escalation or an alternative path when a verification cannot complete, while preserving the outcome.
Government identity
CAC-linked human enrollment
Establishes a reusable human biometric reference linked to a validated Common Access Card or equivalent government credential.
F51Fingerprint verification path
Provides infrastructure-based fingerprint identity verification for settings where cameras cannot be used. A device-local unlock alone does not qualify.
Security assurance
SOC 2 Type II attestation
An independent SOC 2 Type II report for the relevant entity and service, covering controls over a stated period.
F53ISO/IEC 27001 certification
A certified information security management system with an identified entity, edition and scope.
Healthcare
Independent testing
Independent PAD Level 1 test
Independent presentation-attack testing at Level 1 against ISO/IEC 30107-3 for the named component/version.
F56Independent PAD Level 2 test
Independent presentation-attack testing at Level 2 against ISO/IEC 30107-3 for the named component/version.
F57Independent face-match evaluation
A third-party evaluation of biometric matching performance for an identified algorithm/configuration.
F58Independent penetration testing
Documented external adversarial testing of the relevant application, SDK, service or infrastructure.
Platform controls & integration
Mobile driver license verification
Support for verifying compatible mobile driver license credentials, with applicable standards identified.
F60Customer-managed encryption keys
Customer management of keys protecting retained platform data or biometric templates.
F61Mobile runtime protection
Runtime application self-protection or documented equivalent capture-app integrity controls.
F62Signed result callbacks
Authenticated verification-result delivery with documented signature validation.
F63Separated service environments
Documented separation between production and nonproduction API/service environments.
F64Optional FIDO2 support
FIDO2 authentication or device-binding support alongside the reviewed offering.
F65Configurable verification thresholds
Documented ability to tune biometric or liveness decision thresholds by deployment or policy.
F66Passive liveness capture
Liveness verification without requiring scripted user gestures such as head turns or blinking.
F67HSM-backed identity operations
Documented use of a hardware security module in relevant identity, key or evidence operations.
F68Tamper-evident operational logs
Protected logging across relevant verification and downstream integration events.
F69Security evidence on request
Security documentation, audit evidence or testing materials available to qualified buyers.
F70Multispectral document checks
Supported document-security examination using compatible multispectral capture hardware.