Build User Journey

CLEAR’s verification flow is designed to slot into your application’s existing user journey. This section outlines the key stages and responsibilities before, during, and after CLEAR verification.

Pre-CLEAR Verification: Landing Page

• Owned by partner
• What it is: The page in your app where the user starts the verification process.
• What happens here:
  • Provide context — why verification is required, what the user should expect.
  • Display a CLEAR button that launches the verification flow.
  • Under the hood, your backend creates a verification_session and passes the token to your frontend.

✅

Best Practice: Keep branding consistent and clearly explain why identity verification is part of the flow.

Post-CLEAR Verification: Redirect Page or Terminal State

• Two options:
  1. Redirect Page (recommended for web/app flows)
     • User completes CLEAR and is redirected back to the redirect_url you defined when creating the session.
     • Partner confirms results via the Get Verification Session API.
     • Provides a seamless handoff back to your app.
  2. Terminal State (no redirect)
     • User completes CLEAR and remains on a CLEAR-branded confirmation page.
     • Partner must rely on webhooks or polling to detect completion and update downstream systems.

Successful UX

• What it is: The experience the user sees after successfully completing verification.
• Owned by partner
• Requirements:
  • Confirm the session outcome via API (don’t rely on redirect alone).
  • Grant access, provision accounts, or advance the workflow in your system.
  • Provide a clear success message (e.g., “You’re verified with CLEAR. Welcome back!”).

Failure UX

• What it is: The experience the user sees after failing verification.
• Owned by partner
• Requirements:
  • Confirm the failure via API.
  • Define a retry strategy (how many attempts, what triggers a new session).
  • Provide alternate paths (e.g., escalate to support, manual review, or fallback onboarding flow).
  • Ensure error messaging is clear but does not expose sensitive details about why verification failed.

Key Takeaway

• Partner-owned pages bookend the CLEAR experience: Landing Page (before) and Redirect Page or Terminal State (after).
• CLEAR handles the verification flow itself, but success and failure UX are always owned by the partner.
• Always confirm outcomes server-to-server via the Get Verification Session API before updating user state.