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.
Screen ID:documentSupported Document Types:
DRIVERS_LICENCE - Driver’s licence
PASSPORT - Passport
NATIONAL_ID - National identity card
NATIONAL_HEALTH_ID - National health ID / Medicare card
Events:
Event
Description
form:document:ready
User completed document selection and pressed the CTA
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
Displays collected data for user review before submission. In manual mode with verify: true, submits the data for verification and navigates to the appropriate result screen automatically. When customResult: true is also set, the form emits review-level result events instead of navigating to result screens, giving you full control over result handling.Screen ID:reviewEvents:
Event
Description
form:review:ready
User pressed the CTA on the review screen
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
form:review:failed/success/partial/pending require customResult: true in manual mode.These four events are only emitted when customResult: true is set on the review component in manual mode. When customResult is false (the default), the form automatically navigates to the configured result screen — these review-level result events are not emitted. In OCR mode, the only review event is form:review:ready.See verify and customResult in the configuration reference.
Displayed while verification is being processed.Screen ID:loadingThis screen is managed internally by the form module and typically does not require event handling.
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:retryEvents:
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
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
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.
Retry Flow:
Initial verification is submitted from the Review screen
Verification returns a partial result (via partial or 404 alert)
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
Example with retry limit:
const retry = sdk.component('form', { name: 'RETRY', type: 'manual'});const resultFail = sdk.component('form', { name: 'RESULT', type: 'manual', state: 'FAIL', title: { label: 'Max attempts reached' }, descriptions: [ { label: 'You have reached the maximum number of attempts.' } ], cta: { label: 'Close' }});let retryCount = 0;// Fires when user presses CTA on PARTIAL result screenreview.on('form:result:partial', async () => { if (retryCount < 2) { retry.mount('#form-container'); retryCount += 1; } else { resultFail.mount('#form-container'); }});retry.on('form:retry:loaded', (payload) => { console.log('Retry screen displayed - attempt', retryCount);});
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_uploadEvents:
Event
Description
form:partial_document_upload:ready
User completed partial uploads and pressed the CTA