Test an Identity Verification Provider Connection

QCDS provides an explicit Test Connection action for both Global and account-level Identity Verification profiles. The test is provider-specific: it verifies the saved credentials and capabilities QCDS needs, records the connection health, and helps prevent new Level 2 Requests from binding to an unready profile.

Where to Run the Test

• Global profile: Joomla Administrator → QC Digital Signature → Identity Verification. A Super User manages and tests this profile.
• Account-level profile: QCDS frontend → Settings → Identity Verification. The sender must be allowed to manage workspace settings, and an enabled Global profile must not be overriding the account profile.

The Test Connection button is available after the selected provider has saved credentials. Saving provider settings also runs the connection test automatically when credentials are present.

What QCDS Tests for Didit

QCDS first confirms that the API key can read the configured workflow, that the saved Workflow ID exists for that key, and that the workflow is published/active and is a KYC workflow.

It then probes the session-creation endpoint used by the signer workflow. On a sandbox/test application, QCDS creates a sandbox-only approval session, confirms the required session ID and hosted URL, and immediately attempts to delete the preflight session.

On a live Didit application, QCDS deliberately does not create an ordinary live verification merely to test connectivity. If Didit rejects the sandbox-only flag in the expected way, QCDS records the profile as a connected live application without launching a potentially billable live identity session.

What QCDS Tests for Shufti

QCDS calls Shufti's account-information endpoint, requires a successful provider response, and validates the provider response signature. It records the detected account mode as Trial/Test, Production, or unknown when the provider does not report a recognized mode.

A Shufti profile is ready for Level 2 only when its credentials exist, its health is connected/ready, and QCDS has detected Trial/Test or Production mode.

Read the Stored Result

QCDS updates the profile's connection health, Last tested timestamp, last test status, and a safe error classification. The Settings/Administrator card then reflects whether the profile is ready for new Level 2 work.

When a test fails, correct the credential, workflow, account-status, HTTPS/network, or provider-response problem and test again. A successful connection test confirms the configured provider path; it does not guarantee that every future signer transaction will succeed if the provider later becomes unavailable or transaction-specific validation fails.

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.