- Latest available (Revised)
- Original (As adopted by EU)
Council Directive 1999/37/EC of 29 April 1999 on the registration documents for vehicles
When the UK left the EU, legislation.gov.uk published EU legislation that had been published by the EU up to IP completion day (31 December 2020 11.00 p.m.). On legislation.gov.uk, these items of legislation are kept up-to-date with any amendments made by the UK since then.
Legislation.gov.uk publishes the UK version. EUR-Lex publishes the EU version. The EU Exit Web Archive holds a snapshot of EUR-Lex’s version from IP completion day (31 December 2020 11.00 p.m.).
EU Directives are published on this site to aid cross referencing from UK legislation. Since IP completion day (31 December 2020 11.00 p.m.) no amendments have been applied to this version.
THE COUNCIL OF THE EUROPEAN UNION,
Having regard to the Treaty establishing the European Community, and in particular Article 75(1)(d) thereof,
Having regard to the proposal from the Commission(1),
Having regard to the opinion of the Economic and Social Committee(2),
Acting in accordance with the procedure laid down in Article 189c of the Treaty,(3),
(1) Whereas the Community has adopted a certain number of measures that are intended to create an internal market consisting of an area without frontiers within which the free movement of goods, persons, services and capital is guaranteed in accordance with the provisions of the Treaty;
(2) Whereas all of the Member States require the driver of a vehicle registered in another Member State of hold the certificate of registration corresponding to that vehicle, in order for it to be permitted to use the roads on their territory;
(3) Whereas harmonisation of the form and content of the registration certificate will facilitate its comprehension and thus help towards the free movement, on the roads in the territory of the other Member States, of vehicles registered in a Member State;
(4) Whereas the content of the registration certificate must enable it to be checked that the holder of a driving licence issued pursuant to Council Directive 91/439/EEC of 29 July 1991 on driving licences(4) drives solely those categories of vehicles for which he is authorised; whereas such checking helps to improve road safety;
(5) Whereas, as a prerequisite for registering a vehicle that has previously been registered in another Member State, all of the Member States require a document certifying that registration and the technical characteristics of the vehicle;
(6) Whereas harmonisation of the registration certificate will facilitate the re-entry into service of vehicles that have previously been registered in another Member State, and will contribute to the proper functioning of the internal market;
(7) Whereas Member States use a registration certificate consisting either of one single part or two separate parts, and whereas it is currently appropriate to allow both systems to coexist;
(8) Whereas differences remain between the Member States concerning the interpretation of the particulars contained in the registration certificate; whereas, in the interests of the proper functioning of the internal market and of the free movement and checks that these involve, it is therefore appropriate to specify in which capacity the persons named in the certificate may use the vehicle for which it was issued;
(9) Whereas, in order to facilitate those checks specifically intended to combat fraud and the illegal trade in stolen vehicles, it is appropriate to establish close cooperation between Member States, based on an effective exchange of information;
(10) Whereas it is appropriate to provide for a simplified procedure for adjusting the technical aspects contained in Annexes I and II
HAS ADOPTED THIS DIRECTIVE:
[F1This Directive shall apply to the vehicle registration documents issued by the Member States.]
It shall not prejudice the right of Member States to use, for the temporary registration of vehicles, documents which may not meet the requirements of this Directive in every respect.
Textual Amendments
For the purposes of this Directive:
‘vehicle’: shall mean any vehicle as defined in Article 2 of Council Directive 70/156/EEC of 6 February 1970 on the approximation of the laws of the Member States relating to the type-approval of motor vehicles and their trailers(5) and in Article 1 of Council Directive 92/61/EEC of 30 June 1992 relating to the type-approval of two or three-wheel motor vehicles(6);
‘registration’: shall mean the administrative authorisation for the entry into service in road traffic of a vehicle, involving the identification of the latter and the issuing to it of a serial number, to be known as the registration number;
‘registration certificate’: shall mean the document which certifies that the vehicle is registered in a Member State;
‘holder of the registration certificate’: shall mean the person in whose name a vehicle is registered[F1;]
[F2‘ suspension ’ : means a limited period of time in which a vehicle is not authorised by a Member State to be used in road traffic following which – provided the reasons for suspension have ceased to apply – it may be authorised to be used again without involving a new process of registration;
‘ cancellation of a registration ’ : means the cancellation of a Member State’s authorisation for a vehicle to be used in road traffic.]
Textual Amendments
1.Member States shall issue a registration certificate for vehicles which are subject to registration under their national legislation. The certificate shall consist of either a single part in accordance with Annex I or two parts in accordance with Annexes I and II.
Member States may authorise the services they appoint to this end, in particular those of the manufacturers, to fill in the technical parts of the registration certificate.
2.Where a new registration certificate is issued for a vehicle registered prior to the implementation of this Directive, Member States shall use a certification model as defined in this Directive and may limit the particulars shown therein to those for which the required data are available.
3.The data given in the registration certificate, in accordance with Annexes I and II, shall be represented by the harmonised Community codes shown in those Annexes.
[F24. Member States shall record electronically data on all vehicles registered on their territory. Those data shall include:
(a) all mandatory elements in accordance with point II.5 of Annex I as well as the elements of points II.6(J) and II.6(V.7) and (V.9) of that Annex, where the data are available;
(b) other non-mandatory data listed in Annex I or data from the certificate of conformity as provided for in Directive 2007/46/EC of the European Parliament and of the Council (7) , where possible;
(c) the outcome of mandatory periodic roadworthiness tests in accordance with Directive 2014/45/EU of the European Parliament and of the Council (8) and the period of validity of the roadworthiness certificate.
The processing of personal data in the context of this Directive shall be carried out in accordance with Directives 95/46/EC (9) and 2002/58/EC (10) of the European Parliament and of the Council.
5. Technical vehicle data shall be made available to the competent authorities or testing centres for the purpose of periodic roadworthiness testing. Member States may limit the use and the dissemination of such data by testing centres in order to avoid their misuse.]
Textual Amendments
1. Where the competent authority of a Member State receives notification of a periodic roadworthiness test showing that the authorisation to use a particular vehicle in road traffic has been suspended in accordance with Article 9 of Directive 2014/45/EU, the suspension shall be recorded electronically and an additional roadworthiness test shall be carried out.
The suspension shall be effective until the vehicle has passed a new roadworthiness test. On successful completion of the roadworthiness test, the competent authority shall without delay re-authorise the use of the vehicle in road traffic. No new process of registration shall be necessary.
Member States or their competent authorities may adopt measures to facilitate the retesting of a vehicle the authorisation of which for use in road traffic has been suspended. Those measures may include the grant of permission to travel on public roads between a place of repair and a test centre for the purpose of a roadworthiness test.
2. Member States may allow the holder of the registration certificate to submit a request to the competent authority for transfer of the registration to the new owner of the vehicle.
3. In the event that the competent authority of a Member State receives notification that a vehicle has been treated as an end-of-life vehicle in accordance with Directive 2000/53/EC of the European Parliament and of the Council (11) , the registration of that vehicle shall be cancelled permanently and information to that effect shall be added to the electronic register.]
Textual Amendments
For the purposes of this Directive, the registration certificate issued by a Member State shall be recognised by the other Member States for the identification of the vehicle in international traffic or for its re-registration in another Member State.
1.For the purposes of identifying a vehicle in road traffic, Member States may require that the driver carry Part I of the registration certificate.
2.With a view to re-registering a vehicle previously registered in another Member State, the competent authorities shall require the submission of Part I of the previous registration certificate in every case and the submission of Part II if it was issued. These authorities shall withdraw the part(s) of the previous registration certificate submitted and shall keep the latter for a minimum of six months. They shall, within two months, inform the authorities of the Member State which delivered the certificate of its withdrawal. They shall return the certificate which they have withdrawn to those authorities if they so request within six months of its withdrawal.
Where the registration certificate consists of Parts I and II, and Part II is missing, the competent authorities in the Member State where the new registration has been requested may decide, in exceptional cases, to re-register the vehicle, but only after having obtained confirmation, in writing or by electronic means, from the competent authorities in the Member State where the vehicle was previously registered, that the applicant is entitled to re-register the vehicle in another Member State.
[F23. Without prejudice to Articles 5(4) and 8(3) of Directive 2014/45/EU, Member States shall, as a matter of principle, recognise the validity of the roadworthiness certificate in the event that the ownership of a vehicle – which has a valid proof of periodic roadworthiness test – changes.]
Textual Amendments
The Commission shall be empowered to adopt delegated acts in accordance with Article 7 in order to amend:
point II.4, second indent and point III.1.A(b) of both Annex I and Annex II, in the event of enlargement of the Union,
point II.6 of Annex I in relation to non mandatory elements in the event of changes of definitions or of the content of certificates of conformity in the relevant Union type-approval legislation.
Textual Amendments
1. The power to adopt delegated acts is conferred on the Commission subject to the conditions laid down in this Article.
2. The power to adopt delegated acts referred to in Article 6 shall be conferred on the Commission for a period of five years from 19 May 2014 . The Commission shall draw up a report in respect of the delegation of power not later than nine months before the end of the five-year period. The delegation of power shall be tacitly extended for periods of an identical duration, unless the European Parliament or the Council opposes such extension not later than three months before the end of each period.
3. The delegation of powers referred to in Article 6 may be revoked at any time by the European Parliament or by the Council. A decision to revoke shall put an end to the delegation of the power specified in that decision. It shall take effect the day following the publication of the decision in the Official Journal of the European Union or at a later date specified therein. It shall not affect the validity of any delegated acts already in force.
4. As soon as it adopts a delegated act, the Commission shall notify it simultaneously to the European Parliament and to the Council.
5. A delegated act adopted pursuant to Article 6 shall enter into force only if no objection has been expressed by either the European Parliament or the Council within a period of two months of notification of that act to the European Parliament and the Council or if, before the expiry of that period, the European Parliament and the Council have both informed the Commission that they will not object. That period shall be extended by two months at the initiative of the European Parliament or of the Council.]
Textual Amendments
1.Member States shall bring into force the laws, regulations or administration provisions necessary to comply with this Directive by 1 June 2004. They shall notify the Commission thereof immediately.
When Member States adopt these provisions, they shall contain a reference to this Directive or be accompanied by such reference at the time of their official publication. The methods of making such reference shall be laid down by Member States.
2.Member States shall communicate to the Commission the text of the main provisions of national law which they adopt in the field governed by this Directive.
The Commission shall communicate to the Member States all the models for registration certificates used by the national administration.
Member States shall assist one another in the implementation of this Directive. They may exchange information at bilateral or multilateral level in particular so as to check, before any registration of a vehicle, the latter’s legal status, where necessary in the Member State in which it was previously registered. Such checking may in particular involve the use of an electronic network, comprising data from national electronic databases to facilitate the exchange of information.]
Textual Amendments
This Directive shall enter into force on the day of its publication in the Official Journal of the European Communities.
This Directive is addressed to the Member States.
Textual Amendments
graphics,
watermark,
fluorescent fibres, or
fluorescent imprints.
Member States are free to introduce additional security features.
the name of the Member State issuing Part I of the Registration Certificate,
[F4the distinguishing mark of the Member State issuing Part I of the registration certificate, namely:
:
Belgium
:
Czech Republic
:
Denmark
:
Germany
:
Estonia
:
Greece
:
Spain
:
France
:
Ireland
:
Italy
:
Cyprus
:
Latvia
:
Lithuania
:
Luxembourg
:
Hungary
:
Malta
:
Netherlands
:
Austria
:
Poland
:
Portugal
:
Slovenia
:
Slovakia
:
Finland
:
Sweden
:
United Kingdom,]
the name of the competent authority,
the words ‘ Part I of the Registration Certificate ’ or, if the certificate consists of one part only, the words ‘ Registration Certificate ’ , printed in large type in the language or languages of the Member States issuing the Registration Certificate; they shall also appear, after a suitable space, in small type in the other languages of the European Community,
the words ‘ European Community ’ , printed in the language or languages of the Member State issuing Part I of the Registration Certificate,
the number of the document.
Textual Amendments
F4 Substituted by Treaty between the Kingdom of Belgium, the Kingdom of Denmark, the Federal Republic of Germany, the Hellenic Republic, the Kingdom of Spain, the French Republic, Ireland, the Italian Republic, the Grand Duchy of Luxembourg, the Kingdom of the Netherlands, the Republic of Austria, the Portuguese Republic, the Republic of Finland, the Kingdom of Sweden, the United Kingdom of Great Britain and Northern Ireland (Member States of the European Union) and the Czech Republic, the Republic of Estonia, the Republic of Cyprus, the Republic of Latvia, the Republic of Lithuania, the Republic of Hungary, the Republic of Malta, the Republic of Poland, the Republic of Slovenia, the Slovak Republic, concerning the accession of the Czech Republic, the Republic of Estonia, the Republic of Cyprus, the Republic of Latvia, the Republic of Lithuania, the Republic of Hungary, the Republic of Malta, the Republic of Poland, the Republic of Slovenia and the Slovak Republic to the European Union.
registration number;
date of first registration of the vehicle;
personal data;
holder of the Registration Certificate:
surname(s) or business name,
other name(s) or initial(s) (where appropriate),
address in the Member State of registration on the date of issue of the document;
Where the particulars specified in II.6, code C.2 are not included in the Registration Certificate, reference to the fact that the holder of the Registration Certificate:
is the vehicle owner,
is not the vehicle owner,
is not identified by the Registration Certificate as being the vehicle owner;
vehicle:
make,
type,
variant (if available),
version (if available);
commercial description(s);
vehicle identification number;
mass:
maximum technically permissible laden mass, except for motorcycles;
mass of the vehicle in service with bodywork, and with coupling device in the case of a towing vehicle in service from any category other than M1;
period of validity, if not unlimited;
date of the registration to which this certificate refers;
type-approval number (if available);
engine;
capacity (in cm 3 ),
maximum net power (in kW) (if available),
type of fuel or power source;
power/weight ratio (in kW/kg) (only for motorcycles);
seating capacity,
number of seats, including the driver's seat,
number of standing places (where appropriate).
personal data,
owner of the vehicle (repeated as many times as there are owners),
surname or business name,
other name(s) or initial(s) (where appropriate),
address in the Member State of registration, on the date of issue of the document,
natural or legal person who may use the vehicle by virtue of a legal right other than that of ownership,
surname or business name,
other name(s) or initial(s) (where appropriate),
address in the Member State of registration, on the date of issue of the document,
where a change in the personal data given in points II.5, code C.1, II.6, code C.2 and/or II.6, code C.3 does not give rise to the issue of a new Registration Certificate, the new personal data corresponding to these points may be included under codes (C.5), (C.6), (C.7) or (C.8); they are then broken down in accordance with the references in points II.5, code C.1, II.6, code C.2, II.6, code C.3 and II.5, code C.4;
mass:
maximum permissible laden mass of the vehicle in service in the Member State of registration;
maximum permissible laden mass of the whole vehicle in service in the Member State of registration;
vehicle category;
number of axles;
wheelbase (in mm);
for vehicles with a total exceeding 3 500 kg, distribution of the technically permissible maximum laden mass among the axles:
axle 1 (in kg),
axle 2 (in kg), where appropriate,
axle 3 (in kg), where appropriate,
axle 4 (in kg), where appropriate,
axle 5 (in kg), where appropriate,
technically permissible maximum towable mass of the trailer:
braked (in kg),
unbraked (in kg);
engine:
rated speed (in min-1),
engine identification number;
colour of the vehicle;
maximum speed (in km/h);
sound level:
stationary (in dB(A)),
engine speed (in min-1),
drive-by (in dB(A));
exhaust emissions:
CO (in g/km or g/kWh),
HC (in g/km or g/kWh),
NOx (in g/km or g/kWh),
HC + NOx (in g/km),
particulates for diesel (in g/km or g/kWh),
corrected absorption coefficient for diesel (in min-1),
CO2 (in g/km),
combined fuel consumption (in l/100 km),
fuel tank(s) capacity (in litres) [F1;]
proof of having passed the roadworthiness test, date of next roadworthiness test or expiry of current certificate.]
Being a microprocessor card, the chip card shall be designed in accordance with the standards mentioned in Chapter III.5. The data stored on the card should be legible with normal reading devices (such as for tachograph cards).
Printed on the front and back of the card shall be at least the data specified in Chapters II.4 and II.5; these data shall be legible with the eye (minimum character height: 6 points) and printed on as follows. (Examples of possible lay-outs are presented in Figure 1 at the end of this section.)
The basic data shall contain the following:
To the right of the chip location:
in the language(s) of the Member State issuing the Registration Certificate
the words ‘ European Community ’ ;
the name of the Member State issuing the Registration Certificate;
the words ‘ Part I of the Registration Certificate ’ , or, if the certificate consists of one part only, the words ‘ Registration Certificate ’ printed in large type;
another (e.g. previous national) designation of the equivalent document (optional);
the name of the competent authority (alternatively, also in the form of a personalisation imprint as per Letter B);
the unambiguous consecutive number of the document as used within the Member State (alternatively, also in the form of a personalisation imprint as per Letter B);
Above the chip location:
the distinguishing mark of the Member State issuing the Registration Certificate, white in a blue rectangle and surrounded by twelve yellow stars:
Belgium
Bulgaria]
Denmark
Germany
Greece
Spain
France
Croatia]
Ireland
Italy
Luxembourg
The Netherlands
Austria
Portugal
Romania]
Finland
Sweden
United Kingdom
Member States might consider adding, at the lower edge in small type and in their national language(s), the note: ‘ This document should be produced to any authorised person requesting it. ’
The basic colour of the card is green (Pantone 362); alternatively, a green-to-white transition is possible.
A symbol representing a wheel (see proposed lay-out in Fig.1) shall be printed within the printing area in the bottom left corner of the card front.
In other respects, the provisions of Chapter III.13 shall apply.
The personalisation imprint shall contain the following information:
the name of the competent authority — see also Letter Aa)
the name of the authority issuing the Registration Certificate (optional)
the unambiguous consecutive number of the document as used within the Member State — see also Letter Aa)
The following data from Chapter II.5; according to Chapter II.7, individual national codes may be added to the preceding harmonised Community codes:
Code | Reference | |
---|---|---|
(A) | registration number (official licence number) | |
(B) | date of first registration of the vehicle | |
(I) | date of the registration to which this certificate refers | |
personal data | ||
(C.1) | holder of the Registration Certificate | |
(C.1.1) | surname or business name | |
(C.1.2) | other name(s) or initial(s) (where appropriate) | |
(C.1.3) | address in the Member State of registration on the date of issue of the document | |
(C.4) | Where the particulars specified in Chapter II.6, code C.2 are not included in the imprint of the Registration Certificate defined in the Letters A and B, reference to the fact that the holder of the Registration Certificate (a) is the vehicle owner; (b) is not the vehicle owner; (c) is not identified as the vehicle owner in the Registration Certificate; |
The back shall bear at least the remaining data specified in Chapter II.5; in accordance with Chapter II.7, individual national codes may be added to the preceding harmonised Community codes.
In detail, these data are:
Code | Reference | |
---|---|---|
Vehicle Data (in consideration of the notes in Chapter II.5) | ||
(D.1) | make | |
(D.2) | type (variant/version, where appropriate) | |
(D.3) | commercial description(s) | |
(E) | vehicle identification number | |
(F.1) | max. technically permissible laden mass, except for motorcycles (kg) | |
(G) | mass of the vehicle in service with bodywork, and with coupling device in the case of a towing vehicle in service from any category other than M1 (kg) | |
(H) | period of validity, if not unlimited | |
(K) | type-approval number (if available) | |
(P.1) | displacement (cm 3 ) | |
(P.2) | nominal power (kW) | |
(P.3) | type of fuel or power source | |
(Q) | power/weight ratio (in kW/kg) (only for motorcycles) | |
(S.1) | number of seats, including driver's seat | |
(S.2) | number of standing places (where appropriate) |
Optionally, additional data from II.6 (with the harmonised codes) and II.7 may be added on the back of the card.
The threats to the physical security of documents are:
Production of false cards: creating a new object which bears great resemblance to the document, either by making it from scratch or by copying an original document.
Material alteration: changing a property of an original document, e.g. modifying some of the data printed on the document.
The material used for Part I of the Registration Certificate shall be made secure against forgery by using at least three of the following techniques:
microprinting,
guilloche printing*,
iridescent printing,
laser engraving,
ultraviolet fluorescent ink,
inks with viewing angle — dependent colour*,
inks with temperature — dependent colour*,
custom holograms*,
variable laser images,
optical variable images.
Member States are free to introduce additional security features.
As a basis, the techniques indicated with an asterisk are to be preferred as they enable the law enforcement officers to check the validity of the card without any special means.
Preceded by the harmonised common codes (where appropriate, in connection with the individual codes of the Member States according to Chapter II.7), the following data shall or may be additionally stored on the card surface bearing the legible information as per Chapter III.1:
Data as per Chapters II.4 and II.5
All data specified in Chapters II.4 and II.5 shall be mandatorily stored on the card.
Other data as per Chapter II.6
Moreover, the Member States are free to store more data as per Chapter II.6, to the necessary extent.
Other data as per Chapter II.7
Optionally, additional information may be stored on the card.
The data from the letters A and B is stored in two corresponding files with transparent structure (see ISO/IEC 7816-4). The Member States may specify the storage of data from Letter C according to their requirements.
There are no read restrictions on these files.
Write access to these files shall be restricted to the national competent authorities (and their authorised agencies) in the Member State issuing the smart card.
Write access is permitted only after an asymmetric authentication with session key exchange for protecting the session between the vehicle registration card and a security module (e.g. a security module card) of the national competent authorities (or their authorised agencies). Thereby card verifiable certificates according to ISO/IEC 7816-8 are exchanged before the authentication process. The card verifiable certificates contain the corresponding public keys to be retrieved and to be used in the following authentication process. These certificates are signed by the national competent authorities and contain an authorisation object (certificate holder authorisation) according to ISO/IEC 7816-9 in order to encode role specific authorisation to the card. This role authorisation is related to the national competent authority (e.g. to update a data field).
The corresponding public keys of the national competent authority are stored as trust anchor (root public key) in the card.
The specification of the files and commands needed for the authentication process and the writing process is under the responsibility of the Member States. The security assurance has to be approved by common criteria evaluation according to EAL4+. The augmentations are as follows: 1. AVA_MSU.3 Analysis and testing for insecure states; 2. AVA_VLA.4 Highly resistant.
Verification data for authenticity of registration data
The issuing authority calculates its electronic signature about the complete data of a file containing the data of the letter A or B and stores it in a related file. These signatures allow the authenticity of the stored data to be verified. The cards shall store the following data:
electronic signature of registration data related to letter A,
electronic signature of registration data related to letter B,
For verification of these electronic signatures the card shall store:
certificates of the issuing authority calculating the signatures about the data of letters A, B.
Electronic signatures and the certificates shall be readable without restriction. Write access to electronic signatures and certificates shall be restricted to the national competent authorities.
External contacts should be used for interfacing. A combination of external contacts with a transponder is optional.
The card shall have sufficient capacity to store the data mentioned in Chapter III.2.
The chip card and reading devices used shall comply with the following standards:
:
Standards for identification cards (plastic cards): Physical characteristics
:
Physical characteristics of chip cards, dimensions and location of contacts
:
Electrical characteristics of contacts, transmission protocols
:
Communication contents, chip card data structure, safety architecture, access mechanisms
:
Structure of application identifiers, selection and execution of application identifiers, registration procedure for application identifiers (numbering system)
:
Inter-industry data elements for interchange
:
Integrated circuit(s) cards with contacts — Security related inter-industry commands
:
Integrated circuit(s) cards with contacts — Enhanced inter-industry commands
The format shall be ID-1 (normal size, see ISO/IEC 7810).
The card shall support transmission protocol T=1 in compliance with ISO/IEC 7816-3. Additionally other transmission protocols may be supported, e.g. T=0, USB or contactless protocols.
For bit transmission the ‘ direct convention ’ shall be applied (see ISO/IEC 7816-3).
Supply voltage, programming voltage
The card shall work with Vcc = 3V (+/0.3V) or with Vcc = 5V (+/0,5V). The card shall not require a programming voltage at pin C6.
Answer to reset
The Information Field Size Card byte shall be presented at the ATR in character TA3. This value shall be at least ‘ 80h ’ (=128 bytes).
Protocol parameter selection
The support of Protocol parameter selection (PPS) according to ISO/IEC 7816-3 is mandatory. It is used for selecting T=1, if T=0 is additionally present in the card, and to negotiate the Fi/Di parameters for achieving higher transmission rates.
Transmission protocol T = 1
The support of chaining is mandatory.
The following simplifications are allowed:
NAD Byte: not used (NAD should be set to ‘ 00 ’ ),
S-Block ABORT: not used,
S-Block VPP state error: not used.
The information field size device (IFSD) shall be indicated from the IFD immediately after ATR, i.e. the IFD shall transmit the S-Block IFS Request after ATR and the card shall send back S-Block IFS. The recommended value for IFSD is 254 bytes.
The registration certificate in smart card format shall properly function under all climatic conditions usually prevailing in the territories of the community and at least in the temperature range specified in ISO 7810. The cards shall be capable of operating correctly in the humidity range 10 % to 90 %.
If used in accordance with the environmental and electricity-related specifications, the card must function properly for a period of ten years. The material of the card must be chosen in such a way that this lifetime is ensured.
During operation, the cards shall conform to Commission Directive 95/54/EC of 31 October 1995 (15) , related to electromagnetic compatibility, and shall be protected against electrostatic discharges.
Table 1 lists the mandatory elementary files (EF) of the application DF (see ISO/IEC 7816-4) DF.Registration. All these files have a transparent structure. The access requirements are described in Chapter III.2. The file sizes are specified by the Member States according their requirements.
Filename | File Identifier | Description |
---|---|---|
EF.Registration_A | ‘ D001 ’ | Registration data according to the Chapters II.4 and II.5 |
EF.Signature_A | ‘ E001 ’ | Electronic Signature about complete data content of EF.Registration_A |
EF.C.IA_A.DS | ‘ C001 ’ | X.509v3 Certificate of the issuing authority calculating the signatures for EF.Signature_A |
EF.Registration_B | ‘ D011 ’ | Registration data according Chapter II.6 |
EF.Signature_B | ‘ E011 ’ | Electronic Signature about complete data content of EF.Registration_B |
EF.C.IA_B.DS | ‘ C011 ’ | X.509v3 Certificate of the issuing authority calculating the signatures for EF.Signature_B |
The stored certificates are in the X.509v3 format according ISO/IEC 9594-8. The electronic signatures are stored transparently.
The registration data is stored as BER-TLV data objects (see ISO/IEC 7816-4) in the corresponding elementary files. The value fields are coded as ASCII character as defined by ISO/IEC 8824-1, the values ‘ C0 ’ - ‘ FF ’ are defined by ISO/IEC 8859-1 (Latin1 character set), ISO/IEC 8859-7 (Greek character set) or ISO/IEC 8859-5 (Cyrillic character set). The format of dates is YYYYMMDD.
Table 2 lists the Tags identifying the data objects corresponding to the registration data of the Chapters II.4 and II.5 together with additional data from Chapter III.1. Unless otherwise stated, the data objects listed in Table 2 are mandatory. Optional data objects may be omitted. The column of the Tag indicates the level of nesting.
Tag | Description | |||
---|---|---|---|---|
‘ 78 ’ | Compatible tag allocation authority, nesting object ‘ 4F ’ (see ISO/IEC 7816-4 and ISO/IEC 7816-6) | |||
‘ 4F ’ | Application identifier (see ISO/IEC 7816-4) | |||
‘ 71 ’ | Inter-industry template (see ISO/IEC 7816-4 and ISO/IEC 7816-6) corresponding to mandatory data of the registration certificate Part 1, nesting all following objects | |||
‘ 80 ’ | Version of Tag definition | |||
‘ 9F33 ’ | Name of the Member State issuing the registration certificate Part 1 | |||
‘ 9F34 ’ | Another (e.g. previous national) designation of the equivalent document (optional) | |||
‘ 9F35 ’ | Name of the competent authority | |||
‘ 9F36 ’ | Name of the authority issuing the registration certificate (optional) | |||
‘ 9F37 ’ | Character set used: ‘00’ : ISO/IEC 8859-1 (Latin1 character set) ‘01’ : ISO/IEC 8859-5 (Cyrillic character set) ‘02’ : ISO/IEC 8859-7 (Greek character set) | |||
‘ 9F38 ’ | Unambiguous consecutive number of the document as used within the Member State | |||
‘ 81 ’ | Registration number | |||
‘ 82 ’ | Date of first registration | |||
‘ A1 ’ | Personal data, nesting objects ‘ A2 ’ and ‘ 86 ’ | |||
‘ A2 ’ | Holder of the registration certificate, nesting objects ‘ 83 ’ , ‘ 84 ’ and ‘ 85 ’ | |||
‘ 83 ’ | Surname or business name | |||
‘ 84 ’ | Other names or initials (optional) | |||
‘ 85 ’ | Address in the Member State | |||
‘ 86 ’ | ‘00’ : is the vehicle owner ‘01’ : is not the vehicle owner ‘02’ : is not identified as the vehicle owner | |||
‘ A3 ’ | Vehicle, nesting objects ‘ 87 ’ , ‘ 88 ’ and ‘ 89 ’ | |||
‘ 87 ’ | Vehicle make | |||
‘ 88 ’ | Vehicle type | |||
‘ 89 ’ | Vehicle commercial descriptions | |||
‘ 8A ’ | Vehicle identification number | |||
‘ A4 ’ | Mass nesting ‘ 8B ’ | |||
‘ 8B ’ | Mass maximum technically permissible laden mass | |||
‘ 8C ’ | Mass of the vehicle in service with bodywork | |||
‘ 8D ’ | Period of validity | |||
‘ 8E ’ | Date of the registration to which this certificate refers | |||
‘ 8F ’ | Type approval number | |||
‘ A5 ’ | Engine, nesting objects ‘ 90 ’ , ‘ 91 ’ , and ‘ 92 ’ | |||
‘ 90 ’ | Engine capacity | |||
‘ 91 ’ | Engine maximum net power | |||
‘ 92 ’ | Engine type of fuel | |||
‘ 93 ’ | Power weight ratio | |||
‘ A6 ’ | Seating capacity nesting objects ‘ 94 ’ and ‘ 95 ’ | |||
‘ 94 ’ | Number of seats | |||
‘ 95 ’ | Number of standing places |
Table 3 lists the Tags identifying the data objects corresponding to the registration data of Chapter II.6. The data objects listed in Table 3 are optional.
Tag | Description | |||
---|---|---|---|---|
‘ 78 ’ | Compatible tag allocation authority, nesting object ‘ 4F ’ (see ISO/IEC 7816-4 and ISO/IEC 7816-6) | |||
‘ 4F ’ | Application Identifier (see ISO/IEC 7816-4) | |||
‘ 72 ’ | Inter-industry template (see ISO/IEC 7816-4 and ISO/IEC 7816-6) corresponding to optional data of the registration certificate Part 1, Chapter II.6, nesting all following objects | |||
‘ 80 ’ | Version of Tag definition | |||
‘ A1 ’ | Personal data nesting objects ‘ A7 ’ , ‘ A8 ’ and ‘ A9 ’ | |||
‘ A7 ’ | Vehicle owner, nesting objects ‘ 83 ’ , ‘ 84 ’ and ‘ 85 ’ | |||
.. | ||||
‘ A8 ’ | Second vehicle owner, nesting objects ‘ 83 ’ , ‘ 84 ’ and ‘ 85 ’ | |||
.. | ||||
‘ A9 ’ | Person who may use the vehicle by virtue of legal right other than ownership nesting objects ‘ 83 ’ , ‘ 84 ’ , and ‘ 85 ’ | |||
.. | ||||
‘ A4 ’ | Mass, nesting ‘ 96 ’ and ‘ 97 ’ | |||
‘ 96 ’ | Maximum permissible laden mass of the vehicle in service | |||
‘ 97 ’ | Maximum permissible laden mass of the whole vehicle in service | |||
‘ 98 ’ | Vehicle category | |||
‘ 99 ’ | Number of axles | |||
‘ 9A ’ | Wheelbase | |||
‘ AD ’ | Distribution of the maximum permissible laden mass among the axles, nesting objects ‘ 9F1F ’ , ‘ 9F20 ’ , ‘ 9F21 ’ , ‘ 9F22 ’ and ‘ 9F23 ’ | |||
‘ 9F1F ’ | Axle 1 | |||
‘ 9F20 ’ | Axle 2 | |||
‘ 9F21 ’ | Axle 3 | |||
‘ 9F22 ’ | Axle 4 | |||
‘ 9F23 ’ | Axle 5 | |||
‘ AE ’ | Technically permissible maximum towable mass of the trailer, nesting objects ‘ 9B ’ and ‘ 9C ’ | |||
‘ 9B ’ | Braked | |||
‘ 9C ’ | Unbraked | |||
‘ A5 ’ | Engine, nesting objects ‘ 9D ’ and ‘ 9E ’ | |||
‘ 9D ’ | Rated speed | |||
‘ 9E ’ | Engine identification number | |||
‘ 9F24 ’ | Colour of the vehicle | |||
‘ 9F25 ’ | Maximum speed | |||
‘ AF ’ | Sound level, nesting objects ‘ DF26 ’ , ‘ DF27 ’ and ‘ DF28 ’ | |||
‘ 9F26 ’ | Stationary | |||
‘ 9F27 ’ | Engine speed | |||
‘ 9F28 ’ | Drive by | |||
‘ B0 ’ | Exhaust emissions, nesting objects ‘ 9F29 ’ , ‘ 9F2A ’ , ‘ 9F2B ’ , ‘ 9F2C ’ , ‘ 9F2D ’ , ‘ 9F2E ’ , ‘ 9F2F ’ , ‘ 9F30 ’ and ‘ 9F31 ’ | |||
‘ 9F29 ’ | CO | |||
‘ 9F2A ’ | HC | |||
‘ 9F2B ’ | NO X | |||
‘ 9F2C ’ | HC+NO X | |||
‘ 9F2D ’ | Particulates of diesel | |||
‘ 9F2E ’ | Corrected absorption coefficient for diesel | |||
‘ 9F2F ’ | CO 2 | |||
‘ 9F30 ’ | Combined fuel consumption | |||
‘ 9F31 ’ | Indication of the environmental category of EC type-approval | |||
‘ 9F32 ’ | Fuel tanks capacity |
Structure and format of the data according Chapter II.7 are specified by the Member States.
The application ‘ Vehicle Registration ’ shall be selectable by a SELECT DF (by name, see ISO/IEC 7816-4) with its application identifier (AID). The AID value is requested from a laboratory selected by the European Commission.
The files corresponding to Chapter II, Letters A, B and D, shall be selectable by SELECT (see ISO/IEC 7816-4) with the command parameters P1 set to ‘ 02 ’ , P2 set to ‘ 04 ’ and the command data field containing the file identifier (see Chapter X, Table 1). The returned FCP template contains the file size which can be useful for reading these files.
These files shall be readable with READ BINARY (see ISO/IEC 7816-4) with an absent command data field and L e set to the length of the expected data, using a short L e .
To verify the authenticity of the stored registration data, the corresponding electronic signature may be verified. This means that besides the registration data also the corresponding electronic signature may be read from the registration card.
The public key for signature verification can be retrieved by reading the corresponding issuing authority certificate from the registration card. Certificates contain the public key and the identity of the corresponding authority. The signature verification may be performed by another system than the registration card.
The Member States are free to retrieve the public keys and certificates for verifying the issuing authority certificate.
Irrespective of the other provisions herein, the Member States, after notifying the European Commission, may add colours, marks or symbols. In addition, for certain data of Chapter III.2 Letter C, the Member States may allow XML format and may allow access via TCP/IP.
Member States may, with the agreement of the European Commission, add other applications for which no harmonised rules or documents exist yet at EU level (e.g. roadworthiness certificate), on the vehicle registration card to realise additional vehicle related services.
graphics,
watermark,
fluorescent fibres, or
fluorescent imprints.
Member States are free to introduce additional security features.
the name of the Member State issuing Part II of the registration certificate,
[F4the distinguishing mark of the Member State issuing Part II of the registration certificate, namely:
:
Belgium
:
Czech Republic
:
Denmark
:
Germany
:
Estonia
:
Greece
:
Spain
:
France
:
Ireland
:
Italy
:
Cyprus
:
Latvia
:
Lithuania
:
Luxembourg
:
Hungary
:
Malta
:
Netherlands
:
Austria
:
Poland
:
Portugal
:
Slovenia
:
Slovakia
:
Finland
:
Sweden
:
United Kingdom,]
the name of the competent authority,
the words ‘ Part II of the Registration Certificate ’ , printed in large type in the language or languages of the Member States issuing the registration certificate; they shall also appear, after a suitable space, in small type, in the other languages of the European Community,
the words ‘ European Community ’ , printed in the language or languages of the Member State issuing Part II of the registration certificate,
the number of the document.
registration number
date of the first registration of the vehicle
vehicle:
make,
type,
variant (if available)
version (if available)
commercial description(s)
vehicle identification number
type-approval number (if available)
personal data
owner of the vehicle,
surname(s) or business name,
other name(s) or initial(s) (where appropriate),
address in the Member State of registration, on the date of issue of the document,
natural or legal person who may use the vehicle by virtue of a legal right other than that of ownership,
surname(s) or business name,
other name(s) or initial(s) (where appropriate),
address in the Member State of registration, on the date of issue of the document
where a change in the personal data given in point II.6, code C.2 and/or point II.6, code C.3 does not give rise to the issue of a new Part II of the Registration Certificate, the new personal data corresponding to these points may be included under codes (C.5) or (C.6); they are broken down in accordance with point II.6, code C.2 and point II.6, code C.3.
vehicle category.
Being a microprocessor card, the chip card shall be designed in accordance with the standards mentioned in Chapter III.5.
Printed on the front and back of the card shall be at least the data specified in Chapters II.4 and II.5; these data shall be legible with the eye (minimum character height: 6 points) and printed on as follows. (Examples of possible lay-outs are presented in Figure 2 at the end of this section)
The basic data shall contain the following:
To the right of the chip location:
in the language(s) of the Member State issuing the Registration Certificate
the words ‘ European Community ’ ,
the name of the Member State issuing the Registration Certificate,
the words ‘ Part II of the Registration Certificate ’ printed in large type,
another (e.g. previous national) designation of the equivalent document (optional),
the name of the competent authority (alternatively, also in the form of a personalisation imprint as per Letter B),
the unambiguous consecutive number of the document as used within the Member State (alternatively, also in the form of a personalisation imprint as per Letter B).
Above the chip location:
the distinguishing mark of the Member State issuing the Registration Certificate, white in a blue rectangle and surrounded by twelve yellow stars:
Belgium
Bulgaria]
Denmark
Germany
Greece
Spain
France
Croatia]
Ireland
Italy
Luxembourg
The Netherlands
Austria
Portugal
Romania]
Finland
Sweden
United Kingdom
Member States might consider adding, at the lower edge in small type and in their national language(s), the note: ‘ This document should be kept in a safe place outside the vehicle. ’
The basic colour of the card is red (Pantone 194); alternatively, a red-to-white transition is possible.
A symbol representing a wheel (see proposed lay-out) shall be printed within the printing area in the bottom left corner of the card front.
In other respects, the provisions of Chapter III.13 shall apply.
The personalisation imprint shall contain the following information:
the name of the competent authority — see also Letter Aa).
the name of the authority issuing the Registration Certificate (optional).
the unambiguous consecutive number of the document as used within the Member State — see also Letter Aa).
The following data from Chapter II.5; according to Chapter II.7, individual national codes may be added to the preceding harmonised Community codes.
Code | Reference |
---|---|
A | registration number (official licence number) |
B | date of first registration of the vehicle |
The back shall bear at least the remaining data specified in Chapter II.5; according to Chapter II.7, individual national codes may be added to the preceding harmonised community codes.
In detail, these data are:
Code | Reference |
---|---|
Vehicle data (in consideration of the notes in Chapter II.5) | |
D.1 | make |
D.2 | type (variant/version, where appropriate) |
D.3 | commercial description(s) |
E | vehicle identification number |
K | type-approval number (if available) |
Optionally, additional data from II.6 (with the harmonised codes) and II.7 may be added on the back of the card.
The threats to the physical security of documents are:
Production of false cards: creating a new object which bears great resemblance to the document, either by making it from scratch or by copying an original document.
Material alteration: changing a property of an original document, e.g. modifying some of the data printed on the document.
The material used for Part II of the registration certificate shall be made secure against forgery by using at least three of the following techniques:
microprinting,
guilloche printing*,
iridescent printing,
laser engraving,
ultraviolet fluorescent ink,
inks with viewing angle — dependent colour*,
inks with temperature — dependent colour*,
custom holograms*,
variable laser images,
optical variable images.
Member States are free to introduce additional security features.
As a basis, the techniques indicated with an asterisk are to be preferred as they enable the law enforcement officers to check the validity of the card without any special means.
Preceded by the harmonised common codes (where appropriate, in connection with the individual codes of the Member States according to Chapter II.7), the following data shall or may be additionally stored on the card surface bearing the legible information as per Chapter III.1:
Data as per Chapters II.4 and II.5
All data specified in Chapters II.4 and II.5 shall be mandatorily stored on the card.
Other data as per Chapter II.6
Moreover, the Member States are free to store more data as per Chapter II.6, to the necessary extent.
Other data as per Chapter II.7
Optionally, further vehicle-related data of general interest may be stored on the card.
The data from the Letters A and B is stored in two corresponding files with transparent structure (see ISO/IEC 7816-4). The Member States may specify the storage of data from Letter C according their requirements.
There are no read restrictions on these files.
Write access to these files shall be restricted to the national competent authorities (and their authorised Agencies) in the Member State issuing the smart card.
Write access is permitted only after an asymmetric authentication with session key exchange for protecting the session between the vehicle registration card and a Security Module (e.g. a Security Module Card) of the national competent authorities (or their authorised Agencies). Thereby Card Verifiable certificates according to ISO/IEC 7816-8 are exchanged before the authentication process. The Card Verifiable certificates contain the corresponding public keys to be retrieved and to be used in the following authentication process. These certificates are signed by the national competent authorities and contain an authorisation object (certificate holder authorisation) according to ISO/IEC 7816-9 in order to encode role specific authorisation to the card. This role authorisation is related to the national competent authority (e.g. to update a data field).
The corresponding public keys of the national competent authority are stored as trust anchor (root public key) in the card.
The specification of the files and commands needed for the authentication process and the writing process is under responsibility of the Member States. The security assurance has to be approved by Common Criteria Evaluation according to EAL4+. The augmentations are as follows: 1. AVA_MSU.3 Analysis and testing for insecure states; 2. AVA_VLA.4 Highly resistant.
Verification data for authenticity of registration data
The issuing authority calculates its electronic signature about the complete data of a file containing the data of the Letter A or B and stores it in a related file. These signatures allow the authenticity of the stored data to be verified. The cards shall store the following data:
electronic signature of registration data related to Letter A,
electronic signature of registration data related to Letter B.
For verification of these electronic signatures the card shall store:
certificates of the issuing authority calculating the signatures about the data of Letters A, B.
Electronic signatures and the certificates shall be readable without restriction. Write access to electronic signatures and certificates shall be restricted to the national competent authorities.
External contacts should be used for interfacing. A combination of external contacts with a transponder is optional.
The card shall have sufficient capacity to store the data mentioned in Chapter III.2.
The chip card and reading devices used shall comply with the following standards:
:
Standards for identification cards (plastic cards): Physical characteristics,
:
Physical characteristics of chip cards, dimensions and location of contacts,
:
Electrical characteristics of contacts, transmission protocols,
:
Communication contents, chip card data structure, safety architecture, access mechanisms,
:
Structure of application identifiers, selection and execution of application identifiers, registration procedure for application identifiers (numbering system),
:
Inter-industry data elements for interchange,
:
Integrated circuit(s) cards with contacts — Security related inter-industry commands,
:
Integrated circuit(s) cards with contacts — Enhanced inter-industry commands,
The format shall be ID-1 (normal size, see ISO/IEC 7810).
The card shall support transmission protocol T = 1 in compliance with ISO/IEC 7816-3. Additionally other transmission protocols may be supported, e.g. T=0, USB or contactless protocols. For bit transmission the ‘ direct convention ’ shall be applied (see ISO/IEC 7816-3).
The card shall work with Vcc = 3V (+/0.3V) or with Vcc = 5V (+/0.5V). The card shall not require a programming voltage at pin C6.
The Information Field Size Card byte shall be presented at the ATR in character TA3. This value shall be at least ‘ 80h ’ (=128 bytes).
The support of protocol parameter selection (PPS) according to ISO/IEC 7816-3 is mandatory. It is used for selecting T=1, if T=0 is additionally present in the card, and to negotiate the Fi/Di parameters for achieving higher transmission rates.
The support of chaining is mandatory.
The following simplifications are allowed:
NAD Byte: not used (NAD should be set to ‘ 00 ’ ),
S-Block ABORT: not used,
S-Block VPP state error: not used.
The information field size device (IFSD) shall be indicated from the IFD immediately after ATR, i.e. the IFD shall transmit the S-block IFS request after ATR and the card shall send back S-block IFS. The recommended value for IFSD is 254 bytes.
The registration certificate in smart card format shall properly function under all climatic conditions usually prevailing in the territories of the community and at least in the temperature range specified in ISO 7810. The cards shall be capable of operating correctly in the humidity range 10 % to 90 %.
If used in accordance with the environmental and electricity-related specifications, the card must function properly for a period of ten years. The material of the card must be chosen in such a way that this lifetime is ensured.
During operation, the cards shall conform to Directive 95/54/EC, related to electromagnetic compatibility, and shall be protected against electrostatic discharges.
Table 1 lists the mandatory elementary files (EF) of the application DF (see ISO/IEC 7816-4) DF.Registration. All these files have a transparent structure. The access requirements are described in Chapter III.2. The file sizes are specified by the Member States according their requirements.
Filename | File Identifier | Description |
---|---|---|
EF.Registration_A | ‘ D001 ’ | Registration data according to the Chapters II.4 and II.5 |
EF.Signature_A | ‘ E001 ’ | Electronic Signature about complete data content of EF.Registration_A |
EF.C.IA_A.DS | ‘ C001 ’ | X.509v3 Certificate of the issuing authority calculating the signatures for EF.Signature_A |
EF.Registration_B | ‘ D011 ’ | Registration data according Chapter II.6 |
EF.Signature_B | ‘ E011 ’ | Electronic Signature about complete data content of EF.Registration_B |
EF.C.IA_B.DS | ‘ C011 ’ | X.509v3 Certificate of the issuing authority calculating the signatures for EF.Signature_B |
The stored certificates are in the X.509v3 format according ISO/IEC 9594-8.
The electronic signatures are stored transparent.
The registration data is stored as BER-TLV data objects (see ISO/IEC 7816-4) in the corresponding elementary files. The value fields are coded as ASCII character as defined by ISO/IEC 8824-1, the values ‘ C0 ’ - ‘ FF ’ are defined by ISO/IEC 8859-1 (Latin1 character set) or ISO/IEC 8859-7 (Greek character set) or ISO/IEC 8859-5 (Cyrillic character set). The format of dates is YYYYMMDD.
Table 2 lists the Tags identifying the data objects corresponding to the registration data of Chapter II.4 and II.5 together with additional data from Chapter III.1. Unless otherwise stated, the data objects listed in Table 2 are mandatory. Optional data objects may be omitted. The column of the Tag indicates the level of nesting.
Tag | Description | |||
---|---|---|---|---|
‘ 78 ’ | Compatible tag allocation authority, nesting object ‘ 4F ’ (see ISO/IEC 7816-4 and ISO/IEC 7816-6) | |||
‘ 4F ’ | Application identifier (see ISO/IEC 7816-4) | |||
‘ 73 ’ | Inter-industry template (see ISO/IEC 7816-4 and ISO/IEC 7816-6) corresponding to mandatory data of the registration certificate Part 2, nesting all following objects | |||
‘ 80 ’ | Version of tag definition | |||
‘ 9F33 ’ | Name of the Member State issuing the registration certificate Part 2 | |||
‘ 9F34 ’ | Another (e.g. previous national) designation of the equivalent document (optional) | |||
‘ 9F35 ’ | Name of the competent authority | |||
‘ 9F36 ’ | Name of the authority issuing the registration certificate (optional) | |||
‘ 9F37 ’ | Character set used: ‘00’ : ISO/IEC 8859-1 (Latin1 character set) ‘01’ : ISO/IEC 8859-5 (Cyrillic character set) ‘02’ : ISO/IEC 8859-7 (Greek character set) | |||
‘ 9F38 ’ | Unambiguous consecutive number of the document as used within the Member State | |||
‘ 81 ’ | Registration number | |||
‘ 82 ’ | Date of first registration | |||
‘ A3 ’ | Vehicle, nesting objects ‘ 87 ’ , ‘ 88 ’ and ‘ 89 ’ | |||
‘ 87 ’ | Vehicle make | |||
‘ 88 ’ | Vehicle type | |||
‘ 89 ’ | Vehicle commercial descriptions | |||
‘ 8A ’ | Vehicle identification number | |||
‘ 8F ’ | Type approval number |
Table 6 lists the Tags identifying the data objects corresponding to the registration data of Chapter II.6. The data objects listed in Table 6 are optional.
Tag | Description | |||
---|---|---|---|---|
‘ 78 ’ | Compatible tag allocation authority, nesting object ‘ 4F ’ (see ISO/IEC 7816-4 and ISO/IEC 7816-6) | |||
‘ 4F ’ | Application identifier (see ISO/IEC 7816-4) | |||
‘ 74 ’ | Inter-industry template (see ISO/IEC 7816-4 and ISO/IEC 7816-6) corresponding to optional data of the registration certificate Part 1, Chapter II.6, nesting all following objects | |||
‘ 80 ’ | Version of tag definition | |||
‘ A1 ’ | Personal data nesting objects ‘ A7 ’ , ‘ A8 ’ and ‘ A9 ’ | |||
‘ A7 ’ | Vehicle owner nesting objects ‘ 83 ’ , ‘ 84 ’ and ‘ 85 ’ | |||
‘ 83 ’ | Surname or business name | |||
‘ 84 ’ | Other names or initials (optional) | |||
‘ 85 ’ | Address in the Member State | |||
‘ A8 ’ | Second vehicle owner nesting objects ‘ 83 ’ , ‘ 84 ’ and ‘ 85 ’ | |||
… | ||||
‘ A9 ’ | Person who may use the vehicle by virtue of legal right other than ownership nesting objects ‘ 83 ’ , ‘ 84 ’ , and ‘ 85 ’ | |||
… | ||||
‘ 98 ’ | Vehicle category |
Structure and format of the data according Chapter II.7 are specified by the Member States.
The Application ‘ Vehicle Registration ’ shall be selectable by a SELECT DF (by name, see ISO/IEC 7816-4) with its Application identifier (AID). The AID value is requested from a laboratory selected by the European Commission.
The files corresponding to Chapter II, letters A, B and D, shall be selectable by SELECT (see ISO/IEC 7816-4) with the command parameters P1 set to ‘ 02 ’ , P2 set to ‘ 04 ’ and the command data field containing the file identifier (see Chapter X, Table 1). The returned FCP template contains the file size which can be useful for reading these files.
These files shall be readable with READ BINARY (see ISO/IEC 7816-4) with an absent command data field and L e set to the length of the expected data, using a short L e .
To verify the authenticity of the stored registration data, the corresponding electronic signature may be verified. This means that besides the registration data also the corresponding electronic signature may be read from the registration card.
The public key for signature verification can be retrieved by reading the corresponding issuing authority certificate from the registration card. Certificates contain the public key and the identity of the corresponding authority. The signature verification may be performed by another system than the registration card.
The Member States are free in retrieving the public keys and certificates for verifying the issuing authority certificate.
Irrespective of the other provisions herein, the Member States, after notifying the European Commission, may add colours, marks or symbols. In addition, for certain data of Chapter III.2 Letter C, the Member States may allow XML format and may allow access via TCP/IP. Member States may, with the agreement of the European Commission, add other applications for which no harmonised rules or documents exist yet at EU level (e.g. roadworthiness certificate), on the vehicle registration card to realise additional vehicle related services.]
Opinion of the European Parliament of 28 May 1998 (OJ C 195, 22.6.1998, p. 21) Council Common Position of 3 November 1998 (OJ C 388, 14.12.1998, p. 12) and Decision of the European Parliament of 25 February 1999 (not yet published in the Official Journal).
OJ L 237, 24.8.1991, p. 1. Directive as last amended by Directive 97/26/EC (OJ L 150, 7.6.1997, p. 41).
OJ L 42, 23.2.1970, p. 1. Directive as last amended by Commission Directive 98/14/EC (OJ L 91, 25.3.1998, p. 1).
OJ L 225, 10.8.1992, p. 72. Directive as amended by the 1994 Act of Accession.
[F2Directive 2007/46/EC of the European Parliament and of the Council of 5 September 2007 establishing a framework for the approval of motor vehicles and their trailers, and of systems, components and separate technical units intended for such vehicles ( OJ L 263, 9.10.2007, p. 1 ).]
[F2Directive 2014/45/EU of the European Parliament and of the Council of 3 April 2014 on periodic roadworthiness tests for motor vehicles and their trailers and repealing Directive 2009/40/EC ( OJ L 127, 29.4.2014, p. 51 ).]
[F2Directive 95/46/EC of the European Parliament and of the Council of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data ( OJ L 281, 23.11.1995, p. 31 ).]
[F2Directive 2002/58/EC of the European Parliament and of the Council of 12 July 2002 concerning the processing of personal data and the protection of privacy in the electronic communications sector ( OJ L 201, 31.7.2002, p. 37 ).]
[F2Directive 2000/53/EC of the European Parliament and of the Council of 18 September 2000 on end-of-life vehicles ( OJ L 269, 21.10.2000, p. 34 ).]
[F3The certificate consisting of one part only will bear the words ‘ Registration Certificate ’ , and there will be no reference in the text to ‘ Part I ’ .]
[F3Council Directive 70/220/EEC of 20 March 1970 on the approximation of the laws of the Member States relating to measures to be taken against air pollution by gases from positive-ignition engines of motor vehicles ( OJ L 76, 6.4.1970, p. 1 ), Directive as last amended by Commission Directive 2002/80/EC ( OJ L 291, 28.10.2002, p. 20 ).]
[F3Council Directive 88/77/EEC of 3 December 1987 on the approximation of the laws of the Member States relating to the measures to be taken against the emission of gaseous pollutants from diesel engines for use in vehicles ( OJ L 36, 9.2.1988, p. 33 ). Directive as last amended by Commission Directive 2001/27/EC ( OJ L 107, 18.4.2001, p. 10 ).]
[F3Commission Directive 95/54/EC of 31 October 1995 adapting to technical progress Council Directive 72/245/EEC on the approximation of the laws of the Member States relating to the suppression of radio interference produced by spark-ignition engines fitted to motor vehicles and amending Directive 70/156/EEC on the approximation of the laws of the Member States relating to the type-approval of motor vehicles and their trailers (OJ L 266, 8.11.1995 p. 1).]
[F3This Annex is concerned only with Registration Certificates consisting of Parts I and II.]
Latest Available (revised):The latest available updated version of the legislation incorporating changes made by subsequent legislation and applied by our editorial team. Changes we have not yet applied to the text, can be found in the ‘Changes to Legislation’ area.
Original (As adopted by EU): The original version of the legislation as it stood when it was first adopted in the EU. No changes have been applied to the text.
Geographical Extent: Indicates the geographical area that this provision applies to. For further information see ‘Frequently Asked Questions’.
Show Timeline of Changes: See how this legislation has or could change over time. Turning this feature on will show extra navigation options to go to these specific points in time. Return to the latest available version by using the controls above in the What Version box.
Access essential accompanying documents and information for this legislation item from this tab. Dependent on the legislation item being viewed this may include:
This timeline shows the different versions taken from EUR-Lex before exit day and during the implementation period as well as any subsequent versions created after the implementation period as a result of changes made by UK legislation.
The dates for the EU versions are taken from the document dates on EUR-Lex and may not always coincide with when the changes came into force for the document.
For any versions created after the implementation period as a result of changes made by UK legislation the date will coincide with the earliest date on which the change (e.g an insertion, a repeal or a substitution) that was applied came into force. For further information see our guide to revised legislation on Understanding Legislation.
Use this menu to access essential accompanying documents and information for this legislation item. Dependent on the legislation item being viewed this may include:
Click 'View More' or select 'More Resources' tab for additional information including: