Skip to main content

​
Enrichments

Zenoo automatically enriches every verification with additional intelligence. These enrichments run without extra configuration or API calls. The enriched data appears in the pull response and webhook events.

​
Enrichment Summary

EnrichmentWhat It DoesTriggered By
UBO DiscoveryDiscovers beneficial owners from the company registryCompany Verification registry check
Company IntelligenceAI-powered company research and risk insight generationCompany Verification flow
Document ForensicsTamper detection and fraud analysis on identity documentsPerson Verification document upload
Risk Model EvaluationMulti-dimensional risk scoring across four risk dimensionsAll flows
Alert GenerationCreates compliance alerts from screening matchesScreening matches
Cross-Case DeduplicationReuses valid checks from previous verifications of the same entityReturning entities

​
UBO Discovery

When you submit a company for Company Verification, Zenoo queries the company registry to extract beneficial owners (UBOs). These are individuals with significant control or ownership (typically 25%+ voting rights or shares). Discovered UBOs are:
  • Added to the beneficial_owners[] array in the response
  • Automatically screened for PEP and sanctions exposure
  • Merged with any UBOs you provided in the request (deduplicated by name and date of birth)
If the registry does not disclose UBO information (varies by jurisdiction), the response only includes UBOs you submitted.

​
Company Intelligence

For Company Verification flows, Zenoo runs AI-powered research on the company to generate risk insights. This includes:
  • Public filings and regulatory actions
  • Industry risk classification
  • Corporate structure analysis
  • Negative news and reputation signals
The results contribute to the risk_assessment.factors[] array in the compliance report. Company intelligence runs in the background and does not add latency to the primary registry and screening checks.

​
Document Forensics

When a user uploads an identity document during a Person Verification flow, Zenoo performs automated fraud analysis:
  • Digital tampering detection. Identifies pixel-level manipulation, font inconsistencies, and metadata anomalies.
  • Document authenticity. Validates security features (holograms, watermarks, MRZ checksums) against known document templates.
  • Image quality assessment. Detects blurry, cropped, or screen-captured images that may indicate fraud attempts.
Results appear in the document.tamper_result and document.validation_result fields. A Warning or ATTENTION result does not necessarily mean fraud, but it flags the document for manual review.

​
Risk Model Evaluation

Every verification runs through a multi-dimensional risk model that evaluates four dimensions:
  1. Entity-Attribute Risk. Entity type, industry classification, incorporation age, revenue profile.
  2. Country Risk. FATF grey/black list status, Transparency International scores, sanctions program exposure.
  3. Screening Risk. PEP, sanctions, adverse media, and watchlist matches across all screened entities.
  4. Product/Channel Risk. Risk profile of the product type and onboarding channel.
Each dimension contributes a weighted score to the overall risk_assessment.overall_score (0-100) and determines the risk_tier (High, Medium, Low). See Risk Assessment for the full field reference.

​
Alert Generation

When screening returns matches, Zenoo automatically generates compliance alerts:
  • PEP alerts. Created when pep_status is Hit on any entity.
  • Sanctions alerts. Created when sanctions_status is Hit. These are flagged as the highest priority.
  • Adverse media alerts. Created when adverse_media_status is Hit, with the number of articles noted.
  • Data mismatch alerts. Created when submitted data conflicts with verified data (e.g., name on document differs from request).
Alerts are surfaced in the Zenoo dashboard for compliance analyst review. They do not block the API response. Your system receives the full screening results and can implement its own alerting logic based on the screening section of the compliance report.

​
Cross-Case Deduplication

When Zenoo encounters an entity that has been verified before (matched by name, date of birth, and nationality), it checks whether previous verification results are still valid. Valid checks are reused instead of re-executing. This:
  • Reduces verification costs for returning entities
  • Speeds up processing time
  • Maintains a consistent verification trail across cases
Reused checks are marked in the checks_summary with the original case reference. Validity periods vary by check type:
Check CategoryDefault Validity
Identity365 days
Screening90 days
Company180 days
Financial365 days
EDD180 days
If a previous check has expired, a fresh check is executed automatically.