How Lynk Verification Works

A practical verification flow for platforms, contractors, and trust-sensitive in-person interactions.

Choose your role

Platform/Marketplace Flow

Embed Lynk into vendor onboarding and dispatch rules.

Set policy rules and callback endpoints for your platform.

Contractors complete verification during onboarding.

Only verified providers can accept protected jobs.

Allow/deny actions are recorded for compliance and trust.

Technical integration

Direct server-to-server verification checks with policy control.

Best for custom platforms, partner apps, and internal tooling.

Flow breakdown

Create client credentials and approved redirect URIs using developer registration.

Trust Lynk issuer + JWKS

Load discovery metadata and verify signatures with JWKS for token validation.

Read verification claims

Use ID token or UserInfo claims like verification_status and lynk_verified in your policy.

Enforce runtime decisions

Allow, deny, or hold flows based on verified/pending/requires_input in real time.

Key endpoints

POST /api/oauth/developer-register

GET /.well-known/openid-configuration

GET /.well-known/jwks.json

GET|POST /api/oauth/userinfo

Use the discovery document at /.well-known/openid-configuration as the source of truth for endpoint and claim support.

This is a live trust-status verification workflow designed for real-time checks.
This can be combined with provider-based onboarding checks and runtime policy decisions.
This is not a blanket replacement for jurisdiction-specific government ID requirements.

Start in sandbox, move to production, and scale by verification volume.