authsi

A platform in development

Carry less.
Prove what matters.

We’re building tools to help businesses accept digital credentials online and in person. A person should be able to prove what a service needs without handing over everything in their wallet.

Proposed service, not a live verification flow. Authsi currently offers a waitlist and contact form. Wallet access depends on provider approval, supported credentials and devices, and validation of the specific business use case.

One platform. Specific reasons to verify.

Our direction is an SDK and hosted service for businesses that need age or identity checks. Each integration needs a defined purpose, suitable verification method and clear explanation of the information requested.

Age checks

Web implementation in development

Request whether someone meets an 18+ or 21+ threshold, without requesting their name, birthdate or portrait. The web implementation includes credential-verification code; production deployment and live Wallet testing remain outstanding.

Account identity

Planned

Help a business associate a verified identity with an account or sensitive action. Real account-to-identity matching is not yet implemented. A matching name alone does not establish account ownership.

Interview identity

Exploring

Help a business check that an interview participant is the applicant it expects. Session binding and any portrait-comparison process still need to be developed and evaluated. This is not an employment-eligibility or immigration-status check.

DoorID in person

Separate native development

Explore staff-assisted digital ID checks through a native reader. This is separate from the proposed web flow and does not establish approval for online verification.

How a proposed web age check works

This is a description of the intended pilot, not a transaction you can complete on this website.

  1. A business requests a specific proof.

    The business identifies a transaction and an applicable age threshold. The user sees who is requesting the check and why.

  2. The person reviews the request.

    A short-lived link opens the verification experience. Before sharing, the person sees the requested field and the processing and retention explanation, then chooses whether to continue with a supported Wallet credential.

  3. The service checks the presentation.

    The planned service validates the credential presentation and checks that it belongs to the verification session. The age request asks for the threshold flag only.

  4. The business receives a scoped result.

    The result relates to that transaction and threshold. It is not a general guarantee of identity, account ownership, unique personhood or future human activity. If verification cannot complete, the business needs an alternative process.

What remains before a pilot

We need to establish the provider-approved scope for Authsi and participating businesses, complete domain and certificate setup, deploy the verification backend, validate supported credentials on real devices, and finalize verification-data handling and retention. Android Wallet integration is planned, not currently implemented.

We will explain the relevant data practices before a verification flow becomes available. Today’s website practices are in our privacy policy.

Bring us your use case.

Tell us what your customers need to prove, where the check fits in your service, and how you handle it today. We’re looking for businesses to help shape a useful, proportionate verification experience.

Discuss an integration