ONBOARDING
Onboarding built
on explainable
trust.Onboarding
built on
explainable
trust.
Verified claims, bounded access, reviewable decisions. Verification is a contextual input to authorization—never a substitute for it.
What is verified
onboarding?
Verified onboarding uses organization and identity evidence to inform access decisions while keeping verification, authentication, and authorization as separate evaluations.
Key principle: Verification output is a qualified input to a broader trust decision. Verification success does not automatically grant access or assume authority.
Verification alone
is insufficientVerification alone is insufficient
Verification ≠Authentication
Proof that John Smith is a real person doesn't prove that the person logging in right now is John Smith. Authentication requires live identity check.
Verification ≠Authorization
Proof that a company exists doesn't grant its employees access to your resources. Authorization requires separate policy evaluation.
Verification ≠Approval
Successful verification is evidence, not permission. A person or team must review and explicitly approve access to your system.
Distinct actors &
rolesDistinct actors & roles
Applicant
Person or organization submitting claims. Provides evidence (documents, credentials, contact info).
Verifier
System or service validating claims. Checks against databases, registries, and authoritative sources.
Reviewer
Person evaluating verification output. Decides approve/deny. Owns the decision.
Relying Party
Your application. Receives verification result. Applies access policies based on verified claims + org policy.
Organization
Customer entity. Controls membership, can revoke or suspend applicant access anytime.
Auditor
Reviews decision logs and evidence trails. Ensures compliance, fairness and auditability.
Five-step
verification journeyFive-step verification journey
Submit
Applicant provides identity and/or organization claims.
Verify
Claims checked against authoritative sources and evidence.
Review
Human or policy-driven review of verification output.
Decide
Approve, deny, or request additional information.
Grant
If approved, access granted with scope and expiry.
Verification
outcomes & freshnessVerification outcomes & freshness
Verified
Claims validated against authoritative source. Evidence current and matches applicant assertions.
Needs Review
Verification inconclusive or partially successful. Human review required before decision.
Unable to Verify
Claims cannot be validated. Method unsupported, registry unavailable, or evidence insufficient.
Stale / Outdated
Verification older than policy threshold. Re-verification required to proceed.
Revoked
Previously verified claim invalidated. Organization or applicant revoked permission or status changed.
Proof & Freshness
Every verification result includes: Issuer (who verified), Evidence (what was checked), As-of timestamp (when checked), Expiry (when trust expires), Scope (what claim is supported). Never assume universal coverage.
Stale / Outdated
Verification older than policy threshold. Re-verification required to proceed.
Needs Review
Verification inconclusive or partially successful. Human review required before decision.
Verified
Claims validated against authoritative source. Evidence current and matches applicant assertions.
Unable to Verify
Claims cannot be validated. Method unsupported, registry unavailable, or evidence insufficient.
Revoked
Previously verified claim invalidated. Organization or applicant revoked permission or status changed.
Proof & Freshness
Every verification result includes: Issuer (who verified), Evidence (what was checked), As-of timestamp (when checked), Expiry (when trust expires), Scope (what claim is supported). Never assume universal coverage.
Proof inputs &
evidence typesProof inputs & evidence types
Government ID Verification
Government-issued ID matched against national registry. Scope varies by country.
Government ID Verification
Government-issued ID matched against national registry. Scope varies by country.
Biometric Verification
Facial recognition or liveness check... Not yet available.
Biometric Verification
Facial recognition or liveness check... Not yet available.
Business Registry Lookup
Company verified against official business registry. Covers major jurisdictions.
Business Registry Lookup
Company verified against official business registry. Covers major jurisdictions.
Email Domain Verification
Confirms corporate email or domain ownership... Instant verification.
Email Domain Verification
Confirms corporate email or domain ownership... Instant verification.
Phone Number Verification
SMS or voice code verification... Supports most regions.
Phone Number Verification
SMS or voice code verification... Supports most regions.
Financial Account Verification
Bank account or payment details verified. Subject to banking partner availability.
Financial Account Verification
Bank account or payment details verified. Subject to banking partner availability.
Regional & method variability: Not all methods are available in all regions. Coverage depends on local regulations, registry availability, and platform integrations. Check capability status before designing flows.
Authority &
access boundaryAuthority & access boundary
Verified claims inform, but don't grant, access
Verified claims inform, but don't grant, access
Verification as evidence
Input to the access decision
Org policy decides access
Role, scope, time limits
Continuous trust re-evaluation
Expiry, revocation, status changes
Human review &
remediationHuman review & remediation
Manual Review Workflows
Team can review inconclusive verifications. See evidence, ask questions, request additional info or docs.
Resubmission & Remediation
If verification fails, applicant can address issues and resubmit. Clear explanation of what was needed.
Denial Explanations
If rejected, applicant receives reason (without revealing fraud detection rules). Path to appeal or escalate.
Appeal & Escalation
Applicant can request human review of decision. Your team can appeal to verification partner if evidence incorrect.
Accessible Alternatives
If automated method fails, accessible alternative (phone call, video, in-person) available. No one locked out permanently.
Decision Audit Trail
Every decision logged: who decided, when, based on what evidence, and why. Immutable record for compliance.
Architecture &
integrationArchitecture & integration
API first integration
REST API
Start verification, check status, submit remediation
Webhooks
Real-time notifications on status change
SDKs
JavaScript, Python, Node, p8/branca available
No invented endpoints. Available APIs and SDKs shown here reflect released and tested implementations. Planned capabilities marked 'Planned' — do not assume availability. Check live documentation for current status and tested regions.
Lifecycle &
continuous trustLifecycle & continuous trust
Initial Grant
Verification approved, access granted with scope, role, and expiry set.
Monitoring
Ongoing checks: membership, organization status, verification freshness, anomalies.
Re-verification
Periodic or event-driven re-verification. Update evidence. Extend or deny access.
Revocation
Organization or your team can revoke immediately. Sessions terminated. Logged.
Privacy, security
& fairnessPrivacy, security & fairness
Minimal Data Collection
Only essential fields gathered. No unnecessary personal data. Verification data segregated from CRM data.
No Identity Documents on Web
Government IDs, passports, selfies never transmitted or displayed. Verified in secure backend. Never stored on public page.
Least Privilege Access
Verification result shared only with decision-makers. Analytics exclude PII and verification details.
Bias & Fairness Review
Verification outcomes monitored for demographic bias. Manual review process transparent and auditable.
Data Subject Rights
Applicants can request data access, correction, or deletion. Right to appeal decisions. Compliant with regulations.
Automatic Purge
Verification data deleted after retention period unless approval granted. Clear data retention policy.
Verified
onboarding use casesVerified onboarding use cases
Enterprise Onboarding
Verify customer companies before granting account access. Confirm business registry status, leadership identity, and corporate email.
Partner Verification
Onboard resellers, integrators, or affiliates. Verify identity and company before granting API access or partner portal.
Compliance Onboarding
Satisfy KYC/AML and regulatory requirements. Verify identities and organizations before payment or data access.
Frequently asked
questionsFrequently asked questions
Is verification the same as authentication?
No. Verification proves a claim about identity or organization (e.g., 'this person is real' or 'this company exists'). Authentication proves the person acting right now is that person (e.g., with a password or passkey). Both are inputs to authorization.No. Verification confirms claims (such as legal business registry, identity documents, or credentials), while authentication confirms who is currently signing in. Verification serves as a contextual input to authorization, not a substitute for active session authentication.
Does verification automatically grant access?
No. Successful verification is evidence, not permission. An organization or designated reviewer must evaluate the evidence against access policies and explicitly approve or deny access.
What countries/regions are supported?
Support varies by verification method. Business registries and government ID coverage depend on local jurisdictional registries, regulatory availability, and verified partner integrations. Capabilities marked 'Select Regions' require regional check.
Can we revoke access if verification fails later?
Yes. Access is continuously monitored. If a business license expires, an applicant leaves the organization, or credentials are invalidated, access can be revoked immediately, terminating active sessions and recording the event in the audit log.
How long is verification data retained?
Verification data follows strict data minimization and retention policies. Document artifacts and sensitive data are automatically purged after the retention window unless explicitly required for compliance.
What if verification fails or is inconclusive?
Inconclusive or failed verifications enter a human review and remediation workflow. Applicants receive clear explanations (without exposing fraud detection heuristics) and can appeal, resubmit evidence, or use accessible alternative methods.
Onboarding built
on trust you can
explain.
Onboarding built on trust you can
explain.
Verified claims, reviewable decisions, and continuous monitoring—without treating verification as automatic approval.