Trust that scales.
Liability that doesn't.
Verify customers, reach them privately, and keep none of their personal data. Every check is a proof you can audit — and nothing you can leak.
What this actually solves
Three concrete reasons a scoped, provable check beats collecting the document yourself.
Hold less, risk less
Ask for the answer, not the file. You never become the custodian of an ID, a birthdate, or a document you don't otherwise need.
Reach holders where they are
Official accounts and miniapps put your service inside the same app holders already use for identity, checks, and messaging.
Ship checks, not backends
The Attestation Type Studio adds a new predicate to the shared catalog once, so every verifier can request it — not just yours.
What a check looks like from your side
No document ever transits your servers — only the answer to the question you asked.
You ask a predicate
“Is this holder age-eligible?” — scoped to exactly the check your flow needs.
The holder approves privately
Approval happens on their device. You never see the document, the biometric, or the private key.
You get a verified yes
A signed, checkout-bound proof — reviewable, revocable, and scoped to this one relationship.
The review path
Official account and attestation-type access is reviewed, not self-service.
Submit account details
Company, origin, manifest, support, and policy information, plus any miniapp or service proposal.
Review origins and permissions
U-net checks legal fields, requested scopes, and notification behavior before anything goes live.
Receive scoped credentials
Approved accounts get provider credentials scoped to the reviewed relationship, not a blanket identity.
Keep changes accountable
Safe profile edits can ship quickly; trust-sensitive changes stay under review.
Want the technical shape first?
See the SDK your team would integrate, or what changes for the person approving the check.