Configure an EUDI wallet issuer backend following the ARF and implementing PID credential issuance
domain: github.com/eu-digital-identity-wallet · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Review the current ARF version (v1.6, March 2025) for PID (Person Identification Data) attribute requirements; the ARF specifies mandatory attributes including family_name, given_name, birth_date, age_over_18, and the issuing_country
Choose the supported credential formats per ARF: at minimum, SD-JWT VC and ISO 18013-5 mdoc formats must be supported for PID issuance
Implement OID4VCI as the issuance protocol; the EUDI ARF mandates authorization code flow with PAR and PKCE for PID issuance to wallets
Configure your issuer to present a valid trust anchor: your issuer certificate must chain to a trusted root within the EUDI Trust Framework (LOTL - List of Trusted Lists)
Implement the batch credential endpoint if your use case requires issuing multiple credentials in one round trip; batch issuance reduces latency for composite PID+mDL bundles
Test against the EUDI Reference Implementation wallets available at github.com/eu-digital-identity-wallet and run through the interoperability test scenarios published for each ARF iteration
Known gotchas
The ARF is iterative and actively revised in 2026; implementing requirements spec against a specific ARF version and tracking changes between iterations is critical — reopened discussion topics in Iteration 1 (Feb–Apr 2026) may change requirements
EUDI requires wallet attestation (WIA — Wallet Instance Attestation) to be presented alongside credential requests; your issuer must validate the WIA before issuing PID
sd-jwt-vc draft version alignment matters: the ARF cites specific draft versions of sd-jwt-vc and OID4VCI; implementing against a newer or older draft than the ARF references will cause interop failures
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?