## Common errors

The table below outlines common issues that may occur when using Socure Prefill in RiskOS™.

These may stem from input formatting, incomplete data, provisioning gaps, or conflicting identity signals. Understanding these patterns helps fine-tune workflows, reduce null responses, and decide when fallback or escalation logic is needed.

| Issue | Explanation | Suggested fix |
| --- | --- | --- |
| No match / empty response | Inputs conflict, are incomplete, or do not resolve to a single SocureID. | Ensure consistent PII. Encourage users to provide accurate inputs. Prefill only returns data for a confident match. |
| Missing fields | Thin credit file, regional restrictions, or sparse data source coverage. | Anticipate incomplete attributes. Do not assume all fields will be populated. |
| Invalid input formatting | Incorrect formats (e.g., phone not in **E.164**). | Validate and normalize inputs before submission. |
| Not provisioned for Prefill | Workflow is missing entitlements for Prefill. | Confirm Prefill is enabled in your RiskOS™ environment. |
| API misconfiguration | Module not included in request (e.g., missing `