1.   From the start of operations of the Entry/Exit System until the start of operations of the Visa Information System, carriers shall send a query to verify whether in the case of a single-entry visa or a double-entry visa the number of entries authorised by a visa has already been used as referred to in Article 13 of Regulation (EU) 2017/2226 (‘verification query’) through the carrier interface.

2.   From the start of operations of the Visa Information System, carriers shall launch a query through the carrier interface, to verify whether:

3.   From the start of operations of the Visa Information System, carriers shall launch the verification query for the long-stay visa or the residence permit for those long-stay visas and residence permits issued after the start of operations of the Visa Information System. Carriers shall manually check long-stay visas and residence permits issued prior to the start of operations of the Visa Information System.

4.   The verification query shall be sent at the earliest 48 hours prior to the scheduled time of departure.

5.   Carriers shall ensure that only duly authorised staff have access to the carrier interface. The carriers shall put in place at least the following mechanisms:

1.   Carriers shall connect to the carrier interface through one of the following:

2.   Carriers shall access the carrier interface through one of the following:

1.   In order to send a verification query, the carrier shall provide the following traveller data:

The carrier may also provide the number of the short-stay visa, the long-stay visa or the residence permit.

2.   From the start of operations of the Entry/Exit System, where the destination cannot be reached with a single-entry visa, the carrier shall provide information that the itinerary includes two entries into the Member States when submitting the verification query.

From the start of operations of the Visa Information System, where the destination cannot be reached with a single-entry visa, the carrier shall provide information that the itinerary includes two or more entries into the Member States when submitting the verification query.

3.   For the purposes of providing the information referred to in paragraph 1, points (a) to (d), carriers shall be allowed to scan the machine-readable zone of the travel document.

4.   From the start of operations of the Entry/Exit System until the start of operations of the Visa Information System, where the passenger is exempt from the scope of Regulation (EU) 2017/2226 in accordance with Article 2 of that Regulation or is in airport transit, the carrier shall be able to specify it in the verification query.

From the start of operations of the Visa Information System, the carrier shall be able to specify in the verification query, where:

5.   Carriers shall be able to send a verification query for one or more passengers. The carrier interface shall include the reply referred to in Article 6 for each passenger included in the query.

1.   From the start of operations of the Entry/Exit System until the start of operations of the Visa Information System, where the passenger is exempt from the scope of Regulation (EU) 2017/2226 in accordance with Article 2 of that Regulation, is in airport transit or is a holder of a national short-stay visa in the meaning of Article 3(1), point 10 of that Regulation, the reply shall be ‘Not applicable’. In all other cases, the reply shall be ‘OK’ or ‘Not OK’.

2.   From the start of operations of the Visa Information System:

Where a verification query returns a ‘Not OK’ reply, the carrier interface shall specify that the reply is coming from the Entry/Exit System or the Visa Information System.

3.   From the start of operations of the Entry/Exit System until the start of operations of the Visa Information System, replies to verification queries shall be determined in accordance with the following rules:

4.   From the start of operations of the Visa Information System, replies to verification queries in the case that the carrier indicates the Member State of transit in accordance with Article 5(1)(f), point (5), shall be determined in accordance with the following rules:

5.   From the start of operations of the Visa Information System, replies to verification queries in the case that the carrier indicates the Member State of destination in accordance with Article 5(1)(f)(1)-(4), shall be determined in accordance with the following rules:

6.   Where the traveller is visa exempt or the traveller falls within the scope of Regulation (EU) 2018/1240, the provisions defined in the Commission Implementing Regulation C(2022) 4550 (18) applies.

1.   Data on issued, annulled and revoked short stay visas, long-stay visas, airport transit visas, residence permits, and travel authorisations shall be automatically extracted from the Visa Information System, the European Travel Information and Authorisation System and the Entry/Exit System at least daily and transmitted to the read-only database.

2.   All extractions of data into the read-only database pursuant to paragraph 1 shall be logged.

3.   eu-LISA shall be responsible for the security of the web service and of the personal data it contains, and for the process of extracting and transmitting the data referred to in paragraph 1 to the read-only database. The technical implementation details shall be derived from the security plan, following the risk assessment process.

4.   It shall not be possible to transmit data from the read-only database to the Entry/Exit System or the Visa Information System.

1.   eu-LISA shall develop an authentication scheme, taking into account information on security risk management and the principles of data protection by design and default and access control principles, including accountability, and allowing to trace the initiator of the verification query.

2.   The details of the authentication scheme shall be set out in the technical guidelines.

3.   The authentication scheme shall be tested in accordance with Article 12.

4.   Where carriers access the carrier interface using the Application Programming Interface referred to in Article 4(2), point (a), the authentication scheme shall be implemented by means of mutual authentication.

1.   Carriers referred to in Article 13(3) of Regulation (EU) 2017/2226 and Article 45c(1) of Regulation (EC) No 767/2008 operating and transporting passengers into the territory of the Member States shall be required to register prior to gaining access to the authentication scheme.

2.   eu-LISA shall make available a registration form on a public website to be completed on-line. Submission of the registration form shall only be possible where all the fields have been correctly completed.

3.   The registration form shall include fields requiring carriers to provide the following information:

4.   The registration form shall inform the carriers of the minimum security requirements. The carriers shall ensure compliance with the following objectives:

5.   The registration form shall require carriers to declare:

6.   The registration form shall require carriers to attach an electronic copy of their instruments of constitution, including, where applicable statutes, as well as an electronic copy of an extract of their official company registration from either at least one Member State, where applicable, or from a third country in, or officially translated into, one of the official Union or Icelandic or Norwegian. An electronic copy of an authorisation to operate in one or more Member States, such as an Air Operator Certificate, can substitute the official company registration.

7.   The registration form shall notify carriers:

8.   Where the registration form has been submitted correctly, eu-LISA shall register the carrier and notify the carrier that it has been registered. Where the registration form has not been submitted correctly, eu-LISA shall refuse registration and notify the carrier of the reasons.

eu-LISA shall maintain an up-to-date register of registered carriers. Personal data contained in the registration of carriers shall be deleted at the latest one year after the carrier has been deregistered.

1.   Where a carrier informs eu-LISA that it no longer operates or transports passengers into the territory of the Member States, eu-LISA shall deregister the carrier.

2.   Where the logs show that the carrier has not used the carrier interface during a period of one year, it shall be automatically deregistered.

3.   Where a carrier no longer fulfils the conditions referred to in Article 10(5), or has otherwise breached the provisions of this Regulation, the security requirements referred to in Article 10(4) or the technical guidelines, including in case of abuse of the carrier interface, eu-LISA may deregister the carrier.

4.   eu-LISA shall inform the carrier of its intention to deregister the carrier pursuant to paragraphs 1, 2 or 3, together with the reason for the deregistration, one month before deregistration. Before deregistration, eu-LISA shall give the carrier the opportunity to provide written comments.

5.   In case of urgent IT security concerns, including where the carrier is not complying with the security requirements referred to in Article 10(4) or with the technical guidelines, eu-LISA may immediately disconnect a carrier. eu-LISA shall inform the carrier of the disconnection, together with the reason for the disconnection.

6.   To the extent appropriate, eu-LISA shall assist carriers that have received a notice of deregistration or disconnection to remedy the deficiencies that gave rise to the notice and, where possible, for a limited time and under strict conditions, provide the opportunity for disconnected carriers to send verification queries by other means than those referred to in Article 4.

7.   Disconnected carriers may again be connected to the carrier interface following successful removal of the security concerns that gave rise to the disconnection. Deregistered carriers may submit a new request for registration.

8.   At any time following the registration of carriers pursuant to Article 10, eu-LISA may, in particular where there is reasoned suspicion that one or more carriers are abusing the carrier interface or do not fulfil the conditions referred to in Article 10(4), make inquiries with Member States or third countries.

9.   Where the registration form referred to in Article 10(2) is not available for a prolonged period of time, eu-LISA shall ensure that registration in accordance with that Article is possible via other means.

1.   eu-LISA shall make the technical guidelines available to carriers in order to enable them to develop and test the carrier interface.

2.   Where carriers choose to connect through the Application Programming Interface referred to in Article 4(2), point (a), the implementation of the message format referred to in Article 7 and of the authentication scheme referred to in Article 9 shall be tested.

3.   Where carriers choose to connect through the web interface (browser) or application for mobile devices referred to in Article 4(2), points (b) and (c) respectively, they shall notify eu-LISA that they have successfully tested their connection to the carrier interface and that their duly authorised staff has been successfully trained in using the carrier interface.

4.   For the purpose of paragraph 2, eu-LISA shall develop and make available a testing plan, a test environment and a simulator allowing eu-LISA and carriers to test the carriers’ connection to the carrier interface. For the purpose of paragraph 3, eu-LISA shall develop and make available a test environment allowing carriers to train their staff.

5.   Upon successful completion of the registration procedure referred to in Article 10 as well as the successful completion of the testing referred to in paragraph 2 or reception of the notification referred to in paragraph 3, eu-LISA shall connect the carrier to the carrier interface.

1.   Where it is technically impossible to send a verification query because a component of the Entry/Exit System or a component of the Visa Information System failed, the following shall apply:

2.   Where it is technically impossible to send a verification query for other reasons than a failure of any component of the Entry/Exit System or the Visa Information System, the carrier shall notify the ETIAS Central Unit through the means referred to in Article 14.

3.   The carrier shall inform the ETIAS Central Unit, through the means referred to in Article 14, as soon as the issue has been solved.

The ETIAS Central Unit shall inform the Member States of the impossibility of this carrier to send the verification query.

4.   For the purpose of this Article and Article 14, eu-LISA shall make available to the ETIAS Central Unit a ticketing tool. That tool shall offer access to the register of carriers.

5.   The ETIAS Central Unit shall acknowledge receipt of the notifications referred to in paragraphs 1 and 2.

1.   A web form as part of the ticketing tool shall be made available to carriers on a public website in order to allow carriers to request assistance.

The web form shall enable the carriers to provide at least the following information:

2.   Carriers shall receive an acknowledgement of receipt of the request by the ETIAS Central Unit. That receipt shall contain a ticket number.

3.   Where the request for assistance is of a technical nature, the ETIAS Central Unit shall send the request to eu-LISA. eu-LISA shall be responsible for providing technical assistance to carriers.

4.   Where the request for assistance is not of a technical nature, the ETIAS Central Unit shall assist carriers by directing them to relevant information.

5.   Where it is technically impossible to request assistance in accordance with paragraph 1 using the web form, the carrier shall be able to use an emergency phone line connected to the ETIAS Central Unit or eu-LISA.

6.   The assistance provided by the ETIAS Central Unit and eu-LISA shall be available 24/7 and provided in English.

7.   The ETIAS Central Unit shall make available online a list of frequent questions and answers relevant for carriers. That list shall be available in all official languages of the Union. It shall be separate from the questions and answers relevant for travellers.

1.   When verifying the remaining days of authorised stay via a secure internet access to the web service, third-country nationals shall indicate the Member State of destination.

2.   The third-country national shall insert the following data in the web service:

3.   The web service shall provide one of the following replies:

4.   Where the number of remaining days of authorised stay is provided, the web service shall indicate that the number of days was calculated on the basis of the intended date of entry provided by the third-country national and that the actual number of days remaining may vary depending on the actual date of entry.

5.   Where no intended date of entry has been provided by the third-country national, the remaining authorised stay shall be calculated on the basis of the calendar date of the query. In this case, the web service shall indicate that the number of days remaining for authorised stay was calculated on the basis of the calendar date of the query.

6.   During the transitional period provided for in Article 22 of Regulation (EU) 2017/2226, where no data exist in the Entry/Exit System for the third-country national, replies to the verification queries shall be determined in accordance with the following rules:

7.   After the transitional period provided for in Article 22 of Regulation (EU) 2017/2226, replies to the verification queries shall be determined in accordance with the following rules:

8.   The web service shall provide additional information to the third-country national as follows: