Enum DocVerificationStatus
- Namespace
- SEBT.Portal.Core.Models.DocVerification
- Assembly
- SEBT.Portal.Core.dll
Lifecycle states for a document verification challenge.
Transitions: Created → Pending → Verified | Rejected | Expired | Resubmit.
All four post-Pending states are terminal and cannot be overwritten. Resubmit is terminal at
the Socure level (the workflow ended) but retry-eligible at the portal level: a user who
lands on Resubmit can open a fresh challenge against Socure's docv_stepup workflow.
public enum DocVerificationStatus
Fields
Created = 0Challenge has been created but the user has not yet started the Socure DocV flow.
Expired = 4The challenge expired before the user completed the flow. Terminal state.
Pending = 1The user has started the DocV flow and Socure is awaiting document capture/evaluation.
Rejected = 3Socure rejected the user's identity documents. Terminal state.
Resubmit = 5Socure returned a RESUBMIT decision (recoverable failure such as image quality). Terminal at Socure: the workflow ended and a retry must start a brand-new evaluation. Retry-eligible at the portal: a fresh
DocVerificationChallengecan be opened against Socure'sdocv_stepupworkflow when the user clicks "try again".Verified = 2Socure accepted the user's identity documents. Terminal state.