Result Outcomes and Delivery
When a user completes a verification through a VerifyFlow hosted page or a direct API call, VerifyHuman produces a result. This page explains what outcomes mean, how results are delivered, and what you are responsible for.
Verification outcomes
Every verification produces one of these outcomes:
| Outcome | Meaning |
|---|---|
| Verified / Pass | The verification criteria were met |
| Not verified / Fail | The verification criteria were not met |
| Pending | The result is awaiting a manual review step (applies to some identity flows) |
| Error / Inconclusive | The verification could not be completed (e.g. image quality too low, user did not complete the flow) |
What determines an outcome
- For human presence checks: liveness and bot-signal detection
- For age checks: estimated age against your configured minimum age threshold
- For identity checks: selfie-to-ID match and document validity
- For trust review: structured screening signals from the screening layer, classified as
clear,review, orhigh_risk_review— not a pass/fail compliance decision
VerifyHuman produces a signal. Your application or team decides what to do with it.
Confidence levels
Human presence and age assurance results include a confidence level (0–100) alongside the outcome. This represents how confident the system is in the result.
Confidence is capped at 99.9% — no result ever claims 100% certainty.
How results reach you
Dashboard
All results appear in your VerifyHuman dashboard under Results / Verifications. You can filter by date, outcome, and verification type.
Decision-only (default)
By default, VerifyFlow delivers decision-only results — the pass/fail outcome and confidence level, with no personally identifiable information (PII) included in the notification. This is the lowest-risk delivery mode and is on by default.
Non-PII summary notification
On eligible plans, you can configure VerifyFlow to send a non-PII summary notification — for example, "Verification completed: pass, confidence 97.1%." This includes no raw biometric data, no ID document contents, and no name or date of birth from the submitted documents.
Secure package delivery (where configured)
On eligible plans, VerifyFlow can deliver a secure encrypted package containing the full verification report to a configured delivery target (email, S3, or SFTP). The package is encrypted and password-protected. The decrypt password is delivered separately through a secure link — never in the same email as the package.
If you request full package delivery, you are responsible for:
- Handling and storing the decrypted package securely
- Complying with applicable data protection laws (GDPR, CCPA, and others)
- Limiting who has access to decrypted verification results
- Disposing of PII in line with your data retention policy
VerifyHuman's platform invariant: biometric media (selfie images, ID photos) is not retained after a verification completes. The package contains the verification result, confidence scores, and where applicable, extracted identity data — not raw images.
Webhooks
VerifyHuman can send webhook events to your configured endpoint when a verification completes. Webhook payloads use HMAC-SHA256 signing. See Webhooks documentation for payload structure and signature verification.
Result data and privacy
VerifyHuman is designed with a privacy-first architecture:
- Biometric media is not stored — selfie images and ID photos are processed to produce a result and then discarded
- Decision-only mode is the default — no PII travels outside the verification session unless you configure a delivery mode that includes it
- You choose the delivery mode — VerifyHuman gives you control over what result data you receive and how
For a full description of the privacy and data handling architecture, contact support or review your data processing agreement.
Test results
If a user completes a verification on a test hosted page, the result is labeled as a test in your dashboard. Test results:
- Are kept in a separate section from live results
- Do not consume live credits
- Are produced by simulated verification logic, not real AI processing
Do not use test results to make real decisions about users.
Frequently asked questions
Can I receive both a dashboard result and a webhook?
Yes. Dashboard visibility is always on. Webhook delivery is additive — configure your webhook endpoint in the dashboard and events will be sent there.
What happens if a user abandons the verification without finishing?
An incomplete verification does not produce a result record. Only completed attempts (pass or fail) create a result entry.
Does VerifyHuman make a compliance decision for me?
No. VerifyHuman produces a verification signal. Your team or application is responsible for deciding what to do with the result. This applies especially to trust review (VerifyTrust), where VerifyHuman returns screening signals — not final compliance decisions.
How long are results retained?
Result records (the outcome, timestamp, and confidence score) are retained in your dashboard according to your plan's retention period. Raw biometric media is never retained. Contact support for retention details specific to your plan.