Commission Implementing Regulation (EU) 2026/1730 of 15 July 2026 amending Implementing Re…
as it stood on 2026-07-15, permalink: /eu-eurlex/32026r1730/2026-07-15
Point-in-time view as at 2026-07-15. This version has been
superseded, it applied 2026-07-15 → open. Jump to the
version in force today or see
exactly what changed next.
Text included, per-article reading view.
Deterministic extraction of the verbatim retrieved document; each article carries its own hash and anchor.
© European Union, 1998-2026. Reuse permitted with attribution under Commission Decision 2011/833/EU. Consolidated texts have no legal effect; only acts published in the Official Journal are authentic.
art_1
#art_1
Article 1
Implementing Regulation (EU) 2025/848 is amended as follows:
| (1) | In Article 6(3), point (a) is replaced by the following:‘(a)the accuracy, validity, authenticity and integrity of the information required under Annex I, points 1 to 6 and 11 to 16.’; |
|---|---|
| ‘(a) | the accuracy, validity, authenticity and integrity of the information required under Annex I, points 1 to 6 and 11 to 16.’; |
| (2) | In Article 6(3), point (c) is deleted; |
|---|
| (3) | In Article 6, the following paragraph 3a is inserted:‘3a. Registrars shall collect the information referred to in Annex I, points 7 to 10 in an automated manner only for the purpose of transparency and, without prejudice to paragraph 4 of Article 5b of Regulation (EU) No 910/2014, shall not apply any preauthorisation process on this information.’; |
|---|
| (4) | Article 8 is amended as follows:(a)paragraph 1 is replaced by the following:‘1. Member States shall authorise at least one certificate authority to issue wallet relying party registration certificates. Member States shall ensure that providers of wallet-relying party registration certificates issue those certificates in an automated manner and without undue delay after the registration.’;(b)paragraph 2 is replaced by the following:‘2. Member States shall:(a)require providers of wallet-relying party registration certificates to issue wallet-relying party registration certificates exclusively to registered wallet-relying parties;(b)ensure that each intended use is expressed in the wallet-relying party registration certificates;(c)ensure that wallet-relying party registration certificates include a general access policy, being syntactically and semantically harmonised across the Union, informing users that the wallet-relying party is only allowed to request the data specified in the registration certificates for the intended use registered in the registration certificates;(d)ensure that providers of wallet solutions established in that Member State comply with the general access policy by informing users when a wallet-relying party requests data that is not specified in the registration certificates;(e)implement wallet-relying party registration certificates in a syntactically and semantically harmonised manner and in line with the requirements set out in Annex V;(f)implement dedicated certificate policies and certificate practice statements for the wallet-relying party registration certificates in accordance with the requirements set out in Annex V;(g)ensure that wallet-relying parties provide a URL to the privacy policy regarding the intended use.’; |
|---|---|
| (a) | paragraph 1 is replaced by the following:‘1. Member States shall authorise at least one certificate authority to issue wallet relying party registration certificates. Member States shall ensure that providers of wallet-relying party registration certificates issue those certificates in an automated manner and without undue delay after the registration.’; |
| (b) | paragraph 2 is replaced by the following:‘2. Member States shall:(a)require providers of wallet-relying party registration certificates to issue wallet-relying party registration certificates exclusively to registered wallet-relying parties;(b)ensure that each intended use is expressed in the wallet-relying party registration certificates;(c)ensure that wallet-relying party registration certificates include a general access policy, being syntactically and semantically harmonised across the Union, informing users that the wallet-relying party is only allowed to request the data specified in the registration certificates for the intended use registered in the registration certificates;(d)ensure that providers of wallet solutions established in that Member State comply with the general access policy by informing users when a wallet-relying party requests data that is not specified in the registration certificates;(e)implement wallet-relying party registration certificates in a syntactically and semantically harmonised manner and in line with the requirements set out in Annex V;(f)implement dedicated certificate policies and certificate practice statements for the wallet-relying party registration certificates in accordance with the requirements set out in Annex V;(g)ensure that wallet-relying parties provide a URL to the privacy policy regarding the intended use.’; |
| (a) | require providers of wallet-relying party registration certificates to issue wallet-relying party registration certificates exclusively to registered wallet-relying parties; |
| (b) | ensure that each intended use is expressed in the wallet-relying party registration certificates; |
| (c) | ensure that wallet-relying party registration certificates include a general access policy, being syntactically and semantically harmonised across the Union, informing users that the wallet-relying party is only allowed to request the data specified in the registration certificates for the intended use registered in the registration certificates; |
| (d) | ensure that providers of wallet solutions established in that Member State comply with the general access policy by informing users when a wallet-relying party requests data that is not specified in the registration certificates; |
| (e) | implement wallet-relying party registration certificates in a syntactically and semantically harmonised manner and in line with the requirements set out in Annex V; |
| (f) | implement dedicated certificate policies and certificate practice statements for the wallet-relying party registration certificates in accordance with the requirements set out in Annex V; |
| (g) | ensure that wallet-relying parties provide a URL to the privacy policy regarding the intended use.’ |
| (5) | Annex I is amended as set out in Annex I to this Regulation; |
|---|
| (6) | Annex IV is amended as set out in Annex II to this Regulation; |
|---|
| (7) | Annex V is amended as set out in Annex III to this Regulation. |
|---|
art_2
#art_2
Article 2
This Regulation shall enter into force on the twentieth day following that of its publication in the Official Journal of the European Union.
Provenance and validity dates, identifier, hash
| as of | 2026-07-15 → this version applied |
| valid | 2026-07-15 → open publisher-asserted |
| type | REG_IMPL Commission Implementing Regulation (EU) 2026/1730 of 15 July 2026 amending Implementing Regulation (EU) 2025/848 as regards applicable standards and specifications |
| language | en |
| published | 2026-07-15 |
| lex_id | eu-eurlex:32026r1730:2026-07-15 |
| record sha256 | dba45f24eaefc9c2fc20cc021783107f5176cac92cd1b2b34c38af357cd8a345 |
New here? What am I looking at?
This is a consolidated text: the original law with every later amendment merged in, as the official publisher produced it for a given date. Laws are amended constantly, so “the law” has no single text, only a text per date. That date is the banner above.
It has no legal force. Only the version published in the official gazette (Mémorial / Official Journal) is authentic, the publishers say so themselves, and so do we. Lex reproduces their text without altering a byte, and links the source on every page. This is legal information, never legal advice: it reports what the text said, never what it means for your situation.
“Valid from → to” = the window in which this text applied. “Open” = still current as far as the publisher has consolidated. Each article carries its own hash so you can prove it was not tampered with , here is how.
timeline next version (2026-07-15) →
| tier | A, publisher-supplied validity dates |
| history begins | publisher |
| index built | 2026-08-07T19:46:23Z · corpus 8d5e859 |
| stamp signature | valid (ECDSA-P256) |