KYC Validation Routine against Ecuador

How to Communicate Responses

The integration should communicate Uid as the technical correlation value across the capture phase, and TransactionId as the final reference used to retrieve the result. The business-facing response should be derived from the Validation service rather than from the close request itself, because the Validation response is the authoritative source for the final state of the transaction.

Response Received

The most relevant technical outputs of this routine are Uid, which links all intermediate steps, and TransactionId, which identifies the closed transaction. The Validation response can also include functional state information in Extras.IdState and Extras.StateName, as well as optional evidence such as images and other result details.

Flow Diagram

Service Invocation

The sequence begins with Validation/New, which returns the Uid. The same identifier is then reused in DocumentFrontSide, DocumentBackSide, and CloseRegistro. Once the transaction is closed, the resulting TransactionId is passed to Validation/{TransactionId} in order to retrieve the final process outcome.

Recommendations

The exact path and contract of CloseRegistro should be confirmed against the private Swagger before external delivery. The same Uid must be preserved during the full capture phase, and the process should not be considered complete until the Validation endpoint returns the final result. Payload quality checks should be enforced for both document images to reduce invalid image or malformed base64 errors.