API-based transaction review support

Turn transaction data into clear review steps.

Send transaction records through one API workflow, apply configurable AML risk signals, and route selected activity to your team for further assessment.

Explore the workflow Understand the service scope

Input: Structured transaction data
Output: Signals and review context
Decision: Retained by your team

POST /v1/transactions/check 200

{
  "reference": "txn_48A2",
  "review_state": "review",
  "signals": [
    "pattern_variance",
    "velocity_change"
  ],
  "next_step": "analyst_assessment"
}

Example response for illustration

Built around practical review operations

Configurable rules Traceable responses Human decision points Documented API behavior

01 — Workflow

A compact path from raw records to focused review.

Keep your existing case process while adding consistent data preparation and signal evaluation.

01

Submit a record

Send the transaction fields your process uses through a documented request format.
02

Apply your configuration

Evaluate the record against enabled signals and thresholds selected for your operating context.
03

Route for assessment

Receive structured context that can support triage, recordkeeping, and human review.

02 — API outline

Useful context, returned in a predictable structure.

The API is designed to supplement internal review procedures. Responses provide signal context rather than legal conclusions or automatic final decisions.

Consistent request and response fields
References for internal record matching
Configurable signal categories
Review-state output for workflow routing

curl https://api.example.com/v1/transactions/check \
  -H "Content-Type: application/json" \
  -d '{
    "reference": "txn_48A2",
    "amount": 1275.40,
    "currency": "USD",
    "occurred_at": "2026-08-16T09:24:00Z"
  }'

{
  "reference": "txn_48A2",
  "review_state": "review",
  "signal_count": 2,
  "next_step": "analyst_assessment"
}

Illustrative endpoint and sample data. Final fields depend on implementation.

03 — Operating controls

Designed to fit inside a responsible review process.

Human oversight

Keep decisions with qualified reviewers.

Signal outputs can support prioritization. Your organization remains responsible for interpreting results, documenting decisions, and applying its own procedures.

A / 01

Configuration

Choose thresholds and enabled signals according to your documented risk approach.

A / 02

Traceability

Use record references and response context to support internal review notes.

A / 03

Data minimization

Define request fields around the information needed for your selected workflow.

Service scope

Software support, not a substitute for professional judgment.

What it does

Organizes submitted records, evaluates configured signals, and returns context for review.

What it does not do

It does not provide legal advice, determine regulatory status, or guarantee compliance outcomes.

Your responsibility

Validate the workflow for your use case and consult qualified professionals when needed.

04 — Common questions

Before evaluating the API.

Does the API make final compliance decisions?

No. It returns configured signals and review context. Your organization retains responsibility for decisions and obligations.

Can it replace an internal AML program?

No. The service is a software component intended to support an established process, not replace governance, procedures, or professional review.

Are all transactions treated the same way?

No. Available signals and thresholds can be configured around the operating context and the data supplied.

Is the sample endpoint production-ready?

No. The endpoint and records shown on this page are illustrative. Production specifications should be documented during implementation.

Review the approach

Map the API workflow to your existing process.

Start with the data you already collect, the decisions your reviewers make, and the records you need to retain.

Review the API outline