Issuance of the idCAT Certificate

The subscriber of the requested certificate must appear in person at the idCAT Registration Entity, providing the document proving their identity (DNI, NIE, Passport or DNI from other countries). In the case of the Passport and DNI from 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 an idCAT certificate for a third person? ).

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

When accessing the application, you will have to enter the operator certificate PIN, so if you do not enter it correctly, access to it will not be allowed.

NOTE: Error message indicating that the PIN of the Registration Entity Operator certificate has not been 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 don't remember the PIN/PUK of my idCAT operator certificate ).

If the idCAT Registration Entity Operator enters the PIN of their operator certificate correctly, they will access the home screen of the web application, from where they 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 (with letters) or NIE, the following box will appear:

At this point, the citizen will have to say whether they object to consulting their data at the DGP or not and, therefore, authorize us to consult them.

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

They will also need to indicate the reasons for their opposition and include them in the indicated box.

If you do NOT object, a copy of the document will not be required and we can 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 idCAT certificate applicant will appear loaded: Name, Surname, date of birth, number of the accrediting document which will not be editable.

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

Important: If the DGP cannot return the information, it will show us the phrase "IT WAS NOT POSSIBLE TO RECOVER THE DATA FROM THE DGP", in this case, the operator must enter all the data as it appears on the identification document. It will also be necessary to make a photocopy of the accrediting document, an authentic copy and keep it for 15 years from the expiration of the certificate, together with the application form signed by the holder.

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

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

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

It will also be necessary to make a photocopy of the supporting document, an authentic copy, and keep it for 15 years from the expiration of the certificate, along 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.

The Signador tab will then open and you will have to choose the certificate and sign the certificate issuance (the tool will request the operator's certificate PIN).

Then, a screen will 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 Revoke the idCAT ).

See the archiving procedure found in the FAQ Procedures of the idCAT Registration Entities

The Certificate Application Form is the document where all the data of the certificate holder and all the legal clauses related to digital certificates appear.

The delivery form can be issued in different languages. It is important that we mark a language that is understandable to the citizen at the time we are uploading their data. This document contains instructions for downloading the certificate. In addition, the citizen will receive all communications regarding their certificate (notification of issuance, notice of expiration, etc.) in the indicated language.

We also have a revocation form to record your request.

Remember that these documents must be kept for 15 years from the certificate's expiration date, following the instructions in the archiving procedure.

All associated documentation will generate entry entries produced when making the issuances and revocations in the entity's own registry. In case you do NOT have your registration tool integrated into MUX, the entries will be made in your entity's auxiliary registry, as do all the Consortium services, and which you can consult from EACAT.

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

It should be noted that the only data that must match exactly with the identification document in order for the Registration Entity Operator to validate is the data contained in the Certification Data section (with the exception of the email, which must be verbally verified with the citizen to confirm which is correct). The data in the Contact Data section does not have to match, but in the event of a discrepancy with the identification document, the citizen must be informed of this fact. The latter will be modifiable, only in cases that have been entered before September 2023.