Introducing VIDA Identity Stack: All of VIDA, in one place 🎉
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Deduplication Check

Purpose

VIDA's 1:N Deduplication prevents duplicate accounts by searching new applicants against a reference gallery for:

  1. Same ID — duplicate ID Number

  2. Same Face — duplicate portrait image across prior onboardings in the database

This prevents fraud (repeat sign-ups for promos / credit abuse, synthetic or mule recycling) and reduces Ops workload by automatically denying or routing suspicious repeats.

The feature ensures that each ID Number (idNumber) is uniquely associated with a single face image. It helps prevent duplicate enrollments or multiple identities being tied to the same face or ID number.

Supported Cards

Deduplication Check is available for the following ID cards only:

Country
ID Card
Sides Required

Indonesia

KTP

Front

Malaysia

MyKAD

Front + Back

Malaysia

MyPR

Front + Back

Malaysia

MyKAS

Front + Back

Malaysia

MyTentera

Front + Back

Flow

  1. Trigger Condition The duplication check is executed after all other verification operations (such as OCR and ID verification) have completed successfully — that is, no prior step should return an error. The OCR operation is mandatory to trigger this check.

  2. Data Used

    • The ID Number and face portrait are obtained from the OCR operation results.

    • Both values are required to perform the 1:N de-duplication check.

    For Indonesian KTP, the ID Number used is the NIK returned by the KTP OCR operation.

  3. Execution Steps

    The system searches for existing records with either:

    1. The same face image (mapped to multiple ID Numbers), or

    2. The same ID Number (mapped to multiple face images).

    If a duplicate is detected, a relevant warning or error response is returned.

API Description

POST https://{vida-host}/api/v2/verify

Headers

Name
Type
Description

Content-Type

application/json

Format type of request body

Authentication*

String

Bearer <Token>

Request Body

Malaysian ID Card (Front Side & Back Side)

Request for Front Side and Back Side

Indonesian ID Card (Front Side Only

Request for Front Side and Back Side

KTP is a single-sided document, so idBackSideImage is not required. The response will also contain a front object only inside imageQualityResult and ocrResult.

Success Response

HTTP Status Code : 200

Malaysia

Success JSON Response for Front Side and Back Side - No Duplicate Found
Success JSON Response for Front Side and Back Side - With Warning

Indonesia

Success JSON Response - No Duplicate Found
Success JSON Response - With Warning

Returned when the face on the KTP is already associated with a different ID Number. The transaction still succeeds, but the client should route it for review.

Error Response

HTTP Status Code : 400

Malaysia

Error JSON Response for Front Side and Back Side - With Error

Indonesia

Returned when the ID Number is already associated with a different face. Verification fails.

Error JSON Response - With Error

Last updated