Verification API
Coverage & Compliance Index

The uploaded document image is processed in memory for extraction and is not retained after the response is returned.

ID numbers are masked in logs and billing records, in line with the same masking standards used across Veriqos verification APIs.

Every image upload and response travels over TLS 1.2+, matching the transport security of all Veriqos endpoints.

Extraction should only be run on a document the end user has knowingly submitted, consistent with Veriqos consent guidance across all products.

Video sessions and captured document images are encrypted in transit and at rest, and access is limited to authorised compliance reviewers.

The customer's consent to the video KYC process is recorded as part of the session, alongside purpose and timestamp.

Recording and document retention periods are configurable, so you can align storage with your DPDP Act and internal compliance policies.

The verification flow is designed around what India's RBI Video-based Customer Identification Process guidelines expect — document capture, liveness and a live agent — so it fits into an existing V-CIP-based onboarding policy.

All insurance and vehicle data is stored in a secure, encrypted format to prevent unauthorised access or tampering.

Only approved systems and trusted team members can access sensitive policy information.

All API activity is tracked in real time to detect unusual behaviour or possible security risks.

The API follows industry and regulatory standards to keep insurance checks secure, reliable, and trustworthy.

PAN and company association details are encrypted in transit and at rest throughout the verification process.

Every association is validated against official registry records rather than cached or third-hand data.

Scoped API keys and IP allow-listing ensure only authorised systems can call the endpoint.

Every check is logged with a timestamp so compliance reviews can reconstruct any decision.

Verification only succeeds within the OTP's valid session window, limiting replay risk.

This API does not perform OTP or biometric Aadhaar authentication, so your integration stays inside what the offline verification framework permits.

Output is masked to the last four digits, in line with Section 8A of the Aadhaar Act and UIDAI's masking guidance.

Artefacts move over TLS 1.2 or higher and are encrypted at rest, and share codes are used in memory rather than retained.

Every request records consent and stated purpose, and retention windows are configurable so you can align the API with your DPDP Act policies.

Document contents are never transmitted, only the cryptographic hash.

Explicit signer consent is captured before every signature is applied.

Signing certificates are issued for a single transaction and are not reused.

The complete audit response is retained so signatures can be defended if challenged.

Selfies and document images are encrypted in transit and at rest.

Images are processed for the check and are not retained beyond the window you configure.

Consent is captured before any biometric capture takes place.

Every decision is logged with its score and reason so reviews can be reconstructed.

Every check records who verified which entity and when, for internal and external review.

If any suspicious activity or unusual behaviour is detected, the API triggers alerts.

The API keeps Aadhaar, PAN, and other government documents secure during the entire verification process.

All documents are fetched directly from the user's Digilocker account, from trusted government sources.

The API uses AI to detect unusual patterns or inconsistencies in UAN and mobile number records.

The API encrypts all UAN and mobile number information, preventing unauthorized access or changes.

Engineered to handle real-time bank responses, temporary network issues, and bank-side availability challenges.

Supports high-volume verification needs without compromising response time or accuracy.

Controlled access, encrypted data handling, and standardised verification processes.

Account validity and ownership checks are based on live banking responses, improving trust in every result.

All bank account details are transmitted using HTTPS and protected with strong encryption during processing.

Verification responses return masked bank account and IFSC details to protect user privacy.

The API is continuously monitored to identify unusual activity, misuse, or potential threats.

Only authorized applications and verified users can access verification services.

Only authorised users and systems can access the verification process.

Every signature is checked using the same rules to ensure reliable, repeatable results.

All data is encrypted during transfer, ensuring no one can access or modify it.

Built to meet major KYC, AML, and data protection standards for safe onboarding.

Frequent checks help identify risks early and strengthen overall security.