Amiqus

Amiqus integrates Drupal with the Amiqus ID API to support hosted, template-based identity-verification workflows. It records minimal local status information while verification is completed in Amiqus.

Features

• Connects a site-owned Amiqus team using a Personal Access Token stored outside exported configuration.
• Creates and tracks hosted verification records from configurable Amiqus record templates.
• Provides verification profiles, local attempt tracking, administrative status views, and applicant-facing initiation.
• Receives signed Amiqus webhooks and synchronises current remote state through Drupal queues.
• Uses an explicit local decision policy: completed records or webhook receipt alone never approve a person.
• Includes an optional Drupal Commerce checkout pane for sites that require verification before checkout proceeds.

Post-installation

Enable the amiqus module, add the Amiqus Personal Access Token and webhook secret in settings.php, test the connection, and create a verification profile with the relevant Amiqus record-template and required step IDs. Register a signed HTTPS webhook endpoint and ensure Drupal cron processes queues.

Outbound writes are disabled by default through a settings.php kill switch, which should remain disabled on cloned development sites.

Additional requirements

An Amiqus account, a site-owned Personal Access Token, enabled record templates, and a publicly reachable HTTPS webhook endpoint are required. Drupal Commerce is not required for the main module. The optional amiqus_commerce submodule requires Drupal Commerce separately.

Recommended modules/libraries

Drupal Commerce is recommended only when verification must be evaluated during checkout. No Amiqus PHP SDK is required.