Veriff Identity Verification
Full-service identity verification solution for compliance and KYC. Leave identity verification to us and focus on doing what you do best.
Part 1: CAS CLI Configuration
When verification has completed, Veriff notifies CAS via a webhook.
Instructions to create a Veriff webhook for CAS:https://generalbytes.atlassian.net/wiki/spaces/ESD/pages/4497276929
Do not proceed until you have created & successfully tested a working webhook endpoint.
Part 2: Veriff Configuration
An account with Veriff is necessary to proceed - if you’ve decided to use Veriff Custom Configuration.
Navigate to:
Integration settings
“Webhook fullauto URL” is not supported.
You must have a Webhook decisions URL setting for the integration to work with CAS!
Navigate to: Veriff Station Integrations [Select the integration to configure]
Settings
Explanations:
Callback URLOnce your customer completes verification, they will be redirected to the callback URL defined here. The callback does not contain any decision or verification information (yet). If the Callback URL is left empty, the final Veriff screen after customer verification will report: ”You can close this window[…],”. If configured with a valid URL, then a “Continue” button will redirect your customer to the specified URL.
|
Check certificatesKeep Do not allow self signed certificates checked. |
Webhook events URLThis field may be left blank. Veriff events may be sent to a URL. These events are simply noted in the master log - when configured to the same URL as the decision webhook (below). There are two reported events:
|
Webhook decisions URLThe Veriff “Plus” plan is required to access this option.
If there's a network connectivity issue (any technical issue) with delivering the result via the webhook to CAS, Veriff will retry the notification again once per hour (for up to a week, or success). |
Webhook PEP & Sanctions URLNot used |
Webhook fullauto URL Unsupported callback. This new setting may indicate your account cannot be used with CAS.
|
Find your API keys
Your API keys are stored in the Veriff Station. Choose Integrations in the top menu, then select the integration you need. Once you open the integration you'll see Publishable key and Private key.
Private key is your API Secret, and
Publishable key is the API Key.
Part 3: CAS GUI Configuration
Shared instructions: https://generalbytes.atlassian.net/wiki/x/BIBQ_w
Veriff Specific Organization Settings
Navigate to the “Identity Verification Provider” section of your Organization settings.
Select Veriff, and
fill in your Public and Private keys (see: Part 2).
Save it (SUBMIT).
Finally, test it!
You can use any ID (or business card), then after it permits you to upload it, navigate to:
Veriff Station → Verifications → click on the verification → Update Status (Test integrations only) → select status → Update.
This will update the Identity in CAS, and prove the process is working.
Copyright © 2020-2026 General Bytes USA LLC