Issuance of the idCAT Certificate

The subscriber of the requested certificate must present himself at the idCAT Registration Entity by providing the document proving his identity (DNI, NIE, Passport or DNI from other countries). In the case of the Passport and the National Identity Card of other countries, a photocopy of the same must be provided. (More information in Documentation for the issuance of the idCAT and Can a citizen request a idCAT certificate for a third person? ).

To be able to access the web application, the Operator of Registration Entity idCAT will need to have an operator certificate that will have been supplied by the AOC Consortium after verifying the knowledge and receiving sufficient and appropriate training to act as such
This operator will insert the card into the cryptographic card reader and then you will have to choose your operator certificate and “Accept”.
You will access the web application through the following URL: https://scd.idcat.cat/login

At the time of accessing the application, you will need to enter the operator certificate PIN so that if you do not enter it correctly, you will not be allowed to access it.

NOTE: Error message indicating that the Registration Entity Operator certificate PIN was not entered correctly. After entering the PIN incorrectly 3 times, it is necessary to unblock the PIN using the PUK with the Token Management application. After entering the PUK incorrectly 3 times, the operator card is blocked. (See I can't remember my Operator Certificate PIN/PUK idCAT ).

If the Registry Entity Operator idCAT enters the PIN of his operator certificate correctly, he will access the initial screen of the web application, from where he will have access to various functionalities, including issuing certificates .

When we enter the application, the procedure is with the person in front and viewing the supporting document, we will indicate the type of document and its number.

In cases where we indicate DNI (in writing) or NIE, the following box will appear:

At this point the citizen will have to say whether he objects to consulting his data at the DGP or not and, therefore, authorizes us to consult them.

In the event that it is opposed, we will have to make a photocopy of the accrediting document, make an authentic copy and incorporate it into the file and keep the documentation for 15 years from the expiry of the certificate.

It will also be necessary for them to indicate the reasons why they are opposed and to incorporate them in the indicated table.

In the event that you do NOT object, the copy of the document will not be needed and we will be able to continue with the issuance process.

In the next step we will be asked to enter the date of birth of the person for whom we are making the certificate.

Once incorporated we will continue with the issuance process by clicking Continue.

If the DGP can return the information to us, the personal data of the applicant for the idCAT certificate will appear loaded: Name, Surname, date of birth, number of the crediting document which will not be editable.

The rest of the data must be entered by the operator and the process completed as before, only keeping the duly signed application form.

Important: If the DGP CANNOT return the information to us, it will show us the phrase "THE DATA FROM THE DGP COULD NOT BE RECEIVED", in this case, the operator must enter all the data as they appear in the document identifier It will also be necessary to make a photocopy of the accrediting document, an authentic copy and keep it for 15 years from the expiry of the certificate, together with the application form signed by the holder.

The same will happen if the query service in DGP is not working at the time of making the query.

The procedure is the same as in the previous point, but the query to the General Directorate of the Police will not appear.
The operator will need to fill out the form (according to the data in the credentialing document) and continue with the indicated steps.

Once we have entered these data, we go to the confirmation page.

It will also be necessary to make a photocopy of the accrediting document, an authentic copy and keep it for 15 years from the expiry of the certificate, together with the application form signed by the holder.

Once the operator confirms and validates the data, the issue can be signed.

Then a window will appear with the text to be signed and then you must click Continue. This operation will be carried out with the Signador AOC.

Next, the Signador tab will open and you will have to choose the certificate and sign the issuance of the certificate (the tool will ask for the operator's certificate PIN).

A screen will then appear indicating that the signing process has completed successfully.

In this case the form already appears with the certificate data. The application already informs us that in order to issue the new certificate, we must first revoke the previous one (see Revoking the idCAT ).

See the filing procedure found in the Registration Entities Procedures FAQ idCAT

The certificate application form is the document in which all the data of the certificate holder and all the legal clauses related to digital certificates appear.

The delivery slip can be issued in different languages. It is important that we mark a language that is understandable by the citizen at the time when we are uploading their data. Instructions for downloading the certificate appear in this document. In addition, the citizen will receive all communications regarding his certificate (notification of issuance, notice of expiration, etc.) in the indicated language.

We also have the revocation sheet to document the request.

Remember that these documents must be kept for 15 years from the date of expiry of the certificate, following the instructions of the archiving procedure.

All the associated documentation will generate entry entries produced when issuing and revoking the register of the entity itself. In the event that you do NOT have your registration tool integrated into MUX, the entries will be made in the auxiliary register of your entity, as all Consortium services do, and which you can consult from EACAT.

If you have your registration tool integrated with MUX, please note that you will be able to distinguish these new entries because the application that will make them will be “IDCAT”.

It should be noted that the only data that must exactly match the identification document in order for the Registry Entity Operator to be able to validate are the data contained in the Certification Data section (with the exception of the e-mail, of which it is necessary to make a verbal verification contrasting with the citizen which is correct). The data in the Contact data section do not have to match, but in the event of a discrepancy with the identification document, the citizen must be informed of this fact. These seconds will be modifiable, only in cases that have been introduced before September 2023