Skip to main content

Overview

The Transactions module is the entry point for all AML/CFT screening. Every financial transaction your institution processes should be submitted to the /screen endpoint. The platform returns a verdict in under 200ms with a risk score, outcome, and triggered rules.

Common Workflows

Real-time screening: Your core banking system calls /screen on every outgoing transfer → The API returns an outcome → Your system routes the transaction based on APPROVE, REVIEW, ESCALATE, or BLOCK. Post-hoc review: A compliance officer queries the transaction list to review recent screenings, drill into a specific transaction, and view the full verdict breakdown.

Permissions

Endpoints


Screen Transaction

Submit a single transaction for real-time screening. The response includes the final outcome, risk breakdown per engine, triggered rules, and recommended actions. Request Body Example Request
Example Response — 200 OK
Example Response — 400 Bad Request
Example Response — 409 Conflict
Idempotency: Sending the same externalId twice returns the cached verdict without re-screening. This makes retries safe.

List Transactions

Retrieve a paginated list of all screened transactions in your tenant. Query Parameters Example Request
Example Response — 200 OK

Get Transaction Detail

Retrieve the full screening result for a single transaction, including the complete verdict with engine breakdowns. Path Parameters Example Request
Example Response — 200 OK
Transaction data is immutable once screened. If you need to re-evaluate, submit a new transaction with a different externalId.

KYC Trust Modes

Tenants can configure how KYC status is resolved during transaction screening: Set the mode via PATCH /api/v1/tenants/me with kycTrustMode.