What problem does it solve? Verifying ISO/IEC 18013-5 mdoc/mDL credentials in the browser on iPhone and iPad requires handling iOS-specific constraints: the Digital Credentials API runs only over ISO 18013-7 Annex C, requests must always be signed with expectedOrigins, and the verifier backend must coordinate presentation definitions, wallet invocation, and trust-list checks. ## Core Features & Use Cases - iOS DC API verification flow: Builds a presentation definition for ISO 18013-7 Annex C with ISO/IEC 18013-5 mdoc/mDL, creates a v3 verification request with requestByReference, and invokes the wallet from Safari. - Signed request handling: Enforces expectedOrigins for replay protection and shapes the wallet response as a JWE payload posted back through a backend proxy with SSE result delivery. - Trust-list verification: Reads verification history to check verified status, isVerifiedWithTrustList, and trustServiceProvider, with guidance for WRPAC registration. - Use Case: A relying party adds age verification to its web app: iOS users present an mdoc from their EUDI Wallet via the DC API, Android users are routed to the OpenID4VP variant, and a QR flow serves as the universal fallback. ## Quick Start Ask your agent to add iOS Digital Credentials API verification of an mdoc credential to your web app using the iGrant.io verifier backend with a QR fallback.