The CURP Validation module validates a person's CURP (Clave Única de Registro de Población), a personal identification number issued in Mexico, against Mexico's RENAPO registry. It accepts a CURP extracted via OCR, entered manually, or generated from personal data when the user doesn't know it.
For an overview of this module and how it works, see CURP Validation.
Supported with:
✅ Workflows | ✅ Flows
Add CURP Validation to Workflows
- In the left menu in Dashboard, click Flow Builder > Workflows.
- Click New or select an existing Workflow.
- Add the CURP Validation module. Do one of the following, depending on whether you have the New or Classic view enabled in the toggle in the top right:
- New: Click Add node
> Modules, then search for and select CURP Validation. - Classic: From the Modules list, drag and drop the CURP Validation module into the builder.
- New: Click Add node
- You can click Options
> Edit on the module node to open the Configuration Options panel and adjust settings as needed.
Add CURP Validation to Flows
- In the left menu in Dashboard, click Flow Builder > Flows.
- Click New or select an existing Workflow.
- On the Select Modules tab, find the CURP Validation module and click Add.
- You can click Details & Configurations to open the Configuration Options panel and adjust settings as needed.
Configuration Options
This section details all the configuration options available for this module. The options that appear depend on whether you have the New or Classic view enabled in the toggle in the top right in your Flow or Workflow. After changing anything, click Save configuration before closing the configuration panel.
The options you see in your configuration may differ from those documented below. Contact your Incode representative for more information.
Configuration Options: New
View image of Workflow configuration panel

View image of Flow configuration panel

| Setting | Description |
|---|---|
| CURP data match Workflows only |
When enabled, validates that the CURP data returned by RENAPO matches the personal data captured earlier in the session: for example, name and birthdate from ID Capture. |
| Deceased status verification | When enabled, the module checks the RENAPO response for a deceased status and treats a deceased result as a validation failure. |
| Auto-retry on service errors | When enabled, activates asynchronous retry logic if the provider call fails or times out, improving reliability when the primary provider is unavailable. |
Configuration Options: Classic
View image of Workflow configuration panel

View image of Flow configuration panel

| Setting | Description |
|---|---|
| CURP data match Workflows only |
When enabled, validates that the CURP data returned by RENAPO matches the personal data captured earlier in the session: for example, name and birthdate from ID Capture. |
| Deceased status verification | When enabled, the module checks the RENAPO response for a deceased status and treats a deceased result as a validation failure. |
| Async retries enabled | When enabled, activates asynchronous retry logic if the provider call fails or times out, improving reliability when the primary provider is unavailable. |