AlmondTill/G3N API

On this page

confirmFraudAlert

mutation · in the family Fraud alert

What it does

Record a fraud alert as a CONFIRMED finding.

acknowledged → confirmed (a CONFIRMED fraud finding — terminal + immutable but NOT doomed: the finding is a KEPT no-delete business record that stays listed). The optional reason lands on the revision cause — the disposition trail.

What happens

The finding is kept permanently and becomes immutable — it stays on the list as part of the group’s record.

Careful

A confirmed finding cannot be reopened or edited; the alert itself never enforces anything — follow-up actions are yours.

Who may call it

Capability area: Fraud review — Reviewing the fraud signals raised on staff conduct.

Arguments

NameTypeRequiredNotes
idID ID!yesThe id of the record.
revisionID ID!yesThe revision id you read on the record; the change is refused if an edit landed in the meantime.
reasonStringnoNo 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 ExampleConfirmFraudAlert($id: ID!, $revision: ID!, $reason: String) {
  confirmFraudAlert(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": {
    "confirmFraudAlert": {
      "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

Used in