Skip to main content

NL-FS-W full text

Converted text

This is the text of NL-FS-W, converted automatically from the PDF so you can read and search it here. The PDF is authoritative. Tables with merged cells can be flattened, and text inside diagrams is only in the images. The individual requirements are listed separately.

NL-FS-W​

EUDI Wallet Functional Certification Scheme Wallet Solution Conformance

RC1.0 2026-11-06

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 level <identity proofing CIR 2015/1502> and <evaluation, EU Regulation 2019/881>High/High
Subsidiary DocumentsNL Certification System Documents
History of changesHistory of changes
VersionChangeStatusDate
RC1.0First consolidated versionRelease Candidate Draft2026-11-06

1 Scope​

This document specifies the functional certification scope for wallet solutions within the common EUDI Wallet Certification System, as well as the corresponding requirements for functional conformance. It also provides a corresponding Implementation Conformance Statement (ICS).

It identifies the documents that form the legal basis for certification, containing functional requirements applicable to wallet solutions.

This document is one of the two principal scope documents of the functional certification scheme; the other, NL-FS-P, addresses the conformance of a PID issuance service. This document operates within the framework, methodology and evaluation rules defined in NLFS.

This document is intended for conformity assessment bodies and for wallet providers preparing a wallet solution for certification.

2 Legal basis​

The functional certification scope defined in this document derives from Regulation (EU) No 910/2014 as amended by Regulation (EU) 2024/1183, in particular Article 5a (European Digital Identity Wallets) and Article 5c(1) (Certification of European Digital Identity Wallets).

Further functional requirements are specified in the Commission Implementing Regulations adopted under Article 5a(23) and Article 5a(24) of this Regulation, in particular:

  • Commission Implementing Regulation (EU) 2024/2979 (integrity and core functionalities of European Digital Identity Wallets),
  • Commission Implementing Regulation (EU) 2024/2982 (protocols and interfaces to be supported by the European Digital Identity Wallet Framework);
  • Commission Implementing Regulation (EU) 2024/2977 (person identification data and electronic attestations of attributes issued to European Digital Identity Wallets);

Under Article 5c(1), the certification 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).

3 Normative references​

The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document.

  • (a) NL-SYS-02, EUDI Wallet Certification System - Vocabulary
  • (b) NL-FS, EUDI Wallet Functional Certification Scheme
  • (c) Commission Implementing Regulation (EU) 2024/2979
  • (d) Commission Implementing Regulation (EU) 2024/2982
  • (e) Commission Implementing Regulation (EU) 2024/2977
  • (f) RFC 2119, Key words for use in RFCs to Indicate Requirement Levels, S. Bradner, March 1997

4 Terms and definitions​

For the purposes of this document, the terms and definitions given in NL-SYS-02 and NL-FS apply. In particular, the terms test objective, classification, reference test method, test area, verification by inspection and Implementation Conformance Statement (ICS) are used as defined in NL-FS, and the terms wallet solution, wallet instance, WSCA, WSCD and wallet provider are used as defined in NL-SYS-02.

5 Certification scope for the wallet solution​

The object of certification in scope of this document is a wallet solution provided by a wallet provider. The certification scope comprises the conformity of the functional behaviour of the wallet solution observable at its interfaces towards the following other entities in the EUDI Wallet ecosystem:

  • (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

These interfaces are in scope of the certification insofar they are supported by the wallet solution that is being certified. Chapter 6 specifies the conformance requirements regarding support of wallet solution features, and Annex A specifies the corresponding Implementation Conformance Statement that shall be used by wallet providers to declare which features are supported and which are not.

6 Requirements for functional conformance​

6.1 Overview​

This chapter lists the requirements of the scheme regarding the features of wallet solutions mandated in the legal instruments. These requirements for functional conformance enable modularity of the certification regarding these features. This allows a wallet provider to indicate which of the legally mandated features are implemented.

This chapter categorises the conformance requirements according to the CIR in which the corresponding feature is (primarily) discussed. The rightmost column indicates the conformance level of that feature under the scheme.

Note: In this version of this document, the lists of requirements may not be fully complete. Additionally, indicated conformance levels are subject to change.

The indicated conformance levels (Optional, Recommended, Required) shall be interpreted as specified in RFC 2119. In particular, where a feature is indicated as Recommended under the scheme, it means that 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. During the certification process, the certification body shall request this documentation for any recommended feature that is not implemented.

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.2 Requirements from CIR 2024/2979 (Integrity and core functionalities)​

#ItemPrimary legal referencesConformance
1.Wallet solution supports wallet user authenticationCIR 2024/2979 Article 3Required
2.Wallet solution supports wallet secure cryptographic devices and wallet secure cryptographic applicationsCIR 2024/2979 Articles 4 and 5Required
3.Wallet solution supports wallet instance attestationsCIR 2024/2979 Article 6 and Annex 1bRequired
4.Wallet solution supports key attestationsCIR 2024/2979 Article 6 and Annex 1bRequired
5.Wallet solution supports revocation of wallet instance attestations and key attestationsCIR 2024/2979 Article 7 and Annex 1bRequired
6.Wallet solution supports PID and EAA in ISO/IEC 18013-5 (mdoc) formatCIR 2024/2979 Article 7 and Annex 1I (by referencing ETSI TS 119 472-1)Required
7.Wallet solution supports PID and EAA in SD-JWT VC formatCIR 2024/2979 Article 7 and Annex 1I (byRequired
referencing ETSI TS 119 472-1)
8.Wallet solution supports transaction logseIDAS Article 5a(4)(d)(i) CIR 2024/2979 Article 9Recommended
9.Wallet solution supports embedded disclosure policieseIDAS Article 5a(5)(e) CIR 2024/2979 Article 10Optional
10.Wallet solution supports qualified electronic signatures and sealseIDAS Article 5a(4)(e) CIR 2024/2979 Article 11 and 12Optional
11.Wallet solution supports User data export and portabilityeIDAS Article 5a(4)(f) and (g) CIR 2024/2979 Article 13Optional
12.Wallet solution supports pseudonymseIDAS Article 5a(4)(b) CIR 2024/2979 Article 14Optional
13.Wallet solution supports EUDI Wallet Trust MarkeIDAS Article 5a(5)(a)(iv) CIR 2024/2979 Article 14aRequired
14.Wallet solution supports Strong User AuthenticationeIDAS Article 5f(2)Optional

6.3 Requirements from CIR 2024/2982 (Protocols and interfaces)​

#ItemPrimary legal referencesConformance
15.Wallet solution supports attestation issuanceeIDAS Article 5a(5)(a)(i) CIR 2024/2982 Article 4Required
16.Wallet solution support attestation issuance using OpenID4VCI 1CIR 2024/2982, Article 4 and Annex I (by referencing ETSI TS 119 472-3)Recommended
17.Wallet solution support PID issuance using the NL-specific issuance specification 1-Required
18.Wallet solution supports proximity attestation presentationseIDAS Article 5a(5)(a)(iii) CIR 2024/2982 Art 5(1)Recommended
19.Wallet solution supports remote same-device attestation presentationseIDAS Article 5a(5)(a)(iii) CIR 2024/2982 Art 5(1)Recommended
20.Wallet solution supports remote cross-device attestation presentationseIDAS Article 5a(5)(a)(iii) CIR 2024/2982 Art 5(1) and Annex II (12)Recommended

1 Only applicable if requirement #15 is supported.

21.Wallet solution supports remote attestation presentation using OpenID4VP 2CIR 2024/2982, Annex II (by referencing ETSI TS 119 472-2)Recommended
22.Wallet solution supports remote attestation presentation using ISO/IEC 18013-7 2CIR 2024/2982, Annex IIRecommended
23.Wallet solution supports access certificate verificationeIDAS Article 5a(5)(a)(vii) and 5a(5)(c) CIR 2024/2982 Article 3(1)Recommended
24.Wallet solution supports registration certificate verificationeIDAS Article 5b(1) CIR 2024/2982 Article 3(4)Optional
25.Wallet solution supports remote attestation presentation using OpenID4VP and non-API-mediated transmission (i.e., redirects) 3CIR 2024/2982, Annex IIOptional
26.Wallet solution supports remote attestation presentation using OpenID4VP and API-mediated transmission (i.e., the W3C Digital Credentials API)3CIR 2024/2982, Annex IIRecommended
27.Wallet solution supports remote attestation presentation using ISO/IEC 18013-7 and non-API-mediated transmission (i.e., redirects) 4CIR 2024/2982, Annex IIOptional
28.Wallet solution supports remote attestation presentation using ISO/IEC 18013-7 and API-mediated transmission (i.e., the W3C Digital Credentials API) 4CIR 2024/2982, Annex IIRecommended
29.Wallet solution supports data erasure requests to Relying PartieseIDAS Article 5a(4)(d)(ii) and 5a(5)(a)(ix) CIR 2024/2982 Article 6Recommended
30.Wallet solution supports reporting Relying Parties to a DPAeIDAS Article 5a(4)(d)(iii) and 5a(5)(a)(x) CIR 2024/2982 Article 7Recommended

2 Only applicable if either or both of requirements #19 or #20 are supported.

3 Only applicable if requirement #21 is supported.

4 Only applicable if requirement #22 is supported.

31.Wallet solution supports Wallet-to- Wallet attestation presentationseIDAS Article 5a(4)(c) and 5a(5)(a)(vi)Optional

6.4 Requirements from CIR 2024/2977 (PID and EAA)​

#ItemPrimary legal referencesConformance
32.Wallet solution supports PIDeIDAS Article 5a(4)(a) CIR 2024/2977 Article 3Required
33.Wallet solution supports the following types of QEAA: <insert attestation types>eIDAS Article 5a(4)(a) CIR 2024/2977 Article 4Optional
34.Wallet solution supports the following types of PuB-EAA: <insert attestation types>eIDAS Article 5a(4)(a) CIR 2024/2977 Article 4Optional
35.Wallet solution supports the following types of EAA: <insert attestation types>eIDAS Article 5a(4)(a) CIR 2024/2977 Article 4Optional
36.Wallet solution supports PIDs and attestations in mdoc formatCIR 2024/2977 Article 3/4 and Annex (4)Recommended
37.Wallet solution supports PIDs and attestations in SD-JWT VC formatCIR 2024/2977 Article 3/4 and Annex (4)Recommended

7 Implementation Conformance Statement​

7.1 ICS template​

Implementations Conformance Statements (ICS) are declarations, to be completed by the developer of an object of certification, regarding the features that are supported or not supported by the object of certification. For more information on such statements within the context of the scheme, please refer to section 6.3 of NL-FS.

Annex A includes the template of an ICS for wallet solutions. Note that the 'declared implementation choices' in Annex A.3 reflect the functional conformance requirements listed in chapter 6.

Wallet providers seeking functional certification of their wallet solution shall complete this ICS.

Annex A (normative) Wallet solution ICS template​

This Annex provides the template for the Implementation Conformance Statement of the wallet solution. The wallet provider completes the template and submits it as part of the application for certification. The ICS records the object of certification and the declared implementation choices.

A.1 Identification of the object of certification​

ItemDeclaration
Wallet solution name
Version
Relevant operating systemAndroid / iOS
Minimum supported version of OS

A.2 Identification of wallet provider​

ItemDeclaration
Wallet provider name
Wallet provider full address
Contact person name, title
Contact phone number
Contact e-mail address

A.3 Declared implementation choices​

The wallet provider shall declare, using the tables below, whether the wallet solution implements the mentioned features from the cited legal instruments.

A.3.1 Regarding CIR 2024/2979 (Integrity and core functionalities)​

#ItemPrimary legal referencesDeclaration (Yes / No)
1.Wallet solution supports wallet user authenticationCIR 2024/2979 Article 3
2.Wallet solution supports wallet secure cryptographic devices and wallet secure cryptographic applicationsCIR 2024/2979 Articles 4 and 5
3.Wallet solution supports wallet instance attestationsCIR 2024/2979 Article 6 and Annex 1b
4.Wallet solution supports key attestationsCIR 2024/2979 Article 6 and Annex 1b
5.Wallet solution supports revocation of wallet instance attestations and key attestationsCIR 2024/2979 Article 7 and Annex 1b
6.Wallet solution supports PID and EAA in ISO/IEC 18013-5 (mdoc) formatCIR 2024/2979 Article 7 and Annex 1I (by referencing ETSI TS 119 472-1)
7.Wallet solution supports PID and EAA in SD-JWT VC formatCIR 2024/2979 Article 7 and Annex 1I (by referencing ETSI TS 119 472-1)
8.Wallet solution supports transaction logseIDAS Article 5a(4)(d)(i) CIR 2024/2979 Article 9
9.Wallet solution supports embedded disclosure policieseIDAS Article 5a(5)(e) CIR 2024/2979 Article 10
10.Wallet solution supports qualified electronic signatures and sealseIDAS Article 5a(4)(e) CIR 2024/2979 Article 11 and 12
11.Wallet solution supports User data export and portabilityeIDAS Article 5a(4)(f) and (g) CIR 2024/2979 Article 13
12.Wallet solution supports pseudonymseIDAS Article 5a(4)(b) CIR 2024/2979 Article 14
13.Wallet solution supports EUDI Wallet Trust MarkeIDAS Article 5a(5)(a)(iv) CIR 2024/2979 Article 14a
14.Wallet solution supports Strong User AuthenticationeIDAS Article 5f(2)

A.3.2 Regarding CIR 2024/2982 (Protocols and interfaces)​

#ItemPrimary legal referencesDeclaration (Yes / No)
15.Wallet solution supports attestation issuanceeIDAS Article 5a(5)(a)(i) CIR 2024/2982 Article 4
16.Wallet solution support attestation issuance using OpenID4VCI 5CIR 2024/2982, Article 4 and Annex I (by referencing ETSI TS 119 472-3)
17.Wallet solution support PID issuance using the NL-specific issuance specification 5-
18.Wallet solution supports proximity attestation presentationseIDAS Article 5a(5)(a)(iii)

5 Only to be declared if ICS #15 is answered with Yes.

CIR 2024/2982 Art 5(1)
19.Wallet solution supports remote same-device attestation presentationseIDAS Article 5a(5)(a)(iii) CIR 2024/2982 Art 5(1)
20.Wallet solution supports remote cross-device attestation presentationseIDAS Article 5a(5)(a)(iii) CIR 2024/2982 Art 5(1) and Annex II (12)
21.Wallet solution supports remote attestation presentation using OpenID4VP 6CIR 2024/2982, Annex II (by referencing ETSI TS 119 472-2)
22.Wallet solution supports remote attestation presentation using ISO/IEC 18013-7 6CIR 2024/2982, Annex II
23.Wallet solution supports access certificate verificationeIDAS Article 5a(5)(a)(vii) and 5a(5)(c) CIR 2024/2982 Article 3(1)
24.Wallet solution supports registration certificate verificationeIDAS Article 5b(1) CIR 2024/2982 Article 3(4)
25.Wallet solution supports remote attestation presentation using OpenID4VP and non- API-mediated transmission (i.e., redirects) 7CIR 2024/2982, Annex II
26.Wallet solution supports remote attestation presentation using OpenID4VP and API-mediated transmission (i.e., the W3C Digital Credentials API) 7CIR 2024/2982, Annex II
27.Wallet solution supports remote attestation presentation using ISO/IEC 18013-7 and non-API-mediated transmission (i.e., redirects) 8CIR 2024/2982, Annex II
28.Wallet solution supports remote attestation presentation using ISO/IEC 18013-7 and API-mediated transmission (i.e., the W3C Digital Credentials API) 8CIR 2024/2982, Annex II
29.Wallet solution supports data erasure requests to Relying PartieseIDAS Article 5a(4)(d)(ii) and 5a(5)(a)(ix) CIR 2024/2982 Article 6
30.Wallet solution supports reporting Relying Parties to a DPAeIDAS Article 5a(4)(d)(iii) and 5a(5)(a)(x)

6 Only to be declared if either or both of ICS #19 or #20 are answered with Yes.

7 Only to be declared if ICS #21 is answered with Yes.

8 Only to be declared if ICS #22 is answered with Yes.

CIR 2024/2982 Article 7
31.Wallet solution supports Wallet-to-Wallet attestation presentationseIDAS Article 5a(4)(c) and 5a(5)(a)(vi)

A.3.3 Regarding CIR 2024/2977 (PID and EAA)​

#ItemPrimary legal referencesDeclaration (Yes / No)
32.Wallet solution supports PIDeIDAS Article 5a(4)(a) CIR 2024/2977 Article 3
33.Wallet solution supports the following types of QEAA: <insert attestation types>eIDAS Article 5a(4)(a) CIR 2024/2977 Article 4
34.Wallet solution supports the following types of PuB-EAA: <insert attestation types>eIDAS Article 5a(4)(a) CIR 2024/2977 Article 4
35.Wallet solution supports the following types of EAA: <insert attestation types>eIDAS Article 5a(4)(a) CIR 2024/2977 Article 4
36.Wallet solution supports PIDs and attestations in mdoc formatCIR 2024/2977 Article 3/4 and Annex (4)
37.Wallet solution supports PIDs and attestations in SD-JWT VC formatCIR 2024/2977 Article 3/4 and Annex (4)