Troubleshoot Signer Access and Identity Verification

Signer access has two separate gates: the personal invitation/session must still be valid for that participant and Request, and—when Level 2 is required—the bound Identity Verification profile must allow that signer to proceed. Diagnose the access message before resending or replacing anything.

Read the Signer-Link State

QCDS distinguishes several invitation conditions:

  • Invalid: the supplied token does not resolve to a QCDS invitation.
  • Replaced: the sender issued a replacement invitation; the older link/session is intentionally closed.
  • Revoked: the sender explicitly closed every usable link/session for that signer.
  • Expired: the invitation or Request reached its effective expiration date.
  • Request closed/unavailable: the Request is cancelled, expired, voided, declined, failed, or otherwise no longer signable.

If the participant already completed, reopening the original personal invitation returns a truthful completed message instead of pretending another signature is needed, even if the token later moved through another lifecycle state.

Resend and Replace Are Different

Resend Invitation can issue another invitation while earlier unexpired links remain usable. Replace Invitation invalidates the earlier links and active browser sessions but preserves saved field progress. Use Replace when the old access should no longer work.

Signer Browser Sessions Are Scoped

Opening a valid invitation exchanges it for a fresh hash-stored browser session scoped to the exact workspace, Request, participant, and routing stage. Normal active signing sessions are bounded to 24 hours and cannot outlive the invitation/Request expiry. Each device/browser receives its own scoped session.

If sequential routing has not activated that signer yet, do not try to bypass the routing state by sharing another participant's link. QCDS activates and invites the signer when the correct stage becomes active.

Read the Identity Verification State

For Level 2 participants, QCDS can report Not Started, In Progress, Verified, Failed, or Verification Unavailable. Signing is allowed only after a required verification reaches Verified.

Failed means a verification attempt reached a provider/result decision that did not verify the signer. Verification Unavailable means the bound provider profile cannot currently serve that pending Request—for example, credentials were removed or the provider connection is no longer usable.

Repair the Bound Provider, Not the Request

Level 2 provider choice is frozen when the Request is sent. Changing from Didit to Shufti, enabling a different Global profile, or editing another account profile does not migrate the existing Request. Restore/test the exact bound provider profile when a pending signer shows Verification Unavailable.

Didit signers use the hosted provider flow and protected return path. Shufti uses QCDS-managed protected local capture for the required ID image/live face video and removes raw capture media after processing. If the provider itself is failing, preserve the existing Request and provider reference/evidence while repairing connectivity or credentials.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDS feature? Visit the QC Digital Signature Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.