Templates

The ID verification process is built around customizable templates, giving you full control over how each verification session runs. These templates serve as the foundation for your workflow, allowing you to standardize processes, ensure regulatory compliance and align with internal policies.

With templates, you can easily define key verification parameters such as accepted document types, age restrictions, step sequences and response handling. This flexibility helps you strike the right balance between user experience, security, and automation, while tailoring the flow to fit your specific business needs.

A template can control various factors that influence the ID verification session. By adjusting these settings, you can create a verification process that aligns with your specific security, compliance and user experience requirements.

Age limit

Defines the minimum age required for verification.

• Typically used to enforce age-related restrictions (e.g., verifying users must be 18+ for financial services or 21+ for alcohol purchases).

Accepted documents

Specifies which identification documents are allowed.

Response method

Determines how the verification results are handled during the verification flow.

• Specifies how and when the verification outcome is shown to the user.
• Possible response methods include:
  • Asynchronous Callback (ASYNC): The verification flow does not wait for the entire session evaluation, allowing for faster completion.
  • POLLING: The verification flow periodically checks for the evaluation result, providing feedback on the result of the evaluation.

Document check response method

Determines how the Document Check  handled during the verification flow.

• Possible response methods include:
  • ASYNC: The SDK won’t wait for the evaluation result of the document check. If the user provides an invalid identity document, the flow will not be interrupted, and they will not be prompted to retry with a valid document. This allows for a smoother user experience but may require follow-up actions if the document is later deemed invalid.
  • POLLING: The system waits for a request from the customer’s platform before returning document validation results. The customer system must repeatedly check for updates until the document has been processed and a final decision is available. This method ensures that document verification is completed before proceeding with other actions.

Verification steps

Defines the steps the user must complete during the verification process.

Steps:

• Document verification
• Selfie check
• Proof of Address

The SDK supports the use of configured templates to customize the user verification flow based on specific business requirements.

Adding a Template ID

To apply a configured template, provide its Template ID during the SDK initialization step. This enables the session to follow the structure defined by the selected template.

Session behavior

• If a Template ID is specified, the session uses the configuration of that particular template.
• If no Template ID is provided, the session defaults to the default template configured in the system.

Locating Template IDs

Template IDs can be found in the Admin Panel under:

• Settings/ID Verification

From there, you can identify and copy the Template ID corresponding to the desired configuration.

Additional Resources

For specific implementation details on how to include Template IDs in your integration, refer to the relevant Integration Guides for your SDK environment.