On this page
dismissFraudAlert
mutation · in the family Fraud alert
What it does
Dismiss a fraud alert as a false positive — the reason is required.
acknowledged → dismissed (a FALSE POSITIVE — doomed terminal, drops from the listing; reachable by id + History). The reason is REQUIRED and lands on the revision cause.
What happens
The alert drops off the list (still reachable by id); your reason becomes the dismissal record.
Careful
A dismissal cannot be reopened — a recurring pattern raises a fresh alert instead.
Who may call it
Capability area: Fraud review — Reviewing the fraud signals raised on staff conduct.
- Owner
- Manager
- An API key whose scope allows
api:dismissFraudAlert
Arguments
| Name | Type | Required | Notes |
|---|---|---|---|
id | ID ID! | yes | The id of the record. |
revision | ID ID! | yes | The revision id you read on the record; the change is refused if an edit landed in the meantime. |
reason | String String! | yes | No further notes. |
Returns
FraudAlert FraudAlert! — A FraudAlert — the merchant TRIAGE register over the derived fraud-signal layer: a signal crossing a policy threshold raises an alert naming the signal family (void_no_sale · return_refund_abuse · discount_override_abuse · override_pattern · cash_over_short · dispute_chargeback), the normalized score (0..100) vs the crossed threshold, the implicated staff principal and/or facility, the scoring window, and the triggering records. SIGNALS, NOT ENFORCEMENT: the / authority layer enforces; an alert only records and asks. SYSTEM-RAISED end to end — no create surface exists; the merchant triages: acknowledge (open → acknowledged — investigating; disarms the age-out), then confirm (a KEPT immutable finding — terminal but NOT doomed) or dismiss (a false positive — the reason is REQUIRED). Untriaged alerts age out after 30 days (open → expired, the scheduled lane). Triage identity/notes are the revision causes (History + the org-bus render actor + reason + instant — never duplicated fields). NOT searchable (sensitive review data — reached via the A17_FRAUD-gated paginated listing, never name-found); the listing pages NEWEST-first and drops doomed (dismissed/expired) per the - law while confirmed findings stay listed.
Example request
mutation ExampleDismissFraudAlert($id: ID!, $revision: ID!, $reason: String!) {
dismissFraudAlert(id: $id, revision: $revision, reason: $reason) {
id
sysId
type
caption
status
parentId
rootId
createdAt
updatedAt
revisionNum
revision
signalKind
score
threshold
reason
periodKey
implicatedUserId
logicalFacilityId
expiresAt
}
}
Variables:
{
"id": "01900000-0000-7000-8000-37386ae00000",
"revision": "01900000-0000-7000-8000-b7960e180000",
"reason": "Correcting a miscount."
}
Send it with the envelope naming the version: "extensions": {"at": {"version": {"name":"genesis","number":0}}}.
Example response
{
"data": {
"dismissFraudAlert": {
"id": "01900000-0000-7000-8000-37386ae00000",
"sysId": "FA-EXMP-0000-000F",
"type": "FraudAlert",
"caption": "Blue jeans",
"status": "open",
"parentId": "01900000-0000-7000-8000-065235280000",
"rootId": "01900000-0000-7000-8000-a093dd800000",
"createdAt": "2027-01-31T00:00:00.000Z",
"updatedAt": "2027-01-31T00:00:00.000Z",
"revisionNum": 1,
"revision": "01900000-0000-7000-8000-b7960e180000",
"signalKind": "<signal kind>",
"score": 1,
"threshold": 1,
"reason": "Correcting a miscount.",
"periodKey": "<period key>",
"implicatedUserId": "01900000-0000-7000-8000-01219ad10000",
"logicalFacilityId": "01900000-0000-7000-8000-8026f71c0000",
"expiresAt": "2027-01-31T00:00:00.000Z"
}
},
"extensions": {
"at": {
"callId": "01EXAMPLE-CALL-ID",
"version": {
"requested": {
"name": "genesis",
"number": 0
},
"serviced": {
"name": "genesis",
"number": 0
}
}
}
}
}
Errors this call can answer
VALIDATION/INVALID— Something in the request is not valid. (VALIDATION)AUTHN/REQUIRED— Sign in to do this. (AUTHN)AUTHZ/FORBIDDEN— Your role does not allow this action. (AUTHZ)RATE_LIMIT/THROTTLED— Too many requests in a short time. (RATE_LIMIT)NOT_FOUND/*— That record could not be found. (NOT_FOUND)CONFLICT/*— The record’s state, or a change made in the meantime, does not allow this; the codes are on the CONFLICT page. (CONFLICT)VALIDATION/VERSION_REQUIRED— The request did not say which app version it came from. (VALIDATION)