Skip to main content

Antifraud controls

Zyphe runs a set of complementary fraud and financial-crime checks across onboarding (KYC, KYB) and ongoing activity (AML screening, Transaction Monitoring). This page is the map of what exists; each row links to the page that explains how the check works and where you configure it.

Nothing here is a single “fraud score.” Each control produces its own evidence, and you combine them in a flow, a score, or a monitoring rule.

Onboarding: who the user is​

ControlWhat it catchesWhere it lives
Document authenticityTampered IDs, screen or paper copies, fake layouts, MRZ/OCR mismatches, voided documentsDocument verification
LivenessPhotos, videos, masks, and other presentation attacksLiveness
Face match (liveness × document)A live person who is not the portrait on the IDLiveness: compared against the document portrait
Proof of addressWrong document type, stale evidence, name mismatchProof of address
Device and location signalsGPS/IP country mismatch, VPN or proxy, blacklisted IP, device fingerprintGeolocation
Self-exclusion registersPlayers who have barred themselves from gambling, checked at signup, deposit and on triggersSelf-exclusion checks

Identity-document checks run on the capture or upload of a government ID. Corporate and supporting files collected in KYB are cross-checked against the official register and the uploaded evidence (see below), not through the same ID-capture pipeline.

Business verification: who the company is​

ControlWhat it catchesWhere it lives
Register cross-checkBusiness information that does not match the official company register or the uploaded documentsKYB · KYB guide
UBO discoveryHidden beneficial owners; incomplete or circular ownership chainsOwnership structure
UBO and director KYCUnverified people behind the companyEach UBO or director runs a linked KYC flow
PEP and sanctions on the company and UBOsListed entities, politically exposed persons and their relatives or close associates in the ownership chainAML

Ongoing risk: screening and payments​

ControlWhat it catchesWhere it lives
AML screeningSanctions, PEP (relatives and close associates included), watchlists, adverse media: on onboarding, on a cadence for flows that monitor, and on demandAML · Monitoring · AML Screening
Risk scoringWeighted topics from screening, amplified by jurisdiction, position, and relationshipRisk scoring · Scoring
Transaction MonitoringPayments that break your rules (amount, counterparty, country, keywords, timing)Transaction Monitoring
Inconsistency review (AI agents)Hits or fields that look like false positives, and alerts that need a first-line analystSee AI agents

Agents can also flag activity that does not fit the subject’s profile (for example a payment pattern that is inconsistent with declared or registered business activity). On Transaction Monitoring that review sits on raised alerts, not on every Allow.

AI agents as first-line analysts​

Across KYC, KYB, and Transaction Monitoring, the optional AI agent is a first-line compliance analyst: it reads the case, proposes a verdict, and, depending on the mode, either waits for a human or acts under a deterministic guard.

Every module uses the same three modes:

ModeWhat the agent does
DisabledThe agent does not run. Operators review every hit, case or alert.
SuggestThe agent runs and records its verdict and rationale. What it may still enact differs per module (below).
Auto-pilotThe agent may enact the decision. A clear is enacted only when a non-AI guard also passes; anything the guard vetoes is escalated.

What each module's agent reviews, what Suggest means there, and where the mode is set:

ModuleWhat the agent reviewsUnder SuggestWhere the mode is set
KYC (person AML)PEP, sanctions, and adverse-media hits on a personEscalations are enacted so the hit reaches a person; a clear stays a suggestion for a person to confirm.AML Agent Mode on the document-verification step. See AML Agent Mode.
KYBThe company's case: business information vs documents vs the official registerThe agent proposes a decision; a reviewer makes it.KYB Agent Mode on the KYB step. See KYB Agent Mode. Company and UBO screenings use AML Agent Mode on the same step, with the AML meaning of Suggest.
Transaction MonitoringEach new rule alert (first-line triage so analysts see exceptions)The agent records a recommendation and leaves the alert untouched.Transaction Monitoring → TM Settings → Agentic alert review (Admins only). AutoPilot there may close a demonstrable false positive or escalate, within the guard limits set on the same card. See Settings and alerts and Alert Queue.

Some matches always go to a person, whatever the mode. On Transaction Monitoring, sanctions, PEP and other protected typologies, list hits, blocked transactions and incomplete evidence stay with an analyst. On AML, the agent never clears a high-confidence sanctions match, a Critical risk, or a match in a category your compliance policy rejects.

Missing or unparseable configuration fails closed: the agent does not run.

How the pieces combine​

A typical full-cycle setup:

Document verification (+ authenticity checks)
→ Liveness (+ face match)
→ optional Geolocation / Proof of address / Form
→ AML screening → Risk score
→ (businesses) KYB register cross-check + UBO unwrapping
→ ongoing: rescreening + Transaction Monitoring on each payment

Scores and monitoring rules are how you turn those signals into a policy (review, block, escalate). See Scoring and Transaction Monitoring.