IDVB · Fast, focused identity-data matching

Confirm Indonesian identity data without adding a selfie step

IDVB matches NIK, full name, and date-of-birth data against official citizenship records through BOIVA's unified verification API.

Discuss IDVB Read API reference

Product promise

A lean verification layer for teams that need reliable identity-data matching with minimal onboarding friction.

POST /b2b/v1/identity-verification
type: "IDVB"

One verification endpoint

Switch the documented type value to match the verification scope your journey needs.

Built for API workflows

Use sandbox for integration and testing, then move to the production base URL with separate credentials.

Decision-ready signals

Consume explicit response fields in your own policy instead of relying on an opaque, universal verdict.

What IDVB verifies

Clear inputs. Clear signals. Clear responsibility.

IDVB includes the request inputs and returned signals listed below. It does not include the scope-boundary items in the final card.

Included: request inputs

type: IDVB
ktp (NIK)
fullname
birth_date in yyyy-mm-dd format (optional)

Included: returned signals

NIK match
Full-name match
Birth-date match or derived result
Normalized indicator when an inferred date differs from official records

Not included

Selfie comparison
Liveness score

Where it fits

Use IDVB where its evidence matches the decision

Early-stage onboarding

Account registration

Profile validation

Data-match checkpoints before a higher-assurance step

Response design

Give your workflow evidence it can act on

Field-level status for ktp, fullname, and birth_date
A normalized flag in documented date-of-birth discrepancy scenarios
Structured JSON for downstream policy logic

Integration path

From sandbox to a production-ready flow

Authenticate server-to-server

Generate a public access token with your Client ID and Client Key. The token is valid for one hour.

Send the verification request

POST to the unified identity-verification endpoint and set the type field to the product code you selected.

Apply the returned signals

Use the field-level results in your own onboarding, review, or risk policy. BOIVA provides verification signals; your organization owns the final decision.

Open the BOIVA integration guide

Related guide

Plan the workflow around IDVB

Use the practical guide to connect this product scope with capture, integration, exception handling, and business decision design.

Identity verification API guide

Compare the suite

Need a different level of verification?

BOIVA lets you align the verification scope to each customer journey instead of forcing every user through the same flow.

Explore IDVS Explore IDVC