
Certainty made Simple.
Discover the architecture below
On this page
Enrollment
Establish who someone is. VULT Security checks a supported government-issued ID and connects it to the live person presenting it, creating the verified identity that future authentication and authorization checks reference.
Verification
Confirm it’s still them. VULT Security checks the returning person’s identity and live presence for account access, explicit action approval, or age eligibility. Your application uses the result alongside its existing permissions and policies.
Verification record
Review who approved what. For action approvals, VULT Security preserves a protected record connecting the verified person, their live participation, and their approval to the specific action. That context supports later reviews, investigations, and authorization audits.
Enrollment
Establish the identity.
Enrollment establishes the verified identity that future authentication, consent and authorization checks reference. VULT Security connects a supported government-issued ID to the live person presenting it, providing a foundation for customer onboarding, workforce enrollment, marketplace participation, and VULT Security enrollment.
Verify the document.
VULT Security extracts information from the ID and checks its authenticity and consistency. It reads available machine-readable information, including supported machine-readable zones (MRZ) and barcodes, to help establish the identity represented by the document.

Match the person.
Biometric proof of presence helps confirm that the person presenting the ID is its rightful holder. VULT Security then establishes a protected facial biometric template associated with that verified identity.

Additional verification options.
Supported repositories can corroborate identity information or screen against relevant risk registries. Available checks depend on source access, jurisdiction, and configuration. Supported chip-verifiable documents and additional document sources can provide further assurance where your workflow requires it. Required screening is completed before the Proof of Presence token is issued to the relying application. Identity confirmation, screening outcomes, and the event stay connected for review.
Verification
Verify the returning person.
When someone returns, VULT Security performs it’s proprietary biometric proof of presence to match against their enrolled biometric template. Matching compares the fresh capture with the protected template associated with the person’s established identity. The device captures the interaction, while VULT Security performs biometric verification server-side.
Verify for access.
VULT Security verifies who is requesting to sign in and returns an authentication outcome. The same verification can support additional checks during a session, including access to sensitive records or privileged administration.

Verify for approval.
For actions configured to require VULT Security authorization, an active session alone is not enough. VULT Security presents the action’s relevant details and requires the person to complete a fresh verification and explicitly approve it. Their approval is tied to that specific action, and VULT Security returns an event-specific authorization outcome.
This can support changes to payout instructions, sensitive account changes, the release of protected information, and high-impact administrative actions.

Confirm eligibility while preserving privacy.
VULT Security uses age information established during enrollment and a fresh verification to confirm whether the person participating now meets an age requirement. Your application receives the eligibility result, such as confirmation that someone is 21 or older, without requiring disclosure of their birth date or full identity. This supports age-restricted purchases, services, and digital experiences.
Fits inside your existing workflow.
Your organization determines where verification is required and which actions need explicit approval. Verification requests can be delivered through configured push notifications, SMS, QR codes, or web links.
Your application receives the relevant authentication, eligibility, or authorization outcome without receiving the person’s facial biometric template. It evaluates that outcome alongside its existing roles, permissions, and policies to determine what the person may access or do and whether the workflow proceeds.
Verification record
Review the verification record.
For action approvals, VULT Security preserves supporting authorization evidence in a protected record. This gives your organization context to examine an approval for review or further support behavioral analysis algorithms.

The person connected to the action.
The record connects the verified person’s identity and confirmation of their live participation with the specific action, its relevant details, and their explicit approval.
Ready for review.
Your organization can refer to this record during internal reviews, investigations, disputed approvals, and authorization audits. The preserved context helps reviewers examine the authorization beyond its outcome alone, including what the person was asked to approve.
Approval and completion are separate.
The record documents the person’s authorization. It does not, by itself, confirm that the action was completed. Your application determines whether the authorized action proceeds.
Certainty made Simple.
Bring effortless verification to the people your organization depends on. Let’s explore how VULT Security can work for your customers, employees, and partners.
