DEVELOPER GUIDE
Ask for details
when they matter.
Names are optional at signup. When your service needs more information, let the person complete their Hybrid ID profile and decide what to share.
One clear request, approved by the user
- Configure: select first name, last name or both in your app settings and explain why they are needed.
- Request: obtain profile:request consent and create a request from your backend.
- Review: the person sees your app, purpose and fields in Hybrid ID Access requests. They add missing information and approve or decline.
- Continue: your backend reads the approved snapshot before allowing the feature that needs it.
Identity remains in Hybrid ID
Your application never handles the user's Hybrid ID password. The user can decline or withdraw sharing. An approval for one app does not release the requested fields to another.
Existing permissions to read a display name remain separate. Saving names updates the central profile; the review screen explains this before saving.
Profile details are not KYC
Entered names are self-declared. Verified legal identity, documents and liveness belong to the separate verification workflow. Basic signup does not grant access to restricted services.