Ongoing review / Transaction Monitoring

Transaction Monitoring

Frame transaction-monitoring requirements around the activity your team wants to review and the people responsible for responding.

  • Real-time activity monitoring
  • Configurable risk thresholds
  • Human-reviewed alerts

Questions worth exploring

Start with the activity. Then define the response.

A transaction-monitoring evaluation needs more than a list of desired notifications. Consider the activity you want to review, the reason a reviewer would take notice, and the action that should follow. FinTrace Core monitors activity in real time against configurable risk thresholds, with FinTrace Radar adding signals for emerging threats and sanctions-related patterns.

  1. 1

    Monitor activity

    Watch the transactions and addresses in scope.

  2. 2

    Detect risk signals

    Compare activity with your thresholds and rules.

  3. 3

    Generate an alert

    Raise a prioritised alert with its context.

  4. 4

    Assign a reviewer

    Route the alert to the person responsible.

  5. 5

    Investigate evidence

    Examine counterparties, exposure and history.

  6. 6

    Record the decision

    Document the outcome and keep the audit record.

Live monitoring demonstration

Watch activity become a documented response.

Follow a transaction from the live feed to a flagged alert, an assigned reviewer and an escalated case, with filters, rules and history one click away.

Monitored today184,320
Alerts raised68
Open alerts41
Escalated7
TimeWallet · entityAmount · networkRule triggeredScore changeLevelStatus
14:32:020x8d2c…7e1fSanctioned entity48.20 ETHEthereumSanctioned counterparty54→81CriticalEscalated
14:31:48bc1q9x…k7m2Mixer (example)3.85 BTCBitcoinMixer exposure > 10%41→72HighIn review
14:31:200x41a7…9ad2DeFi protocol (example)12.40 ETHArbitrumRapid movement of funds33→58MediumAssigned
14:30:570x7c3e…e0b1Exchange (example)210,000 USDCPolygonAmount threshold18→44MediumOpen
14:30:31TQn9…Zk3pNew counterparty9,400 USDTTronNew counterparty12→21LowOpen
14:30:120xa93f…c04bKnown exchange2.10 ETHEthereumNone9→9No alertCleared
14:29:44bc1p4z…q2vdPrivate wallet0.42 BTCBitcoinNone14→14No alertCleared

Illustrative interface, sample data. Monitoring is not performed on this website.

Rules and alert configuration

Configure what deserves attention.

These controls illustrate the kinds of conditions a team might set. They are evaluation examples; which conditions, thresholds and states are available is confirmed with the team during your evaluation.

Rule builderDraft
Rule nameRapid movement of funds
Transaction amount threshold≥ 50 ETH
Risk-score threshold≥ 75
Sanctions and exposure
Behaviour and counterparties
Severity on triggerLowMediumHighCritical
  • Transaction amount thresholdFlag transfers above a set value.
    Active
  • Risk-score thresholdAlert when a score crosses your level.
    Active
  • Sanctions exposureDirect or indirect links to sanctions sources.
    Active
  • High-risk jurisdictionCounterparties in jurisdictions you list.
    Draft
  • Rapid movement of fundsFunds moved on quickly after receipt.
    Draft
  • Unusual transaction frequencyA burst of transfers in a short window.
    Active
  • New counterpartyFirst interaction with an address.
    Disabled
  • Direct or indirect exposureExposure categories at one hop and beyond.
    Active

Evaluation examples with Active, Draft and Disabled states. Not a list of confirmed rules.

Response management

Clear responsibility from alert to audit record.

Decide what is in scope, what deserves attention and who owns each response before you switch anything on.

  • 01

    Activity in scope

    Outline the transactions, addresses, and business processes you would like to discuss. Identify the networks and time periods relevant to the evaluation.

  • 02

    Review priorities

    Describe the situations that should receive attention and the context a reviewer would need. Discuss how your team would distinguish a useful notification from an unresolved question.

  • 03

    Response ownership

    Identify who would receive an item for review, who could make a decision, and what information should accompany a handover.

How an alert moves between ownersEvery hand-over names a person or a system of record.
  1. Monitoring system

    Detects activity against your rules and raises the alert.

    AutomatedAlert
  2. Compliance analyst

    Reviews the evidence and decides to clear, investigate or escalate.

    Human reviewEscalate
  3. Senior reviewer

    Takes escalated alerts and decides the response.

    Human reviewCase opened
  4. Case management

    Holds the case, its owner and the full activity history.

    System of recordDecision logged
  5. Audit record

    Keeps the evidence, decision and timestamps for later review.

    Retained

Automation surfaces the alert. People make the decision and own the outcome.

Prepare a focused conversation

Bring a scenario. Define what you want to learn.

Bring a fictional example of an activity change and explain why it would matter to your team. We’ll walk through how risk thresholds, rules, and alert delivery would apply to your scenario.

  1. 1Describe the activity
  2. 2Define review priorities
  3. 3Plan the response

A simple way to structure your evaluation call.

Step 1 of 6

Describe monitored activity

Step 2 of 6

Select risk signals

Step 3 of 6

Define alert thresholds

Alert amount≥ 50 ETH
Risk score≥ 75
Step 4 of 6

Choose reviewers

Step 5 of 6

Define escalation steps

  1. 1Analyst reviews and clears or escalates
  2. 2Senior reviewer decides the response
  3. 3Compliance officer signs off
Step 6 of 6

Confirm required evidence

Bring this brief to your demo.Use fictional or approved examples. Nothing you select here is submitted.
Request a Transaction Monitoring Demo

Performance and alert insights

See where alerts come from and how they are resolved.

Operational insights help a team tune its rules, balance reviewer workload and demonstrate control. The figures below are illustrative demo data.

Alerts by severity

68alerts
  • Critical4%
  • High16%
  • Medium38%
  • Low42%

Alerts over time

Last 14 days
14 days agoToday

Average review time

18 minFrom alert to first decision
↓ 3 min vs previous week

Escalated cases

7Of 68 alerts this week
2 awaiting senior review

Most-triggered rules

  • Risk-score threshold
    19
  • Sanctions exposure
    14
  • Amount threshold
    12
  • Unusual transaction frequency
    9
  • Rapid movement of funds
    7

Review status

  • Open34%
  • In review28%
  • Escalated9%
  • Closed29%

Open alerts by reviewer

  • A. Rahman
    14
  • S. Kim
    11
  • J. Meyer
    9
  • L. Brandt
    7

Monitored networks

In this demo data set
  • ΞEthereum38%
  • ₿Bitcoin27%
  • PPolygon14%
  • AArbitrum11%
  • TTron10%

All figures are illustrative demo data, not customer or product results.

Product verification

What needs confirmation

Transaction Monitoring runs configurable risk thresholds against real-time and historical activity, with rule-based alerting delivered through your existing case-management or notification channels. Use these questions to confirm the details that matter for your deployment.

  • Ask · 01

    Real-time versus scheduled monitoring

    Which activity is monitored in real time, and what update cadence applies to your deployment?

  • Ask · 02

    Supported networks and assets

    Which networks and assets can be monitored for your use case?

  • Ask · 03

    Historical data availability

    How far back can historical activity be reviewed against your rules?

  • Ask · 04

    Rule configuration

    Which conditions can your team configure, and who can change them?

  • Ask · 05

    Alert delivery channels

    How are alerts delivered: case management, email or other notification channels?

  • Ask · 06

    User roles and permissions

    How are analysts, senior reviewers and administrators separated?

  • Ask · 07

    Case-management integration

    How do alerts hand over to your existing case-management process?

  • Ask · 08

    Evidence retention

    What evidence is kept with each alert, and for how long?

  • Ask · 09

    API and webhook availability

    Which API endpoints or webhooks are available for alerts?

These are evaluation questions, not confirmed claims. Answers depend on your deployment and are agreed with the team during your evaluation.

Before your demo

Transaction Monitoring: questions and answers

Is real-time monitoring confirmed?

Yes. FinTrace Core monitors activity in real time against configurable risk thresholds. Ask for the current update cadence for your deployment.

Can my team configure rules and alerts?

Yes. Risk thresholds and alert delivery channels are configurable per team. Describe the conditions and delivery channels you need in a demo request.

How does this relate to wallet screening?

Wallet Screening evaluates a single address on demand; Transaction Monitoring watches ongoing activity and raises signals automatically. The two work together in a typical workflow.

Start a conversation

Plan a transaction-monitoring discussion

Describe the activity you care about and how your team would respond to it.