The main aim of the document monitoring phase is to validate the authenticity of the document submitted by the user, such as official identifications and to prevent fraud with false, altered or non-legitimate document.

At times there are documents with back and back, so that will depend if one or two images are caught by document to use this service, these images of these documents have to be converted to Base64 Before they are sent to service. Thus, it's vital to conduct the image encoding process to secure their proper transmission and processing.

Realizes next call API sending images or images of the document.

URL

POST https://api.sandbox.jaak.ai/api/v3/document/verify

Leader

Authorization: Bearer token-session-kyc

Field	Type	Required	Description
Authorisation	string	Yeah.	The Session Token should be sent at this headquarters KYC That's been obtained from the exchange with Short Key

Request

{
    "imageFront": String,
    "imageBack": String,
    "dataVerification": Boolean
}

Field	Type	Required	Description
imageFront	string	Yes	Image from the back of the document in Base64 format. It's required to provide this image for verification.
imageBack	string	Optional	Image from the back of the document in Base64 format. It should be included if the document has a later counterparty.
dataVerification	boolean	Optional	If set in true, the API conduct a comparison of the document's data with the RENAPO (only available for documents issued in Mexico).

Answer

{
    "eventId": String,
    "requestId": String,
    "evaluation": String,
    "document": {
        "type": String,
        "side": String,
        "country": String,
        "icaoCode": String
    },
    "state": {
        "documentCompleteSides": Boolean,
        "dataConsistent": Boolean,
        "documentLiveness": Boolean,
        "securityFeatures": Boolean,
        "documentValidity": Boolean,
        "imageQuality": Boolean,
        "handPresence": Boolean,
        "message": String,
        "validations": {
            "namesMatch": Boolean,
            "lastNameMatch": Boolean,
            "birthDateMatch": Boolean,
            "personalIdNumberMatch": Boolean,
            "message": String
        },
        "photoForgery": Boolean
    },
    "processTime": Integer
}

Field	Type	Description
event	string	ID for traceability of event details.
request	string	ID for demand traceability.
Evaluation	string	The result of the document's assessment.
document	object	Information from the document analysed.
status	object	Results of different verifications about the document.
ProcessTime	integrate	Test processing time for milliseconds.

Subject matter * document *

Field	Type	Description
Type	string	Type of document. See list
side	string	It indicates whether the document has both sides or only one.
Country	string	Country where document is issued.
icaoCode	string	ICAO code associated with document. ( Download list )

Object * state *

Field	Type	Description
complete	boolean	It indicates whether the document has been completely captured from all required sides.
dataConsistent	boolean	It is valid if the information contained in the document is consistent and does not have inconsistencies.
documentation	boolean	He verifies that the document is a physical identification and not a print, photocopy or photo shown on a digital screen.
securityFeature	boolean	Determines whether the document complies with the intended safety elements, such as holographic seals, logos, typography and other anti-fraud features.
document Validity	boolean	It indicates whether the document is valid and remains valid.
imageQuality	boolean	Assess document image quality to ensure precise verification.
handPresence	boolean	Detects if there are hands holding the identification while capturing the image.
photoForgery	boolean	It indicates whether the document's image has been digitally handled with editing tools.
valtiations	object	Special Validation of Mexican Documents
message	string	It provides additional details in case of errors or discrepancies with expected results.

Object * state.validations *

Field	Type	Description
namesMatch	boolean	Check if the name extracted from the document matches the name associated with the personal identification number (CURP with respect to Mexico) according to RENAPO.
lastNameMatch	boolean	Check if the name drawn from the document matches the name associated with the personal identification number (CURP with respect to Mexico) according to RENAPO.
birthDateMatch	boolean	It indicates whether the date of birth drawn from the document coincides with that registered in the database of RENAPO for personal identification number (CURP with respect to Mexico).
personal	boolean	Valids if the personal identification number extracted from the document coincides with the CURP at the database of RENAPO.
message	string	A message that provides additional information in case of discrepancy with validation.

The * state * object, situated within the * Response *, shows the status of document's verification throughout the validation process. That object includes a group of properties that indicate whether or not the document meets the authenticity, quality and consistency requirements.

JAAK recommends that all monitoring properties be successfully completed for better safetywhile this isn't required so you can select only a set of properties as required. Some examples include:

Accept verification if all validations are successful.
Request a new capture if the image quality is low or key elements are missing.
Reject verification if serious data manipulations or inconsistencies are detected.

Each property within * state * plays a specific role in document verification and can be used to make decisions and be integrated into your verification system.

The property * dataVerification * within * Request *, as established as * true *, provides additional validations about data from Mexican documents. These validations, found in * stat.validations * of * Response *, are performed exclusively for Mexican documents through official entities such as RENAPOTo identify other nationalities, all validations will be * false * due to the incompatibility of service with these documents.

After monitoring and validating the document, data can be extracted at the next step, it's important to remember that the same images sent at this step were used at the next step to seek best coherence at the Session KYC.