BOIVA

IDVC · Layered verification for higher-assurance flows

Bring identity, selfie, and liveness signals into one decision flow

IDVC combines Indonesian identity-data matching, selfie comparison, and a liveness confidence score in one comprehensive verification request.

Discuss IDVCRead API reference

Product promise

BOIVA's broadest documented identity verification scope for customer journeys that need layered evidence.

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

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

Clear inputs. Clear signals. Clear responsibility.

IDVC 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: IDVC
  • 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
  • Selfie liveness confidence score
  • Additional documented identity attributes

Not included

  • A replacement for your compliance, fraud, or credit decision

Where it fits

Use IDVC where its evidence matches the decision

Regulated digital onboarding
Higher-risk account activation
Sensitive account recovery
Step-up checks for high-value actions

Response design

Give your workflow evidence it can act on

  • Field-level identity and selfie results
  • selfie_liveness score
  • Structured JSON ready for your risk and review orchestration

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 IDVC

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

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