Product

Transaction Alert Review

Alerts raised by an organisation's own monitoring, reviewed to a recorded outcome, including a reported suspicion.

Racks of the Pleiades supercomputer at NASA Ames
Image: NASA Ames Research Center. NASA library

Customer controlled Linux host · Browser access

On this page
  1. What it does
  2. The fields
  3. The states
  4. Using it
  5. Data handling
  6. Limits
  7. Availability
  8. Evidence

What it does

Transaction Alert Review keeps a register of alert records for your account. Working through alerts to a recorded decision. Alerts come from your own rules, which you state on the screening page or from any other monitoring you run and enter by hand. It does not apply a regulatory watch list or a model and it detects only what your rules say. Each alert has a title and the fields below. Its state moves only along the steps listed. The database refuses any other step and any value outside the field rules. It also refuses any change to a record in a final state.

The fields

FieldHoldsEntry
Alert referenceone line of text (up to 200 characters)required
Raised ona daterequired
Rule or sourceone line of text (up to 200 characters)required
Summarytext (up to 2,000 characters)required
Reviewerone line of text (up to 200 characters)optional

The states

A new alert starts as raised.

StateMay move to
raisedunder review
under reviewclosed no action, escalated
escalatedreported, closed no action
reportedfinal state
closed no actionfinal state

Using it

Signed in accounts open the Transaction Alert Review to add records and move them between states. Each change is recorded in the account's audit chain. A state change names the revision it was made against and is refused if the record has moved on. The same operations are available as JSON on the same address.

Data handling

Records belong to the account that created them and are visible to that account only. They are stored in the platform's PostgreSQL database. Do not store special category personal data in a register unless you have a lawful basis. The privacy notice states what the platform collects and keeps.

Limits

  • It is a register for one account; sharing a register between accounts and attaching files are not built.
  • The account cannot delete or edit a record and a record in a final state is kept as it was. The automated erasure step does not remove register records. The operator completes any erasure request that covers them.
  • There are no reminders or recurring records: dates are stored and shown, nothing is sent when one passes.
  • It does not give legal, clinical or regulatory advice; the account holder remains responsible for what the records mean.

Availability

Transaction Alert Review is running on our own platform. We do not sell a licence for it as a separate product today. The commercial terms state what is on sale. It can be part of the result of an engineering engagement. The written proposal then names it and its licence terms and what you would hold at the end. To discuss it, use Work with Us.

Evidence

The field rules, the permitted steps and the refusal of every other step are enforced by the database and exercised by the platform's own tests. The evidence register lists the graded claims.

Where it runs

Install on a customer controlled Linux x86-64 host with PostgreSQL 18. People use it through a browser that can reach the host.

Installation, updates and recovery
Supported targetA customer-controlled Linux host on x86-64 with PostgreSQL 18 (linux-x86_64-customer-controlled).
Not yet supportedWindows, macOS, phones and tablets, and Linux on other architectures. Each needs its own installation, update and recovery evidence before it is supported.
Check a deviceRun rjv preflight on it. It reads the operating system, architecture, memory, disk, listen address, configuration, database, database role and schema, changes nothing, and exits non-zero if the current release cannot run there.
Installed asOne application and a PostgreSQL database. rjv install lays the current release (schema 162) down with a hardened service unit and an environment file, and installs every system on this site, including Transaction Alert Review.
NeedsNothing beyond the release and its PostgreSQL database.
DataIt stays in the PostgreSQL database you run. The only outside service the release can use is an outbound mail relay that you configure.
UpdatingA release is a numbered build. The schema is applied by a separate owner step (rjv migrate), and the application refuses to serve a schema it was not built for.
Backup and restorerjv backup writes a checksummed dump. rjv restore restores it into an empty database and checks the checksum, the schema version and the audit chain of every account.
LeavingThe data is in your own database and can be dumped at any time. What you may do with the release is set by the terms on deployment and ownership.

On a phone or tablet

Use the browser with a connection to the host.

See what works on your device
Find this offering
Browser (W)
Carry out every authorised operation
Client (C)
Compute on the device itself
Not supported (U)
Use a host you own
Client (C)
Work without the host or the internet
Not supported (U)

Nothing here needs a desktop because every operation that this site offers works in the browser on a screen down to 320 CSS px which is the narrowest width that we test. Where a row reads Not supported the browser is the alternative because we do not install the release on the device and no offline mode exists and the host that you control must be reachable and we do not use device sensors or accelerators.

Published
29 October 2026
Revision
4

Last reviewed 29 October 2026.