Overview
The Form module consists of 13 screens that guide users through the verification flow. Each screen emits events following a consistent naming pattern.Event Naming Convention
All screen events follow the pattern:form:welcome:ready, form:review:success, form:result:pending
Event Stages
| Stage | Description | Emitted By |
|---|---|---|
ready | Screen is ready to be displayed | All screens |
loaded | Screen has been rendered and is interactive | All screens |
failed | Screen failed to load or an error occurred | All screens |
success | Action completed successfully | review, result, doc_upload |
partial | Partial verification result | review, result |
pending | Verification pending review | review, result |
back | User navigated back from screen | document |
navigate | User navigated to another screen | document, doc_upload |
Event Payload
All screen events emit anEventPayload object:
Screen Reference
All examples below assume the SDK has been initialized:
Welcome
The first screen shown to users. Introduces the verification process and provides a call-to-action to begin. Screen ID:welcome
Events:
| Event | Description |
|---|---|
form:welcome:ready | Welcome screen is ready to display |
form:welcome:loaded | Welcome screen has been rendered |
form:welcome:failed | Welcome screen failed to load |
Start
Entry point screen for certain flows. Allows configuration of the initial verification step. Screen ID:start
Events:
| Event | Description |
|---|---|
form:start:ready | Start screen is ready to display |
form:start:loaded | Start screen has been rendered |
form:start:failed | Start screen failed to load |
Consent
Collects user consent for identity verification and data processing. Screen ID:consent
Events:
| Event | Description |
|---|---|
form:consent:ready | Consent screen is ready to display |
form:consent:loaded | Consent screen has been rendered |
form:consent:failed | Consent screen failed to load |
Document Selection
Allows users to select which identity document(s) they want to use for verification (e.g., driver’s licence, passport, national ID, Medicare card). Used in manual and doc_upload flows.In OCR mode, the Document Selection screen is a legacy feature tied to headless OCR flows. Modern integrations use the IDV flow for document capture and the form Review screen to display extracted data.
document
Supported Document Types:
DRIVERS_LICENCE- Driver’s licencePASSPORT- PassportNATIONAL_ID- National identity cardNATIONAL_HEALTH_ID- National health ID / Medicare card
| Event | Description |
|---|---|
form:document:ready | Document selection screen is ready |
form:document:loaded | Document selection screen has been rendered |
form:document:failed | Document selection screen failed to load |
form:document:back | User navigated back from filling document detail to document selection |
form:document:navigate | User selected a document and is navigating forward |
Personal Details
Collects personal information such as name, date of birth, and address. Screen ID:personal
Events:
| Event | Description |
|---|---|
form:personal:ready | Personal details screen is ready |
form:personal:loaded | Personal details screen has been rendered |
form:personal:failed | Personal details screen failed to load |
Review
Displays collected data for user review before submission. After review, submits the data for verification. Emits result-stage events based on verification outcome. Screen ID:review
Events:
| Event | Description |
|---|---|
form:review:ready | Review screen is ready to display |
form:review:loaded | Review screen has been rendered |
form:review:failed | Entity doesn’t pass verification |
form:review:success | Verification completed successfully |
form:review:partial | Partial match - some data verified, some needs attention |
form:review:pending | Verification submitted but result is pending |
Loading
Displayed while verification is being processed. Screen ID:loading
This screen is managed internally by the form module and typically does not require event handling.
Result
Displays the final verification result to the user. Shows success, failure, partial match, or pending status. Screen ID:result
Result States:
| State | Description |
|---|---|
SUCCESS | Verification passed |
FAIL | Verification failed |
PENDING | Verification pending manual review |
PARTIAL | Partial match - some checks passed |
UPLOAD_SUCCESS | Document upload completed |
UPLOAD_FAIL | Document upload failed |
PROVIDER_ERROR | Provider encountered an error |
| Event | Description |
|---|---|
form:result:ready | Result screen is ready to display |
form:result:loaded | Result screen has been rendered |
form:result:failed | Result screen failed to load |
form:result:success | Verification completed successfully |
form:result:partial | Partial verification result |
form:result:pending | Verification pending review |
Retry
Shown when verification returns a partial result and the user can retry. Allows re-entry of data that failed verification and intelligently adapts the retry flow based on the type of failure. Screen ID:retry
Events:
| Event | Description |
|---|---|
form:retry:loaded | Retry screen mounted |
form:retry:ready | User completed the retry form |
form:retry:failed | Retry screen failed to load |
Smart Retry Behavior
The Retry screen intelligently adapts based on the type of verification failure. When verification returns a partial match, the SDK analyzes the failure type and presents the appropriate retry flow.Previous Address Request
Previous Address Request
Triggered when: Verification returns a
partial alert on personal details (e.g., address could not be confirmed against records).What happens: The Retry screen displays the personal details form with an additional toggle asking “Have you been at your current residential address for less than 6 months?” When the user enables this toggle, a previous address field appears prompting them to enter their prior residential address.Purpose: Helps resolve address verification failures by providing additional residential history that the verification provider can use to confirm the user’s identity.Additional ID Request
Additional ID Request
Triggered when: Primary ID verification fails with a
404 alert (e.g., the submitted document could not be verified against records).What happens: The Retry screen displays additional document types that have not been submitted yet, prompting the user to select and fill in an alternative form of ID. Documents already submitted are filtered out from the selection list.Purpose: Provides a fallback path when the initial document cannot be verified, allowing the user to supply a different identity document for verification.- Initial verification is submitted from the Review screen
- Verification returns a partial result (via
partialor404alert) - The SDK determines the failure type: personal details failure (
VERIFICATION_FAILED_IDS.NAME) or document failure (VERIFICATION_FAILED_IDS.ID) - The Retry screen presents the appropriate fields based on the failure type
- The user provides additional information (previous address or alternative ID)
- The flow transitions to the Review screen for re-submission
Document Upload
Main document upload screen for uploading supporting documents. Screen ID:doc_upload
Events:
| Event | Description |
|---|---|
form:doc_upload:ready | Upload screen is ready |
form:doc_upload:loaded | Upload screen has been rendered |
form:doc_upload:success | Document uploaded successfully |
form:doc_upload:failed | Document upload failed |
form:doc_upload:navigate | User navigated from upload screen |
Required Document Upload
Displays documents that are required for verification and must be uploaded. Screen ID:required_document_upload
Events:
| Event | Description |
|---|---|
form:required_document_upload:ready | Required upload screen is ready |
form:required_document_upload:loaded | Required upload screen has been rendered |
form:required_document_upload:failed | Required upload screen failed to load |
Partial Document Upload
Displays a list of documents where a minimum number must be uploaded (e.g., “upload at least 2 of these 4 documents”). Screen ID:partial_document_upload
Events:
| Event | Description |
|---|---|
form:partial_document_upload:ready | Partial upload screen is ready |
form:partial_document_upload:loaded | Partial upload screen has been rendered |
form:partial_document_upload:failed | Partial upload screen failed to load |
Optional Document Upload
Displays optional documents that users can upload to strengthen their verification. Screen ID:optional_document_upload
Events:
| Event | Description |
|---|---|
form:optional_document_upload:ready | Optional upload screen is ready |
form:optional_document_upload:loaded | Optional upload screen has been rendered |
form:optional_document_upload:failed | Optional upload screen failed to load |