Complete Didit Identity Verification as a QCDS Signer

When a QCDS Request requires Level 2 verification through Didit, QCDS sends you from the secure signer page to Didit's HTTPS-hosted verification experience. QCDS does not collect the Didit ID images or facial media in its own signer interface.

Start from Your QCDS Signer Link

  1. Open the personal QCDS signer link from the invitation.
  2. When the Identity Verification panel appears, choose Continue.
  3. QCDS creates a Didit verification session and redirects your browser only to the provider's approved verify.didit.me hosted URL.
  4. Complete the government-ID, liveness, and face-match steps presented by Didit.

Signing fields remain locked until QCDS receives or retrieves a verified provider decision.

Return to QCDS

QCDS gives Didit a protected return URL tied to the browser session that started the verification. If the provider returns to that same browser, QCDS refreshes the decision server-to-server and sends you back to the signing page.

QCDS deliberately ignores a provider-supplied query-string claim such as status=Approved. Signing is unlocked only from QCDS's protected session plus the authenticated Didit webhook or server-to-server decision lookup.

If You Finish on Another Device

Didit's hosted experience may allow a device handoff. If the provider returns on a phone or other browser that does not own the original QCDS signer session, QCDS shows a completion message there instead of exposing or transferring the signer session. Return to the device/browser where you originally opened the QCDS signer link and use the signing page to continue.

Understand the Status

  • In Progress: QCDS is still waiting for or refreshing the Didit decision. Use Check Verification Status if needed.
  • Verified: QCDS unlocks signing and shows the verified state.
  • Failed: use Try Identity Verification Again if another attempt is appropriate.
  • Verification Unavailable: the bound provider profile or provider service cannot currently complete the verification.

What QCDS Retains

QCDS does not store Didit's raw ID images or facial media. It retains limited transaction evidence such as the provider, provider reference, verification time, verified identity metadata when returned, document type/country when available, result/check metadata, and hashes tying the verification to the Request snapshot and document association.

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.