Verifix

Capability pillars

Start with one, add the rest

Each pillar is a product on its own. Combined, they stop being five integrations and become one program.

01

KYC

Document authentication, biometric match, and liveness for individuals.

Explore KYC →

02

KYB

Registry verification, ownership graphs, and UBO discovery for entities.

Explore KYB →

03

AML

Sanctions, PEP, watchlist, and adverse-media screening with reasoning.

Explore AML →

04

KYT

Wallet risk, exposure tracing, and fiat transaction monitoring.

Explore KYT →

05

Travel Rule

Counterparty data exchange, unhosted-wallet proof, and message records.

Explore Travel Rule →

The console

One workspace for every pillar

Analysts do not switch tools between an identity check, a screening hit, and a transaction alert — it is one queue, one record, one trail.

VerifiX Console

Search customers, cases, wallets...

MO

Overview

Verifications

Businesses

Screening

Transactions

Cases

Risk rules

Customers

Settings

Verifications today

128

Sample data

Pending review

9

Sample data

Screening hits

4

Sample data

Avg. decision time

41s

Sample data

Review queueOpen cases

AM

Al Mira Digital Assets FZECleared

KYB · UBO discovery

3 owners resolved · registry match

11:24

SK

Sara K.Manual review

KYC · Emirates ID + liveness

Document authentic · biometric match 0.94

11:09

TX

Wallet bc1q...7f4aEscalated

KYT · inbound transfer

Exposure to high-risk counterparty

10:52

Illustrative interface — sample data

Choosing

Which pillar do you need

Most programs start with the obligation their supervisor examines first, then extend. This is the short version of that conversation.

Pillar

Answers the question

Runs when

Typical trigger to adopt

KYC

Is this person real, present, and who they claim to be?

At onboarding, and on re-verification

You onboard individuals and need documented identity evidence

KYB

What is this entity, and who ultimately owns and controls it?

At onboarding, and on structure change

You onboard companies, funds, or corporate counterparties

AML screening

Is this party sanctioned, a PEP, or adversely reported?

At onboarding, then continuously

Any regulated relationship, screening is rarely optional

KYT

Is this transaction or wallet behaving like the customer we approved?

After approval, on every flow

You move fiat or virtual assets after onboarding

Travel Rule

Who is the counterparty, and did their data travel with the transfer?

Before an in-scope transfer leaves

You are a VASP handling transfers at or above the AED 3,500 threshold

Risk engine

Which policy decided this, and under which version?

On every decision in every pillar

Your policy lives in spreadsheets or in people's heads

Case management

Who reviewed this, on what evidence, and who approved it?

Whenever a human touches a decision

Analysts work in inboxes and alerts are tracked manually

Shared layers

The part vendors leave to you

Screening APIs are commodity. What breaks compliance programs is everything around them, the rules, the queue, the trail.

01

Risk engine

Weighted scoring, a visual rule builder, versioned publishes, and shadow testing against historical traffic.

02

Case management

One queue for every alert type, four-eyes review, escalation paths, SLA timers, and role-based access.

03

Audit trail

Append-only record of every decision, artefact, note, and configuration change, exportable for inspection.

04

Journeys

UAE regulator journeys preset and ready to adjust, with wider GCC journeys next. Each journey step lists the checks it runs.

05

API and webhooks

Every console action is an API call, with webhooks on decision, alert, and rescreening events.

06

UAE data residency

Primary processing and storage in-country, details on the Security page

Five pillars. One decision engine.

Start with one, add the rest

KYC

KYB

AML

KYT

Travel Rule

One workspace for every pillar

Which pillar do you need

The part vendors leave to you

Risk engine

Case management

Audit trail

Journeys

API and webhooks

UAE data residency

A customer, not a pile of vendor responses

See VerifiX on your own onboarding flow