identity.org.au

Pilot proposal · for discussion

A useful fact. Fewer repeated checks.

Help shape a reusable verification experience for an existing service, with an agreed issuer and a narrowly defined eligibility check.

What is available now

The interactive demonstration uses fictional credentials. The production wallet and verifier service are not available. This proposal seeks discussion; no pilot participants, delivery dates or institutional partnerships are confirmed.

The first workflow

An organisation issues an active-membership credential after its existing checks. A person uses it to request a member desk booking at one service and a member workshop at another. Each service agrees to trust the issuer and asks only whether the membership is active. Each presentation needs fresh consent.

This is a proposed scenario. It does not establish government identity, legal age, financial KYC or a universal right to access services.

What each participant brings

  • Issuer: an accountable organisation, a documented evidence process, and a way to correct, expire and revoke credentials.
  • Two services: a real eligibility decision, an existing baseline process and an alternative route for people who cannot use the wallet.
  • Foundation and delivery team: reference software, proposed integration and consent design; production responsibilities must be agreed before enrolment.
  • Participants: voluntary involvement, accessible information and the ability to stop future sharing.

What the pilot should measure

Compare against the same service's current eligibility process using the same requirement. Record completion and abandonment, time to first useful result, repeat-use completion, fields retained, support effort, integration effort and cost per completed check. Report sample size and failed attempts as well as successes.

A small usability pilot cannot establish rare-fraud resistance. Security and identity-assurance evidence need their own assessment.

The path to a real pilot

  1. Agree the workflow, issuer, participants, lawful processing basis, budget and responsible contacts.
  2. Finish required production adapters, authentication, credential checks and recovery. Demonstrate them on supported devices.
  3. Review privacy, security, accessibility and fraud controls; agree retention and incident handling.
  4. Run a synthetic-data rehearsal and independent integration checks. Real data is admitted only after the readiness gate is approved.
  5. Run a bounded, voluntary pilot; review measured results before deciding on expansion.

Policy creates an opportunity, not automatic approval

Australia's announced private-sector opening is an opportunity to evaluate services. It does not mandate adoption of VEID. Accreditation and approval to join AGDIS are separate processes. EU wallet acceptance does not confer recognition on this project.

Australian private-sector announcement · Current regulator forms · EU digital identity regulation

A sustainable service

Service-funded integration, supported verification or enterprise support are possible models to evaluate with pilot participants. No prices are offered here. The proposal does not rely on selling personal information or requiring a new payment system.

Start the discussion

Tell us the workflow you want to improve, what you collect today and who could issue the credential. Please do not send identity documents or participant records. The email link opens your email application; it sends nothing automatically.