Web App

In a web application, CLEAR is embedded through a partner-owned landing page. The entry point should always be a CLEAR button that launches the verification flow. Under the hood, that button uses one of the integration methods (Standard API, OIDC, or Out-of-the-Box).

How It Works

1. Landing Page with CLEAR Button

   • Your app displays a landing page where the user begins verification.
   • Include a CLEAR-branded button that triggers your backend to create a verification_session.
   • From that API call, pass the verification_session.token to your frontend.

   Example:

   HTML

   <button onclick="startClearVerification()">Verify with CLEAR</button>

2. CLEAR Hosted Flow

• When the button is clicked, your frontend directs the user to:

https://verified.clearme.com/verify?token=<VERIFICATION_TOKEN>

`

3. CLEAR securely collects identity documents, biometrics, and any configured checks.

4. Redirect Page (Partner UI)

• After verification, the user is redirected back to your app at the redirect_url defined when creating the session.
• The redirect page provides confirmation and guides the user to the next step.
• Always confirm verification status by calling the Get Verification Session API on your backend.

Best Practices

• Always start with a CLEAR button to make the user action explicit and consistent across flows.
• Keep branding clear — the button should be recognizable as CLEAR but styled to fit your app.
• Use Redirect + UUID (state) to safely correlate returning users to the correct session.
• Don’t trust redirects alone — always fetch results server-to-server before provisioning access or approving workflows.

Key Takeaway

• The CLEAR button is the anchor of the user experience in web apps.
• User clicks CLEAR button → Verification session created → CLEAR hosted flow → Redirect back → Results confirmed.
• This pattern ensures clarity for the user, security for your system, and consistency across all integrations.