Relying-party pilot

Verify once. Ask narrow policy questions.

End-to-end age 21+ Hosted Partner Flow demo using the age_21_retail policy pack. No wallet, zkLogin, stablecoin, or payment required.

Relying-party pilot · age 21+ eligibility

Pilot demonstration of Hosted Partner Flow with age_21_retail. Configure sandbox partners via Integration Studio or environment variables. Callback query parameters are never authorization.

Demo progress

  1. 1
    Request
    Relying partner initiates an age_21_retail verification request.
  2. 2
    Holder authorization
    Holder reviews who is asking, why, and what will be shared.
  3. 3
    Abraxas verification
    Holder satisfies the policy or reuses current Abraxas evidence.
  4. 4
    Policy evaluation
    Abraxas evaluates the pinned policy against holder evidence.
  5. 5
    Signed receipt
    Abraxas issues a partner-bound signed decision receipt.
  6. 6
    Partner verification
    Partner server re-fetches and verifies the public receipt.
  7. 7
    Access decision
    Partner grants or denies access from verified receipt state only.

Start verification

Loading pilot configuration…

Privacy minimization

Traditional repeated verification

Application receives identity data / documents:

  • Government ID images or scans
  • Date of birth
  • Legal name and address
  • Repeated document upload per application

Abraxas

Application receives:

  • age_eligible_21 (boolean-equivalent policy result)
  • Signed receipt bound to this partner and policy
  • Expiry and current-validity metadata
{
  "age_eligible_21": true
}

Optional: partner activity signal (not required for 21+ access)

After receipt verification, a partner may optionally bind a consented activity category from its own records. This does not replace Abraxas verification.