CURP Validation - Error Codes

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 and descripcionRespuesta.
• 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 and codigoError

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:

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

For Group 2 and Group 3, you can handle the same meaning for all combinations: