Kiosk Integration Guide

CLEAR kiosks provide a platform for fast, in-person verification. This guide explains the end-user experience, how kiosk-to-mobile handoff works, and the requirements for deploying kiosks. Toward the end, we cover the configuration steps needed to enable kiosk projects in CLEAR.

End-User Experience

Kiosks are designed for existing CLEAR members who want to verify quickly and continue to their destination workflow (e.g., appointment check-in, hotel key pickup).

Fast sessions: Verification is streamlined, typically using selfie authentication (1FA). Partners may optionally enable step-up with 2FA (e.g., OTP + selfie).
No account creation: New account creation and document upload must not occur at kiosks — these flows should be completed on mobile.
Pre-registration encouraged: Partners should send pre-registration links (via email, SMS, or QR code) to allow account creation ahead of time.
Seamless outcomes: On success, users proceed directly to the partner’s defined “success” state (e.g., check-in complete).

User Flow

For existing CLEAR members:

User approaches kiosk and selects CLEAR verification.
CLEAR launches selfie authentication (1FA) or selfie + OTP (2FA, if enabled).
If successful, user is redirected to the partner’s completion flow.
If blocked or additional checks are required, kiosk triggers a kiosk-to-mobile handoff.

Kiosk-to-Mobile Handoff (Optional)

When a user cannot complete verification at the kiosk (e.g., enrollment, step-up):

CLEAR displays a handoff screen with a QR code and/or sends an SMS link.
User completes the required steps on their mobile device.
The kiosk session and mobile session are securely linked.
After completion, the user is redirected back to a partner-defined kiosk screen.

This ensures kiosks remain fast and lightweight, while still supporting advanced verification when needed.

Hardware Requirements

Kiosks must meet these minimum specifications:

Camera: Front-facing, 1080p minimum (4K preferred). Autofocus optional; fixed focus acceptable for 18–24" user distance.
Display: Touchscreen required, must accurately capture on-screen keyboard input.
Keyboard: Native keyboard or CLEAR’s virtual keyboard.
Connectivity: Persistent Wi-Fi or Ethernet required.

Browser & Software Requirements

CLEAR deploys to kiosks via a browser-based environment. Supported browsers include:

General Browsers

Chrome 64+
Edge 79+
Firefox 67+
Opera 51+
Safari 12+

Additional Browsers

Chrome for Android 70+ (Android 6+)
Chrome (Desktop) 70+ (TLS required)
Edge 70+
Firefox for Android 70+
Firefox (Desktop) 70+
Safari for iOS 14+
Chrome/Firefox for iOS 14.4+
Samsung Internet Browser 7.2–8.2 and 9.2+

Privacy & Session Handling

Session isolation: Each kiosk session must reset before a new user begins.
Exit handling: Provide either an Exit button or an inactivity timeout.
Sensitive data: Selfies and PII must not persist on the device after the session ends.

Project Configuration

To enable kiosk workflows, partners must configure two CLEAR projects:

1. Pre-Registration Project

Purpose: Allow new users to create a CLEAR account before arriving at the kiosk.
Delivery: Links sent via SMS, email, or QR code.

2. Kiosk Project

Purpose: Handle fast, in-person verification at the kiosk.
Configuration options:
- Enrollment support: Block or redirect to mobile
- Step-up support: Block or redirect to mobile
- Exit button: Optional (recommended if no inactivity timeout is set)
- Virtual keyboard: Enable if native keyboard is unavailable
- Redirect URLs: Define for complete, blocked, exited, and mobile handoff events

Key Takeaways

Kiosks are a platform for fast, in-person verification — keep them streamlined.
End-user experience comes first: fast 1FA/2FA verification, with mobile handoff for complex cases.
Partners must meet hardware and browser requirements before configuration.
Two projects are required: one for pre-registration and one for kiosk verification.