Skip to main content

Quickstart

This is the shortest path from zero to a reviewed verification result. Follow the seven steps in order. Each links to the relevant guide if you want more depth. You can complete the whole path in the sandbox, with no contract and no production data.

Where to go for detail

This page is deliberately linear and opinionated. Every capability it touches has a full guide; follow the links when you need options, edge cases, or reference material.

1. Create an account and open the sandbox

Sign up and open your organization in the dashboard. Switch the dashboard to sandbox mode. Everything below runs against synthetic data, so you can build and test without any production entitlement or data-processing agreement.

2. Create your first flow

A flow is the sequence of steps a user goes through to get verified (document check, liveness, proof of address, and so on). Open the flow builder and create one. Start from a template or add a couple of steps such as Document Verification and Liveness.

Create a flow

3. Run a test verification

From the flow you just built, start a verification request in the sandbox and complete it yourself. This produces a flow result: the record you will review in step 6.

Create a flow → running a verification

You have two ways to put the flow in front of a real user (see Choosing an integration method for a full comparison, including MCP agents):

  • Public link: Zyphe hosts the verification UI; you share a URL and receive the result. The fastest path to a working integration. → Sharing a flow
  • SDK: embed verification directly in your web or mobile app for a native experience and full control over the UX. → SDKs

Pick one for now; you can add the other later.

5. Receive a webhook

Register a webhook endpoint so your backend is notified when a verification completes, instead of polling. Zyphe signs every delivery so you can verify it came from us.

Webhooks · Webhook signature

6. Review the result

Open the flow result in the dashboard. You will see its status, the collected data (subject to your role and PII access), and any computed scores. Approve or reject it, or configure manual review to route results to a reviewer automatically.

Manual review · Reviewing scores

7. Prepare for production

When your sandbox integration works end to end, use the full Sandbox and go-live checklist. In short:

  1. Generate production API keys.
  2. Point your webhook at your production endpoint and confirm signature verification.
  3. Review billing and enable the products you need.
  4. Switch your integration from the sandbox to the production environment.
  5. Map statuses and failure reasons with Statuses and codes.

Where to next