Integrations | VerifiX

Where it connects

Six integration surfaces

Each surface names the direction data moves and the endpoints or protocols involved, so your architect can size the work from this page.

01

Core platform

Two-way

Trigger verifications from your exchange, core banking, or account-opening system and write the decision back against the customer record.

POST /v1/verificationswebhook verification.completed

02

Data warehouse

VerifiX → your system

Stream decisions, risk scores, and case events into your warehouse for MI, board reporting, and model review.

GET /v1/audit-eventsscheduled export

03

Workflow and alerting

VerifiX → your system

Route escalations and rescreening hits into the channel your analysts already watch, with a deep link back to the case.

webhook case.escalatedwebhook screening.match_found

04

Ticketing and CRM

Two-way

Open a task when a case needs a document from the customer, and close it automatically when the evidence lands.

webhook case.assignedPOST /v1/cases/{id}/notes

05

Identity and SSO

Your system → VerifiX

SAML and OIDC single sign-on with group-to-role mapping, so console access follows your directory, not a spreadsheet.

SAML 2.0OIDCSCIM provisioning

06

Registries and screening data

VerifiX → your system

Company registries, sanctions and PEP data, adverse media, and chain analytics. Sources are named in your contract and in our sub-processor list.

managed by VerifiXno contract of yours required

How it connects

Four patterns, pick per system

Most customers combine two: hosted flow for the customer-facing capture, REST and webhooks for everything internal.

01

REST + webhooks

The default

You call the API when a customer starts onboarding; we call your endpoint when the decision or an alert is ready.

POST /v1/verifications
→ 201 { "id": "ver_8H2K", "status": "awaiting_subject" }

# later, to your endpoint
POST https://you.example/verifix
{ "type": "verification.completed",
  "data": { "decision": "approved", "risk": { "score": 18 } } }

02

Hosted flow

Fastest to launch

Redirect or embed the hosted verification flow, and skip building capture, guidance, and retry UX entirely.

POST /v1/verifications
{ "journey": "uae_vasp_retail",
  "redirect_url": "https://you.example/done" }

→ { "hosted_url": "https://flow.verifix.ae/s/…" }

03

Bulk and batch

Remediation and periodic review

Upload an existing book for remediation or periodic review, and receive results as they complete rather than in one blocking job.

POST /v1/batches              # CSV or JSONL
→ { "id": "bat_21", "rows": 14820 }

GET /v1/batches/bat_21/results?cursor=…
# results stream as each row completes

04

Export and retention

Audit and archive

Scheduled evidence and audit export to your own object storage, on the retention schedule you set.

GET /v1/audit-events?from=2026-01-01
→ signed archive URL (evidence + trail)

# or scheduled delivery to your bucket
PUT /v1/settings/export

Reference

The endpoints you will actually call

A first integration usually touches five of them.

# Trigger from your core system
POST /v1/verifications                   # start a KYC or KYB journey
GET  /v1/verifications/{id}              # poll if you cannot receive webhooks
GET  /v1/verifications/{id}/evidence     # pull the evidence bundle
GET  /v1/cases?status=referred           # feed your analyst work queue
GET  /v1/audit-events?from=…             # scheduled evidence export

AuthBearer key per environment, scoped and rotatable.

IdempotencyIdempotency-Key accepted on every write.

WebhooksSigned, retried with backoff, replayable from the console.

EnvironmentsSandbox with deterministic test identities, then production.

VersioningMajor version in the path; breaking changes ship as a new version.

Regulator-safe by default

Compliance you don't have to worry your way through

The stressful part of KYC is rarely the technology; it is wondering whether what you did will hold up when someone asks. VerifiX is built so the answer is already on file: UAE-hosted data, journeys mapped to your authority, and a complete evidence trail behind every decision.

VARACBUAECMADFSAFSRA

Hosting

UAE regions on AWS and Azure

Certifications (ITSEC)

ISO 27001 and ISO 22301

Security and data handling →Regulator journeys in detail →

Journeys mapped to your authority

Pick your regulator and the onboarding sequence, checks, and review cycles are already configured, you are not designing a compliance flow from a blank page.

Evidence pack per case

Every decision keeps the documents, screening results, scores, and reviewer actions that produced it, exportable as a single case file when an examiner asks.

Audit trail you did not have to build

Who checked what, when, and on which policy version is recorded automatically, no spreadsheets reconstructed after the fact.

Ongoing obligations run themselves

Rescreening and periodic review run on the cadence set for your license type, so lapses are not something you have to remember.

Fits the stack you already run.

Six integration surfaces

Core platform

Data warehouse

Workflow and alerting

Ticketing and CRM

Identity and SSO

Registries and screening data

Four patterns, pick per system

REST + webhooks

Hosted flow

Bulk and batch

Export and retention

The endpoints you will actually call

Specific systems

Compliance you don't have to worry your way through

UAE regions on AWS and Azure

ISO 27001 and ISO 22301

Journeys mapped to your authority

Evidence pack per case

Audit trail you did not have to build

Ongoing obligations run themselves

Tell us what you run