Skip to main content

Trust Validation Status

For every verification (trust validation), IDmeta calculates an overall status based on the results of all verification components in the Trust Flow. Use this table to understand what each value means and how precedence is applied.
ValueStatus nameDefinitionTrigger conditionPrecedence ruleExample scenario
1RejectedOverall verification failed due to at least one rejected component.At least one verification within the Trust Flow returns Rejected.Takes precedence over Review Needed and Verified.Document verification rejected while Biometrics and AML passed.
2Review NeededVerification requires manual assessment before final decision.At least one component is marked Review Needed, and no components are Rejected.Applies only if no Rejected exists.AML flagged for manual screening review.
3VerifiedAll verification components successfully passed.Every verification step in the Trust Flow returned a successful result.Applies only when all checks pass.Document, Biometrics, and AML all passed automatically.
4IncompleteRequired verification steps were not fully submitted or completed.One or more required verifications were not performed or not finalized.User uploaded a document but did not complete selfie verification.
5In ProgressVerification process is actively ongoing.User has initiated verification and at least one component is currently processing.User is currently performing document upload or liveness check.
6FailedVerification encountered a technical or internal system error.At least one verification component failed due to internal processing error.External provider timeout or internal API error.
99EmptyVerification created but no actions performed yet.Verification record created via API, but no verification components initiated.Default initial state.Immediately after Create Verification API is called.

API Request Status

Individual API requests also return a status code indicating the success of that specific request.
ValueDefinition
0Pending
1Success
2Failed