How an identity verification API supports digital decisions

Choose the required signals

Begin with the decision your workflow must support. BOIVA IDVB matches identity data, IDVS adds selfie comparison, and IDVC combines identity data, selfie comparison, and liveness signals.

• Use IDVB when identity-data matching is sufficient.
• Use IDVS when the workflow also needs a selfie comparison signal.
• Use IDVC when the workflow needs the comprehensive set of supported signals.

Design the integration boundary

Keep credentials and token generation on a trusted server. Your application should handle documented responses, error paths, timeouts, and manual review rules without exposing secrets in browser code.

Keep the final decision in context

Verification results are inputs to a business process. Each organization remains responsible for its compliance, policy, exception handling, and final risk decisions.

Recover from errors without weakening controls

Separate invalid input, authentication failure, service error, and inconclusive verification into different application states. Preserve a correlation reference, show users an actionable message, and route unresolved cases to an authorized review path.

• Retry only conditions documented as recoverable.
• Never expose provider internals or credentials in an error message.
• Measure technical failure separately from verification outcome.