Skip to main content

NL-P-W: Wallet Provider Certification Scheme

NL-P-W: Wallet Provider Certification Scheme

Cover page of the document, as printed
Document referenceNL-P-W
VersionRC1.1
StatusRelease Candidate
Date31/10/2026
Document typeCertification Scheme Scheme Specification (EN ISO/IEC 17067)
Parent frameworkNL-SYS-01, NL-SYS-02, NL-SYS-03, NL-SYS-04, NL-SYS-05
Scheme OwnerKingdom of the Netherlands Minister of Economic Affairs
Certification targetEuropean Digital Identity Wallet Providers (and the Wallet Solutions provided)
Primary audienceScheme Owners, CABs, EUDI Wallet providers
Secondary audienceEUDI Wallet ecosystem stakeholders
Assurance levelHigh/High
Subsidiary DocumentsNL-P-01, NL-P-02, NL-P-03, NL-P-W04
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-P-W specifies the Wallet Provider Certification Scheme, one of the Certification Schemes within the NL EUDI Wallet Certification System, and defines the Certification Scheme (in the sense of ISO/IEC 17067) that accredited Certification Bodies (CABs) shall apply when certifying Wallet Providers (§1, p. 5). It establishes the service requirements (by reference to the subsidiary documents), the evaluation methodology (by reference to normative Annex B and the subsidiary documents) and the conformity assessment procedures (§2, p. 6). It is primarily addressed to CABs; Wallet Providers should read it together with the applicable NL-P-* subsidiary documents, which specify the substantive requirements they shall meet (§1, p. 5).

Scope and object of certification​

  • The scheme is for Wallet Providers that are to be certified and that seek to be admitted to the Dutch National eID Scheme (“Stelsel”) (§2, p. 6).
  • The object of certification "encompasses services that consists of provision and operation of wallet solutions and of the electronic identification schemes under which they are provided" (§2, p. 6).
  • "In the context of this certification scheme, the object of certification is the wallet provider, comprising the organizational arrangements and processes of the Wallet Provider that deliver the wallet related services to individuals (in conjunction with the PID Provider)" (§2, p. 6).
  • §6.1 states: "The object of certification under this scheme is the Provider the electronic identification system under which of European Digital Identity Wallets are provided, as referred to in Article 5c(1) of Regulation (EU) 2024/1183"; the certification covers both the scheme-level governance arrangements and the operational services provided by EUDI Wallet Provider and PID Provider (§6.1, p. 10).
  • Annex B describes the object of certification as "the electronic identification system, elated services and processes" (Annex B, B.2, p. 26) and as "The electronic identification system and related services defined by NL-P-W" (Annex B, B.3.2 Table 1, p. 27).
  • The evaluation scope covers services related to provision and operation of the EUDI Wallet solution in conjunction with the national eID scheme; as a minimum it covers NL-P-01, NL-P-02, NL-P-03, NL-P-W04, NL-P-W04b and the presence of valid NL-FS and NL-CS certificates covering the wallet solution(s) and version(s) in scope (§7.2, p. 13).
  • Outsourced or subcontracted services are in the evaluation scope to the extent they are material to fulfilling the certification requirements (§7.2, p. 13).
  • Acceptable external assurance evidence may reduce the extent of the CAB's own evaluation activities, but the scope of the certification shall not be reduced on that basis (§7.2, p. 13).

Who it applies to​

  • Scheme Owner: owns and supervises the scheme, authorises CABs, maintains the certificate register and monitors the scheme (normative basis ISO/IEC 17067) (§6.2.1 Table 2, p. 10). Attends the kick-off meeting (§8.3.1, p. 17); receives notification of issued certificates and of suspensions, terminations and withdrawals, and updates the Certificate Register (§8.7, p. 19; §8.10, p. 21); decides on extension of a suspension (§8.10, p. 21); may impose contractual arrangements (§9.2, p. 23). The cover names the Scheme Owner as Kingdom of the Netherlands, Minister of Economic Affairs (cover, p. 2).
  • CAB: plans, performs and documents the evaluation; issues the certification decision and certificate of conformity; manages surveillance and recertification (normative basis ISO/IEC 17065; NL-SYS-05) (§6.2.1 Table 2, p. 10). Shall be accredited by the National Accreditation Body under ISO/IEC 17065 with a scope covering NL-P-W and the subsidiary documents (§6.2.2, p. 11) and shall implement impartiality mechanisms per ISO/IEC 17065 (§6.3, p. 11). "In the context of NL-P-W certification scheme only a certification body is considered as a CAB" (§6.1, p. 10). Grants, suspends and withdraws the right to use the mark of conformity (§6.7, p. 12).
  • Applicant / Certificate Holder: submits the eID scheme for certification, provides evaluation evidence and complies with post-certification obligations, including surveillance cooperation and change notification (normative basis NL-P-W) (§6.2.1 Table 2, p. 10).
  • EUDI Wallet Provider: shall notify the Scheme Owner and its NL-P-W CAB without undue delay when an NL-FS, NL-CS or NL-P-W certificate is suspended, withdrawn or expires (§6.4, p. 11); shall cease using the mark of conformity without undue delay when its certificate is suspended or withdrawn (§6.7, p. 12); shall document its rationale where it considers a CIR 2024/2690 "where appropriate/applicable/to the extent feasible" requirement not appropriate, applicable or feasible (§7.5, p. 15).
  • PID Provider: named on the certificate of conformity ("name of PID Provider Provider") (§8.7, p. 19); its personnel may provide statements, explanations and demonstrations as evidence (§7.4, p. 14).
  • National Accreditation Body (NAB): accredits CABs under ISO/IEC 17065 for the relevant scope (normative basis Regulation (EC) No 765/2008) (§6.2.1 Table 2, p. 11).
  • Market Surveillance Authorities: oversight of certified services in the market; "This role will be performed by the NL-TL Scheme Owner" (§6.2.1 Table 2, p. 11).
  • Audit roles in Annex B: Audit Team (one or more auditors appointed by the CAB or its subcontractor, supported by technical experts if necessary), Audit Team Leader (manages the audit and reports findings to the CAB), Technical Expert (provides specialist knowledge, does not act independently as an auditor) (Annex B, B.3.2 Table 1, p. 27). Technical experts shall not act as sole evaluator of conformity or take the certification decision (Annex B, B.10.2, p. 32); the Audit Team shall not issue the certification decision (Annex B, B.12.4, p. 34).

Contents​

  • 1 Foreword — positions NL-P-W in the NL EUDI Wallet Certification System and refers to the additional top-level certificate (p.5).
  • 2 Scope — scheme target and object of certification (p.6).
  • 3 Legal Basis — the EU legal instruments under which the scheme is established, plus a placeholder for NL law (p.7).
  • 4 References — standards, parent, peer and subsidiary documents (p.8).
  • 5 Terms and Definitions — refers to NL-SYS-02 Vocabulary (p.9).
  • 6 Certification Scheme Structure — object of certification, roles, impartiality, relationship to NL-FS/NL-CS and to the subsidiary documents, scheme type, marks of conformity (p.10).
  • 7 Evaluation Framework — scope, methods, evidence, proportionality, re-use of assurance evidence, evaluation criteria (p.13).
  • 8 Certification Process — application, evaluation, certification, efforts, certificate, surveillance, recertification, suspension/withdrawal, implications of NL-FS/NL-CS certificate changes (p.17).
  • 9 Final provisions — national legislation, certification contracts, costs (p.23).
  • Annex A (Normative) — Allocation of legal requirements to subsidiary documents (p.24). Read
  • Annex B (Normative) — Audit framework for planning, conducting and documenting audits (p.26). Read
  • Annex C (Normative) — Minimum contents of an audit plan (p.36). Read
  • Annex D (Normative) — Minimum contents of an audit evidence record (p.37). Read
  • Annex E (Normative) — Evaluation results matrix template (p.38).

Key points​

  • Scheme type: Type 6 model of EN ISO/IEC 17067 (initial testing and evaluation, surveillance of the service delivery, periodic re-evaluation), in accordance with Article 4(3)(a) of CIR (EU) 2024/2981 (§6.6, p. 12).
  • Applicable requirement documents (Table 1): NL-P-01 Organisational and technical requirements for Wallet & PID providers; NL-P-02 Essential Entity Cyber Resilience Requirements; NL-P-03 Development & Vulnerability Mngt Requirements; NL-P-W04 Wallet Onboarding & Lifecycle Mngt Requirements; NL-P-W04b Fraud Mngt Requirements (§6.1 Table 1, p. 10). The CAB assesses conformity against these (§6.1, p. 10); they "constitute the normative substance of the eID Certification Scheme" (§6.5, p. 12).
  • How each applies: NL-P-01 gives management and operational requirements; NL-P-02 gives cyber resilience requirements "in the spirit of NIS2"; NL-P-03 gives development and vulnerability management practices "in the spirit of the CRA"; NL-P-W04 gives requirements for the wallet onboarding process and lifecycle events "to ensure Wallet stay under control of the correct citizen"; NL-P-W04b gives requirements that "should additionally be met" to ensure the service has resistance against fraud modus operandi (§6.5, p. 12).
  • NL-FS and NL-CS certificates are assessed and certified independently from NL-P-W, but the resulting certificates "constitute a necessary condition for certification under NL-P-W" (§6.4, p. 11).
  • The CAB shall verify that the Wallet Provider holds valid NL-FS and NL-CS certificates covering the wallet solution(s) and version(s) in scope; the scheme allows the Wallet Provider to submit declarations that appropriate NL-FS and NL-CS evaluation and certification processes are in place, including a declaration of conformity regarding correct integration with the NL PID provider services; the CAB assesses scope and currency but need not re-evaluate requirements already covered (§6.4, p. 11).
  • Before issuing a certificate, the CAB shall verify valid NL-FS and NL-CS certificates; it "shall not issue a NL-P-W certificate of conformity where any required NL-FS or NL-CS certificate is absent, expired, suspended or withdrawn" (§8.7, p. 19).
  • Evaluation methods: document review, interview, observation, technical testing, sampling (sampling methodology documented in the evaluation plan) (§7.3, p. 14).
  • Evidence types include server-side audit trails and logs from the live operational environment (systems serving real users, as distinct from test, pilot or reference environments) (§7.4, p. 14); evidence is retained per NL-SYS-01 section 5.10 (§7.4, p. 15).
  • Proportionality: requirements derived from CIR 2015/1502 Section 2.4 are commensurate to risks at assurance level High; CIR 2024/2690 requirements are applied taking account of the Wallet Provider's risk exposure (Article 2(2)) (§7.5, p. 15). The CAB considers the risk register (minimum content per NL-SYS-04), with particular attention to risks from integration of the Wallet(s) with the NL PID-provider (§7.5, p. 15).
  • Accepted external assurance evidence: ISO/IEC 27001 certificates from a certification body accredited by a Dutch Accreditation Body under ISO/IEC 17021-1; ETSI EN 319 411-1/-2 certificates; certificates or reports under European or national cybersecurity certification schemes (such as EUCC, or EN 17640-based if mutual-recognition rules exist); other recognised reports meeting §7.7 (§7.6, p. 15-16).
  • Evaluation criteria for assurance evidence (per Annex VI and Annex II of CIR 2024/2981): issuer competence and impartiality, scope adequacy, timeliness, rigor and depth, findings and exceptions (§7.7, p. 16). An ISO/IEC 27001 certificate does not on its own suffice; the CAB performs its own evaluation of the specific controls required by the subsidiary documents (§7.7, p. 16).
  • Reliance (full, partial or none) is formally determined by the CAB per NL-SYS-01 §5.3 and NL-P-W §7.6-7.7, not by the Audit Team (Annex B, B.9.2, p. 31).
  • Certification process phases: preparation and application, evaluation, and certification (§8.1, p. 17).
  • Audit model: the audit forms part of the NL-P-W evaluation phase (Annex B, B.11, p. 32). Initial and re-assessment audits "should normally comprise Stage 1 and Stage 2"; the sequence may be adapted where justified and permitted by NL-SYS-05 and the audit plan (Annex B, B.11.1, p. 32). Stage 1 (documentation and readiness review) is intended to understand the object of certification, confirm audit readiness and plan Stage 2; its results shall be documented and used to finalise the Stage 2 plan; potential nonconformities identified in Stage 1 are treated as areas of concern until supported by sufficient evidence (Annex B, B.11.2, p. 32). Stage 2 (implementation and operational effectiveness) shall collect objective evidence that applicable requirements are implemented and operate effectively, and shall include relevant sites and operational environments unless sufficient equivalent evidence is obtained and the use of remote or external assurance evidence is justified (Annex B, B.11.3, p. 32). Surveillance and special audits can use a targeted, risk-based sequence rather than the full Stage 1 and Stage 2 model (Annex B, B.11.4, p. 33).
  • Sampling shall be risk-based and documented (population, selection method, sample size, items, limitations) (Annex B, B.8.2, p. 30); a sample-based multi-site approach requires common control and a common management and review framework (Annex B, B.8.3, p. 30).
  • Applicability per requirement: Applicable or Not applicable (with documented and accepted rationale); not-applicable requirements receive no conformity result (Annex B, B.12.1, p. 33).
  • Requirement-level results: Conforming; Major nonconformity (substantial security impact and/or substantial impact on achieving the intended service or process outcome); Minor nonconformity (no such substantial impact); Not concluded - insufficient evidence (not treated as conformity, must be resolved before a positive audit recommendation) (Annex B, B.12.2 Table 3, p. 33). Positive or negative observations may be recorded; an observation may not replace a conformity assessment result and shall not, by itself, constitute a failure to meet a requirement (Annex B, B.12.3, p. 33-34).
  • Nonconformities: the Applicant provides correction, root-cause analysis, corrective action, owner, target date and evidence of completion (Annex B, B.14, p. 34). Major nonconformities shall be corrected and closure verified before a positive certification recommendation or decision; timeframes for minor nonconformities are agreed per NL-P-W, "G-SYS-05" and the CAB procedure, and the framework "does not establish an independent fixed deadline" (Annex B, B.14, p. 34).
  • Time limits: kick-off meeting no later than 10 working days after receipt of a complete application (§8.3.1, p. 17); certification decision and informing the Applicant within 5 working days after review of results; certificate issued no later than 14 working days after a positive decision (§8.4, p. 18); written complaint against a negative decision within 14 working days, CAB final decision within 14 working days of receipt of the objection (§8.4, p. 18); CAB notifies the Scheme Owner of an issued certificate within five working days (§8.7, p. 19).
  • Planned CAB effort (initial certification; maximum and planned values, changeable by agreement with the Scheme Owner): Evaluation 30 working days, Certification 15 working days (§8.5 Table 3, p. 18).
  • Certificate validity: four years from the date of issuance (§8.6, p. 18); the certificate states a validity period "not to exceed four years" (§8.7, p. 19).
  • Certificate content: object of certification; scope with explicit reference to each NL-P-W subsidiary document; name of PID Provider; version(s) of the wallet solutions in scope; validity period; any conditions, limitations or exceptions (§8.7, p. 19).
  • Surveillance: annual surveillance activities throughout the validity period, covering at least material changes notified to the CAB, notified incidents or breaches, updates to NL-P-W and subsidiary documents, impact of updates to NL-P-P and subsidiary documents, risk-based targeted evaluation, continued validity of NL-FS and NL-CS certificates, and follow-up of nonconformities (§8.8, p. 19).
  • Vulnerability assessment during initial evaluation, each recertification and "at least every two years during surveillance activities"; penetration testing etc. where risk increases or new threats emerge (§8.8, p. 20).
  • Each surveillance activity within 12 months of certificate issuance and thereafter within 12 months of the previous surveillance; recertification within 12 months after the last surveillance activity (§8.8, p. 20).
  • 4-year life cycle (Table 4): Year 0 initial certification (full evaluation including vulnerability assessment; evaluation of maintenance processes excluding their operating effectiveness; granting of certification and start of the 4-year cycle); Year 1 surveillance (operating effectiveness of maintenance processes; changes impacting security); Year 2 surveillance (vulnerability assessment of the full solution; operating effectiveness of maintenance processes; changes impacting security); Year 3 re-certification (full re-evaluation including vulnerability assessment; simplified evaluation for unchanged features/processes; maintenance processes including their operating effectiveness; granting a new certification) (§8.8 Table 4, p. 20).
  • Recertification is initiated before expiry and follows the initial certification process; it may rely on surveillance evidence (§8.9, p. 20-21). It is also required on a major change, including a wallet solution version not covered by the certificate, a change to the Provider's organisational structure, or a material change to the Trust Framework under NL-SYS-03 (§8.9, p. 21). The Applicant notifies the CAB no later than six months before expiry (§8.9, p. 21).
  • Suspension grounds: corrective actions not implemented within the agreed time after a surveillance nonconformity; prerequisite NL-FS or NL-CS certificate suspended or revoked; notified significant incident or security breach that can impact conformity (pending impact assessment); failure to cooperate with or provide access for surveillance (§8.10, p. 21). The corrective-action timeframe is agreed in writing and documented in the Surveillance Report (§8.10, p. 21).
  • Suspension period shall not exceed 45 days; any extension is subject to Scheme Owner decision "but in any case, may not exceed one 90 days"; suspension does not affect the certificate validity period (§8.10, p. 21).
  • Withdrawal grounds: failure to remedy suspension conditions within the time specified; confirmed nonconformity that cannot be remedied within reasonable time. Termination on request of the Wallet Provider (§8.10, p. 21).
  • NL-FS/NL-CS certificate suspended or revoked: the CAB initiates an impact assessment; suspends the NL-P-W certificate for the affected Wallet Solution if conformity is materially affected, otherwise documents reasoning and continues monitoring; on withdrawal of an NL-FS or NL-CS certificate the NL-P-W certificate shall be suspended immediately with regard to the related Wallet Solution services, pending recertification following restoration of the NL-FS or NL-CS certificate (§8.11, p. 21-22).
  • Mark of conformity: only the NL EUDI Wallet Mark defined in NL-SYS-03; no additional marks are defined (§6.7, p. 12).
  • Information exchange between CAB and Applicant shall be secured with state-of-the-art cryptographic mechanisms approved by the Scheme Owner (§8.6, p. 19).
  • Appeals and complaints are dealt with under the general provisions of NL-SYS-01 (§8.4, p. 18).
  • Certification contract between CAB and Applicant based on NL-P-W; it shall not obstruct correct conduct of certification or transfer of relevant information (§9.2, p. 23). All costs shall be based on actual certification efforts (§9.3, p. 23).
  • Special audits shall be initiated by the CAB on significant changes, security incidents, complaints, failure to implement corrective actions or other information relevant to continued conformity (Annex B, B.15, p. 35).

Process​

  1. Applicant: submits, before evaluation starts, a description of the Wallet Provider's environment and systems; documentation of compliance with the subsidiary documents; valid NL-FS and NL-CS certificates for the wallet solution version(s) in scope or declarations that NL-FS/NL-CS processes are in place; any external assurance evidence; the completed CAB application form. The application may be separate or combined with other schemes per NL-SYS-01 (§8.2, p. 17).
  2. CAB, Applicant and Scheme Owner representatives: kick-off meeting no later than 10 working days after receipt of a complete application; the CAB agrees the evaluation plan (scope, schedule, reliance approach, on-site visits and interviews) with the Applicant (§8.3.1, p. 17).
  3. CAB: performs the evaluation per §7 and "the applicable WM-03 audit framework" and documents it in an Evaluation Report with an overall assessment of conformity with each requirement, the reliance determination for external assurance evidence and a recommendation for the certification decision (§8.3.2, p. 18); under Annex B, initial audits should normally comprise Stage 1 and Stage 2 (Annex B, B.11.1, p. 32). The CAB notifies the Applicant of substantial findings without undue delay; the Applicant may respond within the timeframe agreed at kick-off (§8.3.2, p. 18).
  4. Applicant / CAB: correction of nonconformities; major nonconformities shall be corrected and their closure verified before a positive certification recommendation or decision (Annex B, B.14, p. 34).
  5. CAB: after reviewing the evaluation results, certification decision and informing the Applicant within 5 working days; certificate issued no later than 14 working days after a positive decision (§8.4, p. 18).
  6. Applicant / CAB: on a negative decision, written complaint within 14 working days; CAB final decision within 14 working days of receipt (§8.4, p. 18).
  7. CAB: notifies the Scheme Owner of the issued certificate within five working days (§8.7, p. 19).
  8. CAB: annual surveillance during validity (§8.8, p. 19-20).
  9. Applicant / CAB: recertification, notified at least six months before expiry (§8.9, p. 20-21).
  10. CAB / Scheme Owner: suspension, withdrawal or termination; CAB notifies Scheme Owner, who updates the Certificate Register (§8.10, p. 21).

Requirements in this document​

  • Requirements applicable specifically to the Wallet Provider are located in the subsidiary documents and are not separately listed in Annex A (Annex A, p. 24); the subsidiary documents constitute the normative substance of the scheme (§6.5, p. 12).
  • Annex A uses identifiers REQ-<legal act>-<article/section> to allocate legal requirements to documents: A.1 Regulation (EU) 2024/1183 — REQ-910-01 to REQ-910-06 (6); A.2 CIR (EU) 2015/1502 — REQ-1502-2.1, -2.2, -2.4.1 to -2.4.7 (9); A.3 CIR (EU) 2024/2977 — REQ-2977-3, REQ-2977-5 (2); A.4 CIR (EU) 2024/2979 — REQ-2979-3,4, REQ-2979-6,7, REQ-2979-9,13 (3); A.5 CIR (EU) 2024/2981 — REQ-2981-4, -5, -8(3)(g), -19 (4); A.6 CIR (EU) 2024/2690 — REQ-2690-Annex (1) (Annex A, p. 24-25).
  • Annex E results codes: C / Major NC / Minor NC / N/E / OBS; reliance Full / Partial / None; applicability Applicable / N/A (Annex E, p. 38).
  • NL-SYS-01 (parent): read in conjunction; overarching rules on top-level certificate, accreditation, re-use of evidence (§5.3), surveillance (§5.4), suspension and withdrawal (§5.7, 5.8), record keeping (§5.10), Audit Report content (§6.3), appeals and complaints (§1, p. 5; §6.2.2, p. 11; §7.6, p. 15; §8.8, p. 19; §8.10, p. 21; §7.4, p. 15; Annex B, B.13.1, p. 34; §8.4, p. 18).
  • NL-SYS-02: all terms and definitions (§5, p. 9).
  • NL-SYS-03: NL EUDI Wallet Mark, certificate notification procedure, Certificate Register, Trust Framework (§6.7, p. 12; §8.7, p. 19; §8.10, p. 21; §8.9, p. 21).
  • NL-SYS-04: minimum content of the risk register (§7.5, p. 15; §8.8, p. 19).
  • NL-SYS-05: accreditation requirements and competences for CABs, impartiality, evaluation process requirements (Section 7), corrective-action timeframes (§2, p. 6; §6.2.2, p. 11; §6.3, p. 11; §7.1, p. 13; §8.10, p. 21).
  • NL-TL: the NL Top Level Certification additionally requires an active Wallet Provider Certificate, an active certificate of the PID provider that issues a PID to the wallet, and that the Wallet Provider meets the national admission conditions to connect to the National eID System (§1, p. 5). The Market Surveillance Authority role is performed by the NL-TL Scheme Owner (§6.2.1 Table 2, p. 11). Implications of certificate suspension, withdrawal or expiry for the NL-TL certificate are said to be "addressed in Section 8.11" (§6.4, p. 11).
  • NL-FS (EUDI Wallet Functional Certification Scheme) and NL-CS (EUDI Wallet Cybersecurity Certification Scheme): peer documents addressing the wallet solution as a product; their certificates are a necessary condition for NL-P-W certification (§4.3, p. 8; §6.4, p. 11). Surveillance for product certification is specified in NL-FS and NL-CS (§8.8, p. 19-20).
  • NL-P-P: surveillance includes review of the impact of updates to NL-P-P and subsidiary documents (§8.8, p. 19).
  • Subsidiary documents NL-P-01, NL-P-02, NL-P-03, NL-P-W04, NL-P-W04b (§4.4, p. 8).
  • Standards: ISO/IEC 17065 and ISO/IEC 17067 (§4.1, p. 8); ETSI EN 319 403-1 (audit approach mapped in Annex B) and ETSI EN 319 401 (Annex B, B.1, p. 26); ISO/IEC 27006-1 Annex D (guidelines for audit time) (Annex B, B.5.3, p. 28-29); ISO/IEC 27001, ISO/IEC 17021-1, ETSI EN 319 411-1/-2, EUCC, EN 17640 (assurance evidence) (§7.6, p. 15).
  • EU legal acts (legal basis): Regulation (EU) 910/2014 Articles 5a and 5c; CIR (EU) 2024/2981 (Articles 3-5, 8, 12-14, 19, Annexes I-VII); CIR (EU) 2024/2979; CIR (EU) 2024/2977; CIR (EU) 2015/1502 Annex Section 2.4; CIR (EU) 2024/2690; CIR (EU) 2026/798 (remote onboarding); Regulation (EU) 765/2008 Articles 4 and 5 (§3, p. 7). Regulation (EU) 2024/1183 Article 5c(1) is cited for the object of certification (§6.1, p. 10).

Notes on this draft​

  • National law placeholder: "[Placeholder for references to NL national law when available]" (§3, p. 7).
  • The table of contents does not list sections 8.10 and 8.11, which exist on p.21 (TOC, p. 4; §8.10-8.11, p. 21).
  • Subsidiary document naming varies: cover lists "NL-P-W04" only (no NL-P-W04b) (cover, p. 2); §4.4 and Table 1 list NL-P-W04 and NL-P-W04b (§4.4, p. 8; §6.1, p. 10); Annex A uses "NL-P-W04B", "NL-W-P04B", "NL-P-P04 / NL-P-P04B" and "NS-FS" (Annex A, p. 24-25).
  • The object of certification is described in different words in §2 (the wallet provider, its organisational arrangements and processes), §6.1 ("the Provider the electronic identification system under which of European Digital Identity Wallets are provided", covering services of "EUDI Wallet Provider and PID Provider") and Annex B ("the electronic identification system, elated services and processes") (§2, p. 6; §6.1, p. 10; Annex B, B.2, p. 26).
  • §6.4 says implications for the NL-TL certificate "are addressed in Section 8.11", but §8.11 does not mention NL-TL (§6.4, p. 11; §8.11, p. 21-22).
  • §8.11 refers to "WZ-03 and WP-03 requirements"; §8.3.2 refers to "the applicable WM-03 audit framework"; Annex B refers to "Criteria-specific WM-03-0x documents" and "G-SYS-05"; none of these is defined in the document (§8.11, p. 22; §8.3.2, p. 18; Annex B, B.10.1, p. 32; Annex B, B.14, p. 34).
  • §8.6 refers to "NL-SYS-93, Section 9.2.2", a document not listed in §4 (§8.6, p. 19; §4, p. 8).
  • Annex B B.10.1 refers to "the PL EUDI Wallet Certification System"; §8.3 cites "PN-EN ISO/IEC 17065" (Annex B, B.10.1, p. 31; §8.3, p. 17).
  • §7.7 NOTE 1 refers to "the cases specified in Clauses II and III", which do not exist; §7.5 contains only a clause "I." (§7.7, p. 16; §7.5, p. 15).
  • Suspension extension wording is unclear: "may not exceed one 90 days" (§8.10, p. 21).
  • Certificate content includes "name of PID Provider Provider" (§8.7, p. 19).
  • Validity is four years, while Table 4 places re-certification in Year 3 and §8.8 requires recertification within 12 months after the last surveillance activity (§8.6, p. 18; §8.8, p. 20).
  • Annex B B.7 sentence is truncated: "The CAB shall select an appropriate combination of methods for each evaluation activity. Criteria-specific" (Annex B, B.7, p. 29).
  • §8.8 and §8.10 use the term "CAB-CB" (§8.8, p. 19-20; §8.10, p. 21).
  • The Annex B numbered list item 191 contains only "matters." (continuation of item 190) (Annex B, B.11.5, p. 33).
  • Annex B uses the term "Audit Report" and §8 uses "Evaluation Report"; Annex B B.13.2 explains their relation (Annex B, B.13.2, p. 34).

Sources​