What is digital identity proofing?

Digital identity proofing — often just “proofing” — is the process of establishing that an identity claim is genuine: that this identity exists, and that the person presenting the claim is the person it belongs to, to a stated level of confidence. If verification is the check, proofing is the discipline of building the check: deciding what evidence is enough, and how much confidence the outcome deserves.

Standards bodies phrase it slightly differently, but the plain-English substance is constant. Proofing answers “is this identity real and theirs?” before anything else can be answered about it. The evidence used is usually a mix of identity documents, authoritative records, and a biometric link between the person and the evidence.

Proofing systems reason in three dimensions. Evidence: what was presented — a passport, a licence, a record lookup, a live face. Attributes: what the evidence establishes — name, date of birth, address. Confidence: how strongly the combination supports the claim. A document plus a matching live face under liveness challenge supports high confidence; a document image uploaded without any link to the presenter supports much less, however genuine the document looks.

Confidence is also where the verification result gets its meaning. A level such as Standard or Trusted is a compressed statement of confidence: it says what was checked, without handing over what it was checked from. The wallet's four verification levels work exactly this way.

The failure mode of proofing is collecting more than the purpose requires — demanding passport-grade evidence to read a forum, because collecting is cheap and asking twice is annoying. Every extra document retained is breach risk created for no assurance gained, and every unnecessary hurdle is a barrier for people whose documents are harder to obtain.

Proportionality fixes the direction of travel: the intrusiveness of proofing should match the risk of the action it protects. A low-risk action needs light proofing; a sensitive role justifies hardware-backed biometrics and sustained history. The reasoning, including the objections, is worked through in verification tiers and proportionality.

The other modern shift is treating proofing as an investment rather than a toll. When proofing produces a signed credential held in the person's wallet, the hard work happens once. Later interactions present a proof of that result — a signature check, or a zero-knowledge proof that answers the exact question asked without reopening the evidence.

This changes the economics for everyone. Services get assurance without running their own gauntlet, people face friction once instead of per service, and no new archive is created at each reuse. The verifier-side path — what proofing results look like to a relying service — is set out in become a verifier.