Case Management
When a decision comes back review or block, the system opens a case automatically. The case is assigned to an analyst who reviews the evidence (decision signals, transaction history, KYC data) and takes an action: confirm the decision, override it, escalate, or start a suspicious activity report. Closing the case finalises the audit trail.
Case management has no integration API. The queue, assignment, decision approval and closure are driven from the panel only. This page describes the capability; do not look for an endpoint to wire into your integration.
The part that concerns your integration
A case is born from your call: when the decision API returns review or block, a case is opened in the background. So the only thing you have to get right on the integration side is interpreting the decision.
| Decision | On your side | In the panel |
|---|---|---|
allow | Continue the flow | No case is opened |
review | Hold the transaction, tell the user | A case is opened and queued to an analyst |
block | Reject the transaction | A case is opened and written to the audit trail |
Do not quietly treat review as allow. If a case is open in the panel but the transaction already went through on your side, whatever the analyst decides changes nothing — the case closes and the money is long gone.
Related
- Decision API — where the decision is made
- Flows and Resolution — which flow produced it