Case Types
AiPrise supports two verification patterns. Both rely on the same case structure, but differ in how data is stored and reused.
Independent Cases
A one-time verification where no persistent profile is created. Best for:
- One-off checks
- High-value transaction checks
- Guest users
- Lightweight onboarding flows
Characteristics:
- Data stored only within the case
- No long-term profile maintenance
- Each new verification = new case
- Result delivered via callback
Profile-Based Cases
A case linked to a persistent User Profile or Business Profile. Best for:
- Ongoing customer relationships
- Multi-step onboarding
- Periodic re-verification
- AML monitoring
- KYB with UBOs, officers, subsidiaries
Characteristics:
- Profiles persist across multiple verifications
- You can update profile data anytime
- Each case becomes part of the profile’s history
- Allows continuous monitoring and repeated checks
Updated about 7 hours ago
