IMPORTANT: For any queries about the content or to find out how to respond to the notification you have received, contact the organization that sent it directly.
From AOC Support we can only help you with the notification access process.
The most common errors are listed below. If, however, you have not found an answer to your question or incident in the included support material, you will need to contact the notifying body directly.
The most common errors that appear regarding the one-time code are:
- "The specified NIF is incorrect."
- "The code entered is incorrect."
- "The code you entered has expired. Request another one."
Remember that the one-time code:
- Only allowed in low-level notifications.
- It can only be used to access a specific notification, accessing it from the email and/or SMS notification from the same device.
- It has a limited time validity ( 30 minutes ).
If once received it does not work, it is because when generating it, an identifier is saved in the session so that it can later be validated together with the code received by email or telephone. Therefore, if the browser is closed before accessing the notification, the session is lost and with it this identifier (ID) of the code, therefore, it does not work and another one must be requested.
Remember that notifications that can be accessed with a one-time code are notifications categorized by the issuing entity as having a LOW security level and, therefore, you can access them with any other valid digital identification system, such as idCAT Mòbil, if the notification is for a person. We recommend that you obtain idCAT Mòbil, an identification and signature system that is based on the delivery of a one-time code to your mobile phone and immediate registration online. It can be obtained by following the steps below https://www.idcatmobil.cat/
This error occurs when a digital identifier categorized as low is used and the notification requires a substantial level certificate.
This is because notifications can be configured with three access levels (LOW, SUBSTANTIAL and HIGH) depending on the level of security required to access them.
In this sense, if you access with an authentication mechanism lower than required, this error message appears.
If an access mechanism higher than required is used, the notification can always be accessed and no error message is issued.
If a certificate categorized as substantial is used and the notification requires a high-level certificate.
This is because notifications can be configured with three access levels (LOW, SUBSTANTIAL and HIGH) depending on the level of security required to access them.
In this sense, if you access with an authentication mechanism lower than required, this error message appears.
If an access mechanism higher than required is used, the notification can always be accessed and no error message is issued.
If the certificate used to access is corporate and accessed with the Firefox browser , the reason why the certificate used to access the notification does not appear is that it is not installed in the Windows store.
To solve the problem, you should make a backup copy of the certificate from the Firefox browser and install it in the Windows certificate store.
To perform this action, you must follow the following steps:
- Access the Firefox browser
- Click on the Tools menu – Options – Advanced – Encryption tab .
- Click the “ View certificates ” button.
- Select the certificate you want to use to accept the notification.
- Click the “ Back up ” button that appears at the bottom of the window.
- Select the location for the file that will be created with the certificate and name it (eg: certificate.p12)
- Set a password to access the file
- Once exported, it must be imported into the Windows store: Open the p12 file that was created in the previous step by double-clicking on it.
- Follow the wizard screens and indicate the file access password that was defined in the previous steps when the wizard requires it.
- Verify that on the “Certificate Store” screen, the option “automatically select certificate store based on type” is checked.
- Once the import is complete, the certificate (the same one that was selected to access the notification) should appear when accepting the notification.
It should be noted that the recipient will only see it if the certificate with which they access it contains the NIF to which the specific notification has been associated.
Therefore, when this error occurs, it is very possible that you are trying to access with a certificate that is not issued in the name of the person/company to whom the notification is addressed, or you are acting as a representative of someone else.
Once you access the notification inbox, you will be asked if you want to access as yourself or as a representative of someone else, so check the left side margin for the notifications from whom you are accessing.
It is also possible that an error has occurred on the part of the notifying body. If the body has made an error when entering the NIF in the notification, a new notification will need to be sent with the correct NIF . The previous notification, after 10 days without access, will be considered rejected.