Skip to main content

NL-FS-P: PID Issuance Service Conformance (Issuance Requirements)

NL-FS-P: PID Issuance Service Conformance (Issuance Requirements)

Download PDF (275 kB, 14 pages)Read the full text4 requirements
Cover page of the document, as printed
Document referenceNL-FS-P
VersionRC1.0
StatusRelease Candidate
Date2026-11-06
Document typeFramework document
Parent frameworknone
Scheme OwnerKingdom of the Netherlands Minister of Economic Affairs
Certification targetEuropean Digital Identity Wallets and the electronic identification scheme under which they are provided
Primary audienceSystem/Scheme Owner, CABs, PID providers
Secondary audienceEUDI Wallet ecosystem stakeholders
Assurance levelHigh/High
Subsidiary DocumentsNL Certification System Documents
How to read this page

This page summarises the document. Every statement points to the section and page of the authoritative PDF it comes from: click a reference such as §6.1, p. 10 to open that page. If this summary and the PDF differ, the PDF applies.

What this document is​

NL-FS-P specifies the functional certification scope for a person identification data (PID) issuance service within the common EUDI Wallet Certification System and the corresponding requirements for functional conformance, and provides a corresponding Implementation Conformance Statement (ICS) (§1, p. 5). It identifies the documents forming the legal basis for certification (§1, p. 5). It is one of the two principal scope documents of the functional certification scheme (the other is NL-FS-W) and operates within the framework, methodology and evaluation rules of NL-FS (§1, p. 5).

Scope and object of certification​

  • The object of certification is "a PID issuance service provided by a PID provider" (§5, p. 9).
  • The certification scope comprises: (a) the conformity of the functional behaviour of the service observable at its interface towards the wallet unit, by which person identification data is issued; (b) the conformity of the person identification data issued by the service (§5, p. 9).
  • Legal derivation: Regulation (EU) No 910/2014 as amended by Regulation (EU) 2024/1183, in particular Article 5a and Article 5c(1); under Article 5c(1) the scope comprises the requirements of Article 5a(4), (5) and (8) and, where applicable, the standards and technical specifications referred to in Article 5a(24) (§2, p. 6).

Who it applies to​

  • Conformity assessment bodies: the document is intended for them (§1, p. 5). During certification the certification body shall request the documentation for any Recommended feature that is not implemented (§6.1, p. 10).
  • PID providers preparing a PID issuance service for certification: the document is intended for them (§1, p. 5). PID providers seeking functional certification "shall complete this ICS" (§7.1, p. 12) and shall declare whether the PID issuance service implements each listed feature (Annex A.3, p. 13). For a Recommended feature not implemented, the PID provider shall understand and weigh the implications and document these considerations (§6.1, p. 10). The PID provider shall declare which optional PID attributes and metadata it supports using an ICS that is part of the test case specification for PID contents (Annex A.3 Note, p. 13).

Contents​

  • §1 Scope: what the document specifies and for whom; p.5. Read
  • §2 Legal basis: eIDAS Article 5a and 5c(1) and CIR 2024/2979, 2024/2982, 2024/2977; p.6. Read
  • §3 Normative references: NL-SYS-02, NL-FS, the three CIRs, RFC 2119; p.7. Read
  • §4 Terms and definitions: terms from NL-SYS-02, NL-FS and Article 2 of CIR 2024/2977; p.8. Read
  • §5 Certification scope for a PID issuance service: object of certification and scope; p.9. Read
  • §6 Requirements for functional conformance: overview and conformance levels (6.1), requirements per CIR (6.2 CIR 2024/2979: none; 6.3 CIR 2024/2982; 6.4 CIR 2024/2977); p.10. Read
  • §7 Implementation Conformance Statement (7.1 ICS template): what the ICS is and who completes it; p.12. Read
  • Annex A (normative) PID issuance service ICS template: A.1 identification of the object of certification, A.2 identification of PID provider, A.3 declared implementation choices (A.3.1–A.3.3); p.13. Read

Key points​

  • Chapter 6 lists the requirements regarding features of PID issuance services mandated in the legal instruments; these "enable modularity of the certification" and allow a PID provider to indicate which legally mandated features are implemented (§6.1, p. 10).
  • Requirements are categorised by the CIR in which the feature is (primarily) discussed; the rightmost column gives the conformance level (§6.1, p. 10).
  • Conformance levels Optional, Recommended, Required "shall be interpreted as specified in RFC 2119" (§6.1, p. 10).
  • Recommended: "there may exist valid reasons in particular circumstances for a PID provider to not implement such a feature in their PID issuance service, but the PID provider shall understand and carefully weigh the full implications before doing so and shall document these considerations"; the certification body shall request this documentation for any recommended feature not implemented (§6.1, p. 10).
  • "Where a PID issuance service implements a feature, it shall comply with all related functional requirements in the legal basis and in the corresponding standards mentioned therein" (§6.1, p. 10).
  • Note in the document: "In this version of this document, the lists of requirements may not be fully complete. Additionally, indicated conformance levels are subject to change" (§6.1, p. 10).
  • No requirements are listed from CIR 2024/2979 ("None.") (§6.2, p. 10; Annex A.3.1, p. 13).
  • Requirements: #1 PID issuance using OpenID4VCI — Recommended; #2 PID issuance using the NL-specific issuance specification — Required (legal reference "-") (§6.3, p. 10); #3 PIDs in mdoc format — Required; #4 PIDs in SD-JWT VC format — Required (§6.4, p. 11).
  • The ICS declared implementation choices (Annex A.3) reflect the conformance requirements of Chapter 6 (§7.1, p. 12), with a "Declaration (Yes / No)" column (Annex A.3.2–A.3.3, p. 13–14).
  • The PID provider does not declare in this ICS which optional PID attributes and metadata it supports, although PID contents are specified in CIR 2024/2977; it shall declare this using an ICS that is part of the test case specification for PID contents (see NL-FS §6.3) (Annex A.3 Note, p. 13).
  • Annex A.1 identification fields: PID issuance service name; Version (Annex A.1, p. 13).
  • Annex A.2 identification fields: PID provider name; full address; contact person name, title; contact phone number; contact e-mail address (Annex A.2, p. 13).

Requirements in this document​

All 4 entries are listed one by one, with their text and PDF page, on the NL-FS-P requirements page. You can also search them together with all other requirements.

Notes on this draft​

  • §6.1 Note: "the lists of requirements may not be fully complete. Additionally, indicated conformance levels are subject to change" (§6.1, p. 10).
  • The Annex A introduction of the PID issuance service ICS template reads "This Annex provides the template for the Implementation Conformance Statement of the wallet solution. The wallet provider completes the template..." (Annex A, p. 13).
  • Numbering mismatch: §6.4 items #3 and #4 are numbered 1 and 2 in Annex A.3.3 (§6.4, p. 11; Annex A.3.3, p. 14).
  • Legal references differ between §6.4 ("CIR 2024/2977 Article 3 and Annex (4)") and Annex A.3.3 ("CIR 2024/2977 Annex section 4") (§6.4, p. 11; Annex A.3.3, p. 14).
  • Item #2 "NL-specific issuance specification" has no legal reference ("-") and that specification is not listed in the normative references (§3, p. 7; §6.3, p. 10).
  • The "test case specification for PID contents" containing the PID attribute ICS is referred to but not identified (Annex A.3 Note, p. 13).
  • Footer reads "NL-FS - EUDI Wallet Functional Certification – PID Issuance Conformance Issuance" (p. 2).
  • The cover title lacks the word "Scheme" ("EUDI Wallet Functional Certification"), unlike NL-FS-W (p. 1).
  • §4 says the terms "classification, reference test method, test area, verification by inspection" are used "as defined in NL-FS" (§4, p. 8); NL-FS §4 (NL-FS p.10) contains no definitions of these terms.
  • "Implementations Conformance Statements" (typo) (§7.1, p. 12).

Sources​