Skip to main content

NL-FS-W: Wallet Solution Conformance (Presentation Requirements)

NL-FS-W: Wallet Solution Conformance (Presentation Requirements)

Download PDF (342 kB, 18 pages)Read the full text37 requirements
Cover page of the document, as printed
Document referenceNL-FS-W
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, EUDI Wallet 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-W specifies the functional certification scope for wallet solutions 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-P) 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 wallet solution provided by a wallet provider" (§5, p. 9).
  • The certification scope is the conformity of the functional behaviour of the wallet solution observable at its interfaces towards: (a) PID or attestation issuance services, (b) Relying Parties, (c) Users, (d) auxiliary components such as Trusted Lists, List of Trusted Entities, and certificate revocation services (§5, p. 9).
  • These interfaces are in scope "insofar they are supported by the wallet solution that is being certified" (§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).
  • Wallet providers preparing a wallet solution for certification: the document is intended for them (§1, p. 5). Wallet providers seeking functional certification "shall complete this ICS" (§7.1, p. 14); the wallet provider completes the Annex A template and submits it as part of the application for certification (Annex A, p. 15); it shall declare whether the wallet solution implements each listed feature (Annex A.3, p. 15). For a Recommended feature not implemented, it shall understand and weigh the implications and document these considerations (§6.1, p. 10).

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 taken from NL-SYS-02 and NL-FS; p.8. Read
  • §5 Certification scope for the wallet solution: object of certification and interfaces in scope; p.9. Read
  • §6 Requirements for functional conformance: overview and conformance levels (6.1), and requirement tables per CIR (6.2 CIR 2024/2979, 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.14. Read
  • Annex A (normative) Wallet solution ICS template: A.1 identification of the object of certification, A.2 identification of wallet provider, A.3 declared implementation choices (A.3.1–A.3.3 per CIR); p.15. Read

Key points​

  • Chapter 6 lists the requirements regarding features of wallet solutions mandated in the legal instruments; these "enable modularity of the certification" and allow a wallet 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 wallet provider to not implement such a feature in their wallet solution, but the wallet 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).
  • The document does not itself define Required and Optional beyond the reference to RFC 2119 (§6.1, p. 10).
  • "Where a wallet solution 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).
  • Some items are conditional (footnotes): #16 and #17 "Only applicable if requirement #15 is supported" (§6.3, p. 11); #21 and #22 "Only applicable if either or both of requirements #19 or #20 are supported"; #25 and #26 only if #21 is supported; #27 and #28 only if #22 is supported (§6.3, p. 12).
  • Item #17 "Wallet solution support PID issuance using the NL-specific issuance specification" is Required and has "-" as primary legal reference (§6.3, p. 11).
  • Items #33–#35 (QEAA, PuB-EAA, EAA) contain the placeholder "<insert attestation types>" (§6.4, p. 13; Annex A.3.3, p. 18).
  • The ICS template's "declared implementation choices" in Annex A.3 reflect the conformance requirements of Chapter 6 (§7.1, p. 14); Annex A.3 uses the same numbering (#1–#37) with a "Declaration (Yes / No)" column instead of the conformance column (Annex A.3, p. 15–18).
  • Conditional ICS items are "Only to be declared if" the prerequisite item is answered Yes: #16–#17 if ICS #15 is Yes (Annex A.3.2, p. 16); #21–#22 if #19 or #20 is Yes; #25–#26 if #21 is Yes; #27–#28 if #22 is Yes (Annex A.3.2, p. 17).
  • Annex A.1 identification fields: Wallet solution name; Version; Relevant operating system (Android / iOS); Minimum supported version of OS (Annex A.1, p. 15).
  • Annex A.2 identification fields: Wallet provider name; full address; contact person name, title; contact phone number; contact e-mail address (Annex A.2, p. 15).
  • For general information on ICSs the document refers to section 6.3 of NL-FS (§7.1, p. 14).

Requirements in this document​

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

  • Requirements are numbered consecutively #1–#37 across three tables, each with columns "#", "Item", "Primary legal references", "Conformance" (§6.2–6.4, p. 10–13).
  • §6.2 Requirements from CIR 2024/2979 (Integrity and core functionalities): #1–#14 (§6.2, p. 10–11).
  • §6.3 Requirements from CIR 2024/2982 (Protocols and interfaces): #15–#31 (§6.3, p. 11–13).
  • §6.4 Requirements from CIR 2024/2977 (PID and EAA): #32–#37 (§6.4, p. 13).
  • Counts by conformance level (counted from the tables): Required 11 (#1–#7, #13, #15, #17, #32); Recommended 14 (#8, #16, #18–#23, #26, #28–#30, #36, #37); Optional 12 (#9–#12, #14, #24, #25, #27, #31, #33–#35) (§6.2–6.4, p. 10–13).
  • NL-FS: provides the framework, methodology and evaluation rules (§1, p. 5); terms test objective, classification, reference test method, test area, verification by inspection and ICS are "used as defined in NL-FS" (§4, p. 8); section 6.3 of NL-FS for more on ICSs (§7.1, p. 14).
  • NL-FS-P: the other principal scope document, for PID issuance services (§1, p. 5).
  • NL-SYS-02: terms wallet solution, wallet instance, WSCA, WSCD and wallet provider (§4, p. 8).
  • RFC 2119: interpretation of conformance levels (§3, p. 7; §6.1, p. 10).
  • Regulation (EU) No 910/2014 as amended by Regulation (EU) 2024/1183 (Articles 5a, 5a(4), 5a(5), 5a(8), 5a(23), 5a(24), 5b(1), 5c(1), 5f(2)): legal basis and per-item references (§2, p. 6; §6.2–6.4, p. 10–13).
  • CIR 2024/2979 (integrity and core functionalities), CIR 2024/2982 (protocols and interfaces), CIR 2024/2977 (PID and EAA): sources of functional requirements (§2, p. 6).
  • ETSI TS 119 472-1 (referenced in items #6 and #7), ETSI TS 119 472-3 (item #16, OpenID4VCI) and ETSI TS 119 472-2 (item #21, OpenID4VP), each "by referencing" via the CIR legal references (§6.2–6.3, p. 10–12); ISO/IEC 18013-5 (mdoc), ISO/IEC 18013-7, SD-JWT VC, OpenID4VCI, OpenID4VP, W3C Digital Credentials API named in items (§6.2–6.4, p. 10–13).

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).
  • Item #17 and its "NL-specific issuance specification" have no legal reference ("-") and that specification is not listed in the normative references (§3, p. 7; §6.3, p. 11).
  • Items #6 and #7 ("supports PID and EAA in ISO/IEC 18013-5 (mdoc) format" / "in SD-JWT VC format") are Required, while items #36 and #37 ("supports PIDs and attestations in mdoc format" / "in SD-JWT VC format") are Recommended (§6.2, p. 10; §6.4, p. 13).
  • Legal references "Annex 1b" and "Annex 1I" for CIR 2024/2979 appear as written (§6.2, p. 10).
  • §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 and refers to ISO/IEC 17000, 17065, 17067 and NL-SYS-02.
  • Grammar: "Wallet solution support attestation issuance" (#16) and "Wallet solution support PID issuance" (#17) (§6.3, p. 11); "insofar they are supported" (§5, p. 9); "Implementations Conformance Statements" (§7.1, p. 14).
  • Footer reads "NL-FS - EUDI Wallet Functional Certification – Wallet Solution Conformance" rather than "NL-FS-W" (p. 2).
  • Placeholders "<insert attestation types>" in #33–#35 (§6.4, p. 13).
  • Annex A.1 pre-fills "Android / iOS" in the Declaration column for "Relevant operating system" (Annex A.1, p. 15).

Sources​