Docs
API referenceComplianceSupportHomeLog inSign up
  • Introduction
  • Guides
    • API Quick Guide
      • Perform AML Screening
      • Perform Document Check
      • Perform Identity Check
      • Perform Proof of Address Check
      • Perform Multi-Bureau Check
    • Web Portal Quick Guide
      • Perform AML Screening
      • Perform Document Check
      • Perform Multi-Bureau Check
      • Send verification link to client
    • Web SDK Guide
      • Web SDK integration guide
      • Web SDK customizations
    • Mobile SDK Guide
      • Mobile SDK integration guide
      • Mobile SDK stages
      • Mobile SDK tracked events
      • Mobile SDK error codes
    • Hosted Solution Guide
      • Integration guide
    • Postman Guide
    • Webhooks Guide
    • Integration Checklist
  • Check Types
    • AML Screening Check
      • Lists coverage
    • Document Check
      • ID coverage
      • RFID authentication
      • Redaction
      • Expected sides per type
    • Identity Check
    • Enhanced Identity Check
    • Proof of Address Check
    • Multi-Bureau Check
      • Service coverage
    • Face Authentication Check
    • Age Estimation Check
    • Automation
  • Other Services
    • AML Risk Profile
    • Bulk Processing
    • Autofill
    • Company Search
    • Address Search
    • Custom Lists
    • Advanced Case Management
  • Access Management
    • Teams and User Roles
    • Single Sign On (SSO)
      • SSO with Okta
      • SSO with Microsoft Entra ID
  • Useful Resources
    • Testing Data
  • API Reference
Powered by GitBook
On this page
  • Screening Check
  • Thresholds
  • Exclusion rules
  • Search mode
  • Document Check
  • Minimum age
  • Security element matching threshold
  • Inflight check attempts via SDK
  • Additional checks
  • Identity Check
  • Facial similarity threshold
  • Liveness threshold
  • Enrolled faces limit
  • Proof of Address Check
  • Document age threshold
  • Age Estimation Check
  • Minimum age

Was this helpful?

  1. Check Types

Automation

Customise and automate our services to meet your compliance needs.

PreviousAge Estimation CheckNextAML Risk Profile

Last updated 1 year ago

Was this helpful?

ComplyCube provides the ability to customize check thresholds and settings. This allows you to automate your checks in line with your risk-based approach.

You can amend these automation rules through the .

Screening Check

Thresholds

To simplify usage, ComplyCube represents the outcome of the analysis in the form of a match score. A match score can range from 0 to 100, with 100 being the best match.

By default, an AML Screening Check will only return matches with a match score over 85 and automatically reject matches with a score ranging between 85 and 90. Ultimately, only matches with scores higher than 90 will require manual checks.

You can adjust these automation thresholds according to your risk-based framework and internal process.

Exclusion rules

By default, ComplyCube will not exclude any matches. We will return matches without a DOB, gender, nationality, or incorporation country details. Furthermore, ComplyCube will also return inactive, deceased, and low-quality alias matches.

Search mode

Depending on your risk tolerance and preference, you can select from two distinct name-matching techniques:

  1. Fuzzy (default): applies various linguistic, phonetic, and near-match techniques on names to find matches.

  2. Precise: only matches names that are exact

The search mode only applies to the name-matching aspect of the Screening Check. ComplyCube utilizes other proprietary algorithms to find matches using other attributes.

Document Check

Minimum age

This setting empowers age verification compliance by allowing you to set a minimum acceptable age before your client ID is flagged.

By default, a Document Check will flag anyone younger than 18 years of age.

Security element matching threshold

ComplyCube returns a security element match score for each analyzed security element present on a document. A match score can range from 0 to 100; the closer the score is to 100, the greater the confidence that the security element is authentic.

By default, a Document check will deem a security element real when the match score is over 65.

Inflight check attempts via SDK

ComplyCube performs inflight quality checks on document images uploaded via the Web and Mobile SDKs. This setting configures the maximum number of times our quality checks are performed before sending a document for full processing, regardless of its quality.

By default, a document's quality will be checked up to 5 times on upload before it's sent for complete processing.

Additional checks

ComplyCube extends further optional checks, including:

  • Client data validation: this check compares the client record data (e.g., first and last names) with data extracted from an ID document.

  • Document model validation: this check considers the visual consistency, at a pixel level, of a single or two-sided document.

By default, ComplyCube will only perform document model validation.

Identity Check

Facial similarity threshold

ComplyCube represents the outcome of a facial analysis in the form of a facial similarity score. A facial similarity score can range from 0 to 100, with 100 being an exact match.

By default, an Identity check will deem two faces a match when the facial similarity score is over 80.

Liveness threshold

ComplyCube returns a liveness score, representing the outcome of a liveness analysis. A liveness score can range from 0 - 100; the closer the score is to 100, the greater the confidence that your client is a real person.

By default, an Identity check will deem a client real when the liveness score is over 50.

Enrolled faces limit

ComplyCube returns a previously enrolled face indicator, asserting whether a face was registered as a different client.

By default, an Identity check will deem a face previously enrolled when registered more than once.

Proof of Address Check

Document age threshold

By default, a Proof of Address check will automatically flag documents older than 3 months. You can adjust the threshold to be between 1 to 12 months.

Age Estimation Check

Minimum age

This setting empowers age estimation compliance by allowing you to set a minimum acceptable age before your client is flagged.

By default, an Age Estimation check will flag anyone younger than 18 years of age.

ComplyCube'smatching engine is purpose-built to find and match comparable identity data from any language or script. It incorporates sophisticated fuzzy matching algorithms, heuristics, linguistic variance, and phonetic analysis to find matches without producing costly and time-wasting lists of false positives.

ComplyCube's uses OCR technology and advanced analytics to authenticate and extract data from your clients' ID documents.

ComplyCube's utilizes computer vision, liveness, spoof-detection technologies, and facial comparison algorithms to determine whether two faces belong to the same client.

ComplyCube's aims to establish the issuing date of an eligible document using OCR. If a document is older than a specified threshold (e.g., 3 months), the document age analysis will be flagged for the check.

ComplyCube's uses facial recognition and liveness detection technology to estimate the age of your clients.

AML Screening
Document Check
Identity Check
Proof of Address Check
Age Estimation Check
Web Portal (Automation)