Error Code Changes for US GovMatch
Error code definitions and response statuses for the GovMatch module for the United States changed in April 2026. These changes improve result explainability, reduce ambiguity, and make it easier to interpret session outcomes in Dashboard and via API responses.
Action RequiredIf 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 |
|---|---|---|---|
providerNotConfigured | Provider is not configured or incorrectly configured for this flow | FAIL | UNKNOWN |
missingDocumentId | Document number missing or has an invalid pattern | FAIL | UNKNOWN |
invalidExpirationDate | Expiration date is not valid per document standards | FAIL | UNKNOWN |
notEnoughData | One or more required fields are missing or invalid | FAIL | UNKNOWN |
missingSelfie | Provider requires selfie for processing but not provided in session | FAIL | UNKNOWN |
connectionError | Error occurred during processing within provider environment | FAIL | UNKNOWN |
infrastructureError | Error occurred during processing within Incode environment | FAIL | UNKNOWN |
If you prefer to continue failing sessions that now return UNKNOWN, such as connectionError during a provider outage, you can configure this in Business Rules without any code changes on your end.
Deprecated Error Codes and New Mapping
The following error codes are deprecated and no longer returned. Sessions that would have previously triggered these codes will now return one of the more specific replacement codes listed below.
| Deprecated Code | Old Description | Now Mapped To |
|---|---|---|
validationError | Grouped validation failure covering: record not found, data mismatch, restricted record, or face match failed | userNotFound, faceComparisonFailed (more specific codes per actual failure reason) |
providerUnavailable | DMV or AAMVA provider service unavailable or credentials invalid | connectionError |
Updated Error Descriptions
Some error codes retain the same status but have updated descriptions for improved clarity. No behavioral changes were made.
| Error Code | Description |
|---|---|
providerNotConfigured | Provider Not Configured Provider is not configured or is incorrectly configured for this flow. |
missingDocumentId | Missing Document Number Document number missing or has an invalid pattern. |
invalidExpirationDate | Invalid Expiration Date Expiration date is not valid per document standards. |
notEnoughData | Missing Required Data One or more required fields are missing or invalid. |
missingSelfie | Missing Selfie Provider requires selfie for processing but not provided in session. |
documentTypeNotSupported | Document Type Not Supported Invalid document type for validation by the configured provider. |
geographicRegionNotSupported | Country Not Supported Document country not supported by the configured provider. |
geographicStateRegionNotSupported | State Not Supported Document state not supported by the configured provider. |
connectionError | Provider Connection Error Error occurred during processing within provider environment. |
infrastructureError | Incode Processing Error Error occurred during processing within Incode environment. |
userNotFound | User Not Found ID data doesn't match the government database. |
faceComparisonFailed | Face Match Failed Selfie does not match government database portrait. |
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 renamed and updated ones, continue to be exposed in Business Rules, so you can configure
FAILorUNKNOWNhandling as needed. - Error codes remain unchanged for non-US connections. The error codes for all non-US government verification connections remain unchanged.
- Billing behavior is unchanged for all affected codes.
Updated 1 day ago