> ## Documentation Index
> Fetch the complete documentation index at: https://docs.smartcomply.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Transaction Monitoring

> Real-time transaction analysis and automated alerting to detect suspicious activity.

## Overview

Transaction Monitoring provides real-time analysis of every transaction processed through your Adhere account. It evaluates transactions against a set of configurable rules and automatically triggers alerts when suspicious patterns are detected — helping you comply with AML regulations and prevent fraud proactively.

## How It Works

**1. Submit a transaction**

Send transaction data to the [Transaction Monitoring endpoint](https://docs.smartcomply.com/v3/transaction/transaction_monitoring/post_transaction_request.md) via your backend.

**2. Rules are evaluated**

The system checks the transaction against your configured rules (amount limits, frequency, geography, merchant category, and more).

**3. Alert is generated (if triggered)**

If one or more rules fire, the transaction is flagged as suspicious and an alert is sent via webhook or email.

**4. Review and action**

Investigate the alert in the Adhere dashboard — approve, reject, or escalate the transaction.

## Key Features

> [card] Customizable Rules
>
> Configure rules based on transaction amount, frequency, geographic location, merchant category, time of day, and more.

> [card] Automated Alerts
>
> Get notified instantly via webhook, email or Slack when a transaction breaches a rule.

> [card] Case Management
>
> Review flagged transactions, approve or reject them, and escalate to support from the Adhere dashboard.

> [card] AML Screening
>
> Optionally screen transactions and counterparties against global watchlists and sanction databases.

## Supported Transaction Types

The Submit Transaction endpoint accepts four `transaction_type` values, each with a different payload shape. Pick the type that matches the transaction you're submitting.

> [card] Transfer
>
> Account-to-account transfer. Requires `origin_account` and `destination_account`. The most common transaction type.

> [card] USSD
>
> USSD-initiated transaction. Same payload as Transfer — only `transaction_type` changes to `ussd`.

> [card] Web
>
> Web-initiated transaction. Same payload as Transfer — only `transaction_type` changes to `web`.

> [card] Card
>
> Card transaction. Requires `card_details` (BIN + last4) and optionally `merchant_details`. No `origin_account` or `destination_account` required.

See [Submit Transaction](https://docs.smartcomply.com/v3/transaction/transaction_monitoring/post_transaction_request.md) for the full request, examples per type, and response codes.

## Rule Criteria

Rules can be based on any combination of the following:

| Criterion | Example |
| - | - |
| Transaction amount | Flag any transaction over ₦500,000 |
| Transaction frequency | Flag more than 10 transactions in 1 hour |
| Geographic location | Flag transactions from high-risk countries |
| Merchant category | Flag gambling or crypto merchant codes |
| Time of day | Flag transactions between 1am–4am |
| Account type | Apply different rules to individual vs. business accounts |

## Webhook Notifications

When a transaction is flagged, Adhere sends a `suspicious_transaction` event to your configured webhook URL. See [Webhooks](https://docs.smartcomply.com/webhooks.md) for the full payload structure and signature verification guide.

## Next Steps

> [card] [Submit a Transaction](https://docs.smartcomply.com/v3/transaction/transaction_monitoring/post_transaction_request.md)
>
> Send your first transaction for monitoring.

> [card] [User Journey](https://docs.smartcomply.com/v3/transaction/transaction_monitoring/user_journey.md)
>
> Understand the end-to-end flow from submission to resolution.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.