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.

Permission required: Yes, this method requires registration before you can activate it for your users. Please contact Trinsic to begin this process.
Cost: Contact the Trinsic team.

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 API is not a requirement.
You can integrate with this provider using the 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.

Field	Availability	Notes
`person.fullName`	Always	-
`person.dateOfBirth`	Always	-
`document.type`	Always	-
`document.number`	Always	-
`match.nationalIdNumber`	Always	-
`match.fullName`	Always	-
`match.dateOfBirth`	Always	-
`match.faceMatch`	Sometimes	If biometric match is enabled
`match.liveness`	Sometimes	If biometric match is enabled
`match.imageAuthenticity`	Sometimes	If biometric match is enabled
`attachments.selfie`	Sometimes	If biometric match is enabled
`attachments.documentFront`	Sometimes	If provided

Field	Optional	Description	Example Values
`nationalIdNumber.inputValue`	Yes	The NIK (Nomor Induk Kependudukan) submitted for this check. NIK is Indonesia's unique population identity number, issued by Indonesia's population administration and civil registration authority (Dukcapil) under the Ministry of Home Affairs. Format: - 16 numeric digits. - Digits 1-2 are the province code. - Digits 3-4 are the regency or city code within that province. - Digits 5-6 are the district code within that regency or city. - Digits 7-12 encode date of birth as DDMMYY. For female NIK holders, the day is increased by 40. - Digits 13-16 are an issuance serial number.	3171017101800001
`nationalIdNumber.outcome`	Yes	The provider assessment result for the submitted NIK. Local integration code expects the provider to return 0 or 1 for this assessment.	1
`fullName.inputValue`	Yes	The full name submitted for this check.	Siti Aminah
`fullName.outcome`	Yes	The provider assessment result for the submitted full name. Format: numeric score from 0.0 to 1.0, where higher values indicate closer agreement with the Dukcapil record.	0.98
`dateOfBirth.inputValue`	Yes	The date of birth submitted for this check.	1980-01-31
`dateOfBirth.outcome`	Yes	The provider assessment result for the submitted date of birth. Local integration code expects the provider to return 0 or 1 for this assessment.	1
`provinceCode`	Yes	Two-digit Indonesian government administrative region code for the province, extracted from digits 1-2 of the submitted NIK number. Source system: Kode Wilayah Administrasi Pemerintahan, maintained by Indonesia's Ministry of Home Affairs. The first digit indicates the island group: 1-2 Sumatra, 3-4 Java, 5 Bali and Nusa Tenggara, 6 Kalimantan, 7 Sulawesi, 8 Maluku, and 9 Papua. The second digit follows the province creation order.	31
`regencyOrCityCode`	Yes	Four-digit Indonesian government administrative region code for the regency or city, extracted from digits 1-4 of the submitted NIK number. Source system: Kode Wilayah Administrasi Pemerintahan, maintained by Indonesia's Ministry of Home Affairs. Format: two-digit province code followed by a two-digit regency or city sequence; suffixes 01-69 identify regencies and suffixes 71-99 identify cities. The NIK stores this value without dot separators.	3171
`districtCode`	Yes	Six-digit Indonesian government administrative region code for the district (kecamatan), extracted from digits 1-6 of the submitted NIK number. Source system: Kode Wilayah Administrasi Pemerintahan, maintained by Indonesia's Ministry of Home Affairs. Format: two-digit province code, two-digit regency or city code, and two-digit district sequence. The NIK stores this value without dot separators.	317101
`sexNationalIdNumber`	Yes	Sex extracted from the birth-day portion of the submitted NIK number. Known values: - Male: The encoded day value is 40 or lower. - Female: The encoded day value is greater than 40.	Female
`serialNumber`	Yes	Four-digit issuance serial number extracted from digits 13-16 of the submitted NIK number.	0001
`phoneNumber`	Yes	The phone number submitted for this verification, if provided. Format: international E.164 phone number.	+6281234567890
`consentGivenAt`	Yes	The consent timestamp submitted for this verification.	2026-01-31T08:30:00+07:00
`email`	Yes	The email address submitted for this verification, if provided.	[email protected]

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.