1. Account
  2. What to scan
  3. Consent
  4. Payment
  5. Scan
  6. Confirm it is you
  7. Report

One last check before we open your report

Your scan is finished. Before it opens, we confirm that you are the person it is about.

Confirm the phone on your account

A report like this one is a map of somebody. Handing it to whoever typed their name into a form would make it a tool for finding people, which is the opposite of what it is for.

You verified this phone when you made your account. We just texted it a code. Enter it to confirm the identity the scan ran on is yours.

Mock: any 6 digits work.

Mock: this code confirms nothing. It stands in for the phone OTP the real check sends.

Design note, SCO-26 / concierge launch. This check gates the report rather than signup, because the design answer is to gate the aggregated output rather than the individual lookup. For the concierge launch it is a second phone OTP: email and phone are verified at signup, and the phone is confirmed again here before the report opens.

The stronger biometric-ID gate (wallet mDL first, vendor face-match as fallback) is deferred and is not part of this launch. The surrounding flow is written against “a check happens here”, so if that gate is added later this is the file that changes.