Incode uses a third party provider to access to the official Renapo records.
Errors while requesting the CURP validation might come from different sources: Provider and Renapo.
The details of the error will be included within the error
field in the response.
- The errors from the Provider suggest a connectivity error. These are provided via a pair of fields:
codigoRespuesta
anddescripcionRespuesta
. - Renapo errors are of a different nature, as they indicate errors with the CURP data itself or Renapo internal errors. These errors are provided with a pair of fields:
tipoError
andcodigoError
Provider Error Codes
Errors originated directly from the Provider do not reach to query the information at the Renapo services.
When an error at happens at the Provider level, you should get a response similar to this:
{
"success": false,
"error": {
"codigoRespuesta": "01",
"descripcionRespuesta": "SIN RESPUESTA DE RENAPO",
"referencia": "",
"respuestaRENAPO": null
},
"result": ""
}
Here are the possible values of the codigoRespuesta
and descripcionRespuesta
fields:
codigoRespuesta | descripcionRespuesta | Description |
---|---|---|
01 | SIN RESPUESTA DE RENAPO | No response from Renapo |
02 | SERVIDOR SVBI NO RESPONDE SE HA ALCANZADO EL LIMITE DE TRANSACCIONES PERMITIDAS POR MINUTO SE HA ALCANZADO EL LÍMITE DE TRANSACCIONES PERMITIDAS POR DIA | - SVBI server is not responding - The limit of transactions allowed per minute has been reached - The limit of transactions allowed per day has been reached |
03 | LOS DATOS SON INCORRECTOS | Data is incorrect |
05 | ERROR INESPERADO | Unexpected error |
Renapo Error Codes
When a CURP validation request is successful (meaning, RENAPO responded), you will get a response that looks like the following:
{
"success": false,
"error": {
"codigoError": "06",
"tipoError": "01",
.. // other fields
},
"result": "",
"transactionId": "",
"renapo_valid": false
}
Errors are divided in 3 groups. You can identify them by the tipoError
and codigoError
fields.
- Group 1: Errors most likely to be found. Might be due to incorrect curp input in the session.
- Group 2: Connectivity errors (within Renapo). Most of these should be transient and might require you to retry.
- Group 3: Internal errors. These should not be found. Please reach out to Incode technical support if you find any of these.
Group 1
tipoError | codigoError | message | Description |
---|---|---|---|
01 | 04 | CURP previamente dada de baja | The CURP was previously deactivated. |
01 | 06 | La CURP no se encuentra en la base de datos. | The CURP is not found in the database. |
01 | 09 | La llave de la CURP no está bien formada. | The CURP key is not correctly formatted. |
01 | 20 | Más de una CURP para estos datos | More than one CURP exists for this data. |
03 | 01 | [Nombre campo]: No cumple con el formato especificado | [Field name]: Does not meet the specified format. |
For Group 2 and Group 3, you can handle the same meaning for all combinations:
tipoError | codigoError | Meaning | Group |
---|---|---|---|
01 | 13 | Connection Error | Group 2 |
01 | 14 | Connection Error | Group 2 |
01 | 18 | Connection Error | Group 2 |
02 | 01 | Connection Error | Group 2 |
02 | 02 | Connection Error | Group 2 |
02 | 03 | Connection Error | Group 2 |
04 | 01 | Connection Error | Group 2 |
99 | 01 | Connection Error | Group 2 |
99 | 02 | Connection Error | Group 2 |
01 | 01 | Internal Error | Group 3 |
01 | 02 | Internal Error | Group 3 |
01 | 03 | Internal Error | Group 3 |
01 | 05 | Internal Error | Group 3 |
01 | 07 | Internal Error | Group 3 |
01 | 08 | Internal Error | Group 3 |
01 | 10 | Internal Error | Group 3 |
01 | 11 | Internal Error | Group 3 |
01 | 12 | Internal Error | Group 3 |
01 | 15 | Internal Error | Group 3 |
01 | 16 | Internal Error | Group 3 |
01 | 17 | Internal Error | Group 3 |
01 | 19 | Internal Error | Group 3 |
03 | 02 | Internal Error | Group 3 |
05 | 01 | Internal Error | Group 3 |