
Checking evidence that connects a signing participant to the real-world identity they claim, beyond controlling an inbox or phone.
Signer identity verification checks evidence connecting the person participating in a signing process to the real-world identity they claim. The broader process is often called identity proofing. It asks a different question from whether someone controls a password, inbox or phone.
NIST’s identity-proofing overview distinguishes three related activities:
This is a useful conceptual framework, not a claim that every signing service or document must use the same NIST assurance level.
Collecting an ID attachment is not the same as checking it. An uploaded file may be unreadable, unrelated to the person presenting it or otherwise insufficient. A selfie or biometric comparison can contribute to a defined process, but the label alone does not establish its quality, fraud controls or outcome.
By contrast, signer authentication checks the relevant credential or channel. Multiple authentication factors do not automatically replace identity proofing. After any check, document permissions and legal signing authority remain separate questions.
Sign.Plus documents a separately configured ID Check using an identity document and selfie; supported documents vary by country and feature activation and credits are required. Its recipient-verification feature overview covers product options.
An ID-check result does not automatically create a qualified electronic signature or complete every obligation in a know-your-customer (KYC) program. Establish the evidence and process required for the particular transaction, including appropriate handling of the sensitive information collected.
A Common Case: Checking evidence for a services agreement
For a Massachusetts professional-services agreement, the recipient might be asked to complete a supported ID-check process. The firm would distinguish a successful identity check from the separate question of whether that person may sign for the contracting business, and handle the collected information appropriately.
No. Collecting a file and checking its authenticity and connection to the person presenting it are separate activities.
No. QES requires its own qualified-certificate and creation-device conditions; an identity check alone does not establish that signature level.