# adobe sign recipient failed identity verification: how to fix it

Identity verification fails on mismatched personal details, expired ID documents, or knowledge-based questions the signer cannot answer. Switch the verification method to a phone-based one, confirm the signer details match their ID exactly, and resend.

```text
adobe sign recipient failed identity verification
```

## When to use this skill
- Signer repeatedly fails the identity check
- Knowledge-based questions block a legitimate signer

## When not to use this skill
- Signer never got the email (a delivery issue)
- Signer fails on the second factor only (an SMS issue)

## Tool compatibility
Adobe Sign identity verification. Related area: authentication and identity.

Related area: proposal automation and agent-assisted RFP workflows.

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 signer repeatedly fails the identity check, start at step 1 below.
- If instead signer never got the email (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 signer details match their ID

```
Compare the name, address, and date of birth in the agreement against the signers government ID.
```
Expected: Expected: every field matches character for character.

### 2. Switch to phone verification

```
Change the identity verification method to phone-based authentication.
```
Expected: Expected: the signer receives a code by phone.

### 3. Resend the agreement

```
Send the agreement again so the new method applies.
```
Expected: Expected: signer completes verification on the first attempt.

### 4. Confirm the signed document

```
Check the audit trail for a passed verification entry.
```
Expected: Expected: audit trail shows verification passed, then the signature.

## 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 signer details match their ID): Expected: expected: every field matches character for character.
- Step 2 (switch to phone verification): Expected: expected: the signer receives a code by phone.
- Step 3 (resend the agreement): Expected: expected: signer completes verification on the first attempt.
- Step 4 (confirm the signed document): Expected: expected: audit trail shows verification passed, then the signature.

## Quick recap
1. Confirm signer details match their ID
2. Switch to phone verification
3. Resend the agreement
4. Confirm the signed document

## 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
### adobe sign identity verification failed
Method switch plus detail check fixes it. If this matches what you saw, the steps above apply as written.

### adobe sign id check failed recipient
Exact detail match is required. If this matches what you saw, the steps above apply as written.

## Why it happens
Knowledge-based verification pulls from public records that can be stale or wrong for the signer, and any mismatch against the ID document fails the check. Phone-based methods avoid the stale-data problem entirely.

## Edge cases
- Signers get locked out after repeated failures; wait for the lockout window before resending
- Name suffixes like Jr and Sr cause mismatches; include them exactly as on the ID
- Some agreements require verification on every signer, not just the first

## Provenance

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