The user photographs a government-issued ID and records a short selfie video in their phone's browser. KayWhySee checks the document, liveness and face match server-side, and each session ends with an outcome and reason codes.
Captures are encrypted on upload. Your servers never receive ID images.
link Start here
link Three ways to start a verification
| Way | Best for | Code needed |
|---|---|---|
| The API | Sign-up and onboarding flows in your product | One server-side call |
| A verify button | Websites and landing pages | A script tag |
| A hosted link | Email, chat and support teams | None |
link How it fits together
You start a session
Your server asks for a verification for one of your customers, using your own reference for them. You get back a start_url.
Your customer verifies on their phone
They open the link. On a computer they scan a QR code to carry on on their phone. They agree to the check, photograph their ID and record a short selfie.
You get the decision
The session moves to clear, consider or rejected. Read it from the API or have it sent to your webhook.
Early access
KayWhySee is in early access. The capture flow, the API on these pages and the document's consistency checks work today. Forensic, face and liveness checks are being added one by one; until they land, finished sessions stop at submitted.