A protocol-neutral verification layer accepts credential presentations through different delivery protocols while preserving the claims’ meaning for authorization. Users may present employment, certification, or clinical credentials through DID-based flows, OpenID4VC, QR codes, browser redirects, or wallets supporting both; only the experience and transport change. section 16.7
The layer separates protocol handling from business authorization by:
- Receiving presentations and validating their signatures. section 16.7
- Verifying issuer trust and checking revocation status through integrated trust-store and issuer-governance information. section 16.7
- Returning consistent, normalized attributes to the policy decision point, so new credential protocols do not require policy or application rewrites. section 16.7
Clinical access across ecosystems
Clinicians access health systems using mobile wallets with DID-based or OpenID4VC credentials and respond through QR codes or browser redirects. The same authorization policies evaluate the resulting trusted attributes. section 16.7
