UnifyIDDeveloper

Solution patterns

Use UnifyID across real products

Combine authentication, verified claims, document access, consent, and lifecycle events according to the decision your product actually needs.

Consumer and workforce experiences

Account access

Verified sign-in

Authenticate a known person with openid profile email identity_verified. Store the pairwise subject, not email, as the account link.

Marketplace

Trusted participants

Confirm identity and age while letting buyers, sellers, hosts, drivers, or freelancers share only approved information.

Workforce

Employee onboarding

Establish the person behind a new employee record before issuing internal access or beginning regulated screening.

Financial and regulated products

Use caseRecommended informationOperational event
Cross-border accountlegal_name nationality identity_verified identity_documents document_validityStop processing after consent.revoked.
Age-restricted productage_over_18 identity_verifiedReauthorize when assurance becomes stale.
Document-backed accountidentity_documents document_type document_issuing_country document_verifiedRevalidate only when policy or risk requires it.
High-value recoveryopenid identity_verified liveness_verified face_match_verifiedCreate a separate high-assurance authorization transaction.

Education and opportunity

Scholarship, examination, and admissions platforms can establish eligibility before collecting a long application. Prefer age_over_18 over an exact birth date, and request nationality only where the programme genuinely depends on it.

scope=openid profile email legal_name age_over_18 nationality identity_verified identity_documents document_type
purpose=Assess eligibility for an international scholarship

Travel, mobility, and hospitality

Use document summaries to confirm that an approved travel document is verified and active. Retrieve a masked identifier unless the complete value is legally necessary and your Production application has received restricted-scope approval.

Healthcare and sensitive services

Use UnifyID to link a verified person to your internal patient or member record. Do not place medical information in OAuth purposes, webhook metadata, public profiles, or identity claims.

Developer and enterprise workspaces

Authenticate workspace members through UnifyID, then apply your own organization roles and least-privilege authorization. Identity proof answers who the person is; your application still decides what that person may do.

Reusable decision patterns

01Define the decision
02Choose minimum scopes
03Explain the purpose
04Handle revocation
05Delete when no longer needed

Do not confuse identity with authorization

Select an integration

Use Hosted UnifyID for the fastest secure implementation, the component for an embedded entry point, or the OAuth API for complete transaction control.

Was this page helpful?
UnifyID Developer Documentation · Version V.1 · Updated July 2026