# docusign recipient failed authentication id check: how to fix it

A DocuSign recipient failing the ID check usually means the details they entered dont match the records, or they picked the wrong verification method. Confirm the name and details match the envelope exactly, then retry the check. After too many failures the recipient locks out, so get the details right before trying again.

```text
docusign recipient failed authentication id check
```

## When to use this skill
- A signer cant get past the ID verification step
- The check fails despite the person being legitimate

## When not to use this skill
- The signer never got the envelope (a delivery issue)
- The check method itself errors technically (a platform issue)

## Tool compatibility
DocuSign eSignature recipient authentication. ID verification methods.
Related area: business SaaS platforms and vendor portals.
Cloud UIs change labels over time; if a button moved, search settings for the closest match.

## Before you start
- Sign in to the tool and keep one tab open so sessions stay clean
- Copy the exact error text and note the time it happened
- Set aside 15 to 20 minutes; most of these resolve in a single pass

## Quick diagnosis
Make sure this is the right skill before you invest the 15 minutes.
- If you are dealing with a signer cant get past the ID verification step, start at step 1 below.
- If instead the signer never got the envelope (a delivery issue), stop here; you need a different skill.
- If neither quite matches, compare your screen against the verbatim error block at the top; that block is exactly what this skill covers.

## Fix it in steps
### 1. Confirm the envelope details

```
Check the exact name and any pre-filled details on the envelope.
```
Expected: you know precisely what the check compares against.

### 2. Coach the recipient on exact matching

```
Tell them to enter details exactly as shown, watching capitalization and suffixes.
```
Expected: they understand what to type.

### 3. Retry the ID check once

```
Have them attempt the verification again with the corrected details.
```
Expected: the check passes and signing opens.

### 4. Switch methods if it keeps failing

```
As sender, change the authentication method to something the recipient can complete, like access code or phone.
```
Expected: the recipient authenticates via the simpler method.

## Confirm each step worked
Run through this checklist before moving on. If a check fails, redo that step instead of pushing ahead.
- Step 1 (confirm the envelope details): Expected: you know precisely what the check compares against.
- Step 2 (coach the recipient on exact matching): Expected: they understand what to type.
- Step 3 (retry the id check once): Expected: the check passes and signing opens.
- Step 4 (switch methods if it keeps failing): Expected: the recipient authenticates via the simpler method.

## Quick recap
1. Confirm the envelope details
2. Coach the recipient on exact matching
3. Retry the ID check once
4. Switch methods if it keeps failing

## Still stuck?
Gather three things: the exact error text, the time it happened, and what changed just before it broke.
Check the vendor status page for an active incident. Then open a support ticket with those three things;
it cuts the back-and-forth in half. For agent runs, attach the last 50 lines of the agent log too,
since the loop or timeout signature in the log usually names the cause.

## Variant phrasings
### docusign id check failed
Exact-match details fix most failures. If this matches what you saw, the steps above apply as written.

### recipient failed authentication docusign
After lockout, only the sender changing the method helps. If this matches what you saw, the steps above apply as written.

## Why it happens
ID checks compare signer-entered details against third-party records with strict matching. A middle initial, a suffix, or an old address is enough to fail, and repeated failures trigger a lockout.

## Edge cases
- Lockouts require sender action to clear
- International signers fail knowledge-based checks often, use a different method
- Test the method yourself before sending to executives

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_lsf6g_XXVfy_MieJzgMzqw