How it works
- You define rules with conditions that describe suspicious patterns (e.g., “withdrawal over $10,000 from a high-risk customer”).
- Each incoming transaction is evaluated against all active rules.
- When a rule matches, the configured actions fire — creating an alert, halting the transaction, or both.
- Your compliance team triages the resulting alerts in the Alerts queue.
Rule lifecycle
Every rule follows a three-stage lifecycle:| Status | Meaning |
|---|---|
| Draft | The rule is being authored or tested. It does not evaluate live transactions. |
| Active | The rule runs against every incoming transaction in real time. |
| Disabled | The rule is paused. It can be re-activated at any time. |
Two ways to create rules
Start from a template
Browse Corsa’s library of pre-built templates for common compliance scenarios and copy one into your workspace as a draft.
Build from scratch
Use the no-code Rule Builder to define custom conditions, configure alert priority, and test before activating.
Two ways to interact
You can manage rules through the Corsa dashboard (no-code Rule Builder) or programmatically through the REST API and SDKs.| Approach | Best for |
|---|---|
| Dashboard | Compliance analysts building and testing rules visually. |
| API / SDK | Engineering teams automating rule management, CI/CD pipelines, or bulk operations. |
Explore this section
Rule templates
Browse and copy pre-built rules for common compliance scenarios.
Building rules
Walk through the Rule Builder wizard step by step.
Conditions reference
Operators, entities, aggregations, time windows, and actions.
Testing rules
Validate rules against historical transactions before going live.
Rules & Evaluation API
Manage rules and evaluate transactions programmatically.