When creating a document in Mifiel, it is possible to specify that it must be signed using the e.firma corresponding to a particular RFC. This puts a lock that prevents anyone else from signing it.
Therefore, if you were invited to sign a document with an e.firma corresponding to a specific RFC, you will only be able to sign it with the private key and public certificate corresponding to that RFC.
If when trying to sign you get an error saying that the document must be signed using the e.firma associated to another RFC, there may be several reasons. Below we explain them and offer solutions for each case.
Reasons
- If you already have a Mifiel account
- You have more than one e.firma and you have already signed documents in Mifiel with one that corresponds to a different RFC
- You are using the mobile app, which only allows you to link one e.firma
- The document manager made a mistake when writing your RFC or sent you the wrong invitation
- If you don't have a Mifiel account
If you already have a Mifiel account
There are three reasons why your RFC may be incorrect:
a. You have more than one e.firma and you have already signed documents in Mifiel with one that corresponds to a different RFC
At the moment you can only have one e.firma registered in your account so it will be preloaded. However, if you have access to the e.firma corresponding to the RFC that the document requests (e.g. your account has your personal e.firma linked but the document must be signed with the e.firma of a legal entity in which you are the legal representative), you can use it to sign by clicking on the "Select other" link during the signing process.
b. You are using the mobile app, which only allows you to link one e.firma
This can be solved in the same way as the previous problem -- at the moment it is not possible to link more than one e.firma to the Mifiel app.
c. The document manager made a mistake when writing your RFC or sent you the wrong invitation
The invitation email specifies the RFC required to sign the document. If it is different from yours (either because of a typo or because the RFC is not yours), please contact the person who sent you the invitation to have it resolved. You can do this by using the "There is a problem preventing me from signing" link during the signing process if it is available for the document.
If you don't have a Mifiel account
Most likely the document creator made a mistake when writing your RFC or sent the invitation to the wrong person. You can verify this information in the signing invite email or during the signing process.
If there is an error in your RFC or it is not yours, please contact the creator to have it corrected. This can be done through the "There is a problem preventing me from signing" link during the signing process if it is available for the document.
Whether you have an account or not, if you have several .cer files and you don't know which RFC they belong to, you can consult this post on how to distinguish your e.firma files. When you select your certificate, the RFC field will be automatically completed on the page.