Verifix

Inside the engine

What a rule can read and do

Rules read every signal the journey produced and write a decision, a band, or a branch, never a bare score.

01

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.

02

Visual rule builder

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

03

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.

04

Shadow testing

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

05

Journey overrides

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

06

Explainability

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

Draft to production

How a policy change ships

Edit, simulate against past sessions, approve, publish, with the version pinned to every decision.

01

1

Start from a preset

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

02

2

Tune the weights

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

03

3

Shadow test

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

04

4

Publish and monitor

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

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

Chain of custody

One policy change, as the record shows it

Illustrative sample data. A decision always names the rule version that produced it.

2026-02-11 09:40

Draft created · high_risk_jurisdiction_edd

2026-02-11 09:58

Simulated · 1,204 past sessions replayed

2026-02-11 10:12

Reviewed by MLRO · comments recorded

2026-02-12 08:05

Published · ruleset v7 live

2026-02-12 08:05

Prior version retained · old decisions still resolve

Named modules

The orchestration modules

Case work, reporting, and evidence export live on the case management page.

Journeys and risk rules

2 modules

The two modules that decide which checks run, in what order, and what their results mean.

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

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

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.

Continue

The rest of the platform

Most regulated journeys combine several of these. Each page covers one in the same detail.

KYC

Person, document, liveness

KYB

Entity, ownership, controllers

AML screening

Sanctions, PEP, adverse media

KYT

Transactions and wallets

Travel Rule

Counterparty data exchange

Case management

Queues, four eyes, audit

Your policy, written as rules instead of tribal knowledge.