Collect once
Person and business verification with geo-aware fields and documents.
OriginOath
KYC, KYB, consent-based reuse, and share tokens — built for money products.
Person and business verification with geo-aware fields and documents.
Email ownership before an active identity is shared across destinations.
Share tokens and reliance packets stay inside the scopes you grant.
Hosted collect stays embedded, or drive every step through the API.
Flow
One verification record. Email and type up front. Collect when needed, reuse when earned.
Open a verification with kind (KYC or KYB) and the customer’s email. The response says whether to collect or verify email next.
Embed the hosted frame, or drive the REST API. Returning customers confirm email ownership before reuse.
Status lands on your webhook. Approved subjects can be shared or relied on by authorized destinations.
Product
Collection, consent-based reuse, and compliance controls shaped for payment and money products.
Collect
KYC and KYB share the same verification record, geo packs, and decision lifecycle—so your money product does not juggle separate onboarding stacks.
Name, date of birth, address, and country-specific documents through to a clear decision.
Legal entity details, registered address, and beneficial owners with the same geo packs.
Embed country, identity, documents, and terms without leaving checkout or dashboard.
Skip a full recollect when an active identity already exists for the email.
Email codes prove ownership before reuse or cross-merchant sharing.
Enrolled partners can rely on a subject you already verified, inside your scopes.
One-time tokens let another destination attach the same approved subject.
Reuse & trust
Returning customers should not re-upload the same documents. OriginOath gates reuse with email proof, then share tokens and reliance for authorized destinations.
Geo-aware field and document packs resolve from the selected country—without a separate build per region.
Identity fields and document bytes stay in a private vault with retention and access controls—never on a public CDN.
Create verifications, upsert subjects, upload documents, attest terms, submit, and poll status. Browse the interactive reference in API docs.
Trust
Verification should not mean losing control of identity data. Collection, retention, and reuse stay explicit.
Leave your work email. We will follow up when access opens.