Skip to content

Platform

One platform for digital identity onboarding

Capture identity documents and selfies, run the verification checks each product needs, and give your team a clear decision with a complete record, through a guided mobile journey and a versioned API.

Capabilities

Capture, verify and decide

Combine these building blocks into the journey each product needs. Each one shows its availability: available in the SANDBOX with synthetic data, illustrative, or planned. SANDBOX access opens after acceptance testing.

Purpose-bound requests

Every verification starts with a stated purpose that limits what can be asked for.

Applicant consent

The person sees who is asking and why, and nothing proceeds without their agreement.

Decision management

Configurable rules return verified, referred for review or not verified, each with a plain-language reason your team can act on.

Customer information collection

Guided forms collect only the information your onboarding policy needs, validated as the customer types.

Configurable onboarding workflows

Choose the steps and checks for each product, and how exceptions reach your team.

Guided document capture

Step-by-step capture of identity documents on the applicant's phone, with image-quality feedback.

OCR and MRZ extraction

Reading document fields and machine-readable zones to reduce manual capture.

Guided selfie capture

On-screen prompts help customers take a clear selfie for Yimi's native face matching.

Optional external checks

Government identity records, credit-bureau and other provider-backed checks, added per journey and charged separately.

Native face matching

Yimi Core compares the selfie with the document photo using Yimi's own face-matching engine, included in core onboarding.

Liveness detection

Confirms the customer is physically present. Distinct from face matching; its scope is confirmed in your quote.

Audit record

A time-stamped trail of each request, consent, check and decision.

Retention controls

Lapsed requests expire and personal details are redacted on a schedule.

The customer journey

See the platform onboard a remittance customer

Step 1 of 9

Customer registration

The customer

The customer opens the app to send money abroad and taps Create account. Before anything is captured, they see who is asking for their identity, why, and what will be collected.

What Yimi does

Yimi presents the business's purpose and records the customer's consent before the journey continues.

Illustrative journey with a fictitious business and a synthetic customer. No government database or external data provider is connected in this demonstration.

How the pieces fit

Your channels, one platform, replaceable providers

  1. Layer 1

    Your channels

    Business console · your app via the API

  2. Layer 2

    Yimi platform

    Requests · consent · orchestration · outcomes · audit

  3. Layer 3

    Verification providers

    Optional government, credit-bureau and other external checks

Providers connect behind a single interface, so checks can be added or replaced without changing how your team or your application works with Yimi.

For every team

One platform, three ways in

Your business

A workspace to request checks, follow progress and review outcomes.

Your partners

A partner workspace that keeps each customer's information private.

Your developers

Versioned API contracts and a SANDBOX with deterministic synthetic scenarios.
Request a DemoExplore Solutions