Electronic Certificate Issuance will allow you to check whether the NIK from your Indonesian ID is registered in the government database and create an Electronic Certificate as proof.

🎈Dashboard Features

Demo

Access Verihubs Dashboard, and click on DEMO on the sidebar menu. You can easily try to check your ID just a click away.

To try DEMO you can follow these steps:

1. Select which Application Name you want to try this DEMO on. Make sure you have created one, tho.
2. Input the fields you need to check with the following information :

• NIK should be 16 digits number.
• Name should be the full name based on the identity card in string format.
  Allowed strings: Alphabet [a-z][A-Z], dot (.), comma (,), single quote ('), slash (/), dash (-).
  Minimum length: 2 character alphabet
• Date of Birth format should be 'DD-MM-YYYY'.
• Email should be in email format and unique per NIK.
• Phone number must be a valid phone number, use the country code but without the (+) symbol. Phone number must be unique per NIK.
• Selfie Photo should be min 100kB - max 4MB, or minimum 480x640 pixels. Image format should be in .jpg, .jpeg, .png
• KTP Photo should be min 100kB - max 2MB, or minimum 480x360 pixels. Image format should be in .jpg, .jpeg, .png

3. You will be given a quota for each Application Name to try the DEMO. Your remaining quota will also be shown at the top of the Application Name.
4. Click on the "Check Now" button to check the ID with the details.
5. Click on the "Contact Us" button when you feel like need more information about the service. It will redirect you to the Verihubs Representative WhatsApp number.

Transaction Details

The transaction details menu will show every detail of your transaction in the table. The table will consist of the following data:

You can also filter the transaction based on the following data:

Don't forget to click on the Apply button to view transactions based on the selected filter.

The transactions can be exported into CSV or XLSX by clicking Export as CSV button or Export as XLSX button.

🎈Response Details

Reject Field

The reject field indicates if a parameter is returned incorrectly after being checked from the data source side.

Detail for Success Transaction

This case occurs if all parameters get successful results from the results of checking the data source (all valid data).

Detail for Success but Not Verified Transaction

This is a response that indicates there is an incorrect parameter after checking the data source. Below are also some examples of requests/responses.

Invalid NIK

Invalid Name

Invalid Birth Date

Invalid Selfie Photo

Invalid KTP Photo

Detail for Success but Verified with Reason Transaction

This case occurs where email, phone, or both have been correlated with a certain NIK, causing the status "verified_with_reason". If this case occurs, please contact Privy's customer support directly ([email protected]).

Conflict Email

Conflict Phone

Conflict Email and Phone

Detail for Failed Transaction

Here are some examples of cases for validating the format of existing parameters. If validation fails, the transaction will receive a 400 response along with details such as:

• error_code
• error_fields
• message

VALIDATION FORMAT NIK

VALIDATION FORMAT BIRTH DATE

VALIDATION FORMAT SELFIE PHOTO

VALIDATION FORMAT SELFIE PHOTO (NO FACE DETECTED)

VALIDATION FORMAT KTP PHOTO

VALIDATION FORMAT EMAIL

VALIDATION FORMAT PHONE

Detail for Success Transaction but Liveness Check False/Failed

🎈Transaction Status

All transactions with response code 200 will be charged, with further explanations:

🎈Recommended Timeout Setting

This service depends on connection to Data Source. Based on our monitoring, the recommended setting for timeout is 60 seconds.

🎈Status Page

We also provide a website to monitor this service, which can be viewed or accessed via Status Page. Incidents or if there is a problem with the service will be updated on that page.

🎈Channel Payload for Brand Name

If channel payload is used in the request parameter, your users will get email containing a PRIVY ID with channel payload as the brand name. If you did not include your brand on the payload, YOUR COMPANY SHORT NAME will be used as the brand’s name in the email (highlighted below).

Channel payload will also be used as a brand name when the user is using another email address to verify identity (the user did not verify using the same email when signing up to privy). The example is highlighted below.

🎈Best Practice

Here are some of the best practices for taking selfies, ID Card (KTP), and Liveness

Selfie Image

To help the process of checking images run optimally, here are some examples of right and wrong in taking selfies:

1. Showing the whole face (eyes, nose, and mouth) and having good lighting

2. Selfie sample that cannot be processed: The user's face is partially/fully blocked by other objects (KTP, full masks, etc)

3. Selfie sample that cannot be processed: Multiple faces in one frame and a selfie is taken from another device (image from another phone/screen)

4. Selfie sample that cannot be processed: Selfie taken is too far or too dark

ID Card (KTP)

1. Make sure the photo of KTP is clearly visible

2. If your mobile application has border, make sure the KTP is inside the border.

3. KTP sample that cannot be processed: The card is physically broken

4. KTP sample that cannot be processed: The photo is a blur

5. KTP sample that cannot be processed: KTP photo is edited

6. KTP sample that cannot be processed: KTP photo is black & white (photocopy)

7. KTP sample that cannot be processed: KTP is NOT inside the border of your mobile application.

Liveness

Liveness detection is the ability of a system to detect if a face is real or fake. Here are some examples of performing liveness:

1. Only one face exists in the image sent
2. The face in the image must not be blocked by anything, i.e., take off masks, sunglasses/light reflection on glasses, hat
3. Make sure the image has good quality (avoid blur & dark)
4. The minimum resolution of the image is Height: 640 x Width: 480
5. Minimum size for each image: it’s recommended to be 200kb with minimum quality is JPEG 90%
6. Avoid backlight
7. Avoid taking images in a dark environment
8. No editing on the image
   • prioritize for users to directly capture face images from mobile phone camera
   • do not compress or crop the image
   • do not add any elements to the image, i.e., padding

Case examples:

1. Look straight (face should be looking straight)

2. Lighting condition (avoid taking images in backlight or low light conditions. It may reduce the visibility of the facial features)

3. Orientation (the orientation of the face should be portrait with the correct orientation)

4. Face in the center (the face should be in the center to avoid half-face images which might lead to no face detected)

5. Background condition (avoid taking the image in a crowded background as it might affect the result)

6. No attributes covering the face (avoid wearing attributes or anything that cover your faces such as sunglasses/glasses with light reflection, face masks, hat, and hair)

7. No blur (the blurrier the face photo, the less liveness accuracy)

8. No holding identity card (do not hold identity cards as it will affect the liveness result)