Skip to content

Documentation

VULT SECURITY DOCUMENTATION

Find the right section

Event and identity bound authorizations

Know who’s
behind the action.

Verify the actual human. Confirm their presence.
Bind their approval to the exact action.

VULT Security establishes identity through comprehensive document validation and a biometric match. Each authorization confirms the person against their established biometric profile and binds their explicit approval to the specific action.

Your systems. Your permissions. Their personal approval.

  1. Action

    Access employee records in the HR administration portal.

  2. Confirmation

    The person reviews, approves, and confirms their identity.

  3. Record

    Their identity and approval are linked to this access authorization.

Identity authority

The right information.
The actual person.

Knowing a password or possessing a device does not establish who is approving an important action.

Connect verified identity, biometric proof of presence, and explicit approval to the exact event.

Identity Authority

Identity and approval,
built into your systems.

Identity established. Presence verified again. This is the VULT Security difference.

A verified government-issued ID establishes the person’s identity. Biometric proof of presence confirms the same person whenever authorization is required.

Identity and approval bound to the exact action.

Connect the verified person’s identity and explicit approval to the specific action, change, or decision presented.

Verify identity without retaining ID images or face photos.

Your biometric profile protects your established identity. Organizations can choose verification without image retention, or configure retention to support their lawful collection and recordkeeping requirements.

Add VULT Security to your existing systems.

Keep your identity platform, permissions, and business workflows. Introduce verified-human authorization at the points where it matters.

Capabilities

Find the capability
your workflow needs.

Secure identity at enrollment. Confirm the person when they return. Bind their identity and approval to the exact action.

Identity Verification

Start with the actual person.

Establish a VULTid by binding comprehensive document validation to a matching biometric profile.

Identity Secured

Establish who’s behind the account.

Validate the identity document, match the person, and establish a VULTid for future identity checks and approvals.

Identity documentBiometric matchIdentity SecuredYour biometric profile now protects this identity.

What VULT Security does

  • Extracts information from supported identity documents.
  • Checks document authenticity and consistency.
  • Validates supported document information using the checks configured for your workflow.
  • Confirms the presenter’s identity through a biometric match.
  • Establishes a biometric profile that protects the verified identity.

Additional verification options

Depending on document, jurisdiction, and configuration:

  • Chip-enabled verification for supported electronic passports and identity documents.
  • Document information corroboration through supported third-party, domain-specific knowledge repositories.
  • Sanctions and politically exposed person screening through configured integrations.

Where it fits

Customer onboarding, workforce enrollment, marketplace participation, and VULTid enrollment.

What happens next

Future authorizations verify the person against the established identity. They do not require repeating the document check for every action.

Biometric Proof of Presence

Require the person to be present.

Confirm the person’s biometric presence when their identity is used to access a service or authorize an important action.

What VULT Security does

  • Confirms the person’s presence biometrically.
  • Requests the person’s participation for the verification event.
  • Matches their scan to their established biometric profile.
  • Connects the confirmation to the relevant request.

Where it fits

Enrollment, account access, privileged operations, payments, and sensitive approvals.

What your system receives

A verification outcome incorporating the required presence check.

VULTid presence checkVerifyingVerified

Presence confirmed biometrically

The person participates.
The event gets a result.

Presence confirmation supports the identity check for this request. It is not permission to act on a different request.

1:End Identity Continuity

One established identity. Connected to each authorization.

Connect the person’s established identity to subsequent verification and authorization events through their biometric profile.

Your biometric profile now protects this identity.

What VULT Security does

  • Establishes a biometric profile during enrollment.
  • Matches subsequent scans to that profile.
  • Confirms the person’s biometric presence.
  • Requires successful verification before accepting the person’s authorization.

Where it fits

Returning-user authentication and identity-bound approvals.

What your system receives

The verification outcome needed to continue the workflow, without receiving the person’s biometric profile.

Identity Confirmation

Know who’s requesting access.

Confirm the returning person against their established biometric profile.

Your organization continues to define what that person is permitted to access or do.

What VULT Security does

  • Verifies the returning person against their established identity.
  • Confirms identity against the person’s established biometric profile.
  • Supports verification through the person’s camera-enabled device.
  • Supports configured verification requests through push, SMS, QR, or web links.

Where it fits

Account access, privileged administration, sensitive records, and step-up authentication.

What your system receives

An authentication outcome that your application evaluates alongside its roles and permissions.

Age Verification

Confirm their age.
Protect their privacy.

Determine whether the verified person meets an age requirement without disclosing their full identity to the requesting organization.

Privacy-preserving age gating

Confirm eligibility.
Keep details private.

Your application can receive the age-threshold result without the person’s birth date or full identity details.

A person behind frosted privacy glass, with only an age-eligibility result shown in front
Age verified
21+Requirement met

What VULT Security does

  • Uses age information established through identity verification.
  • Confirms the person is present through biometric identity confirmation.
  • Returns the required eligibility result.

Where it fits

Age-restricted purchases, services, and digital experiences.

What your system receives

An eligibility result, such as meeting a 21-and-over requirement, without requiring disclosure of the person’s birth date.

Sensitive Actions & Approvals

Make consequential actions personal.

Require the verified person’s participation and explicit approval before your workflow proceeds.

What VULT Security does

  • Identifies the action requiring authorization.
  • Presents the relevant details.
  • Confirms the approving person’s identity and presence.
  • Binds their explicit approval to that action.
  • Preserves supporting authorization evidence.

Where it fits

  • Changes to payout instructions.
  • Sensitive account changes.
  • Release of protected information.
  • High-impact administrative actions.

What your system receives

An event-specific authorization outcome for evaluation against your organization’s policies.

Solutions

What do you need
to protect?

Bring verified-human authorization to the access, changes, and decisions that matter.

Identity Verification

Verify a customer before opening an account.

Authentication & Access

Confirm the person requesting access to employee records, a university portal, or a sensitive database.

Sensitive Actions & Approvals

Confirm the account owner approves a change to payout instructions or release of protected information.

Age Verification

Confirm the person meets an age requirement while limiting personal information disclosure.

Transaction Authorization

Know who approved
the exact transaction.

The amount, recipient, and relevant details belong to the authorization. A different transaction or a material change requires its own authorization.

Bank · Enterprise1 / 8

Open a request

The banker opens the selected wire request to review the details and send it to the customer.

Illustrative wire authorization: customer and bank administrator.

The complete workflow

From banker queue
to a protected record.

Review the customer and bank steps below. Each person approves the specific action before identity confirmation begins.

The QR scan opens the administrator’s request on a phone. Biometric identity confirmation follows their approval. The bank reports whether the transfer completed.

Review the details

Present the amount, recipient, and specific action for the person to review.

Confirm the person

Match their scan to their established biometric profile after they approve.

Record the outcome

Keep the identity, approval, event details, and bank-confirmed result connected.

A phone showing an illustrative wire authorization record and VULT Security verification

Specific approval

One approval.
One defined action.

Identity confirmation establishes who participated. Explicit approval establishes what they authorized. The protected record keeps those facts together.

Authorization and execution are separate results. Your systems determine whether the authorized action proceeds.

When both parties matter

Accountability
on both sides.

For workflows that require it, ask the sender and recipient to each confirm their identity and approve their part of the same event.

Their authorizations remain distinct and connected to the shared event. A bank administrator’s approval is a different role from a recipient’s confirmation.

Sender

Alex Morgan

Authorize sending $12,500

Identity Confirmed
Recipient

Jordan Lee

Confirm receipt details

Identity Confirmed
One event. Two authorizations.Illustrative example

Authorization Evidence

Know who
authorized what.

Confirmed identity and explicit approval, linked to the specific action in a protected authorization record.

Approval and execution are distinct.

The authorization record shows what was approved. Linked execution records establish what the system actually did.

Identity, the specific action, and explicit approval are connected in a protected record.

Who

The person whose identity was confirmed and who gave approval.

What

The specific event, relevant details, and recorded authorization outcome.

When and context

The time and associated context available for the event, including location signals where supported.

IP location and device-reported location are separate context signals. They support review and do not substitute for identity confirmation.

Reusability

Establish identity once.
Verify the person. Every time it matters.

Establish a VULTid with comprehensive document validation and a biometric match. Confirm the person against their established biometric profile for each important action.

Enroll once

  1. Person · VULTid

    Secure Your Identity

    Identity is secured by binding a comprehensive document validation to a matching biometric profile.

Repeat for every important action

  1. Enterprise · Application

    Define the action

    Your application specifies the transaction, change, or decision that requires authorization.

  2. Person · VULTid

    Verify the person

    The person reviews and approves the action, then confirms their identity with their pre-established biometric profile.

  3. Enterprise · Application

    Receive the result

    Your application receives the authorization outcome, with a protected record linking the confirmed identity, specific action, and approval.

Identity Confirmed. Every time it matters.Your scan matched your biometric profile.

Enroll once · Repeat for every important action

Identity Secured

Your biometric profile now protects this identity.

Identity Confirmed

Your scan matched your biometric profile.

Subsequent authorizations use the established identity. The workflow may require renewed document checks when its requirements change.

Integration

Add VULT Security.
Keep what already works.

Introduce identity-bound authorization alongside your existing identity platform, permissions, and transaction systems.

VULT Security

Confirm their identity.Capture their approval.

  • Identity Confirmed
  • Biometric profile matched
  • Explicit approval

Your existing system

Receive the result.Keep the protected record.

  • Authorization outcome
  • Linked to the specific action
  • Protected authorization record
VULT Security confirms identity and captures approval.

Match the person’s scan to their biometric profile and record their explicit approval for the specific action.

Your workflow receives the result.

Receive the authorization outcome and protected record. Continue, decline, or route the request within your existing workflow.

Your application requests authorization. VULT Security confirms the person and returns the outcome.

Your systems retain their roles

Continue managing accounts, roles, limits, and execution in your existing environment.

VULT Security confirms the person

Request identity verification, identity confirmation, or event-specific authorization at the relevant point in your workflow.

Your application receives the result

Use the returned outcome to continue, decline, or route the request. Retain its associated authorization record.

Signals Layer

Confirm the person.
Add the context that matters.

Configured screening layers supplement VULTid’s core document validation and biometric verification.

  1. Identity

    Identity confirmed

    Document validation and biometric confirmation establish the person.

  2. Context

    Required checks

    Screen the confirmed identity against configured third-party, domain-specific knowledge repositories.

  3. Record

    Results attached

    Log each screening result in the VULTid audit trail and attach it to its verification event record.

Domain-specific knowledge

Supported repositories can corroborate identity information or screen against relevant risk registries. Available checks depend on source access, jurisdiction, and configuration.

Document assurance

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.

Development

Connect verification
to the next action.

Define the person and the event. Receive an outcome your application can use.

Application programming interfaces and software development kits

Integrate supported verification and authorization workflows into your application.

Defined requests and results

Associate the request with the person and the exact event requiring approval.

Callbacks and webhooks

Connect supported workflow updates to your application’s next step.

Authorization evidence

Associate the outcome and available evidence with the relevant event in your system.

Request · Illustrative
Action
Access employee records
Resource
HR administration portal
Person
Jordan Lee
Result · Illustrative
Identity
Identity Confirmed
Approval
Recorded for this action
Record
Linked to the event

Security & Privacy

Your identity protected.
Your retention requirements respected.

Choose verification without retaining ID images or face photos, or configure retention to support lawful collection and recordkeeping requirements.

Image retention is a choice

Organizations can choose verification without image retention. Retention requirements are defined for the configured workflow.

A protected biometric profile

Your biometric profile protects your established identity and supports subsequent identity confirmation.

The result your organization needs

Receive the verification or authorization result and the attributes permitted by your configured workflow.

Identity confirmation and authorization evidence serve different purposes.

The biometric profile supports confirmation of the person. The authorization record preserves their connection to the specific approved event.

For technology leaders

Integrate identity and approval into the workflows you already operate.

For security leaders

Review identity assurance, data handling, retention choices, and authorization evidence.

Put the verified person
behind the decision.

Start with the action you need to protect.