Legal entity existsProduction prerequisite
The relying party can be identified and entered into the applicable production trust or registration process.
Turn the fuzzy pre-registration phase into seven concrete decisions. The check runs locally in your browser and never represents provider approval.
The relying party can be identified and entered into the applicable production trust or registration process.
You can explain the exact user journey, requested attributes, and why each attribute is necessary.
Your organization controls an HTTPS domain that can host policy, metadata, and wallet return paths.
The notice names the data processed, purpose, retention, recipients, and user rights for this flow.
The flow asks for the smallest useful claim set—for example an age result instead of a date of birth.
Your business has a documented policy for results, evidence, source files, and user access periods.
Users who lack an eligible wallet or credential have a deliberate alternative and support route.
The checker measures whether your inputs are ready to enter Alentra’s onboarding process. It cannot predict whether a provider, trust authority, or Member State will accept a production relying party.
Use synthetic credentials to validate the user journey and requested outcomes before registration.
Prepare the entity, domain, purpose, policies, claims, and operational decisions Alentra needs.
Alentra completes the applicable conformance, trust, and country rollout work before a route is marked live.
Questions this checker answers
No. It means your relying-party input packet is prepared. Provider registration, conformance, trust enrollment, and country rollout remain external production gates.
Government-wallet proof, ready to repeat.
Start with Alentra