igrantio-dcapi-ios

Implements same-device and cross-device mdoc credential verification on iOS via the Digital Credentials API.

1|Updated Jul 14, 2026
One-click install
npx skills add https://github.com/L3-iGrant/skills --skill igrantio-dcapi-ios-l3-igrant
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: igrantio-dcapi-ios
Source: https://github.com/L3-iGrant/skills/tree/main/workflows/igrantio-dcapi-ios
Command: npx skills add https://github.com/L3-iGrant/skills --skill igrantio-dcapi-ios-l3-igrant

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about igrantio-dcapi-ios

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify mdoc credentials in the browser on iOS?▼

On iOS, verify mdoc credentials through the Digital Credentials API over ISO 18013-7 Annex C. Create a presentation definition for ISO/IEC 18013-5 mdoc, issue a v3 verification request with requestByReference, invoke the wallet from Safari, and post the JWE response back through your backend.

What is the difference between DC API verification on iOS and Android?▼

On iOS the Digital Credentials API runs only over ISO 18013-7 Annex C with ISO/IEC 18013-5 mdoc credentials, and the request is always signed with mandatory expectedOrigins. Android uses OpenID4VP with plain or signed requests, so deployments should detect the platform and route each to the matching flow.

Why is expectedOrigins required for iOS Digital Credentials API requests?▼

iOS DC API requests are always signed, and expectedOrigins provides replay protection by binding the request to your page origin. You must list every origin serving the page, since www and bare domains count as different origins.

Does the iOS DC API flow work without a trust-list registration?▼

The flow works, but the wallet shows an unverified warning until your Wallet-Relying Party Access Certificate is registered in the trust list. Register the WRPAC through iGrant.io support before going live so the wallet displays your organisation as verified.

What happens when the Digital Credentials API is unavailable in the browser?▼

The recommended fallback is a QR-based cross-device flow, which requires Bluetooth on both devices. Detect DC API support in the browser and route unsupported clients to the QR flow as the universal fallback.