VEverihubs
Sandbox - Electronic Certificate Issuance Service

Electronic Certificate Issuance Service

Electronic Certificate Issuance allows you to check whether the NIK and other data from your client's KTP is registered in the government database. Please refer to Verihubs Documentation for guidelines and best practice

Scenario Description

Success Scenario

ScenarioRequest PayloadDescription
User input all valid data8522011808880001 <br> JOHN DOE <br> 18-08-1988 <br> johndoe@sandbox.com <br> 6281256898760 <br> {base64 Selfie} <br> {base64 KTP} <br> {reference_id free to fill}Data inputted based on rules & registered in Authoritative source based on NIK

NIK Scenario

ScenarioRequest PayloadDescription
NIK Not Inputted{empty NIK value} <br> JOHN DOE <br> 18-08-1988 <br> johndoe@sandbox.com <br> 6281256898760 <br> {base64 Selfie} <br> {base64 KTP} <br> {reference_id free to fill}NIK is a mandatory parameter.
NIK Non-Numeric85220118ABCD0001 <br> JOHN DOE <br> 18-08-1988 <br> johndoe@sandbox.com <br> 6281256898760 <br> {base64 Selfie} <br> {base64 KTP} <br> {reference_id free to fill}Indonesian NIK inputted must be numeric.
NIK Not 16-Digit852201180888000 <br> JOHN DOE <br> 18-08-1988 <br> johndoe@sandbox.com <br> 6281256898760 <br> {base64 Selfie} <br> {base64 KTP} <br> {reference_id free to fill}Indonesian NIK inputted must be 16 digit.
NIK Not Verified{OTHER THAN PREDETERMINED NIK} <br> JOHN DOE <br> 18-08-1988 <br> johndoe@sandbox.com <br> 6281256898760 <br> {base64 Selfie} <br> {base64 KTP} <br> {reference_id free to fill}The NIK inputted is not registered in Authoritative source thus the other data can not be checked.

Name Scenario

ScenarioRequest PayloadDescription
Name Not Inputted8522011808880001 <br> {empy name value} <br> 18-08-1988 <br> johndoe@sandbox.com <br> 6281256898760 <br> {base64 Selfie} <br> {base64 KTP} <br> {reference_id free to fill}Name is not inputted in the payload.
Name Not Verified8522011808880001 <br> {OTHER THAN REGISTERED NAME} <br> 18-08-1988 <br> johndoe@sandbox.com <br> 6281256898760 <br> {base64 Selfie} <br> {base64 KTP} <br> {reference_id free to fill}The name inputted is not an exact match with the name registered on Authoritative source.

Birth Date Scenario

ScenarioRequest PayloadDescription
Birth Date Not Inputted8522011808880001 <br> JOHN DOE <br> {empty birth_date value} <br> johndoe@sandbox.com <br> 6281256898760 <br> {base64 Selfie} <br> {base64 KTP} <br> {reference_id free to fill}Birth date not inputted in payload.
Birth Date Not in DD-MM-YYYY Format8522011808880001 <br> JOHN DOE <br> 1988-08-18 <br> johndoe@sandbox.com <br> 6281256898760 <br> {base64 Selfie} <br> {base64 KTP} <br> {reference_id free to fill}Birth date must be in DD-MM-YYYY format. Inputting random string will also trigger this validation.
Birth Date Not Verified8522011808880001 <br> JOHN DOE <br> {OTHER THAN REGISTERED BIRTH DATE} <br> johndoe@sandbox.com <br> 6281256898760 <br> {base64 Selfie} <br> {base64 KTP} <br> {reference_id free to fill}Birth date inputted is not an exact match with birth date registered in Authoritative source.

Selfie Photo Scenario

ScenarioRequest PayloadDescription
Selfie Photo Parameter Empty8522011808880001 <br> JOHN DOE <br> 18-08-1988 <br> johndoe@sandbox.com <br> 6281256898760 <br> {empty selfie_photo value} <br> {base64 KTP} <br> {reference_id free to fill}Selfie photo parameter is empty/not containing any base64 values.
Selfie Photo is Not Base648522011808880001 <br> JOHN DOE <br> 18-08-1988 <br> johndoe@sandbox.com <br> 6281256898760 <br> {input any value non base64} <br> {base64 KTP} <br> {reference_id free to fill}Selfie photo inputted is non-base64 format.
Selfie Photo Pixelation is Below Requirementnik: 8522011808880001 <br> name: JOHN DOE <br> birth_date: 18-08-1988 <br> email: johndoe@sandbox.com <br> phone: 6281256898760 <br> selfie_photo: {base64 Selfie (below pixel requirement)} <br> ktp_photo: {base64 KTP} <br> reference_id: {reference_id free to fill}The resolution of the selfie photo is below 480px (horizontal) x 640px (vertical)
Selfie Photo Below 100KB8522011808880001 <br> JOHN DOE <br> 18-08-1988 <br> johndoe@sandbox.com <br> 6281256898760 <br> {base64 Selfie <100kb} <br> {base64 KTP} <br> {reference_id free to fill}Selfie photo size must be 100KB-4096KB
Selfie Photo Size Above 4096KB8522011808880001 <br> JOHN DOE <br> 18-08-1988 <br> johndoe@sandbox.com <br> 6281256898760 <br> {base64 Selfie >4096kb} <br> {base64 KTP} <br> {reference_id free to fill}Selfie photo size must be 100KB-4096KB
Selfie Photo Not Verified8522011808880001 <br> JOHN DOE <br> 18-08-1988 <br> johndoe@sandbox.com <br> 6281256898760 <br> {not verified base64 SELFIE} <br> {base64 KTP} <br> {reference_id free to fill}The face in the selfie photo inputted is not a match to face registered in Authoritative source.
Rejected by Passive Liveness8522011808880001 <br> JOHN DOE <br> 18-08-1988 <br> johndoe@sandbox.com <br> 6281256898760 <br> {LIVENESS REJECTED} <br> {base64 KTP} <br> {reference_id free to fill}Face in the selfie photo is classified as non-alive/non-human by passive-liveness.

KTP Photo Scenario

ScenarioRequest PayloadDescription
Empty KTP photo8522011808880001 <br> JOHN DOE <br> 18-08-1988 <br> johndoe@sandbox.com <br> 6281256898760 <br> {base64 Selfie} <br> {empty ktp_photo value} <br> {reference_id free to fill}KTP photo is not inputted in the payload.
KTP photo is not Base648522011808880001 <br> JOHN DOE <br> 18-08-1988 <br> johndoe@sandbox.com <br> 6281256898760 <br> {base64 Selfie} <br> {input any value not_base64} <br> {reference_id free to fill}KTP photo is not in Base64 format. Inputting random string will also trigger the same result.
KTP photo resolution is below minimum requirement8522011808880001 <br> JOHN DOE <br> 18-08-1988 <br> johndoe@sandbox.com <br> 6281256898760 <br> {base64 Selfie} <br> {low_resolution_base64} <br> {reference_id free to fill}Minimum KTP photo requirement of 480px (horizontal) x 360px (vertical).
KTP photo size below minimum requirement8522011808880001 <br> JOHN DOE <br> 18-08-1988 <br> johndoe@sandbox.com <br> 6281256898760 <br> {base64 Selfie} <br> {base64 KTP <100kb} <br> {reference_id free to fill}KTP photo size must be 100KB-2096KB.
KTP photo size above maximum requirement8522011808880001 <br> JOHN DOE <br> 18-08-1988 <br> johndoe@sandbox.com <br> 6281256898760 <br> {base64 Selfie} <br> {base64 KTP >2048kb} <br> {reference_id free to fill}KTP photo size must be 100KB-2096KB.
Invalid KTP photo8522011808880001 <br> JOHN DOE <br> 18-08-1988 <br> johndoe@sandbox.com <br> 6281256898760 <br> {base64 Selfie} <br> {input failed KTP} <br> {reference_id free to fill}KTP photo classified as not a real KTP. A fake/copied/highly blur/cropped KTP photo will trigger this validation.

Email Scenario

ScenarioRequest PayloadDescription
User did not input value in Email payload8522011808880001 <br> JOHN DOE <br> 18-08-1988 <br> {empty email value} <br> 6281256898760 <br> {base64 Selfie} <br> {base64 KTP} <br> {reference_id free to fill}Data inputted missing value in Email payload
User did not input Email based on format8522011808880001 <br> JOHN DOE <br> 18-08-1988 <br> johndoe.sandbox.com <br> 6281256898760 <br> {base64 Selfie} <br> {base64 KTP} <br> {reference_id free to fill}Data inputted not a valid format
User did not input unique email to the Email payload (using the same email for another NIK)8522011808880001 <br> JOHN DOE <br> 18-08-1988 <br> janedoe@sandbox.com <br> 6281256898760 <br> {base64 Selfie} <br> {base64 KTP} <br> {reference_id free to fill}Inputted data and got verified_with_reason status with reject_field Email

Phone Scenario

ScenarioRequest PayloadDescription
User did not input value in Phone payload8522011808880001 <br> JOHN DOE <br> 18-08-1988 <br> johndoe@sandbox.com <br> {empty phone value} <br> {base64 Selfie} <br> {base64 KTP} <br> {reference_id free to fill}Data inputted missing value in Phone payload
User did not input Phone based on format8522011808880001 <br> JOHN DOE <br> 18-08-1988 <br> johndoe@sandbox.com <br> 62812 <br> {base64 Selfie} <br> {base64 KTP} <br> {reference_id free to fill}Data inputted is not based on format
User did not input unique Phone to the Phone payload (using the same phone for another NIK)8522011808880001 <br> JOHN DOE <br> 18-08-1988 <br> johndoe@sandbox.com <br> 6281234123412 <br> {base64 Selfie} <br> {base64 KTP} <br> {reference_id free to fill}Inputted data and got verified_with_reason status with reject_field Phone
post/v2/data-verification/certificate-electronic/sandbox

Request

  • Base URL
    https://api.verihubs.com
  • URL
    https://api.verihubs.com/v2/data-verification/certificate-electronic/sandbox
  • Auth
    none declared. Required headers: App-ID, API-Key

Headers

App-IDstring required
API-Keystring required

Request body

nikstring required

16 digit numeric Identifier Number from ID.

namestring required

Full name from ID.

birth_datestring required

Date of birth from ID in DD-MM-YYYY format.

emailstring required

Email address (must be unique per nik).

phonestring required

Valid phone number, use country code but without symbol (+), (must be unique per nik).

selfie_photostring required

Selfie photo in base64 format, size min. 100 kB max. 4 MB, min pixel 640px x 480px.

ktp_photostring required

KTP photo in base64 format, size min. 100 kB max. 2 MB, min pixel 480px x 360px.

channelstring

Brand's name (will be used in email).

reference_idstring

Use to indicate your company's transaction (must be unique).

Response

Successful Response

messagestring required

Shows message of the response

Example response

{
  "message": "Certificate Electronic has been done",
  "data": {
    "id": "8e31a91c-7437-4ed1-b086-06cbe247d6e7",
    "status": "verified",
    "reference_id": "ref_certel#e87c8bc2-5d10-455b-98a0-187d60f72873"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.