Documentation Index
Fetch the complete documentation index at: https://docs.idmetagroup.com/llms.txt
Use this file to discover all available pages before exploring further.
Trust Validation Statuses
For every 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.| Value | Status name | Definition | Trigger condition | Precedence rule | Example scenario |
|---|---|---|---|---|---|
| 1 | Rejected | Overall 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. |
| 2 | Review Needed | Verification 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. |
| 3 | Verified | All 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. |
| 4 | Incomplete | Required 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. |
| 5 | In Progress | Verification 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. |
API Request Status
Individual API requests also return a status code indicating the success of that specific request.| Value | Definition |
|---|---|
| 0 | Pending |
| 1 | Success |
| 2 | Failed |