Digital Identity States
A Digital Identity's state has two independent dimensions: the outcome of its checks (the trust axis) and its relationship to other identities (the duplication axis). This page is the detailed reference; for the introductory view see Digital Identity Lifecycle.
The two axes
Trust axis — the outcome of the verification's checks:
| State | Meaning |
|---|---|
| Incomplete | Not finished; no decision. |
| Review | Awaiting an operator decision. |
| Accepted | Checks passed. |
| Rejected | Checks failed. |
| Anonymized | Personal data erased (terminal). |
Duplication axis — what duplicity check found:
| State | Meaning |
|---|---|
| Unique | No match — a distinct person. |
| Hit with Customer | Matches an existing Customer. |
| Concurrent | Matches another in-flight verification that is waiting for manual review. |
| Hit with Blocklist | Matches a blocked person. |
| Merged | Resolved by linking to an existing Customer. |
A Digital Identity occupies one state on each axis at once — for example Accepted + Hit with Customer.
Keeping hit lists consistent
When an operator resolves one verification, other verifications that had matched it are updated so their duplication state stays correct — for example, resolving a source as Unique re-points later matches to the new Customer. This happens automatically and is recorded in each affected record's audit log.