Skip to main content

Identity Verification Rules | March 2026

Written by Eric Range
Updated yesterday

Released: March 26, 2026

This update introduces Identity Verification Rules, enabling more granular control over when and how identity verification is applied within applications. Previously managed at the application level, identity verification can now be configured using conditional rules similar to submission prevention and payment rules.

Administrators can now define more targeted scenarios where identity verification is required or happens before or after submission of the application. Rules can be based on specific segments or application conditions, allowing institutions to tailor verification requirements to particular populations such as program type or residency status.

This update also unlocks the ability to leverage the post-submission fraud status evaluation to trigger the Identify Verification requirement.

  • No change to existing configurations. Application level settings remain in effect. You can add rules whenever you like.

  • New rule-based configuration to control identity verification using conditional logic

  • Segment targeting to apply verification requirements to specific applicant groups (e.g., program, residency, custom segments)

  • Dedicated settings interface with a new “Identity Verification Rules” tab under Application Settings

  • Multiple rule creation options including leveraging existing segments, inline built segments filters, and application field conditions

  • Rule prioritization allowing administrators to define execution order, with the first matching rule applied

  • Default state configuration (existing config) to set identity verification on or off at the application level and layer rules on top

This enhancement provides greater precision and flexibility in managing identity verification, allowing institutions to apply verification only where it is most relevant. By targeting specific populations and enabling post-submission workflows, users can reduce unnecessary friction for applicants while strengthening fraud prevention processes. The result is a more efficient, controlled, and adaptable verification experience.

Did this answer your question?