Request errors
CSD errors
The merchant's CSD could not be validated.
link: https://developers.heru.app/errors/csd · status 422
Returned by PUT /merchants/{id}/csd when the files or the password fail a check. The merchant keeps its current CSD, so nothing stops working while you fix it.
{
"code": "CSD_WRONG_PASSWORD",
"status": 422,
"message": "The password does not open the private key. Check it with the merchant and upload again.",
"link": "https://developers.heru.app/errors/csd",
"fields": [
{ "field": "password", "reason": "does not open private_key" }
],
"request_id": "req_01m4xqfj7we58tkj2xahacdjny"
}| Code | What happened | What to do |
|---|---|---|
CSD_WRONG_PASSWORD | The password does not open the private key. It is the most common error. | Ask the merchant for the password of this .key. The e.firma password is usually different. |
CSD_KEY_MISMATCH | The .key does not belong to the .cer. | Ask for both files from the same CSD; they are issued together. |
CSD_IS_EFIRMA | The files are the e.firma, not the CSD. | Ask for the CSD, the certificate the SAT issues for sealing invoices. |
CSD_RFC_MISMATCH | The certificate belongs to another RFC. | Check that the files are this merchant's, or fix the merchant's RFC. |
CSD_EXPIRED | The certificate is expired. | The merchant requests a new CSD from the SAT with their e.firma. |
CSD_INVALID_CERTIFICATE | The .cer is damaged or is not a certificate. | Upload the original .cer file, without converting it. |
CSD_INVALID_KEY | The .key is damaged or is not a private key. | Upload the original .key file, without converting it. |