Platform

Run identity verification as part of your own operation.

One console for the whole job: the flows people go through, the rules that decide, the queue where your team reviews, and a record of every identity an auditor can follow.

  • Free credit to start
  • No monthly minimum
  • White label included
Illustration of the Identiko console: the identity record for Layla Haddad, approved, with three sessions (onboarding, re-verification and a step-up in review), each linked to the workflow version it ran on. Her details show where each value came from: checked, read from the document, or disputed. Her face is registered in the collection, with no duplicate and no blocklist hits.

How it works

One verification, through the whole platform.

From the link your applicant opens to the record your team keeps. Watch one run through, or pick a step.

Illustration of one verification travelling from the applicant’s phone, past the document and face capture, through four checks and your rules, which choose Approve over Reject or Review, into the evidence cabinet with its video record.
  1. Your applicant opens the link, in your brand. On a desktop, a QR code moves them to their phone.

  2. The camera captures the document, then the face for liveness and face match. Uploads aren’t accepted.

  3. ID, liveness, face match and AML run in your order. Your rules approve, reject or send to review.

  4. Reviewers release cases with a recorded reason. Video evidence and the audit log stay with the identity.

Core concepts

Three building blocks. Everything else hangs off them.

Identities, verifications and workflows are kept apart on purpose. That is what lets you re-verify, step up or re-screen a person without creating a duplicate.

01Identity

Identities

Every person who goes through your flow gets a single record that groups all their activity and results.

1 per individual

02Session

Verifications

The sessions a person goes through over time. Each one is linked to a specific workflow version.

1 identity : N sessions

03Logic

Workflows

Checks and decisions that define what runs, in what order and under which conditions.

1 session : 1 workflow

Modules

Six modules, one record behind them all.

Each module works on the same identity record, so a check, the decision it led to and the evidence behind it stay together. Pick one, or let the tour run.

See the nine checks

Design the flow. Publish it. Change it any time.

Checks, conditions and outcomes on one canvas, with the cost of a verification shown before you publish.

  • Nine checks, in any order
  • Conditions on any earlier result
  • Manual review, notifications, reminders and webhooks as steps
  • Versions frozen when published
Illustration: the workflow builder with Standard KYC. Email, ID Verification, Liveness and Face Match run in order; if the face match similarity is at least 95%, AML Screening runs and the rules decide; otherwise the session goes to manual review and reviewers are notified. The inspector shows the condition, the cost per verification ($1.30) and the versions.

Your team decides what the rules can’t.

Sessions your rules can’t settle arrive with the evidence attached. Reviewers release single checks, and every release carries a reason.

  • Routed by your rules, never by a model
  • Notifications and reminders
  • The form and the document side by side
  • Every action written to the audit log
Illustration: the review queue with three open sessions. Layla Haddad was sent to review by rule 4 because her address differs between the form and the document. The reviewer records a reason and approves.

Every verification makes the next one safer.

Search one face against everyone you have verified, and block known documents and faces so future matches are flagged automatically.

  • Face Search 1:N at $0.10 per search
  • Duplicate identities and multi-accounting
  • Block documents or faces, by value or by image
  • Blocklist included on every plan
Illustration: a 1:N face search for Sam Keller. The closest match, identity 7F2A at 97%, is on the blocklist, so the session is flagged automatically. The blocklist lists a face blocked by image and documents blocked by value and by image.

Ask your records. Check the answer.

Sara answers questions about your verification activity in plain English, shows which records it read, and turns an investigation into a report you can share.

  • Answers backed by your own records
  • Works within each person’s permissions
  • Every lookup is logged
  • Reports you can share
Illustration: Sara is asked what changed this week. It reads three sets of records, then answers: verifications rose 18% to 1,240, the approval rate held at 91%, manual reviews doubled and four sessions matched blocklisted faces. A shareable report is ready.

Your brand, from the first screen to the last email.

Applicants see your name, your logo, your colours and your words. Never ours.

  • Logo, colours, fonts and theme
  • Welcome, success and failure messages
  • Branded applicant emails
  • Included on every plan
Illustration: white label settings for Meridian Bank, with its logo, colours, font, theme, messages and branded emails, beside a live preview of the hosted flow in the bank’s brand.

Ready for any auditor.

Video evidence, an audit log of every action and a complete history for every identity, with files shared through links that expire.

  • Who did it, and when
  • Video recorded with notice
  • Per-check evidence on the record
  • Export and erasure from the console
Illustration: the audit log with attributed actions, including an approval with a reason by A. Rahman, a rule sending a session to review, a recorded video, a published workflow and a new scoped API key; beside it, the session’s video evidence and its files.

Hosted flow

What your applicants see. Your brand, on their phone.

The hosted flow runs your workflow’s steps under your brand, in English or Spanish. Capture is camera-only and liveness can’t be skipped.

  1. 01Link

    Opens in your brand

    The applicant opens your link. On a computer, a QR code moves them to their phone.

  2. 02Capture

    Camera only

    The camera captures the document. Uploaded and edited files are refused at the door.

  3. 03Liveness

    A real person

    Liveness confirms someone is in front of the camera, then Face Match compares them with the document.

  4. 04Done

    Back to you

    Your rules decide. The applicant returns to your app, and your systems hear about it by webhook.

Integration & control

Fits your systems. Answers to your controls.

A few API calls in, a signed webhook out. Access scoped to the job, and a record of who did what.

Integration

Illustration of one integration: your server creates an identity and a verification (201 Created), sends the applicant to the hosted link, receives a signed verifications.approved webhook, verifies its signature within 300 seconds, and reads the verification (200 OK).
  • Scoped API keysEach key has its own scopes and an optional expiry.
  • A hosted linkOne per verification, and back to your app when done.
  • 35 signed eventsHMAC-SHA256, retried for about a day.
  • Idempotent createsRetries are safe; responses replay for 24 hours.

Control

Illustration of a custom role called Integration developer. Verifications, webhooks and read-only workflows are switched on; applicant data has no access. Saving the role asks for a two-factor code, and the change appears at the top of the audit log.
  • Roles and permissionsFour built-in roles, plus your own.
  • Two-factor sign-inAsked again for sensitive actions.
  • Audit logsWho did it, and when.
  • Privacy controlsExport and erasure from the console.

Workspace

Run it in-house. Nine areas, one workspace.

Everything a regulated team needs to run identity verification as part of its own operation.

  • White label

    Deliver the verification experience under your own brand.

  • Webhooks

    Push verification events to your systems as they happen.

  • API keys

    Create and manage credentials for server-side integration.

  • Team

    Invite and manage the members of your organisation.

  • Roles

    Control what each member can see and do.

  • Billing

    Track usage and the cost of every check that ran.

  • Audit logs

    Keep a traceable record of actions in your workspace.

  • Privacy

    Manage privacy and data-handling preferences.

  • Settings

    General configuration of your workspace.

Pay only for the checks that run. No monthly minimum on pay as you go. White label and the blocklist are included.

In production with government, immigration and trading institutions

One platform for six regulated sectors: the same checks, the same rules engine and the same evidence trail.

Questions

The platform, answered plainly.

Anything else, ask us at hello@identiko.io

  • What is Identiko?

    An identity verification platform. You build a verification flow from document, biometric, compliance and risk checks, send people through it under your own brand, review anything your rules can’t settle, and keep a complete, auditable record of everyone you verify.

  • How does it connect to our systems?

    Your server creates an identity and a verification through the API, using a scoped API key, and sends the applicant to the hosted flow. Signed webhooks tell your systems about every outcome. The developer guide covers identities, verifications, workflows, webhooks and API keys.

  • Does a model ever approve or reject someone?

    No. Models read documents and assess risk. Every outcome follows rules your team configured, and anything your rules can’t settle goes to your review queue with the evidence attached.

  • Can we re-verify an existing customer?

    Yes. Identities and verifications are kept apart, so the same person can be re-verified, stepped up or re-screened on one identity record, without creating a duplicate.

  • How do we catch people who verify twice?

    Every successful verification adds a facial vector to your private collection. Face Search 1:N compares a face with everyone you have verified, and the blocklist flags any future match with a blocked document or face automatically.

  • Can the flow carry our brand?

    Yes. Your logo, colours, fonts, theme, messages and applicant emails, on every plan at no extra cost. Desktop users continue on their phone with a QR code.

  • Which languages does Identiko support?

    English and Spanish.

  • How is access controlled?

    Four built-in roles plus your own custom roles, two-factor sign-in with a second confirmation for sensitive actions, API keys scoped to what an integration needs, and an audit log of every action. More on the security page.

  • How is Identiko priced?

    Per check that runs, from $0.05. There is no monthly minimum on pay as you go, and a full KYC and AML flow costs $1.30 at list price. White label and the blocklist are included. See pricing.

Get started

Run your first verification today.

Start free with credit on us and every check included, or book a demo for your institution.

Book a demo

Or write to hello@identiko.io

30 min

Verifications a month

We use these details only to reply to your request. See our Privacy policy.

Rather explore on your own? Start free