Overview
After a customer completes their KYC verification, you can query the results to check the verification status, extracted data, and decision details. This is useful for:- Checking if verification is complete
- Retrieving verified customer information
- Getting verification results and risk assessment
- Auditing verification history
While you can poll this API, we strongly recommend using webhooks to receive real-time notifications when verification completes.
Get Validation by ID
Retrieve a specific validation using its ID:Endpoint
Example
Get Current Validation for Entity
If you don’t have the validation ID, retrieve the current active validation for a person entity:Endpoint
Example
Get Entity KYC Status
Get a summary of an entity’s KYC verification status:Endpoint
Response
Example
Understanding Validation Results
Status Values
Current validation status:
pending- Validation created, waiting for customer to startin_progress- Customer is actively completing verificationapproved- Verification successful, identity confirmedrejected- Verification failed, identity not confirmedexpired- Verification session expired (typically after 7 days)abandoned- Customer started but didn’t complete verification
Decision Object
When status isapproved or rejected, the decision field contains detailed results:
Verification Results
Each verification check has a result:| Check | Description | Possible Values |
|---|---|---|
documentAuthenticity | Is the document genuine? | pass, fail, pending |
faceMatch | Does selfie match document photo? | pass, fail, pending |
liveness | Is the person real (not a photo/video)? | pass, fail, pending |
aml | Sanctions/watchlist screening | clear, match, pending |
Extracted Data
UseextractedData to update customer records with verified information:
List All Validations for Entity
Get the complete verification history for an entity:Endpoint
Response
Sync Validation Status
If you suspect the validation status is out of sync with the identity provider, trigger a manual sync:Endpoint
Example
Common Integration Patterns
Pattern 1: Check Before Allowing Action
Pattern 2: Conditional Features Based on Verification
Pattern 3: Periodic Re-verification Check
Best Practices
Use Webhooks, Not Polling
Use Webhooks, Not Polling
Instead of repeatedly checking validation status, use webhooks to receive real-time notifications. This is more efficient and provides better user experience.
Cache Verification Status
Cache Verification Status
Store the verification status in your database and update it via webhooks. Don’t query the API on every request.
Handle Expired Verifications
Handle Expired Verifications
Verifications may expire after a certain period (typically 1 year). Check
needsReverification and prompt customers to reverify when necessary.Store Validation IDs
Store Validation IDs
Always store the validation ID in your database linked to the customer. This allows you to audit verification history and retrieve detailed results later.