Wallette Identity
Wallette Identity is an end-to-end identity verification platform that lets operators design verification journeys visually, run them at scale, and review every outcome with full evidence. This guide is for the people who use the Identity Portal — verification operators, compliance officers, fraud analysts, and the workflow designers who shape how applicants are verified.
If you are integrating an SDK or calling the API, see the Get Started and API sections instead.
Accessing the portal
The Identity Portal is available at two URLs:
| Environment | URL |
|---|---|
| Production | portal.identity.wallette.io |
| Staging | portal-staging.identity.wallette.io |
Sign in with your tenant-scoped operator account. Your role determines which areas of the portal you can access — see your administrator if a menu item is missing.
Explore the essentials
Document suite
The document tasks — capture, validation, verification — what they do, what they output, what to branch on.
Biometric suite
The face tasks — capture, validation, matching, verification — how they bind a person to a document.
Workflows
The verification journeys you design, version, and publish.
Workflow editor
The visual canvas for building and changing verification logic.
Task reference
Every task type — what it does, what it outputs, what you configure.
Sessions
Live and historical verification runs, filters, and statuses.
Session detail
Reviewing a single session — timeline, inputs, outputs, and cases.
How verification works in Wallette
Verification in Wallette Identity is workflow-driven. A workflow is a directed graph of small, focused tasks — capture a document, validate its quality, match a face, branch on a result. When an applicant starts verification, the platform creates a session that runs through that workflow from start to finish, recording every step and its inputs and outputs along the way.
A finished session lands on a terminal status — typically APPROVED, REJECTED, EXPIRED, or queued for REVIEW — and produces an evidence trail you can replay in the portal or hand to auditors.
Terminology
The rest of these docs use these terms consistently:
Session — one verification attempt for one applicant, running one specific workflow version end to end.
Workflow — a named verification journey. Workflows have one or more versions, of which exactly one is active at a time.
Workflow version — an immutable snapshot of a workflow's logic. New sessions always run against the active version.
Task — a single step inside a workflow (e.g. Document Capture, Face Matching, Approve). Tasks are the building blocks of a workflow.
Task definition — the type of a task (e.g. face-capture). Every
task placed in a workflow is an instance of a task definition.
Condition — a logic task that routes the session into one of several branches based on previous task outputs.
Branch — one possible path out of a condition. The first branch whose IF clause matches is taken; otherwise the else branch runs.
Applicant — the person being verified.
Case — an investigation record attached to a session for manual review, escalation, or audit.
Tenant — the customer-facing organization a session belongs to; sessions are tenant-scoped.
Where things live in the portal
| Area | What it's for |
|---|---|
| Operations → Sessions | Watch live and historical verification runs |
| Operations → Workflows | Browse, create, and version verification journeys |
| Operations → Cases | Triage sessions that need manual review |
| Operations → Applicants | Look up people across sessions |
| Configure | Themes, counters, task providers, PDF templates |
This guide focuses on Sessions and Workflows — the two areas where most operator work happens. Other areas are covered separately.