Use cases
The transactions screening service APIs enable real-time anti-money laundering (AML) checks on financial transactions before processing, helping to detect and flag suspicious or high-risk activities early. They also support updating the screening status after manual or automated review, ensuring smooth collaboration between automated systems and compliance teams, improving risk management, compliance, and audit traceability.
1. Initiate transaction screening
API: POST /request-transaction-screening
Purpose:
To perform real-time AML screening on financial transactions before execution, ensuring that high-risk or suspicious activities are identified and flagged for review.
Use case description:
Scenario:
A customer initiates a fund transfer via mobile banking, internet banking, or at a bank branch. Before the transaction is processed, the system must assess the AML risk level based on the involved parties and transaction context.
System action:
The system submits the transaction data (including sender/receiver info, bank details, transaction amount and purpose, and optionally shipping or documentation info) to the /request-transaction-screening API.
The service screens this data against internal and external watchlists, high-risk patterns, and policy rules.
The response includes an initial screening result:
- CLEAR: Transaction may proceed.
- REVIEW: Transaction requires manual investigation.
- REJECT: Transaction is blocked based on critical risk signals.
Outcome:
The transaction is either executed immediately, held for compliance review, or rejected—depending on the risk level detected.
Benefit:
- Ensures early detection of suspicious or prohibited transactions.
- Automates compliance workflows.
- Reduces manual workload by pre-filtering low-risk transactions.
- Enhances trust and integrity in financial operations.
2. Update transaction screening status
API: POST /update-status-aml
Purpose:
To update the AML screening status of a transaction after further analysis or compliance officer review, ensuring that case handling is traceable and auditable.
Use case description:
Scenario:
A transaction previously flagged for REVIEW is being assessed by a compliance analyst. After verifying documents and context, the analyst needs to update the system with a decision (e.g., approved or rejected), along with remarks and audit information.
System action:
The compliance portal or internal system calls the /update-status-aml API with updated screening result, decision status (e.g., approved, rejected, escalated), and any supporting notes.
This updates the transaction’s AML case log and triggers the next step in the processing workflow.
Outcome:
The transaction status is updated across systems, ensuring consistent data for processing, auditing, and reporting.
Benefit:
- Enables coordinated action between systems and compliance staff.
- Ensures end-to-end traceability of AML decision-making.
- Helps meet audit and regulatory reporting standards.
- Supports timely and informed decisions on suspicious transactions.
