Policy Waits on Engineering
A change of risk appetite becomes a ticket, a sprint and a release. The compliance officer owns the obligation but not the switch.
Veri Compliance
KYC, KYB and AML behind a single integration. Veri sits between your product and the providers that verify identities, screen names and check companies. You integrate once; Veri orchestrates the providers, normalises their answers, applies your rules and returns one decision — with the evidence and audit trail attached.
The Problem
A change of risk appetite becomes a ticket, a sprint and a release. The compliance officer owns the obligation but not the switch.
Once a provider's status names and document taxonomy are stored in your tables, that provider is no longer replaceable.
When an examiner asks why a customer was onboarded, the answer lives in four consoles, two spreadsheets and someone's memory.
Synchronous calls put a vendor's availability on your critical path. Onboarding stops, queues back up, and support absorbs the difference.
The Platform
Veri owns the workflow, the normalisation, the rules, the risk and the decision. Providers supply evidence. That separation — kept strictly, everywhere in the codebase — is what makes a vendor replaceable and a decision explainable.
Individuals, legal entities, related parties and documents — all resolving to one record.
Versioned flows, steps, requirements and expiry — configured, not coded.
Weighted, deterministic scoring with tenant rule sets. Your policy lives as configuration.
One outcome, reasons attached, full event store — raw and normalised responses for every decision.
Coverage
Documents, liveness, face match and address verification through identity engines.
Biometric confirmation with session-based flows and anti-spoofing.
KYB checks across company records, directors, shareholders and ultimate beneficial owners.
Screening against sanctions lists, politically exposed persons and adverse media.
Configurable requirements, risk weightings and deterministic decisioning built into the platform.
One event store for every request, response and decision — with webhooks, idempotency and full observability.
Architecture
Everything the dashboard does is available on the same versioned REST API.
Every record is tenant-scoped; no request can cross a tenant boundary.
Provider work runs on queues: retryable, idempotent, observable and bounded.
Separate keys and scripted scenarios; sandbox never touches production.
Talk to us about a sandbox evaluation or production onboarding.
Talk to Sales