Case vs Profile
Relationship Between Profiles and Sessions
Profiles and Case/sessions work together:
- A profile persists identity information long-term.
- A session represents a single verification attempt.
- Multiple sessions can be linked to the same profile.
- Sessions inherit their workflow configuration from templates but reference the profile for identity context.
Example Flow
- Create profile
- Update details as needed
- Run verifications against the profile
- Receive results, warning codes, and risk scoring
- Re-run verification later for periodic review
- This unlocks continuous compliance without re-collecting data from scratch.
Profile vs. Session (Common Comparison)
| Feature | Case (Session) | Profile |
|---|---|---|
| Scope | Single verification workflow | Long-term identity management |
| Identity Storage | No persistent identity record | Complete identity record maintained |
| Re-verification | New session required | Can run multiple verifications |
| Document Storage | Session-linked only | Persistent document library |
| AML Monitoring | Continuous monitoring | Continuous monitoring |
| Historical Tracking | Single result snapshot | Full verification history |
| Use Case | One-time verification | Ongoing customer relationship |
| Lifecycle | Create → Process → Complete | Create → Verify → Monitor → Update → Deactivate |
| Risk Scoring | One-time calculation | Recalculated on updates |
| Compliance Reporting | Single event | Audit trail across all activities |
Updated about 7 hours ago