---
Source: https://docs.microblink.com/verify/v2/recommended-outcome
Title: Recommended outcome
Description: Explanation of the recommended outcome returned by the Verify API
---

# Recommended outcome

The highest-level verification output is the `RecommendedOutcome` field.

It's the culmination of all the checks, options, properties of the document, and the properties of the captured images.

The purpose of the `RecommendedOutcome` is to answer what to do with the document and the end user.

The answer depends on how you've defined fraud and desired behavior using the [`UseCase`](./configuration.md#use-cases) system and specific [`Options`](./configuration.md#options).

## Possible values

The following things can happen when verifying a document:

- We can be sure it's genuine and live.
- We can be sure it's not genuine or not live.
- We can be unsure about one or both of the above.
- The document could be completely unextractable or unsupported.
- We can be fairly certain the quality of the images is poor to a degree that would affect the system's ability to make a fraud verdict.

Thus, the `RecommendedOutcome` can be one of the following values:

- `Accept`: the document is genuine and live
- `Reject`: the document is not genuine or not live
- `Retry`: the document cannot be verified due to image quality issues with the current configuration
- `ManuallyReview`: the document should be reviewed manually. 
  You still get a verdict, and detailed check results.
- `Undeterminable`: we know the document is not supported by our systems, or the image is so poor we couldn't even find a supported document in it.

## A demonstration with default options

Let's look at an example of Verify's `RecommendedOutcome`s (using default options and a default use case) for various scenarios.



<!-- interactive component omitted -->


Last updated on Aug 3, 2026