Verification Session Flows
How Remllo verification sessions fit into your onboarding path when users or businesses need identity checks.
Section
When to use session-based flows
Use session-based verification when your product needs a structured KYC or KYB flow with status tracking, evidence handling, and webhook updates.
- retail onboarding where identity checks must be created and tracked consistently
- business onboarding where company records and screening checks must be reviewed
- API-led onboarding where your backend owns the customer experience and Remllo owns verification orchestration
Section
Recommended integration shape
- your platform creates a verification session
- your backend or console flow submits the required verification data and evidence
- Identity processes the flow and updates verification status
- webhooks notify your backend when the profile is approved, rejected, or needs review
Section
What stays in Identity
- raw documents
- biometric evidence
- provider responses
- manual review artifacts
WatchTower boundary
When Identity is linked to WatchTower, only investigation-safe summaries should cross into monitoring. Raw onboarding artifacts remain in Identity.
Next UpIdentity Console
Continue Through The DocsIdentity Documentation