BOIVA

Compare IDVB, IDVS, and IDVC identity verification

Select identity-data matching, add selfie comparison, or use a comprehensive flow with selfie and liveness signals—all through BOIVA's documented API.

Compare the Three ProductsExplore solution options

Product comparison

Choose the smallest verification scope your workflow needs

Each product has a defined input and verification scope. Choose the smallest set of signals your workflow requires, then process the documented result in your own decision logic.

IDVB

Identity Verification Basic

For workflows that need identity-data matching without a selfie.

Typical use cases:

  • Early onboarding
  • Account registration
  • Data-match checkpoints

Documented inputs and signals:

  • Required: type, ktp, and fullname
  • Optional: birth_date
  • No selfie required
POST /b2b/v1/identity-verification
type: "IDVB"
Explore IDVB in detail Canonical API reference
IDVS

Identity Verification with Selfie

For workflows that need identity-data matching plus a selfie comparison signal.

Typical use cases:

  • Onboarding with selfie capture
  • Identity and face comparison
  • Step-up verification

Documented inputs and signals:

  • Required: type, ktp, fullname, and selfie_photo
  • Optional: birth_date and birth_place
  • JPG, JPEG, or PNG selfie up to 5 MB
POST /b2b/v1/identity-verification
type: "IDVS"
Explore IDVS in detail Canonical API reference
IDVC

Identity Verification Comprehensive

For workflows that require identity data, selfie comparison, and liveness signals together.

Typical use cases:

  • Layered onboarding checks
  • Customer verification workflows
  • Step-up review paths

Documented inputs and signals:

  • Identity-data verification
  • Selfie and liveness signals
  • Structured verification outcome
POST /b2b/v1/identity-verification
type: "IDVC"
Explore IDVC in detail Canonical API reference

One API pattern, three verification scopes

Not every onboarding path requires the same identity signals.

IDVB covers identity-data matching without a selfie. IDVS adds selfie comparison. IDVC combines identity data, selfie comparison, and liveness signals.

Choose by required input and output. Map each product to a clear decision point in your onboarding flow and document how your application handles the result.

Use IDVB for data matching. It accepts core identity fields and does not require a selfie.

Use IDVS when a selfie comparison is required. It extends the identity-data request with a biometric comparison signal.

Use IDVC when the workflow requires identity data, selfie comparison, and liveness signals together. Your organization remains responsible for the final policy and decision.

Why Identity Verification Is a Business Problem

Identity verification isn't a technical checkbox. It's a fundamental business risk that impacts every organization that interacts with users, customers, or partners. As your business scales, the cost of getting identity wrong increases exponentially.

Fraud risk increases as businesses scale. Every new user represents a potential security vulnerability. Without proper identity checks, fraudsters exploit weak onboarding processes, leading to financial losses and operational disruption. The faster you grow, the more attractive you become as a target.

Regulatory exposure and compliance pressure. Regulators demand auditable identity verification processes. Whether it's KYC, AML, or industry-specific requirements, businesses that can't demonstrate proper identity checks face fines, sanctions, and reputational damage.

Cost of manual verification. Reviewing identity documents manually doesn't scale. It's expensive, slow, and error-prone. As your business grows, manual verification becomes a bottleneck that slows customer acquisition and increases operational costs.

Poor-quality users and customers. Weak identity checks attract fraudsters and low-quality users who drain resources without contributing value. Your customer acquisition costs increase while your revenue per user decreases.

Reputational damage from weak identity checks.When fraud happens because identity verification failed, customers lose trust. News of security breaches or identity theft spreads quickly, damaging brand reputation and customer relationships that took years to build.

The question isn't whether your business needs identity verification. It's how to implement it in a way that balances security, compliance, and growth.

How Businesses Use IDV Strategically

Identity verification isn't one-size-fits-all. Smart businesses use different verification levels strategically, matching verification rigor to business risk and user context.

Start with IDVB → upgrade as risk increases

Many businesses begin with basic data verification for all users, then upgrade specific users to IDVS or IDVC when they engage in higher-risk activities, like large transactions, account changes, or accessing sensitive features.

Different verification levels for different customer segments

Segment your users by risk profile. Low-risk segments might use IDVB for fast onboarding. High-risk segments, like financial services users or enterprise customers, might require IDVC from the start to meet compliance requirements.

Align verification cost with business risk

Use IDVB for high-volume, low-risk flows where cost efficiency matters. Use IDVS for moderate-risk scenarios where identity assurance is important but full KYC isn't required. Reserve IDVC for regulated flows and high-value transactions where compliance and auditability are non-negotiable.

The goal is simple: match your verification investment to your business risk, so you're neither over-spending on unnecessary verification nor under-investing in critical identity assurance.

Built for Trust, Accountability, and Growth

BOIVA's core philosophy: identity verification must be explainable, traceable, and scalable. Every verification decision supports your business goals: reducing fraud, meeting compliance, and building trust with customers and regulators.

Identity Decisions Must Be Explainable

Every verification result includes clear reasoning. When verification fails or succeeds, your team understands why. No black boxes, no unexplained outcomes.

Verification Results Must Support Audits and Reviews

Complete audit trails for every verification request. Reference IDs, timestamps, and verification outcomes support compliance audits and regulatory reporting.

Trust Must Scale with the Business

BOIVA is built as a long-term identity partner, not just a tool. As your business grows and your verification needs evolve, BOIVA scales with you, from startup to enterprise.

Position BOIVA as a long-term identity partner, not just a verification tool. Build verification strategies that support your business today and scale as you grow.

Who This Is For

BOIVA serves organizations that require reliable, compliance-ready identity verification, from startups building their first verification workflows to enterprises managing complex regulatory requirements.

Financial Services

Banks, credit unions, and financial institutions that require KYC-compliant identity verification for account opening, transactions, and regulatory reporting.

Fintech & Digital Platforms

Financial technology companies and digital platforms operating in regulated markets where identity verification is essential for compliance and trust.

Marketplaces

Online marketplaces that need to verify both buyers and sellers to reduce fraud, build trust, and meet regulatory requirements.

Enterprises Handling Sensitive Data

Large organizations operating in regulated industries where identity verification is essential for risk management, compliance, and protecting sensitive user data.

Clear Next Steps

Review the required fields and response format for IDVB, IDVS, and IDVC. Then choose the product whose verification scope matches your onboarding decision point.

Compare IDVB, IDVS, and IDVCExplore solution optionsView Documentation