Skip to content

How Signers Are Identified: Email Links, Codes and ID Checks

Reviewed on November 16, 2026

A tool can't see who's holding the phone. It can only ask for proof, and each kind of proof is a bit harder to fake than the one before.

One vendor guide defines the goal. It's confirming the person signing "is who they claim to be."1 Wikipedia says an electronic signature is meant to give "a secure and accurate identification method."2

Checks from lightest to heaviestSigning link sent by emailOne-time code by email or textAccess code shared separatelyTwo or more checks combinedGovernment ID check
Senders choose a level to match the document.

The email link

This is the baseline. The tool sends a signing link to the address you typed. Whoever can open that inbox can open the link.

Example: you send a lease addendum to a tenant's email. If a family member shares that inbox, they could sign by accident or on purpose. The tool wouldn't know.

The same guide says this level suits low-risk documents. It adds that email alone "may not meet the requirements for sensitive or regulated transactions."1

A one-time code by email or text

Here the signer opens the link and then asks for a code. One help page describes a one-time access code by email, with a text option too.3 On that tool, "The code is valid for 20 minutes."3 Other tools set their own limits.

A text code proves the person has the phone, not only the inbox. That's a small step up.

An access code from the sender

An access code works differently. The sender creates it and passes it on separately. One guide says the signer must enter "a pre-shared password or PIN" before viewing or signing.1

It also says the code is typically delivered outside the signing workflow, by phone or a secure internal channel.1 That separation is the point. If someone copies the email, they still lack the code.

The weak spot is the sharing. Pass the code by a different route than the link, and never put it in the same message.

Questions about the signer

Some tools offer knowledge-based checks. The vendor guide says "Knowledge-based authentication verifies a signer" by asking personal questions drawn from public or proprietary records.1 The guide says KBA is often used for financial documents or higher-value agreements, and that it "introduces more friction than basic methods."1

Combining checks

Multi-factor authentication combines two or more verification methods.1 For instance, email access followed by a code sent to a phone.1 Two weak signals together beat one.

A government ID check

The heaviest option. Signers must "upload an official form of identification."1 The tool or a service then reviews it.

You'd see this for sensitive agreements. For a routine quote it would likely feel like overkill, and some signers will drop out.

What gets recorded

Whatever the method, the tool logs it. One vendor's certificate lists "Public IP addresses" and "Timestamps" among its items.4 A different guide says a signing summary shows "which eSignature authentication method was used."1 That's why the choice matters later. The audit trail at the end of a signed file keeps that detail.

Picking a level

Ask three plain questions:

  • What would go wrong if the wrong person signed?
  • Do you already know this signer well?
  • Will someone else, such as a bank or regulator, require a certain check?

Match the check to the answers. The legal side is covered separately. Ask a lawyer about anything high stakes.

Where the facts come from

  1. Electronic signature authentication, Docusign
  2. Electronic signature, Wikipedia
  3. Link Authentication Options, Thomson Reuters
  4. Certificates of Completion, Oracle (documentation describing a vendor's certificate)