Select context
Fix evidence revision, evaluation time, trust anchors and validation-policy revision. Verification permission does not grant source-content access.
MOBILE-ID · TRUSTED LTANS
Verification Service
Evaluate data/evidence binding under a specified time, policy and trust context.
Outcome and scope
Produce a context-bound conclusion showing which checks ran and where evidence is missing.
Documentation scope Workflow design and integration contract; operational configuration is confirmed per environment.
| Prepare | Receive |
|---|---|
| Check preserved records, exports or supplied evidence with the appropriate original data. | A report explains each check, outcome and reason when evidence is insufficient. |
Participants: Verifiers, record owners and authorized auditors.
Workflow and decision points
Check binding
Recompute input digests and check hash-tree paths and bindings to each archive timestamp.
Evaluate history
Check renewals, token signatures, certificate paths and time-relevant status data; identify checks that could not run.
Read report
The report records evaluatedAt, policy/context, per-step outcomes and overall reasons. A SUCCEEDED job does not imply a VALID result.
States, guards and authority
| Current | Guard | Actor | Next | Artifact / recovery |
|---|---|---|---|---|
| QUEUED | Pin evidence, evaluation time and policy | Verification Service | RUNNING | Persist evaluation parameters; no implicit session trust context. |
| RUNNING | Complete steps, including missing-material findings | Verification Service | SUCCEEDED | The job ends; the separate report has VALID / INVALID / INDETERMINATE. |
| RUNNING / WAITING_EXTERNAL | Execution failure or unavailable dependency | Verification + Operations | RETRY_PENDING / FAILED | Separate execution failure from crypto conclusion; a new assessment retains earlier reports. |
Exceptions and controls
| Situation | Action | Boundary |
|---|---|---|
| Digest or signature failure | Report the failed step and policy-defined conclusion. | Do not relabel a cryptographic failure as missing data. |
| Missing CRL/OCSP/certificate | Identify missing material and assessment limits. | Never infer GOOD from UNKNOWN. |
| Additional material supplied | Create a new assessment linked to the earlier report. | Do not overwrite historical conclusions. |
Authorization, approval and recovery
verification:write does not grant payload access. Validate data binding, hash trees, renewal history and certificate status at the relevant times.
Missing revocation material or certificates yields INDETERMINATE, never an automatic VALID. Supply missing material and create a linked replacement report.
Reconciliation artifacts and acceptance
Retain tool/policy versions, trustContextId, time and reasonCodes; link new reports to prior ones instead of overwriting.
- Run intact, byte-tampered and missing-status fixtures; compare step results rather than only HTTP 200.
- The report identifies the exact evidence and context used; mock execution does not establish independent interoperability.
Integration and data contract
| API | Application scope | Documentation |
|---|---|---|
POST /v1/archives/{archiveId}/verification | verification:write | Verification API |
GET /v1/verifications/{verificationId} | verification:read | Verification API |
Technical input and references
| Element | Definition |
|---|---|
| Input | Candidate data, evidence version, evaluation time, validation policy and independent trust context. |
| Output | VALID, INVALID or INDETERMINATE report with per-step results, algorithms, certificate path and reasons. |
Execute and reconcile a scenario
| Element | Action |
|---|---|
| Synthetic ID | ver-test-001 |
| Task | Select evidenceVersion, policyVersion and trustContextId; read each step/reasonCode. |
| Acceptance case | Synthetic token absence remains INDETERMINATE; actual verification needs provisioned material. |
These are business test criteria; synthetic packages alone do not establish backend execution or valid ERS.