Section 1: Set of natural person identification data
Data identifier | Definition
family_name | Current last name(s) or surname(s) of the user to whom the person identification data relates.
given_name | Current first name(s), including middle name(s) where applicable, of the user to whom the person identification data relates.
birth_date | Day, month, and year on which the user to whom the person identification data relates was born.
birth_place | The country as an alpha-2 country code as specified in ISO 3166-1, or the state, province, district, or local area or the municipality, city, town, or village where the user to whom the person identification data relates was born.
nationality | One or more alpha-2 country codes as specified in ISO 3166-1, representing the nationality of the user to whom the person identification data relates.
portrait | Except where the user explicitly opts out, where applicable, the facial image of the user to whom the person identification data relates, compliant with the quality requirements for a full frontal image type as set out in ISO/IEC 39794-5 or, for backward compatibility, ISO/IEC 19794-5, clauses 8.2, 8.3 and 8.4, provided as encoded image data without the headers or blocks as specified in clause 5 of ISO/IEC 19794-5, except for the image data itself (a JPEG) shall apply from 11 August 2028.
Member States may provide that the user has the option to decline the insertion of the portrait to the person identification data.
Member States shall ensure that the selective disclosure applies to each data identifier, including the portrait.
Where the birth date of the natural person is not known, Member States shall choose appropriate values that comply with the specifications set out in sections 4.1 or 4.2 (as appropriate) to this Annex.
Where the nationality of the natural person is unknown, Member States shall use the value 'QU'.
Where the natural person does not hold a nationality, Member States shall use the value 'QS'.
Where the user opts out of the inclusion of the portrait, Member States shall set the value empty.
[P. Resnick, Ed., ‘Internet Message Format,’ RFC 5322, October 2008.]
Data identifier | Definition
resident_address | The full address of the place where the user to whom the person identification data relates currently resides or can be contacted (street name, house number, city, etc.).
resident_country | The country where the user to whom the person identification data relates currently resides, as an alpha-2 country code as specified in ISO 3166-1.
resident_state | The state, province, district, or local area where the user to whom the person identification data relates currently resides.
resident_city | The municipality, city, town, or village where the user to whom the person identification data relates currently resides.
resident_postal_code | The postal code of the place where the user to whom the person identification data relates currently resides.
resident_street | The name of the street where the user to whom the person identification data relates currently resides, including the house number and any affix or suffix thereof.
personal_administrative_number | A value assigned to the user to whom the person identification data relates that is unique among all personal administrative numbers issued by the provider of person identification data. Where Member States opt to include this attribute, they shall describe in their electronic identification schemes under which the person identification data is issued, the policy that they apply to the values of this attribute, including, where applicable, specific conditions for the processing of this value.
family_name_birth | Last name(s) or surname(s) of the user to whom the person identification data relates at the time of birth.
given_name_birth | First name(s), including middle name(s), of the user to whom the person identification data relates at the time of birth.
sex |
Values shall be one of the following:
0 = not known;
1 = male;
2 = female;
3 = other;
4 = inter;
5 = diverse;
6 = open;
9 = not applicable;
For values 0, 1, 2 and 9, ISO/IEC 5218 applies.
email_address | Electronic mail address of the user to whom the person identification data relates [in accordance with RFC 5322].
mobile_phone_number | Mobile telephone number of the user to whom the person identification data relates, starting with the ‘+’ symbol as the international code prefix and the country code, followed by numbers only.
Section 2: Set of legal person identification data
Data identifier
current legal name
a unique identifier constructed by the sending Member State in accordance with the technical specifications for the purposes of cross-border identification and which is as persistent as possible in time
Where a data identifier is not known for the person or cannot otherwise be issued as part of the person identification dataset, Member States shall instead use an attribute value appropriate to the situation.
[Directive (EU) 2017/1132 of the European Parliament and of the Council of 14 June 2017 relating to certain aspects of company law (OJ L 169, 30.6.2017, p. 46, ELI: http://data.europa.eu/eli/dir/2017/1132/oj).] [Commission Implementing Regulation (EU) 2022/1860 of 10 June 2022 laying down implementing technical standards for the application of Regulation (EU) No 648/2012 of the European Parliament and of the Council with regard to the standards, formats, frequency and methods and arrangements for reporting (OJ L 262, 7.10.2022, p. 68, ELI: http://data.europa.eu/eli/reg_impl/2022/1860/oj).] [Commission Implementing Regulation (EU) No 1352/2013 of 4 December 2013 establishing the forms provided for in Regulation (EU) No 608/2013 of the European Parliament and of the Council concerning customs enforcement of intellectual property rights (OJ L 341, 18.12.2013, p. 10, ELI: http://data.europa.eu/eli/reg_impl/2013/1352/oj).] [C ouncil Regulation (EU) No 389/2012 of 2 May 2012 on administrative cooperation in the field of excise duties and repealing Regulation (EC) No 2073/2004 (OJ L 121, 8.5.2012, p. 1, ELI: http://data.europa.eu/eli/reg/2012/389/oj).]
Data identifier
current address
VAT registration number
tax reference number
European unique identifier referred to in Directive (EU) 2017/1132 of the European Parliament and of the Council
Legal Entity Identifier (LEI) referred to in Commission Implementing Regulation (EU) 2022/1860
Economic Operator Registration and Identification (EORI) referred to in Commission Implementing Regulation (EU) No 1352/2013
excise number provided in Article 2(12) of Council Regulation (EU) No 389/2012
Section 3: Set of metadata about person identification data
Data identifier | Definition | Presence
issuing_authority | Name of the administrative authority that issued the person identification data, or the ISO 3166 alpha-2 country code of the respective Member State if there is no separate authority entitled to issue person identification data. | mandatory
issuing_country | alpha-2 country code, as specified in ISO 3166-1, of the country or territory of the provider of the person identification data. | mandatory
expiry_date | Date (and if possible time) when the administrative validity period of the person identification data will expire. | optional
document_number | A number for the person identification data, assigned by the provider of person identification data. | optional
issuing_jurisdiction | Country subdivision code of the jurisdiction that issued the person identification data, as specified in ISO 3166-2:2020, Clause 8. The first part of the code shall be the same as the value for the issuing country. | optional
issuance_date | Date, and if possible time, when the administrative validity period of the person identification data started. | optional
Section 4: Encoding of natural person identification data attributes
Natural person identification data shall be issued in accordance with the standards set out in Annex II to Implementing Regulation (EU) 2024/2979, clauses 5 (SD-JWT VC format) and 6 (ISO/IEC-mdoc format) as applicable to electronic attestations of attributes. Clauses 5.2.2, 5.2.4, 5.2.5, EAA-6.1-03, 6.2.2, 6.2.3,6.2.4 and 6.2.5 shall not apply.
The encoding of natural person identification data shall comply with the technical specifications in sections 4.1 and 4.2 of this Annex.
4.1 Encoding of natural person identification data in ISO/IEC-mdoc format
The attestation type for person identification data in ISO/IEC mdoc format shall be 'eu.europa.ec.eudi.pid.1'. The identifier of the namespace for the person identification data attributes set out in this Annex shall be 'eu.europa.ec.eudi.pid.1'.
Where the person identification data includes data for which data identifiers are not set out in this Annex, these data shall be defined within a domestic person identification data namespace that uses the general format eu.europa.ec.eudi.pid.[ISO 3166-1 alpha-2 country code or the ISO 3166-2 region code] followed by an optional dot and version number.
Where the domestic namespace is used, its scheme, including all data identifiers, their definitions, presence and encoding formats, shall be published in accordance with Article 8 of Commission Implementing Regulation (EU) 2025/1569 [Commission Implementing Regulation (EU) 2025/1569 of 29 July 2025 laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards qualified electronic attestations of attributes and electronic attestations of attributes provided by or on behalf of a public sector body responsible for an authentic source (OJ L, 2025/1569, 30.7.2025, ELI: http://data.europa.eu/eli/reg_impl/2025/1569/oj).].
The person identification data and its metadata set out in sections 1 and 3 of this Annex shall be included in person identification data elements within the meaning of ISO/IEC mdoc format specifications.
The deviceKey member within the deviceKeyInfo member of the instance of MobileSecurityObject type shall contain a public key.
That public key shall correspond to a private key that is stored in the wallet secure cryptographic device (‘WSCD’) of the wallet user.
The Protected Header of the CB-AdES digital signature signing a person identification data in ISO/IEC-mdoc format shall contain the x5u and the x5t header parameters, both specified in RFC 9360 [J. Schaad, ‘CBOR Object Signing and Encryption (COSE): Header Parameters for Carrying and Referencing X.509 Certificates’ (https://datatracker.ietf.org/doc/rfc9360/).].
The digest algorithm used in the x5t header parameter shall be SHA-256.
The requirements for encoding person identification data in ISO/IEC-mdoc format are set out in Table 6:
Data Identifier | Attribute identifier | Encoding format
family_name | family_name | tstr
given_name | given_name | tstr
birth_date | birth_date | full-date
birth_place | place_of_birth | place_of_birth
nationality | nationality | nationalities
resident_address | resident_address | tstr
resident_country | resident_country | tstr
resident_state | resident_state | tstr
resident_city | resident_city | tstr
resident_postal_code | resident_postal_code | tstr
resident_street | resident_street | tstr
personal_administrative_number | personal_administrative_number | tstr
portrait | portrait | bstr
family_name_birth | family_name_birth | tstr
given_name_birth | given_name_birth | tstr
sex | sex | uint
email_address | email_address | tstr
mobile_phone_number | mobile_phone_number | tstr
expiry_date | expiry_date |
tdate
or full-date
issuing_authority | issuing_authority | tstr
issuing_country | issuing_country | tstr
document_number | document_number | tstr
issuing_jurisdiction | issuing_jurisdiction | tstr
issuance_date | issuance_date |
tdate
or full-date
The notation of the encoding format of the attributes specified in Table 6 shall use representation types as specified in RFC 8610 [C. Vigano and H. Birkholz, ‘Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures’, RFC 8610, June 2019.], with the following additional requirements:
a tstr shall be encoded in UTF-8;
a tstr shall support the full Unicode range;
a tstr shall have a maximum length of 150 characters;
a date shall be encoded as specified in RFC 8943 [M. Jones, A. Nadalin and J. Richter, ‘Concise Binary Object Representation (CBOR) Tags for Date’, RFC 8943, November 2020.];
a full-date shall be interpreted as #6.1004(tstr), where tag 1004 is as specified in RFC 8943;
a tdate attribute shall contain a date-time string as specified in RFC 3339 [G. Klyne and C. Newman, ‘Date and Time on the Internet: Timestamps’, RFC 3339, July 2002.];
a full-date attribute shall contain a full-date string as specified in RFC 3339, in accordance with RFC 8943;
a representation of a date in attributes shall, unless otherwise indicated:
not use fractions of seconds;
not use a local offset from UTC and the time-offset specified in RFC 3339 shall be set to 'Z'.
an integer with major types 0 and 1 shall be as small as possible, as specified in RFC 8949 [C. Bormann and P. Hoffman, ‘Concise Binary Object Representation (CBOR)’, RFC 8949, December 2020.], section 4.2;
a place_of_birth shall contain at least one of the following key-value pairs: 'country', 'region', or 'locality';
the expression of the length in a bstr, tstr, array or map shall be as short as possible, as specified in RFC 8949, section 4.2;
the attribute nationality shall be encoded as an array of alpha-2 country codes as specified in ISO 3166-1. Where CDDL notation as specified in RFC 8610 is used, the encoding of this attribute shall be:
nationalities = [+ CountryCode];
CountryCode = tstr; alpha-2 country code specified in ISO 3166-1;
where a wallet user to whom the person identification data relates has multiple nationalities and the provider of person identification data attests to these multiple nationalities, the provider of person identification data may include all the nationalities in the person identification data;
the attribute place_of_birth shall be encoded as a type place_of_birth. Where CDDL notation as specified in RFC 8610 is used, the encoding of this attribute shall be:
place_of_birth =
{
? 'country': tstr; a single alpha-2 country code as specified in ISO 3166-1
? 'region': tstr; the name of a state, province, district, or local area
? 'locality': tstr; the name of a municipality, city, town, or village
}
4.2 Requirements for encoding person identification data in SD-JWT VC format
The person identification data and its metadata specified in this section shall be included in a person identification data as claims in the meaning of SD-JWT VC format specifications.
All claims in the issued person identification data, referenced in the previous indent, shall be selectively disclosable individually, except those claims defined as non-selectively disclosable in SD-JWT VC format.
Table 7 specifies the encoding of claim names that are public names.
Table 8 specifies the encoding of claim names that are specific to the person identification data.
A JSON string used in person identification data encoded in SD-JWT VC shall be encoded in UTF-8 and shall support the full Unicode range, unless explicitly specified otherwise in Table 8 below or the references therein.
The JWT claims nbf and exp as defined in RFC 7519 [J. Jones, et al., ‘JSON Web Token (JWT)’, RFC 7519, May 2015.] shall be used to express the technical validity period of person identification data compliant with SD-JWT VC format.
Person identification data shall incorporate the cnf claim as defined in RFC 7800 [M. Jones, et al., ‘Proof-of-Possession Key Semantics for JSON Web Tokens (JWTs)’, RFC 7800, April 2016.], which shall be a public key generated from a private key stored in the WSCD of the wallet users wallet unit.
The Protected Header of the digital signature signing a person identification data in SD-JWT VC format shall contain the x5u and the x5t#S256 header parameters, specified in RFC 7515 [M. Jones, et al., ‘JSON Web Signature (JWS)’, RFC 7515, May 2015.].
Data Identifier | Attribute identifier | Encoding format
family_name | family_name | string
given_name | given_name | string
birth_date | birthdate | string, ISO 8601-1, YYYY-MM-DD format
birth_place | place_of_birth | JSON structure
nationality | nationalities | array of strings
resident_address | address.formatted | string
resident_country | address.country | string
resident_state | address.region | string
resident_city | address.locality | string
resident_postal_code | address.postal_code | string
resident_street | address.street_address | string
family_name_birth | birth_family_name | string
given_name_birth | birth_given_name | string
email_address | email | string
mobile_phone_number | phone_number | string
portrait | picture | string; data URL containing a base64-encoded portrait in JPEG format
Data Identifier | Attribute identifier | Encoding format
expiry_date | date_of_expiry | string, ISO 8601-1, YYYY-MM-DD format
issuance_date | date_of_issuance | string, ISO 8601-1, YYYY-MM-DD format
personal_administrative_number | personal_administrative_number | string
sex | sex | number
issuing_authority | issuing_authority | string
issuing_country | issuing_country | string
document_number | document_number | string
issuing_jurisdiction | issuing_jurisdiction | string
The base type of person identification data shall be 'urn:eudi:pid:1', included in the vct claim. All person identification data shall use types in the namespace 'urn:eudi:pid:'.
Where person identification data includes attributes that are not specified in this Annex, these attributes shall be defined within a domestic type.
Where the domestic type is used, its scheme, including all data identifiers, their definitions, presence and encoding formats, shall be defined in a scheme that is published in accordance with Article 8 of Implementing Regulation (EU) 2025/1569.
Section 5: Trust infrastructure details
The list of providers of person identification data made available by the Commission in accordance with Implementing Regulation (EU) 2024/2980 shall enable the authentication of person identification data.