Skip to content
toden

Use case · Suspicious transaction reporting

Suspicious transaction reporting

From an alertto a filedreport.

A monitoring rule firing is the start of the work. Toden groups alerts into a case with a deadline, keeps the investigation notes as a permanent record, drafts the report in the goAML format financial intelligence units accept, and requires a second person to file it.

The workflow

Alerts, cases and goAML suspicious transaction reports, with four-eyes control and an audit trail. This is a starting point: add, remove or reorder any step in the workflow builder.

Step 01

Transaction assessment

A decision and a risk score for each payment

Per check

Step 02

Decision rules

Alert, case, and a drafted goAML report

Included

Then your rules decide

A starting rule set

  • Nothing unusualApprove
  • Amounts structured just under a thresholdReview
  • Money in and straight out againReview
  • A counterparty on your blocked listDecline

Every rule is yours to change on a visual canvas, and each result records which rule decided it. Publishing a new version needs no release.

Try the workflow builder

How it works

1

Events are scored

Each transaction you send is scored as it arrives. A review or block raises an alert, and repeats fold into the same alert.

2

An investigator opens a case

Alerts on a customer group into a case with a priority and a deadline. Notes cannot be edited or deleted afterwards.

3

A second person files

The report is drafted from the case, checked for missing fields, exported as goAML XML, and marked filed by someone other than its author.

What powers it

  1. Each case has a priority and a deadline that follows it, and one that runs late is reported by webhook.

Integrate

Mount the SDK with the workflow you published, or send a hosted link and write no code. The result arrives by signed webhook, and changing the workflow never needs a release.

Verify.tsxTypeScript · React
import { TodenVerification } from "@todenhq/sdk-react";
 
export function Verify({ userId }) {
  return (
    <TodenVerification
      apiKey="pk_test_..."
      workflowId="wf_AbC123dEf456"
      userId={userId}
      onSubmit={(s) => save(s.verificationId)}
    />
  );
}
verification.completedWebhook · JSON
{
  "event": "verification.completed",
  "data": {
    "verificationId": "ver_8fk2...",
    "status": "verified",
    "assuranceLevel": "gov_db",
    "idType": "bvn",
    "country": "NG",
    "dataMatch": true,
    "facialMatch": true,
    "facialConfidence": 91
  }
}

Products involved

This solution combines products you can use on their own too.

Compliance

Transaction Monitoring

Score each transaction as it arrives against rules you control, and route what they flag to alerts and cases.

Learn more
Compliance

Cases & SAR Filing

Turn alerts into cases, record the outcome, then draft and export a goAML-format SAR or STR.

Learn more
Beta

Risk Intelligence

Monitor transactions and account activity against your own rules, then investigate what they flag.

Learn more

Related use cases

AML & Monitoring

The ongoing AML workflow: screening, monitoring, cases and goAML reporting.

Learn more

Fraud Detection

One engine that turns identity, behaviour, device and screening signals into a live, explainable risk decision.

Learn more

High-value payment approval

A decision on every payment, and a face check on the few that deserve one.

Learn more

Frequently asked

  • goAML XML, the format used by financial intelligence units in many countries, including Nigeria. Suspicious transaction and suspicious activity reports are both supported.

Suspicious transaction reporting,in one workflow.

The sandbox opens when you sign up. Usage-based pricing, no sales call.

Start freeTalk to us