Overview
TXCloud’s verification flow is designed to be flexible, supporting both synchronous (instant) and asynchronous (session-based) verification patterns.Verification Methods
Instant Verification
Single API call with all images. Best for server-side integrations.
Session-Based
Multi-step upload flow. Best for mobile apps and web frontends.
Instant Verification Flow
Use this when you have all documents ready to submit at once:Session-Based Flow
Use this for mobile apps where users capture documents step-by-step:Step 1: Create Session
Step 2: Upload Documents
Step 3: Complete Session
Verification Checks
Each verification can include multiple checks:| Check | Description | Time |
|---|---|---|
ocr | Extract text from document | ~1s |
face_match | Compare selfie to document photo | ~1s |
liveness | Detect if selfie is from live person | ~1s |
fraud | Check for document tampering | ~2s |
data_validation | Validate extracted data formats | ~0.5s |
age_verification | Verify user meets minimum age | ~0.5s |
Verification Statuses
| Status | Description | Final? |
|---|---|---|
pending | Processing in progress | No |
verified | All checks passed | Yes |
failed | One or more checks failed | Yes |
expired | Session expired before completion | Yes |
cancelled | Verification was cancelled | Yes |
manual_review | Requires human review | No |
Handling Results
Best Practices
Validate Images Before Upload
Validate Images Before Upload
Check image quality client-side:
- Minimum resolution: 1280x720
- File size: Under 10MB
- Format: JPEG or PNG
- No blur or glare
Use Webhooks for Async
Use Webhooks for Async
Don’t poll — use webhooks for real-time updates on session-based verification.
Handle All Statuses
Handle All Statuses
Implement handlers for every possible status, including edge cases like
expired.Store Verification IDs
Store Verification IDs
Always store the verification ID for future reference and audit trails.