Indonesia Biometric Match

Overview

Indonesia's official national identification number used for identity verification. Verifies the 16‑digit National Identity Number against government records and returns confirmed personal details.

  • ID: indonesia-dukcapil-match
  • Type: eID (database)
  • Verification Type: Match
  • Regions: Asia
  • Countries: ID
  • Adoption: 220,000,000
  • URL: https://vida.id/

Integration with Trinsic

Indonesia Biometric match verification allows businesses to verify name, date of birth, NIK number, phone number, and a selfie against the government system of record in Indonesia.

User Flow

Indonesia Biometric Match requires the user to input some data about themselves into a form. A match against the system of record is then completed against the data. To see a demo of this flow, visit this link.

Customers can bypass the form-fill step by passing in known identity data about the user when launching the integration.

How to Test

While using a Verification Profile in the Test Environment, launch the Trinsic Widget or launch the Provider directly.

  • Enter the following test data:
    • Full Name: UserGDAA
    • Date of Birth: 1980-01-01
    • NIK ID Number: 3511000101806300
    • Phone Number: +6281312345678
    • Selfie
      • Upload any image which contains a detectable human face.
  • Consent & Submit.
  • At the end, you will be presented with test data for the verification session.


Direct API Requirements

📘

Direct is not a requirement.

You can integrate with this provider using the Widget or Hosted UI instead, with no additional integration requirements on your end.

What your integration must support in order to use this provider with the Direct Provider Sessions API.

  • Supports Direct Provider Sessions: ✅
  • Launch Method: None — No user-facing action is required to start the flow.
  • Collection Method: PollResult — Results arrive asynchronously; poll with the resultsAccessKey returned at session creation.
  • Requires Input: This provider requires input before verification can proceed.
  • Trinsic-Hosted UI: A Trinsic-Hosted Fallback UI exists for this provider, which may be invoked to cover gaps in your integration's capabilities.

Outputs

ℹ️

Normalized Attributes

These attributes form part of our normalized model, a standardized set used across providers. Trinsic normalizes this for you and lets you know when a property is available for each provider.

FieldAvailabilityNotes
person.fullNameAlways-
person.dateOfBirthAlways-
document.typeAlways-
document.numberAlways-
match.nationalIdNumberAlways-
match.fullNameAlways-
match.dateOfBirthAlways-
match.faceMatchSometimesIf biometric match is enabled
match.livenessSometimesIf biometric match is enabled
match.imageAuthenticitySometimesIf biometric match is enabled
attachments.selfieSometimesIf biometric match is enabled
attachments.documentFrontSometimesIf provided

Frequently Asked Questions

Is the selfie always required?

No, the integration can be configured to include the biometric match, or only match the demographic attributes.