OriginOath

KYC and KYB for money products.

KYC, KYB, consent-based reuse, and share tokens — built for money products.

Collect once

Person and business verification with geo-aware fields and documents.

Reuse with proof

Email ownership before an active identity is shared across destinations.

Rely with control

Share tokens and reliance packets stay inside the scopes you grant.

Ship in your UI

Hosted collect stays embedded, or drive every step through the API.

Flow

From create to decision

One verification record. Email and type up front. Collect when needed, reuse when earned.

  1. Create

    Open a verification with kind (KYC or KYB) and the customer’s email. The response says whether to collect or verify email next.

  2. Collect or prove email

    Embed the hosted frame, or drive the REST API. Returning customers confirm email ownership before reuse.

  3. Decide

    Status lands on your webhook. Approved subjects can be shared or relied on by authorized destinations.

Product

Features

Collection, consent-based reuse, and compliance controls shaped for payment and money products.

Collect

Verify people and businesses in one product surface

KYC and KYB share the same verification record, geo packs, and decision lifecycle—so your money product does not juggle separate onboarding stacks.

KYC

Name, date of birth, address, and country-specific documents through to a clear decision.

KYB

Legal entity details, registered address, and beneficial owners with the same geo packs.

Hosted collect

Embed country, identity, documents, and terms without leaving checkout or dashboard.

Reuse

Skip a full recollect when an active identity already exists for the email.

Consent

Email codes prove ownership before reuse or cross-merchant sharing.

Reliance

Enrolled partners can rely on a subject you already verified, inside your scopes.

Share tokens

One-time tokens let another destination attach the same approved subject.

Reuse & trust

Prove email, then reuse what you already earned

Returning customers should not re-upload the same documents. OriginOath gates reuse with email proof, then share tokens and reliance for authorized destinations.

Trust

Built around privacy

Verification should not mean losing control of identity data. Collection, retention, and reuse stay explicit.

  • Privacy by law Country packs decide which fields and documents are required before submit.
  • PII handling Private vault storage for identity fields and document bytes, with access controls.
  • Consent before reuse Email proof and destination grants gate share tokens and reliance.