BOIVA

IDVS · Identity data plus face comparison

Connect identity data to the person presenting it

IDVS adds a required selfie comparison to NIK and full-name verification, helping teams strengthen digital onboarding without building separate identity and face-match integrations.

Discuss IDVSRead API reference

Product promise

One request for identity-data matching and a selfie comparison signal, designed for Indonesian customer journeys.

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

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 IDVS verifies

Clear inputs. Clear signals. Clear responsibility.

IDVS 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: IDVS
  • ktp (NIK)
  • fullname
  • selfie_photo as Base64
  • birth_date in yyyy-mm-dd format (optional)
  • birth_place (optional)

Included: returned signals

  • NIK, name, and birth-data match
  • Selfie comparison against the registered identity image
  • Gender and address fields documented in the response
  • Normalized indicator for applicable birth-date scenarios

Not included

  • Liveness confidence score

Where it fits

Use IDVS where its evidence matches the decision

Digital account opening
Selfie-assisted onboarding
Step-up identity checks
Account recovery with an identity comparison step

Response design

Give your workflow evidence it can act on

  • Field-level identity match results
  • selfie_photo match status
  • Structured identity attributes and normalization status when applicable

Integration path

From sandbox to a production-ready flow

1

Authenticate server-to-server

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

2

Send the verification request

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

3

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 IDVS

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

Selfie verification 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 IDVB Explore IDVC