This page describes the product flow for Veriff powered by zkMe, the on-chain IDV/KYC solution on Moca Network. It is not an integration guide; for AIR Kit setup and APIs, see AIR Kit.Documentation Index
Fetch the complete documentation index at: https://docs.moca.network/llms.txt
Use this file to discover all available pages before exploring further.
End-to-end flow
User starts verification in your app
The user launches the Veriff powered by zkMe experience inside your application (AIR Kit surfaces the flow; your product does not need to host raw KYC storage to participate).
Programmatic path (default)
The user completes document capture, NFC chip read where the document supports it (electronic passport / eID), liveness, and face matching. On supported documents, zkPassport establishes cryptographic authenticity of the chip (ICAO-style passive authentication). The verified outcome feeds the AIR Credential with whatever disclosure level the issuance and verification programs require — from pass/fail only through selective attributes to full raw payloads where CAK and user consent apply.
AML and sanctions screening
Screening runs as part of the on-chain IDV/KYC pipeline so the resulting credential reflects both identity and financial crime compliance signals your programs require.
Manual reverification (when needed)
If the automated path cannot complete — for example unreadable chip, document edge case, or biometric mismatch — the session moves to human review under Veriff powered by zkMe. From the user’s perspective this matches a traditional eKYC outcome: approved, rejected, or more information requested.
Credential issuance (AIR)
On success, zkMe (as Issuer) issues an AIR Credential into the user’s AIR Account. Cryptographic commitments anchor on Moca Chain; sensitive payloads remain under zkMe’s protection model (see Data collection & sharing and zkMe security architecture).
Verification at any partner
When the user presents the credential elsewhere in the ecosystem, the verifier calls AIR Kit verification and receives whatever the verification program is configured to return — a pass/fail signal, a selective set of attributes, or the full raw dataset under explicit user consent (including the CAK path when enabled).
Sequence overview
Geographic coverage (zkPassport)
For electronic passport flows that rely on published country signing keys, zkPassport supports a large set of issuing countries. Documents from other jurisdictions may still be verified through the document-and-biometric path without NFC, subject to Veriff powered by zkMe coverage rules. For the authoritative country list, see zkMe documentation: Supported countries.Related reading
Overview
On-chain IDV/KYC positioning, disclosure flexibility, and what the bundle includes.
Data lifecycle
What each party sees and stores across pass/fail, selective, and full-raw modes.