Update case
Updates a transaction monitoring case.
Path parameters
Globally unique identifier for the case.
Request body
Status of a case as it progresses through the review workflow:
- OPEN - The case has been created and is still collecting matching transactions
- ASSIGNED - An analyst has been assigned and transaction collection has stopped
- IN_REVIEW - The case is actively being investigated
- ESCALATED - The case has been reviewed and requires additional oversight
- RESOLVED - A determination has been made and a resolution recorded
- CLOSED - The case is finalized
New title for the case, or null to clear it
New assignee for the case, or null to unassign
Outcome recorded when a case is resolved:
- CONFIRMED_FRAUD - The reviewed activity was confirmed to be fraudulent
- SUSPICIOUS_ACTIVITY - The activity is suspicious but not confirmed fraud
- FALSE_POSITIVE - The activity was legitimate and the alert was a false positive
- NO_ACTION_REQUIRED - No further action is required
- ESCALATED_EXTERNAL - The case was escalated to an external party
Notes describing the resolution
Arbitrary key-value metadata to set on the case
Priority level of a case, controlling queue ordering and SLA urgency
New SLA deadline for the case, or null to clear it
Optional client-provided identifier for the actor performing this action, recorded on the resulting activity entry. This value is supplied by the client (for example, your own internal user ID) and is not authenticated by Lithic
Response
Case
Globally unique identifier for the case
Short, human-readable summary of the case
Status of a case as it progresses through the review workflow:
- OPEN - The case has been created and is still collecting matching transactions
- ASSIGNED - An analyst has been assigned and transaction collection has stopped
- IN_REVIEW - The case is actively being investigated
- ESCALATED - The case has been reviewed and requires additional oversight
- RESOLVED - A determination has been made and a resolution recorded
- CLOSED - The case is finalized
Token of the queue the case belongs to
Priority level of a case, controlling queue ordering and SLA urgency
Identifier of the user the case is currently assigned to
Token of the transaction monitoring rule that triggered the case
Outcome recorded when a case is resolved:
- CONFIRMED_FRAUD - The reviewed activity was confirmed to be fraudulent
- SUSPICIOUS_ACTIVITY - The activity is suspicious but not confirmed fraud
- FALSE_POSITIVE - The activity was legitimate and the alert was a false positive
- NO_ACTION_REQUIRED - No further action is required
- ESCALATED_EXTERNAL - The case was escalated to an external party
Free-form notes describing the resolution
Deadline by which the case is expected to be resolved
Arbitrary key-value metadata associated with the case
Date and time at which the case was created
Date and time at which the case was last updated
Date and time at which the case was resolved
Date and time at which transaction collection stopped for the case
Whether the case still has transaction scopes pending resolution