CHECKID · ELECTRONIC AUTHENTICATION

e-Authentication

Confirms the current actor for a session or access event without automatically becoming the relying organisation’s authorisation decision.

SERVICEPurpose → Method → Result
TRUSTSource → Evidence → Scope
OPERATIONSSaaS · API · SDK · SLA
SERVICE BOUNDARY

Authentication differs from proofing, verification and authorisation

Authenticate the actor; do not overstate the business decision.

Definition

Electronic authentication confirms electronic identification or a known actor in an access/session event. It does not necessarily re-verify the entire identity record.

Not authorisation

Authentication can be an input to the relying party; final access or transaction authorisation remains governed by the relying organisation’s policy.

Step-up

Where risk increases, a relying party can require a stronger method or combine e-Verification/assurance if the actual integration supports it.

Federation

OIDC/federation is described as an integration mechanism where implemented; a standard reference is not treated as proof of a deployed service.

Evidence

An authentication event requires correlation/evidence according to the contract when CheckID is part of the processing chain; fields are not invented.

Product scope

The website does not claim a standalone authentication product without Tier-1 evidence; this page establishes the service/capability boundary to prevent ambiguity.

TECHNICAL REFERENCES

Definition and standards references

A reference does not by itself mean CheckID conforms to or is certified against the document.