LDX

VERI

One API. Every compliance check.

KYC, KYB and AML behind a single integration, with one decision, evidence and audit trail.

Built for fintechs, PSPs, banks, wallets, VASPs and regulated marketplaces that cannot afford five vendor integrations forever.

Compliance infrastructure by LDX

Compliance stopped being a policy problem and became an integration project

A regulated business today buys identity verification from one vendor, sanctions and PEP screening from another, company data from a third, and often a fourth for a market the others do not cover well. Each arrives with its own API, field names, statuses and webhooks. The compliance team writes the policy; the engineering backlog decides when it can be applied.

VERI removes that dependency. One integration covers every provider. One schema carries every result. Your policy lives as configuration (flows, rules and risk weightings) you can change without a release. Because VERI, not the provider, makes the final call, replacing a vendor becomes a configuration change rather than a rebuild.

  • Policy waits on engineering

    A tighter PEP stance or a new high-risk country list becomes a ticket, a sprint and a release.

  • Vendor semantics leak into the product

    Once a provider's status names live in your code, that provider is no longer replaceable.

  • The audit trail is assembled by hand

    When an examiner asks why a customer was onboarded, the answer lives in four consoles and two spreadsheets.

  • A provider outage becomes your outage

    Synchronous calls put vendor availability on your critical path. Onboarding stops and queues back up.

1

Integration, not five

3

Check families: identity, business, screening

<15

Minutes to a first sandbox request

0

Code changes to switch provider

What VERI covers today

A multi-tenant, API-first compliance orchestration platform: it abstracts providers, normalises their responses, identifies what is missing, calculates explainable risk, applies your rules and returns a single decision with complete auditability.

> KYC

Identity and document verification, liveness and face match.

> KYB

Company, directors, shareholders and UBO checks.

> AML

Sanctions, PEP and adverse media screening.

> Decisioning

Requirements, risk weightings and policy rules owned by your compliance team.

> Events & audit

Webhooks, an event store, and raw plus normalised responses kept side by side.

> Provider freedom

Swap Sumsub, Veriff, ComplyAdvantage, World-Check and registries without rewriting your app.

Three jobs, done once instead of five times

  1. 01

    Orchestrate

    Which checks run, in which order, against which provider, and what happens when one is unavailable. Flows are named, versioned and immutable once live.

  2. 02

    Normalise

    Every provider response lands in the same plain format. The original answer is kept alongside it for audit, dispute and review.

  3. 03

    Decide

    Results, screening hits, missing requirements and your own rules resolve into one outcome with the reasoning attached. No provider determines a VERI decision.

  4. 04

    Contain failure

    Queued, idempotent jobs, timeouts, circuit breakers and provider fallback so a vendor outage does not become your outage.

Built for regulated teams

Policy as configuration

Flows and rules are versioned and effective immediately. Compliance owns the switch, not the sprint board.

One event store

Raw and normalised responses, reasons per decision, ready when an examiner asks.

Delivered by LDX

Mauritius and South Africa, fintech since 2006. Live today, with sandbox for evaluation and production on onboarding.

From sandbox to production

  1. 1

    Integrate once

    Connect your product to VERI instead of each vendor separately.

  2. 2

    Configure policy

    Set requirements, flows, rules and risk weightings without a release.

  3. 3

    Run in sandbox

    Reach a first sandbox request in minutes and prove the decision path.

  4. 4

    Go to production

    Onboard with LDX, keep providers swappable, and keep the audit trail complete.

What your engineering team no longer absorbs

  • No per-vendor applicant, session or case models in your code
  • No hand-built reconciliation of four definitions of verified
  • No weeks of engineering to add one more provider end to end
  • No rewrite to replace a KYC or screening vendor
  • Explainable risk and requirements decisioning
  • Security and auditability designed for regulated environments