Fraud protection and audit logs
Fraud protection
Fraud protection shows patterns worth a look — never an automatic refusal.
Required role: store owner, branch manager (their branches) and analyst can view. Deciding an investigation is the owner's.
A detector raises a signal for a person to review. Nothing here blocks a customer. A pattern worth a look is not proof that anyone did anything wrong.
You see what each signal is about and what to do. You do not see the thresholds behind it; every store is treated the same way.
Review an investigation
- Open the investigation.
- Press Start review and read the evidence, the related transactions and its history.
- Add notes as you check.
- Close it with an outcome and a reason — for example Dismiss as a false positive — or Escalate to SPKTRM, which opens a support case.
A closed investigation can be reopened.
Audit logs
Audit logs record who did what, inside your team — and SPKTRM's actions against your store too: membership changes, invitations, role changes, offer approvals and rejections, scanner enrolment and revocation, redemptions, payment and settlement changes, support access by SPKTRM, and administrative overrides.
Required role: store owner, branch manager (their branches) and analyst.
- Search people, roles, actions, record names and ids, reasons, references and change text — for example a correlation id.
- Filter by action, actor or record type, and by date.
- Press Details to see the field-by-field change, then Open the record.
- Export the events that match your search and filters.
Nothing in the portal edits or deletes an entry. But in the preview this log lives in browser storage, so it is not tamper-evident and must not be relied on as proof.