Skip to content
← All use cases

KYC onboarding with evidence

Verify customers with a flow you can explain and evidence you can delete.

Versioned verification flows with consent captured before any check, explainable risk with a second reviewer, payloads kept in the customer’s region, and deletion that leaves proof behind.

For Compliance, Risk, Operations

Download the brief(PDF)

Start freeTalk to us
Admin console
Verification attempts in the admin console: two approved, one waiting for consent, and one in review with the first reviewer’s reasoned decision recorded.Verification attempts in the admin console: two approved, one waiting for consent, and one in review with the first reviewer’s reasoned decision recorded.
Each attempt with its checks, consent, review and whether it was billed. Shown with demo data.

The situation

Onboarding checks run through a vendor portal. The rules change without a version, a borderline case is decided by whoever is on shift, and nobody can prove when a customer’s documents were deleted.

How it works

Step by step, and the product each step happens in.

  1. 01

    Publish the flow

    Define the steps a person or a business goes through as a versioned flow, so every attempt records the version it ran.

    In Verify
    Admin console
    Verify applicants listed by opaque identifier, region and retention, above three versioned flows and their ordered checks.Verify applicants listed by opaque identifier, region and retention, above three versioned flows and their ordered checks.
    Applicants hold references, not documents; flows are versioned. Shown with demo data.

  2. 02

    Capture consent in region

    Consent is recorded before any check, and the applicant’s payload stays within its region.

    In Verify

  3. 03

    Run the checks and decide

    Provider checks produce an explainable risk score; a borderline case goes to review with dual control.

    In Verify
    Admin console
    Verification attempts in the admin console: two approved, one waiting for consent, and one in review with the first reviewer’s reasoned decision recorded.Verification attempts in the admin console: two approved, one waiting for consent, and one in review with the first reviewer’s reasoned decision recorded.
    Each attempt with its checks, consent, review and whether it was billed. Shown with demo data.

  4. 04

    Delete on schedule, with proof

    Retention deletes the payload when its time is up and leaves deletion evidence behind.

    In Verify

What you get

  • Decisions you can explain

    Each attempt carries its flow version, its checks and the reasons behind its risk score.

  • Businesses as well as people

    KYB, reusable identity and bank verification run in the same product.

  • Ongoing, not one-off

    Fraud signals, ongoing AML and transaction monitoring continue after onboarding.

The products involved

Questions, answered

How is it billed?

Per completed attempt, at the published Verify rates in Platform Credits, on the same invoice as the rest of the platform.

Can we prove a customer’s data was deleted?

Yes. When retention deletes an applicant’s data it leaves deletion evidence behind.

Related use cases

KYC onboarding with evidence · ProjectX