Namespace SEBT.Portal.Core.Models.DocVerification
Classes
- DocVerificationChallenge
Represents a single document verification attempt for a user. Each challenge tracks its own lifecycle independently from the user's overall proofing status. The user entity is only updated when a challenge reaches a terminal state.
- SocureDocvSession
Represents the response from Socure's DocV token generation. Contains the transaction token and URL needed by the frontend SDK.
Enums
- DocVerificationStatus
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_stepupworkflow.