identity.org.au · specimen
Example · Membership
- Claim
- Active membership
- Result
- Yes
- Record
- IDAU-0001
- Documents
- Not shared
IDAUASPECIMEN<<PROOFCLAIM<ACTIVEMEMBERSHIP
IDAU0001<AUSRESULT<YES<<DOCS<NONE
Reference implementation
The Identity Wallet · in development
Prove what a service needs. Share less of your identity.
An open-source wallet powered by VEID for reusable, consent-based verification. Explore the experience and help test it through a service pilot.
Production wallet not available. The demo uses fictional credentials. Operated by a not-for-profit foundation, independent of the Australian Government; no accreditation is claimed.
Fictional membership specimen. Explore the consent flow in the demo.
The service
One credential, more than one useful moment
The proposed experience lets people reuse trusted evidence across services that accept its issuer. Each service asks for a specific fact, and each request needs your decision.
Capture + wallet Mobile wallet Guided local document capture and OCR. Original scans stay on your phone; only separately approved derived data may be encrypted for submission. Manage + present Web wallet — my.identity.org.au Explore the proposed browser experience for presentation, consent and sessions. The production portal is not available. Overview The Identity Wallet service What the service is, how the surfaces fit together, and how verification works on the network.
Everyday uses
What the reference design explores
- 01 Verify your identity once Complete a guided verification on your phone, then reuse it everywhere the wallet is accepted.
- 02 Prove your age without your documents Answer whether you are over 18 with a cryptographic yes. Your birth date and documents stay private.
- 03 Share with services on your terms See exactly what a service is asking for, approve or decline, and set consent to expire.
- 04 Change your mind, any time Every consent you grant can be revoked. Every use of your data is recorded where you can see it.
- 05 Build a stronger verification level Four levels, from Basic to Trusted, unlock more as your identity evidence gets stronger.
- 06 Understand deletion and retention Review what can be deleted, what a service may retain, and the limits of immutable records.
In everyday use
Prove the thing. Keep the document.
The reference capture flow explores liveness checks as one part of verification. Production adapters and independent testing are still required; a selfie alone is not proof of identity.
A live check in ordinary light: what the wallet needs is a moment of presence, not your archive.
Reference journey
Explore the proposed capture journey
Read the capture design, then try a fictional membership presentation. Setup duration and real-device performance have not been established for production.
-
Step 1 of 3: Scan your identity document
Front and back, guided by the camera. The app reads the details and you check them before anything is submitted.
-
Step 2 of 3: Take a selfie with liveness checks
Blink, turn your head, smile — short challenges that prove a live person is present, not a photo.
-
Step 3 of 3: Review and submit — encrypted
The reference design packages approved data for verification. Production encryption and device integrations must be completed and tested before real use.
Verification levels
Four levels. Services ask for what they need — no more.
| Level | In plain terms | Typical use |
|---|---|---|
| Unverified | You have a wallet, but no identity checks have been completed yet. | Browsing services that accept the wallet |
| Basic | Early checks have passed. This level can support a limited claim when a specific service asks for it and you choose to present it. | A specific offer's disclosed proof request, when the current service supports it |
| Standard | A verification scope has been completed. Original identity document images and full OCR output stay on your device; only separately approved derived data may be submitted. | Age and attribute proofs (for example, proving you are over 18) |
| Trusted | The strongest level: everything in Standard, plus hardware-backed biometric checks, device integrity attestation, and a sustained verification history. | Protocol roles or services with separately disclosed, supported proof requirements |
Your data, in plain terms
Collect less. Make the data boundaries clear.
The design keeps source document images local and limits submitted data. A real pilot must demonstrate the complete data flow, encryption, processing access and retention before admitting participants.
- Stage 1 Captured On your phone: document scan, selfie, liveness.
- Stage 2 Original stays local The document image never leaves your device. OCR and checks run locally.
- Stage 3 Derived data, if approved Only minimum user-approved fields may leave, encrypted for VEID processing.
- Stage 4 Transient data cleared Temporary processing data is cleared under the scope lifecycle; source images remain local.
- Stage 5 Selective result The network records the verification result and required encrypted references, never source images.
| Your data | Where it lives | Who can read it |
|---|---|---|
| Document scans and photos | Original images stay on your device; only approved derived data may be submitted encrypted | You control the image. The network receives no document scan. |
| Biometric templates | Production encryption and processing depend on completed, tested adapters | Never shared with services. Never sold — prohibited regardless of consent. |
| Verification results | On the network — your level and pass/fail outcomes | Services you explicitly consent to, per request. |
| Consent records | Auditable history — every grant, every revocation, timestamped | You, in full. Services see only their own grants. |
Insights
Analysis on digital identity
Evergreen explainers on fraud, architecture, cryptography, consent and rights.
All insights Guides Definitions Synthetic media Identity in the synthetic era Generative tools can now produce convincing faces, voices and documents. What breaks when seeing is no longer believing — and what verification has to become instead. Fraud AI-generated fraud and fake IDs Generated document images and synthetic faces have industrialised identity fraud. How modern verification systems — liveness, hardware attestation, cryptographic results — are designed to answer it. Architecture Why centralised identity databases fail Every central store of identity documents is a honeypot: maximum value to attackers, catastrophic and irreversible when breached. The structural argument for never building the archive at all.
Trust
Why you can check our claims
Open source
The reference software is public for inspection. Open source supports scrutiny; independent assurance and production testing remain separate requirements. About the code
Not-for-profit foundation
Operated by DETIO FOUNDATION LTD (ACN 699 651 771), with a constitution that directs assets and income toward its public-benefit purposes. Who runs it
Patented method, public interest
The verification method is Australian patent AU2024203136B2, held inside the public-benefit structure. The patent in plain terms
Honesty first
This wallet is open-source reference software. Some production adapters remain extension points. The interactive demo models consent using fictional credentials; it performs no cryptographic verification. No app-store availability or government accreditation is claimed.
Support
Popular help topics
Build with us
Make verification useful. Keep collection proportionate.
Explore the demonstration, review the pilot proposal, or follow availability updates. Production release depends on engineering, assurance and operational readiness.