Eligibility

Prove a requirement, keep the rest.

The intended workflow for selective eligibility proofs. Every step that would contact a provider is disabled until a reviewed provider is configured; no checkbox, wallet or local flag can produce a verified result.

1. Requirement

Not configured

Verification provider not configured. ELIGIBILITY_PROVIDER is not set.

Choose the requirement to proveNon-U.S. person status example templateThe holder is not a U.S. person as defined in Regulation S.Qualified or professional investor status example templateThe holder meets the issuer's qualified-investor definition for the relevant jurisdiction.Sanctions screening passed example templateThe holder passed a sanctions screening within the freshness window.

2. What would be disclosed

Disclosed to the verifier

✓ requirement satisfied: yes/no
✓ credential issuer
✓ expiry

Stays with you

– name
– date of birth
– address
– document numbers
– country beyond the predicate

Trusted issuers for this requirement: A credential issuer the operator has reviewed and listed.

3. Request the proof

A proof request binds a random challenge to this application, this session and the chosen requirement, so a proof cannot be replayed elsewhere.

Verification provider not configured. Identity documents are never uploaded to this application.

Workflow

1Identify the requirement
2Review disclosed fields
3Request the minimum proof
4Check freshness, expiry, replay and revocation
5Result

Result

Unavailable — no provider

Possible results once a provider exists: verified, expired, rejected, unavailable. Each is derived from a provider record that passes the binding and freshness checks, never from a local setting.