Technical evaluation

Evaluate CardIQ for Enterprise Identity Control

Validate capabilities in your intended plan and deployment instead of relying on generic feature claims.

Evaluation checklist

Ask CardIQ to demonstrate each relevant control in the proposed environment.

Company-managed identity fields, administrative roles, tenant scope, permissions and support access boundaries.

Domain verification, Trusted Domains, employee issuance, public profiles and current-status signals.

QR/NFC, vCard, signature and meeting identity; confirm Wallet platform configuration separately.

Detail updates, audit logs, employee deactivation, public inactive behavior and separate company lifecycle controls.

Bulk import, confirmed API scopes and signed lead webhooks. Treat native SCIM, Entra ID and Okta provisioning as not currently supported.

SaaS plus availability of contract-scoped dedicated cloud/self-hosting, responsibility boundaries and supported data export.

Run the test with a non-production employee and record the observed behavior.

Create an employee and issue a company-managed identity using an authorized Company Admin.

Open the active identity through the public profile and its QR/NFC URL.

Update the job title, then confirm the same public URL shows the current approved detail.

Deactivate the employee, then confirm the URL no longer presents an active company identity.

Document what is available now, configured for this deployment, or not currently supported.

Which roles, MFA requirements, audit records, alerts and support workflows apply?

Which specific API scopes and webhook events are supported? Do not substitute SSO for provisioning.

Who owns updates, backups, availability, data location, incident response and export under the chosen deployment?

Which company/employee signals are enabled, and how are recipients told that CardIQ is not KYC, government ID or universal fraud prevention?

Explore the CardIQ platform or review the workflow from verification through identity deactivation.