Skip to content
VerifiX, secured by ITSEC

Roadmap

UAE PASS integration, coming to VerifiX journeys.

Residents and businesses will be able to establish their identity with the UAE's national digital identity inside the same VerifiX journey, with the screening, risk rules, case queue, and audit trail around it unchanged.

Tell me when it is liveSee KYC available today

Status

Where this stands

Stated plainly, because a compliance roadmap is not a marketing surface.

UAE PASS integrationComing soon

The integration is in progress. We are not publishing a live date until it is committed, and this page is where the status will change when it is.

Status
In progress
Live date
Not published
Identity path today
Emirates ID + liveness
Integration impact
Journey version only

What UAE PASS is

A national identity credential, in compliance terms

Most teams know UAE PASS as the government sign-in app. This is what it means inside a regulated onboarding journey.

01

A national digital identity

UAE PASS is the UAE's national digital identity, used by residents and businesses to sign in to government and private services with credentials already tied to their identity records.

02

An identity step, not a replacement platform

For a compliance program, UAE PASS is one way to establish who the applicant is. The obligations around it, screening, risk decisioning, review, record keeping, stay exactly where they are.

03

Available to your existing journeys

When it goes live in VerifiX, it becomes a selectable step inside the journeys you already run, alongside document capture and liveness rather than instead of the wider journey.

How it will fit

One step changes, the journey does not

The sequence below is the journey you run today, with UAE PASS in the identity position instead of document capture.

  1. 1

    The applicant chooses UAE PASS

    In a journey where the step is enabled, the applicant picks UAE PASS instead of scanning a document. Journeys can offer both, so anyone without UAE PASS still completes the same flow.

  2. 2

    The applicant consents to share their identity data

    Consent happens on the UAE PASS side. VerifiX receives what the applicant agreed to share and records the consent event on the session, so the basis for holding the data is part of the file.

  3. 3

    The identity data lands on the same session object

    The returned attributes populate the same customer record that document capture would have populated, so nothing downstream needs to know which route the applicant took.

  4. 4

    Screening and risk rules run unchanged

    Sanctions, PEP, and adverse-media screening execute on the resolved identity, and your versioned risk rules produce the decision, approve, review, or decline.

  5. 5

    Reviews and evidence stay in one place

    Anything needing a human lands in the same case queue, with the identity source, consent record, screening results, and reviewer actions on one append-only trail.

What does not change

Adopting it later is a journey change, not a rebuild

  • The same API and webhooks, the identity step changes, your integration does not
  • The same journey builder, so enabling UAE PASS is a journey version, not a project
  • The same screening, risk rules, and thresholds you already published
  • The same case queue, four-eyes thresholds, and roles
  • The same evidence record and export bundle for a supervisory request
  • The same fallback path for applicants who do not use UAE PASS

Build on the live path now

Teams waiting for UAE PASS before starting lose months for a step they can swap in later. Integrate the journey today, then enable UAE PASS on the same journey when it ships.

See the integration path

Available today

The identity path running in production now

Nothing on this page depends on UAE PASS to go live with a UAE-ready onboarding journey.

01

Emirates ID and passport capture

Document authentication, chip read where available, and data extraction on Emirates ID, passports, and residency documents.

02

Biometric match and liveness

Passive and active liveness with face match against the document portrait, so the person is proven present rather than merely documented.

03

Screening and the full audit trail

Sanctions, PEP, and adverse-media screening, versioned risk rules, case management, and an append-only evidence record.

Full detail on the KYC page and in the module catalog.

Questions

Frequently asked

Is UAE PASS available in VerifiX today?
No. It is in progress and marked coming soon on this page and in the product. Everything described in the journey above works today with Emirates ID capture and liveness as the identity step.
When will it go live?
We do not publish a date we cannot commit to. Contact us and we will tell you where the integration stands and notify you when it is available.
Will we need to re-integrate when it ships?
No. UAE PASS arrives as an identity step inside the journey builder. You enable it on a journey, publish a new journey version, and your existing API integration keeps working.
Does UAE PASS remove our screening or record-keeping obligations?
No. It establishes identity. Screening, risk decisioning, ongoing monitoring, and evidence retention remain your obligations, and VerifiX runs them the same way regardless of how identity was established.
What happens to applicants who do not use UAE PASS?
They complete the document and liveness path in the same journey. A journey can offer both routes and record which one produced the identity evidence.

See VerifiX on your own onboarding flow

A 30-minute walkthrough with a compliance engineer, or a request for sandbox access.

Book a demoRequest sandboxProduct guide (PDF)