Skip to content
VerifiX — secured by ITSEC

Platform · Risk engine

Your policy, written as rules instead of tribal knowledge.

A weighted scoring model and visual rule builder that turn your risk appetite into versioned, testable, explainable logic — the same engine behind every KYC, KYB, AML, KYT, and Travel Rule decision.

Request sandboxBook a demo
Rule definition
rule "high_risk_jurisdiction_edd" {
  when {
    customer.residency in policy.high_risk_countries
    or entity.jurisdiction in policy.high_risk_countries
  }
  then {
    score += 25
    require "enhanced_due_diligence"
    route_to "mlro_queue"
  }
}

# version 14 · effective 2026-08-01 · author m.othman
# jurisdiction risk list source: set per tenant in console

What it checks

Every check, named

No bundled black box. Each check is listed, configurable, and visible in the decision it produced.

Weighted scoring

Each factor contributes a transparent weight to a 0–100 score, and the breakdown is shown on the decision — never an unexplained number.

Visual rule builder

Compliance staff build and edit rules without engineering tickets, using the same primitives the API exposes.

Versioning

Every rule set is versioned with an author and effective date, so a two-year-old decision can be replayed against the logic that produced it.

Shadow testing

Run a candidate rule set against historical traffic to see what would have changed before it touches a live customer.

Journey overrides

Retail, corporate, and high-value journeys can carry different thresholds while sharing one policy library.

Explainability

Each decision returns the triggered rules, factor contributions, and the threshold it crossed — in the API and in the case record.

How it runs

From request to decision

The same sequence whether you call the API directly or use the hosted flow.

  1. 1

    Start from a preset

    Load a UAE regulator journey preset, then adjust it instead of writing a policy from an empty page.

  2. 2

    Tune the weights

    Set factor weights and score bands for clear, review, and blocked per journey.

  3. 3

    Shadow test

    Replay historical verifications to see the change in clear rate, review load, and block rate before publishing.

  4. 4

    Publish and monitor

    Publish as a new version, then watch decision distribution and review volume for drift.

Modules

The checks behind this pillar

Each one is a separate module you can switch on, order, threshold, or skip inside a journey.

Platform and orchestration

6 modules

The surfaces around the checks: journey builder, case management, reporting, evidence export, and the audit trail.

Journey builder

journey_builder

Composes modules into an ordered journey with branching: run this check only if that one flags, escalate to enhanced due diligence on a risk band, skip a step for a low-risk segment.

Input
Journey definition, versioned
Returns
an executable journey ID your API calls reference by name

Risk scoring engine

risk_engine

Weighted, explainable scoring across every signal produced in the journey. Each score shows the contributing factors and the policy version that produced it.

Input
Journey signals and your weights
Returns
score, risk band, contribution breakdown, policy version

Case management

case_management

Alert queues, assignment, four-eyes approval, escalation paths, notes, and a full decision history for every customer and every alert.

Input
Cases created by journeys and monitoring
Returns
case state machine, reviewer actions, SLA timers

Regulatory reporting workpapers

reporting

Assembles the case narrative, evidence, and decision history into the workpaper an analyst files with the relevant financial intelligence unit.

Input
Escalated case
Returns
report pack, filing record, retained submission evidence

Immutable audit trail

audit_trail

Append-only record of every check, decision, override, policy change, and export — who, what, when, and under which policy version.

Input
All platform activity
Returns
queryable event log and a signed evidence export

Evidence export

evidence_export

Produces a decision PDF or evidence bundle per case, and bulk exports to your warehouse or object storage for inspection and retention.

Input
Case or date range
Returns
PDF, JSON, or archive with a manifest and checksums

See the full module catalog — every KYC, KYB, AML, KYT, and platform module with its inputs and outputs.

Evidence retained

What your auditor sees

  • Rule set version, author, and effective window
  • Factor weights and score bands at decision time
  • Triggered rules per decision with the values that triggered them
  • Shadow-test results retained against the version they informed
  • Full change history for every published version
Score
0–100 with per-factor contribution
Bands
clear · review · blocked, configurable
Versioning
immutable published versions, replayable
Access
console builder and API for both

Questions

Frequently asked

Can engineers manage rules in code?
Yes. Rules are readable and writable through the API, so you can keep them in your own repository and promote them through your pipeline.
Who can publish a rule change?
Publishing is permission-gated and can require a second approver, with the change recorded in the same audit trail as case decisions.
How do the UAE presets map to obligations?
Each preset rule states the obligation it addresses, and the mapping is reviewed with you during onboarding.

See VerifiX on your own onboarding flow

A 30-minute walkthrough with a compliance engineer, or a sandbox key in your inbox today.

Book a demoRequest sandbox