Error Code Changes for Colombia

Error code definitions and response statuses for the Government Verification module for Colombia changed in June 2026. These changes improve result explainability, reduce ambiguity, and make it easier to interpret session outcomes in Dashboard and via API responses.

Warning

Action Required

If your implementation uses the impacted error codes for later decisioning logic or alerting, please review the status changes carefully and update your logic accordingly.

Status Changes for Select Error Codes

Several error codes that previously returned FAIL status now return UNKNOWN. This is more accurate. These outcomes are not definitive verification failures; instead, they indicate the verification could not be completed due to missing inputs, configuration issues, or connectivity problems.

Error Code	Description	Old Status	New Status
`NOT_ENOUGH_DATA`	One or more required fields are missing or invalid.	`FAIL`	`UNKNOWN`
`CONNECTION_ERROR`	Error occurred while trying to connect to the provider or during provider processing.	`FAIL`	`UNKNOWN`

If you prefer to continue failing sessions that now return UNKNOWN, such as CONNECTION_ERROR during a provider outage, you can configure this in Business Rules without any code changes on your end.

New Error Codes and Mapping

The following error codes can now be returned. Previously, these scenarios were grouped under broader codes. They now map to more specific codes to provide more precision in result handling.

New Code	Description	Status
`PROVIDER_UNAVAILABLE`	Provider has been intentionally disabled.	`UNKNOWN`
`PROVIDER_NOT_CONFIGURED`	Provider is not configured or is incorrectly configured for this flow.	`UNKNOWN`
`USER_NOT_FOUND`	The document was not found in the government database.	`FAIL`

Updated Behavior for VALIDATION_ERROR

VALIDATION_ERROR continues to return FAIL, but it is now applied more precisely to only include genuine verification failures, such as a document being found but in a canceled/not-valid state. Scenarios that are not true verification failures—such as connectivity, availability, and missing input data—are now mapped individually instead of being grouped under VALIDATION_ERROR.

Error Codes

Reason Code	Description	Status
`PROVIDER_UNAVAILABLE`	Provider has been intentionally disabled.	`UNKNOWN`
`PROVIDER_NOT_CONFIGURED`	Provider is not configured or is incorrectly configured for this flow.	`UNKNOWN`
`NOT_ENOUGH_DATA`	One or more required fields are missing or invalid.	`UNKNOWN`
`CONNECTION_ERROR`	Error occurred while trying to connect to the provider or during provider processing.	`UNKNOWN`
`USER_NOT_FOUND`	The document was not found in the government database.	`FAIL`
`VALIDATION_ERROR`	Document exists in the government database but is an invalid status.	`FAIL`

Unchanged Behavior

The API interface is unchanged. Error codes continue to be returned in the same fields and the same response structure. This update is fully backwards compatible; no integration changes are required.
Error codes remain available in Business Rules. All error codes, including newly distinguished ones, continue to be exposed in Business Rules, so you can configure FAIL or UNKNOWN handling as needed.