BOIVA

Getting started

From identity requirement to production integration

A practical path for product, engineering, QA, security, and risk teams adopting BOIVA identity verification.

Explore solution optionsRead developer guide

Phase 01

Choose the verification scope

Map the decision to IDVB, IDVS, or IDVC. Define required evidence, exceptions, and who owns the final review.

Phase 02

Activate sandbox access

Register for the sandbox environment and coordinate account activation and credentials with the BOIVA team.

Phase 03

Integrate server-to-server

Generate a one-hour public token, send a verification request, and handle every documented field and error path.

Phase 04

Complete SIT and UAT

Exercise the selected APIs in sandbox, validate operational handling, and complete the documented readiness process.

Phase 05

Move to production

Use production credentials and change the API base URL from sandbox.boiva.id to api.boiva.id.

Sandbox

Test and development

https://sandbox.boiva.id

Production

Live applications with production credentials

https://api.boiva.id

Keep credentials environment-specific and server-side. Never copy sandbox credentials into production or expose Client ID, Client Key, or public tokens in frontend code.