Getting started¶
The VCSP service is meant to be integrated into the consumer business logic. The complexity of this integration will vary depending on the use case and the topology of the applications with which it interacts.
To simplify the integration process, the VCSP provides a number of tools and resources, including:
- This integration guide that provides step-by-step instructions for integrating the VCSP with different types of applications.
- A set of APIs that allow developers to programmatically integrate the VCSP with their applications.
- A support team that can help with any integration issues.
Before starting with the integration, please be aware of the following:
- Service Access: This service is accessible via Veridas' cloud platform, so an internet connection is required.
- Contract Agreement and Environment Provisioning: Once an agreement is reached with Veridas, a sandbox environment will be provisioned, along with the necessary access credentials like an API key.
- Audio/Face Capture Compliance: It's crucial to ensure that audio or face capture complies with the product's format requirements. This task can range from straightforward, like using Veridas’ face capture HTML/Android/IOS SDKs, to requiring dedicated resources, especially in specific scenarios like extracting audio from SBC/PBX systems .
- Subject Identification Strategy: A unique code for identifying subjects within the VCSP is required. Often, this identifier may already exist within the client's infrastructure, but you can use any existing identifier. This concept is called Identity Proofing, and it’s explained in the Stages of biometric authentication(1:1) or identification (1:N) section.
- Service integration: VCSP exposes an API that requires to be consumed from customers' systems, which requires some integration layer not provided by Veridas.
- Processing Results: The VCSP returns operation results in JSON objects. These results must be processed by the client to implement the business logic required for their use case.