# KYC Verification Routine
The Customer Verification routine is designed for users who already have a previously successful identity record. The routine should only be triggered after `FindByNumberIdSuccess` returns a successful match for the customer. In this case, the platform performs a new verification against the existing enrolled identity instead of creating a brand-new enrollment flow.
## Services
[](https://docs.ado-tech.com/uploads/images/gallery/2026-03/OTRcVj9jxG7tLBSm-face-comparison-process-2026-03-24-174755.png)
How to Communicate Responses
The first communication checkpoint is the result of `FindByNumberIdSuccess`. When that service returns a successful record, the customer is eligible for verification. When it returns `404`, the correct business decision is to use Enrollment instead. The second communication checkpoint is the direct result of `CustomerVerification`, which indicates whether the verification transaction was registered successfully. If the consuming platform requires a consolidated audit trail, the transaction can then be queried through the Validation endpoint.
## Response Received
The most relevant output of this routine is `TransactionId`, which identifies the verification transaction. When a Validation lookup is performed, the response may also include `Extras.IdState`, `Extras.StateName`, and scoring data that can be used for monitoring or compliance review.
## Flow Diagram
[](https://docs.ado-tech.com/uploads/images/gallery/2026-03/mE1xBWEpwFVVXKCy-liveness-validation-new-2026-03-26-153611.png)
## Service Invocation
The routine starts with `FindByNumberIdSuccess`. When the result confirms that the customer already has a successful identity record, the platform invokes `CustomerVerification`. If the response contains a transaction identifier, that value can be reused in `Validation/{TransactionId}` whenever a normalized audit response is needed.
## Recommendations
This routine should not be used when the customer does not have a prior successful record. The facial image provided to the verification request should meet the expected quality conditions, and the integration should preserve token validity if OAuth is enabled in the project. Any user-facing conclusion should be aligned with the service outcome and, when needed, with the final Validation response.