Docs
Introduction
Remote identity verification as a platform: documents, faces, compliance and the tools to run them.
What the platform is
NeuroVision is an identity verification platform. A user shows a document, takes a selfie and follows a short liveness step. The platform reads the document, checks it for fraud, matches the face and confirms a live person. International AML screening can run in the same flow. See the platform overview.
Concepts
- Scenario. The recipe for a verification: its steps, documents, countries, thresholds and rules. You build scenarios in the no-code editor, and each has an identifier.
- Session. One verification of one user, created from a scenario. A session has a status and a list of results, one per step.
- Widget. The branded web screen your user sees. It runs in desktop and mobile browsers in 29 interface languages. See the web SDK.
- Results. The outcome of each step, read through the API.
- Webhooks. Four events that tell your backend when a session, questionnaire, database check or erasure completes. See webhooks.
- Dashboard. Session log, export, manual decision, roles, statistics and costs, plus API tokens and the IP allowlist.
How a request flows
- Your backend creates a session through the REST API.
- Your page opens the widget for that session.
- The user completes the steps.
- Your backend reads the result, or receives a webhook.
Where to go next
- The quick start walks through the five steps.
- Authentication explains token types.
- Session statuses lists every status.