Innov8tif EMAS eKYC APIs Process Flow
Overall Process Flow of eKYC APIs
Last updated
Overall Process Flow of eKYC APIs
Last updated
The user is required to enter the username and password that will be provided by Innov8tif Solutions upon request for the APIs testing. By obtaining the Journey ID, the user will have the access to all of the APIs that are requested to Innov8tif Solutions so that the user can call each of the APIs.
The user will need to provide the input (input 2 in the flow chart) to be able to test the API. The main purpose of this API is to perform OCR and extract the data from the ID card. It will output the extracted data out for the user to check on the extracted information.
The API will also return cropped ID card from the submitted image and cropped portrait from the ID card. User will also need to follow a set of rules can be found here to make sure the result is desired.
The user will need to submit a selfie to test on the Centralized OkayFace API. The purpose of this API is to compare the facial image on the ID card with the Selfie taken in this API to check if the user is the same as the ID card's owner.
The API also contains an option to enable the OkayLive API also known as "Liveness Detection" to make sure that the selfie is taken from a real person. This will greatly increase the security level of the OkayFace API to help counter against fake selfie submission. Additional information can be found here.
This process is running in the background as explained in the figure above. It will process the input submitted by the user from the Centralized OkayID. The purpose of this API is to perform multiple checkings. The checkings are discussed here. However, all these checkings only available to MyKad for now.
A list of check types is listed down below:
Font Checking
Microprint Check
Photo Substitution Check
Color Mode
Hologram
Screen Detection
Ghost Photo Color Detection
ID Blur Detection
ID Brightness Detection
Landmark Checking
Content Substitution (beta)
This process will be running in the background after the launch of the Centralized OkayID API due to the input of Centralized OkayID is the same image. Although the input of OkayID and OkayDoc should be the same, it is not necessary for the document to pass from Centralized OkayID to Centralized OkayDoc.
The purpose of this API is to perform landmark checking, screen detection and more. However, only some of the supported countries that contain the checkings that can find here.
The user will need to submit the input (input 4 in the flow chart) to be able to test the API. It will process the input submitted by the user. The purpose of this API is to record down the details of each passport for the user.
A list of check types is listed down below:
Landmark Checking
Blurriness Detection
Brightness Detection
Color Detection
Screen Detection
The Centralized OkayDoc API also contains Machine-Readable Zone (MRZ) Visual Consistency Check and MRZ Validity for the Passport in OkayDoc. The MRZ code is standard and strictly regulated to comply with the International Civil Aviation Organization. Therefore, the MRZ checks on Centralized OkayDoc will provide assurance on Passport checking. Additional information can be found here.
Please refer to the "Image Requirement" section to get the best result for each API return
