BOIVA
IDENTITY VERIFICATION FOR INDONESIA

Your Complete Identity Verification Ecosystem

Integrate IDVB for identity-data matching, IDVS for identity and selfie comparison, or IDVC for a comprehensive flow with selfie and liveness signals.

IDVB · Data matchIDVS · Selfie matchIDVC · Liveness signals
OJKBSIPSEFintech Indonesia
Explore Identity Verification Login View Documentation

Organizations using the Brick verification ecosystem

ACC One
Advance AI
Akar Inti Data
CTBC Bank
JULO
Orderfaz
Tribelio
ACC One
Advance AI
Akar Inti Data
CTBC Bank
JULO
Orderfaz
Tribelio

VERIFICATION SUITE

IDVB, IDVS, and IDVC: three precise levels of identity verification

Start with identity-data matching, add selfie comparison when you need a biometric signal, or use the comprehensive flow for identity, selfie, and liveness checks. All three products use the same documented API pattern.

Identity Verification Basic
IDVB

Identity Verification Basic

Foundational identity-data checks for workflows that do not require a selfie or liveness signal.

Foundational data check

Included checks

  • Structured field-level results
  • No selfie required
  • Consistent API response
View IDVBRead the guide
Identity Verification with Selfie
IDVS
Extended assurance

Identity Verification with Selfie

Adds selfie comparison to the identity-data checks when your workflow requires a biometric signal.

Adds a biometric signal

Included checks

  • Identity-data verification
  • Selfie comparison
  • Additional review signal
View IDVSRead the guide
Identity Verification Comprehensive
IDVC

Identity Verification Comprehensive

Combines identity data, selfie comparison, and liveness signals for workflows that require layered verification.

Layered verification workflow

Included checks

  • Identity-data verification
  • Selfie and liveness signals
  • Structured verification outcome
View IDVCRead the guide

Industry workflows

Apply the right checks at the right decision point

BOIVA provides verification building blocks. Your team remains responsible for the business decision, policy, and regulatory process around each result.

Banking & Financial Services

Combine identity checks with your customer onboarding and review workflow.

Customer onboarding
Banking & Financial Services

Fintech & E-Commerce

Add identity signals to account opening and transaction-risk workflows.

Account verification
Fintech & E-Commerce

Insurance

Support policy applications and claimant verification with structured results.

Policyholder checks
Insurance

Multi Finance

Validate applicant identity data before financing decisions move forward.

Applicant verification
Multi Finance

ONBOARDING WORKFLOW

Build a verification path your team can explain

Start with the checks your use case needs, add stronger signals when risk or policy requires them, and keep the outcome available to your application for follow-up decisions.

  • Multi-level identity verification (IDVB, IDVS, IDVC)
  • Selfie matching and liveness signals where required
  • Configurable multi-step verification flows
  • Reference IDs and structured result statuses
User verifying identity documents on laptop

99.9%

Identity Verification Accuracy

15M+

Identities Verified

200+

Enterprise Clients

95%

Faster KYC Onboarding

Trust by design

Clear controls for implementation and review

BOIVA is designed around authenticated access, structured results, documented integration, and separated environments. Product outputs support your workflow; they do not replace your organization's own compliance and risk decisions.

Authenticated API access

Token-based requests keep verification endpoints separate from public website traffic and associate usage with the calling organization.

Traceable request lifecycle

Reference identifiers and status responses give implementation teams a consistent way to follow each verification request.

Documented integration

Authentication, verification requests, response fields, and error handling are documented for teams building and operating the integration.

Environment separation

Keep test activity and credentials separate from production so teams can validate workflows without mixing operational data.

DEVELOPER FIRST

Built for Seamless Integration

Use the documentation to prepare authentication, send a verification request, interpret each response field, and handle errors explicitly in your application.

See API Docs
POST /b2b/v1/identity-verification
1{
2 "type": "IDVB",
3 "ktp": "3275012345678901",
4 "fullname": "BUDI SANTOSO",
5 "birth_date": "1995-06-15"
6}
7
8200 OK
9{
10 "ktp": true,
11 "fullname": true,
12 "birth_date": true
13}

Brick Ecosystem Partner Voices

Trusted collaboration, built around identity

Sumsub

"Brick has been an exceptional partner to Sumsub. Our collaboration brought a perfect innovation for user verification, making the entire experience seamless and impactful."

Tee Kok Ong

Tee Kok Ong

Director APAC

VIDA

"Brick Teknologi Indonesia is a company that brings current technology innovations and solutions to support Indonesia's digital progress."

Dedy Tri Cahyono

Dedy Tri Cahyono

VIDA Channel Manager

Product answers

BOIVA identity verification, explained clearly

Compare the three available products and understand the integration path before you speak with our team.

Read all product FAQs
What is BOIVA?

BOIVA is an identity verification API platform for businesses operating onboarding and customer-verification workflows in Indonesia. It offers three products: IDVB, IDVS, and IDVC.

What is the difference between IDVB, IDVS, and IDVC?

IDVB matches core identity data without a selfie. IDVS adds selfie comparison to identity-data verification. IDVC combines identity-data verification, selfie comparison, and liveness signals in a comprehensive flow.

Which BOIVA product should I use?

Use IDVB when your workflow only needs identity-data matching. Choose IDVS when you also need a selfie comparison. Choose IDVC when your process requires layered identity, selfie, and liveness signals. Your organization remains responsible for its final policy and risk decisions.

How do developers integrate BOIVA?

Developers use a Client ID and Client Key to generate a public access token, then POST to /b2b/v1/identity-verification with type set to IDVB, IDVS, or IDVC. Credentials should remain in a protected server-side environment.

Plan your verification workflow with BOIVA

Compare IDVB, IDVS, and IDVC, then share your expected volume and integration requirements through the existing form.

Find a solutionCompare Products