Make identity verification work for everyone, with privacy at its heart.
Verify once. Share only the proof a service needs. See who asks, what they will receive and where your identity goes.
§01
What we do
One verified identity. Three ways to use it.
A request should explain its purpose, what Passtru processes and what the recipient gets. Account access, identity verification and approval of an action are distinct decisions.
Illustrative authorization record. Recipient, scope, expiry and revocation describe an approval; they do not establish that a purchase occurred.
Verified
Authorization receipt
§03
Reuse model
Verify once. Reuse with control.
01
Verify your identity
Passtru checks the document and face capture needed for your request. Some requests need fresh evidence.
§04
Different by design
What makes Passtru different
01
User-held, not service-trapped
Most verification dies inside the one service that paid for it. With Passtru, the person holds their verified evidence and reuses it across services.
§05
Trust and compliance
Built for high-trust services
A request must explain processing, recipient results, consent and recovery. An illustrative record is not a certification.
§06
Team
Who's building Passtru
We are building Passtru to make identity verification useful to people and the services they choose.
Build on verified identity.
Whether you're onboarding users, checking a single attribute, or authorizing an agent's action, let's talk about what Passtru can do for your product.
Login with Passtru
Sign in to a connected service. Account access and sharing verified identity are distinct decisions.
Share the proof needed
Passtru checks the evidence. The service receives the age result.
An approval record describes a bounded authorization. External execution needs its own confirmation.
Passtru user · checks current
Service provider API
Real-time status endpoint
Held in vault; released only where contract and law require
02
Choose what to share
Passtru checks the evidence. The service receives the age result. In an age-only request, the service receives the age result without your name, date of birth or document.
03
Use it again
Keep your records and requests together. Your history shows who received what and when.
02
Real verification behind every proof
Document, liveness, screening, and decisioning sit behind each claim, not a lightweight checkbox or a self-asserted toggle.
03
Honest about regulation
Share a private attribute where the law allows it. Produce the underlying evidence where regulation requires it. We don't pretend a proof is a document, or a document is a proof.
04
No special hardware
A smartphone and a document. No dedicated device, no dongle, no closed wallet.
Building reusable, consent-first identity infrastructure for people and the services they trust.
