Skip to main content
Automation rules enable automatic decision-making during KYC session processing. Configure rules to automatically approve, deny, flag, or require manual review based on various conditions.

Overview

Automation rules are defined in the validation_config.automation_rules object of a workflow. When a session is processed, all enabled rules are evaluated and actions are triggered accordingly.

Actions

All automation rules can trigger one of these actions:
Actions are prioritized: auto_deny > manual_review > flag > auto_approve. If multiple rules trigger, the highest priority action wins.The flag action results in a flagged final decision. Flagged sessions are considered approved (the session status is approved) but are marked for extra attention or monitoring. This is useful for industries or conditions that don’t warrant rejection but require oversight.

Base Configuration


Country Rules

Trigger actions based on nationality, residence, or incorporation country.

Properties

How It Works

Country rules match against:
  1. Country fields in forms with matching country_type
  2. Address fields with matching country_type
  3. Extracted document data (e.g., nationality from passport)
Use applies_to to differentiate between nationality and residence rules. A user with nationality: IR and residence: US can have different rules applied.

List Match Rules

Trigger actions based on sanctions/watchlist matches.

Properties

Entity Scope

If you have different risk appetite for directors vs the primary subject, use multiple rules with different entity_scope values.

Face Deduplication

Detect repeat applicants by comparing faces across sessions.

Configuration

Config Properties

Rule Properties

Use Cases

  • Flag repeat applicants: Detect when same person applies multiple times
  • Fraud prevention: Auto-deny after 3+ rejected applications
  • Account linking: Identify potential duplicate accounts

Document Rules

Validate document age, expiration, validity, and image quality.

Properties

Document Validation Checks


Extraction Validation Rules

Run additional validations on fields extracted from documents.

Properties

Validation Types


Form Field Rules

Trigger actions based on user-declared form field values.

Properties

Operators


Volume Rules

Trigger actions based on declared transaction volume.

Properties

Volume rules apply to volume fields and currency fields with apply_volume_rules: true.

Time to Complete Rules

Trigger actions based on how long the session took to complete.

Properties

Use Cases

  • Bot detection: Flag if completed in < 30 seconds
  • Abandonment: Flag if took > 24 hours

Email Verification Rules

Trigger actions based on email verification results.

Config Properties

Rule Properties


Face Match Rules

Configure face matching between ID photo and selfie/liveness.

Properties


Web Validation Rules

Comprehensive rules for website/domain validation. See Web Validation for background.

Rule Components

Trigger actions based on overall reliability score (0-100).
Rules for SSL certificate validation.
Rules for specific page statuses.
Rules for industry classification.Evaluation priority: blocked industries are checked first, then flagged industries, then industry mismatch. A blocked industry will not also trigger the flagged rule.
Rules for adverse media check results.
Rules for domain sanction check.
Rules for social media presence.
Rules based on Tranco popularity ranking.
Rules for page content evidence.
Rules for website policy analysis: Terms & Conditions (terms_rules), AML/KYC policy (aml_rules), return policy (return_rules), and refund policy (refund_rules). Each policy triggers rules of type web_policy_terms, web_policy_aml, web_policy_return, web_policy_refund respectively.Common properties (all four policy types):Additional properties for terms_rules and aml_rules:terms_rules only:aml_rules only:

Watchlist Auto-Add

Automatically add entities to watchlists based on session outcome.

Config Properties

Rule Properties

Entity Types


Complete Example

Processing Flow

When a session is processed with automation rules:
  1. Validation runs: Lists, adverse media, crypto, face match
  2. Rules evaluated: All applicable rules are checked
  3. Actions collected: All triggered actions are recorded
  4. Final decision: Highest priority action determines outcome
  5. Status mapping: The final decision maps to a session status:
    • auto_approveapproved
    • auto_denyrejected
    • flagapproved (with final_decision = flagged)
    • manual_reviewmanual_review
    • no_actionmanual_review (default for safety)
  6. Watchlist add: If configured, entities are added to watchlists
  7. Response returned: Includes automation_flags and final_decision

Response with Automation Results