Skip to main content
A guide to the types of issues that can arise during KYC workflows and how to handle them.
Note:
In the FrankieOne v2.0.0 API, an “issue” is a fundamental concept used to communicate problems, errors, or specific outcomes that require attention. Issues can arise from simple input validation errors to complex workflow results that require manual review.

The Structure of an Issue

An issue is typically represented as an Issue object, which contains details about what went wrong and where. While the exact structure can vary slightly depending on the context (e.g., a synchronous API error vs. a workflow result), it generally contains the following key fields:Example: 400 Bad Request Error Response

How Issues are Created

Synchronous errors occur when an API request cannot be fulfilled due to issues like invalid authentication, malformed requests, or server-side problems. The API returns a standard Error object with a relevant HTTP status code (e.g., 400, 401, 500).Common Error Scenarios:
  • 400 Bad Request: Validation errors (e.g., malformed entityId)
  • 401 Unauthorized: Missing or invalid api_key
  • 404 Not Found: Resource does not exist
  • 5xx Server Error: Internal platform issues
When a workflow runs, the platform performs a series of checks. If any check produces a result that requires attention, a Workflow-Issue object is generated and included in the workflow execution summary.Example: Workflow-Execution-Summary with an Issue

Issue Severity Levels


Workflow Issue Categories

This table lists the general categories that an issue can fall under.

Workflow Issue Types & Descriptions

KYC Summary Issue CodesKYC Detailed Issue Codes
For more information on how these conditions are evaluated and configured, please refer to the KYC Ruleset page.

Workflow Issue Severity Levels

Severity levels help determine the urgency and impact of an issue. Use them to drive workflow logic and user experience.

Best Practices for Handling Issues

  • Monitor theissues array in workflow results to drive automated decisions or flag cases for manual review.
  • MapissueLocation to specific fields in your UI for targeted feedback.
  • Useseverity to determine whether to block, warn, or allow user progression.
  • LogissueId and requestId for troubleshooting and support.
Tip:
By building logic around issues, you can streamline compliance, automate onboarding, and improve user experience.