Customer Preferences
The Customer Preferences module allows institutions to configure how the AI Compliance Agent behaves for their specific operational and regulatory context.
Configurable Preferences
| Preference | Description |
|---|---|
| Risk Tolerance | Conservative, balanced, or progressive compliance posture |
| Auto-Approve Thresholds | Transaction amounts below which compliance is automatic |
| Manual Review Triggers | Conditions that always escalate to human review |
| Jurisdiction Restrictions | Block or flag transactions involving specific jurisdictions |
| Asset Restrictions | Block or flag specific token types |
| Data Sharing Preferences | Which identity fields to share by default vs. on-request |
| Notification Settings | How and when to receive compliance alerts |
How Preferences Are Applied
- Institution configures preferences via the CRYMBO Platform
- Preferences are stored and associated with the institution's Oracle profile
- Every transaction involving the institution is processed through the AI Compliance Agent with these preferences applied
- Preferences can be updated at any time — changes take effect immediately
Default vs. Custom
New institutions start with CRYMBO's default compliance profile, which follows conservative best practices. Institutions can then customize based on their regulatory requirements and risk appetite.