How QCDS Preserves Identity Verification Evidence

QCDS preserves Level 2 evidence as transaction metadata tied to the immutable Request—not as a permanent copy of the provider's raw identity media. The record is designed to show which provider verified the signer, when it happened, and which Request/document state that verification belonged to.

Evidence Is Bound at Send Time

For each participant marked as requiring Identity Verification, QCDS creates a verification record when the Request is sent. The initial evidence records that Level 2 was required, the selected provider and stable provider-profile ID, the detected provider mode/Test state, the immutable Request snapshot SHA-256, and a document-association SHA-256.

This provider binding belongs to that transaction. Later Global/account setting changes do not migrate an already-sent Request to another provider profile.

What a Successful Verification Adds

After an authenticated verified result, QCDS records a restrained set of identity evidence. Depending on what the provider returns, this can include:

  • provider and provider reference/session reference;
  • verified name;
  • government-ID document type and issuing country;
  • verification confirmation time in UTC;
  • provider mode/Test indication;
  • limited provider decision/check metadata;
  • the Request snapshot and document-association hashes that tie the verification to the transaction.

QCDS also records Identity Verification timeline/domain events for required, started/retried, verified, failed, or unavailable transitions.

What Appears in the Completion Audit Trail

For a verified participant, the generated completion audit trail identifies Identity Verification as verified, clearly labels Trial/Test evidence as TEST ONLY — not production identity evidence, and can include the verified identity, verification method, document type, issuing country, confirmed time, provider, provider reference, Request snapshot SHA-256, and document-association SHA-256.

The normal creator-facing Request status intentionally does not expose the raw internal provider-code/evidence JSON. It shows a restrained verification state instead.

Raw Identity Media Is Not Permanent QCDS Evidence

  • Didit: the identity work happens in Didit's hosted experience. QCDS does not receive or retain the raw ID images or facial media.
  • Shufti: QCDS temporarily stores signer capture media in protected storage only long enough to submit/process the attempt. After an authenticated signed provider response, QCDS deletes the raw local capture. Abandoned temporary media is cleaned up within the locked one-hour maximum.

Provider Changes Do Not Rewrite History

Disabling a provider, changing Global/account configuration, or removing credentials later does not rewrite the verification evidence already recorded for a completed transaction. The historical record remains tied to the original provider/profile and immutable Request hashes.

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.