Purpose: Investigate flagged transactions. Cases are auto-created when rules trigger, or manually created by compliance officers.Documentation Index
Fetch the complete documentation index at: https://ratel-docs.bevars.com/llms.txt
Use this file to discover all available pages before exploring further.
| Action | Endpoint | Who Can Do It |
|---|---|---|
| Create case | POST /api/v1/cases | SUPER_ADMIN, BANK_ADMIN, COMPLIANCE_OFFICER, ANALYST |
| List cases | GET /api/v1/cases | All authenticated users |
| Get case detail | GET /api/v1/cases/:id | All authenticated users |
| Update status | PATCH /api/v1/cases/:id/status | SUPER_ADMIN, BANK_ADMIN, COMPLIANCE_OFFICER |
| Assign case | PATCH /api/v1/cases/:id/assign | SUPER_ADMIN, BANK_ADMIN, COMPLIANCE_OFFICER |
| Add note | POST /api/v1/cases/:id/notes | All authenticated users |
| Type | When It’s Created |
|---|---|
SUSPICIOUS_TRANSACTION | Transaction BLOCKED by screening |
AML_ALERT | Transaction ESCALATED |
SANCTIONS_HIT | Sanctions list match detected |
PEP_MATCH | Politically Exposed Person matched |
FRAUD_ALERT | Behavioral anomaly detected |
KYC_REVIEW | KYC verification issue |
REGULATORY_INQUIRY | Manual regulatory investigation |
BEHAVIORAL_ANOMALY | Device/velocity anomaly flagged |

