# Response Scenarios This section aims to support you in mapping your decision matrix with the scenarios that by Client may return, as well as our recommendations for decision-making. ## Onboarding Flow

status	unicoId.result	liveness	identityFraudsters.result	score	Sugestão	Descrição
5	-	-	-	-	Retry	Error processing the request.
3	inconclusive	1	inconclusive	score=0	Retry	We do not have sufficient evidence to determine if the face belongs to the CPF holder, nor a deterministic answer regarding their behavior, and we also lack sufficient evidence to conclude whether there is a probabilistic risk (possible error in the CPF).
3	inconclusive	1	inconclusive	-	Retry	We do not have sufficient evidence to determine if the face belongs to the CPF holder, nor a deterministic answer regarding their behavior. We attempted to use the risk score, but there was an error and it was not possible to generate the probabilistic score.
1/2	inconclusive	1	yes	-	Reprove or Perform the Get Process and make the decision based on the score	We do not have sufficient evidence to determine if the face belongs to the CPF holder; the face has previously been associated with other CPFs in our database (possible fraudster). We will integrate this with the risk score to return a probabilistic score.
1/2	inconclusive	1	inconclusive	-	Perform the Get Process	We do not have sufficient evidence to determine if the face belongs to the CPF holder, nor a deterministic answer regarding their behavior. We will integrate this with the risk score to return a probabilistic score.
3	inconclusive	1	yes	score=0	Reprove	We do not have sufficient evidence to determine if the face belongs to the CPF holder; the face has previously been associated with other CPF numbers in our database (possible fraudster), but we do not have enough probabilistic evidence that the face is that of the actual CPF holder.
3	inconclusive	2	-	-	Reprove	Liveness Detection declined.
3	inconclusive	1	yes	score<0	Reprove	We do not have sufficient evidence to determine if the face belongs to the CPF holder, the face has previously been associated with other CPFs in our database (possible fraudster), and we have evidence indicating a high probability that the face does not belong to the CPF holder.
3	inconclusive	1	inconclusive	score<0	Reprove	We do not have sufficient evidence to determine whether the face belongs to the CPF holder, nor a deterministic answer regarding the behavior, but we have evidence indicating a high probabilistic risk that the face does not belong to the CPF holder.
3	no	-	yes	-	Reprove	The face does not match the CPF holder's face, and the face has already been associated with other CPFs in our database (possible fraudster).
3	no	-	inconclusive	-	Reprove	The face does not match that of the CPF holder, but we don't have a definitive answer regarding the behavior. It could have been a registration error.
3	inconclusive	1	yes	score entre +10 e +49	Analysis	We do not have sufficient evidence to determine if the face belongs to the CPF holder, and the face has previously been associated with other CPFs in our database (possible fraudster), but we do have sufficient probabilistic evidence that the face belongs to the actual CPF holder.
3	yes	-	yes	-	Analysis	The face belongs to the CPF holder, but the face has previously been associated with other CPFs in our database (possible fraudster).
3	inconclusive	1	inconclusive	score>= +50	Approve	We do not have sufficient evidence to determine whether the face belongs to the CPF holder, nor a deterministic answer regarding their behavior, but we do have sufficient probabilistic evidence that the face belongs to the actual CPF holder.
3	yes	-	inconclusive	-	Approve	The face belongs to the CPF holder and has no history of fraudulent behavior.

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://devcenter.unico.io/unico-idcloud/by-client-integration/by-client-api/response-scenarios.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.