Start
Zippy KYC overview
Integrate identity verification with hosted flows, APIs, and signed webhooks.
Zippy KYC helps merchants verify customer identity with inquiry templates, hosted verification, review decisions, and signed webhooks.
Start building
Quickstart
Create a key, configure a webhook, and open your first inquiry.
Authentication
Secure backend requests with the X-Api-Key header.
Inquiry lifecycle
Handle verification states and terminal decisions correctly.
Web SDK
Embed the template-driven verification experience in your application.
Webhooks
Receive events and verify every delivery signature.
Models
Integration models
API-key merchant flow
Your backend opens an inquiry with X-Api-Key, stores the returned inquiry identifier, and directs the customer to the hosted flow.
Portal hosted inquiry link
Operators create inquiries from the dashboard (openedSource=PORTAL_LINK). Customers complete verification on the hosted experience; your systems still consume webhooks and status APIs.
Architecture
How Zippy works
Merchant backend
Opens an inquiry
Zippy API
Returns inquiryId
Hosted verification
Customer completes KYC
Decision
Policy and review outcome
Decision events
inquiry.approved
inquiry.review_in_progress
inquiry.declined
Decisions land as inquiry statuses such as Approved, Needs Review, and Declined. Document images are exportable when status is Approved or Needs Review.
Quickstart
10-minute integration path
- Create a portal account / tenant and publish an inquiry template with webhook subscriptions.
- Create an API key (
zk_live_..., shown once). - Register an HTTPS webhook endpoint and store
whsec_.... - Open an inquiry and send the customer to the hosted verification flow.
- Verify webhook signatures and handle approved / needs review / declined.
- Fetch documents when status is APPROVED or NEEDS_REVIEW.