Introduction
Zyphe is identity infrastructure built so organizations can verify, reuse, and monitor trust, without treating personal data as a free-for-all.
One platform covers:
- Identity verification (KYC): document, liveness, address, phone, forms, and more, composed into flows
- Business verification (KYB): companies, directors, and beneficial owners
- Reusable credentials: one-click KYC and KYC Passport so partners reuse an existing verification with user consent
- AML screening & monitoring: sanctions, PEP, adverse media, and ongoing risk
- Transaction monitoring: rules, lists, and Allow / Review / Block decisions
Privacy is not a slogan here: PII is stored with user-centric controls, access is role-based, and sharing is grant-driven. For the architecture behind that, see Decentralized Identity; for what you decide as controller and what Zyphe retains, see Privacy, consent and retention.
Start here
| Path | Who it's for | Time |
|---|---|---|
| Quickstart | Anyone shipping a first verification | Shortest linear path |
| Verification types | Anyone comparing what each check verifies and returns | One-page map of every check |
| Choosing an integration method | Engineers deciding hosted link vs SDK vs agent | Decision page |
| Integration | Hosts, HTTP API, mobile WebView, export, go-live | Backend recipe hub |
| Environment setup | Anyone calling the API (hosts, keys, .env) | Read once |
| Sandbox and go-live | Teams ready for production | QA + cutover checklist |
| Privacy, consent and retention | DPOs, legal and integrators acting as controller | Roles, retention, deletion |
| Guides | Configuring and operating each capability | Task-oriented how-tos |
| Statuses and codes | Interpreting webhooks and API outcomes | Reference |
| API reference | Coding against the exact contract | OpenAPI + schemas |
Core objects
These are the concepts you will see across the product and API:
| Object | What it is |
|---|---|
| Flow | The sequence of verification steps a user completes (document, liveness, PoA, …) |
| Verification request | One run of a flow for a specific user |
| Flow result | The reviewed outcome, scores, and collected data (subject to role and PII access) |
| Webhook | Signed real-time notification when a result or status changes |
| Score | Explainable risk or quality signal derived from tags, factors, and checks |
| Transaction | An activity event evaluated by transaction-monitoring rules |
Deeper model: Verification process · Data flows
Products
Every check on one page, with what it verifies and what it returns: Verification types.
| Product | Outcome | How it works | Guide |
|---|---|---|---|
| Flows / KYC | Onboard users with composable checks | Verification process · Document · Liveness | Create a flow |
| Proof of address | Verify residency evidence | PoA | Configure PoA |
| KYB | Verify businesses and ownership | KYB | Business verification |
| Reusable credentials | Reuse trust across partners | One-click KYC | KYC Passport |
| AML | Screen and monitor financial crime risk | AML | Risk scoring · Agentic review · Monitoring |
| Transaction monitoring | Continuous Allow / Review / Block | TM concepts | TM operation |
| Scoring & review | Turn signals into decisions | - | Scoring · Manual review |
| Antifraud controls | Document, liveness, KYB, AML, TM, agents | Antifraud controls | Linked from that map |
Who this documentation is for
Engineers: integrate with a public link, SDK, webhooks, or an MCP-compatible AI agent. Start with the Quickstart.
Compliance & operations: review results, configure scores, manage AML and transaction-monitoring cases, and enforce role-based PII access. See Manage users, Scoring, and Privacy, consent and retention.
Partners & networks: invite organizations and reuse verifications with user consent via KYC Passport and reusable credentials.
How the docs are organized
| Section | Intent |
|---|---|
| Quickstart | One opinionated path from zero to a reviewed result |
| Overview | What the product is, why it works this way, conceptual data flows |
| Guides | How to configure and operate each capability |
| Reference | Statuses and codes, OpenAPI, LLM-friendly docs |
Rule of thumb: deciding whether → Overview · fastest try → Quickstart · configure → Guides · code the contract → Reference.