Handle IDV decision reason codes and route cases to a manual review queue

Steps

1. Collect the full set of reason codes and their definitions from each IDV vendor's documentation and maintain an internal mapping to standardized internal rejection categories
2. In your decision processing logic, inspect both the overall decision status and the array of reason codes or sub-results returned by the vendor
3. Classify each reason code as auto-reject (for example, suspected document fraud), manual review required (for example, data extraction failure or unclear image), or customer-actionable retry (for example, image too dark)
4. For manual review cases, persist the full IDV result payload, the reason codes, the applicant PII, and any available document images in a case management system accessible to your review team
5. Implement SLA tracking on the manual review queue to ensure cases are reviewed within your regulatory or internal time commitment
6. Feed final manual review outcomes back to the vendor if the vendor supports reviewer feedback loops for model improvement