QCDS Identity Verification: Level 2 Overview and Plan Requirements

What provider-backed Identity Verification adds, current Pro/Max/All Access availability, Didit and Shufti support, and the difference between ordinary secure-link signing and Level 2 verification.

This guide applies to Pro / Max / All Access and follows the accepted QC Digital Signature 2.0.7 implementation. Where older walkthrough language differs from the current interface or source behavior, use the current QCDS state as the authority.

Before You Begin

  • Treat the signer link as personal transaction access. Do not publish, forward, or paste it into public support posts.
  • If Level 2 Identity Verification is required, confirm the applicable Didit or Shufti provider profile is configured and tests successfully before sending.
  • Test the signer experience in a normal browser/mobile context, not only while logged into Joomla as an administrator.

Step-by-Step Workflow

  1. Open the QCDS screen or record that owns the topic so you are reading the current state rather than an old screenshot or memory.
  2. Compare the visible state with the current 2.0.7 rules described in this guide.
  3. Identify whether the value belongs to global installation settings, one sender workspace, a reusable Template, or one immutable/sent Request.
  4. Make changes only at the layer that owns the behavior.
  5. Verify the result with a safe test and preserve historical Requests/evidence.

Provider-backed Identity Verification adds

QCDS keeps the underlying Base tier separate from the Effective tier that controls features now. All Access or an active Max Preview can elevate a Basic base installation to Effective Max without rewriting the purchased/base product state. This distinction matters when diagnosing a control that is visible today but could become unavailable after an entitlement or preview change.

For QCDS Identity Verification: Level 2 Overview and Plan Requirements, verify this behavior using the actual object involved rather than a generic assumption. A global administrator setting, a sender-workspace preference, a reusable Template, and a sent Request have different ownership and history rules. QCDS is intentionally designed so changes for future work do not silently rewrite the evidence of an already-sent transaction.

Pro/Max/All Access availability

QCDS keeps the underlying Base tier separate from the Effective tier that controls features now. All Access or an active Max Preview can elevate a Basic base installation to Effective Max without rewriting the purchased/base product state. This distinction matters when diagnosing a control that is visible today but could become unavailable after an entitlement or preview change.

For QCDS Identity Verification: Level 2 Overview and Plan Requirements, verify this behavior using the actual object involved rather than a generic assumption. A global administrator setting, a sender-workspace preference, a reusable Template, and a sent Request have different ownership and history rules. QCDS is intentionally designed so changes for future work do not silently rewrite the evidence of an already-sent transaction.

Didit and Shufti support

QCDS keeps the underlying Base tier separate from the Effective tier that controls features now. All Access or an active Max Preview can elevate a Basic base installation to Effective Max without rewriting the purchased/base product state. This distinction matters when diagnosing a control that is visible today but could become unavailable after an entitlement or preview change.

And the difference between ordinary secure-link signing and Level 2

QCDS keeps the underlying Base tier separate from the Effective tier that controls features now. All Access or an active Max Preview can elevate a Basic base installation to Effective Max without rewriting the purchased/base product state. This distinction matters when diagnosing a control that is visible today but could become unavailable after an entitlement or preview change.

How This Fits into the QCDS Workflow

Ordinary QCDS signing is a secure-link workflow and does not require the signer to have a Joomla account. Identity Verification is an additional assurance layer for selected transactions; it does not replace the core signing system.

Signer usability and evidence quality are linked. Clear field placement, private secure-link handling, and explicit Identity Verification requirements make it easier for the signer to complete the intended act without ambiguous workarounds.

Verify the Result

  • Provider Test Connection succeeds and a representative Level 2 test follows the expected provider flow.
  • A direct follow-up test confirms the change affects future/current workflow behavior without rewriting historical sent Request evidence.

Common Mistakes to Avoid

  • Treating provider-backed Identity Verification as required for every ordinary secure-link signing workflow.
  • Posting provider credentials, webhook secrets, or identity evidence in public diagnostics.

Troubleshooting

  • If Level 2 verification fails, use the provider Test Connection and inspect provider/profile/callback configuration; ordinary Level 1 signing and historical evidence should not be reset.

Operational Best Practice

Test meaningful changes with controlled data before relying on them in production. Keep QCDS, Joomla mail, Scheduled Tasks, and entitlement health observable; preserve successful Requests and completed evidence; and make the smallest change that solves the actual problem. For handoff or support, record the QCDS version, relevant Request/Template reference, the exact action taken, and the visible result without including secrets.

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.