Skip to main content

​
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 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

Customizable Rules

Configure rules based on transaction amount, frequency, geographic location, merchant category, time of day, and more.

Automated Alerts

Get notified instantly via webhook, email or Slack when a transaction breaches a rule.

Case Management

Review flagged transactions, approve or reject them, and escalate to support from the Adhere dashboard.

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.

Transfer

Account-to-account transfer. Requires origin_account and destination_account. The most common transaction type.

USSD

USSD-initiated transaction. Same payload as Transfer — only transaction_type changes to ussd.

Web

Web-initiated transaction. Same payload as Transfer — only transaction_type changes to web.

Card

Card transaction. Requires card_details (BIN + last4) and optionally merchant_details. No origin_account or destination_account required.
See Submit Transaction for the full request, examples per type, and response codes.

​
Rule Criteria

Rules can be based on any combination of the following:

​
Webhook Notifications

When a transaction is flagged, Adhere sends a suspicious_transaction event to your configured webhook URL. See Webhooks for the full payload structure and signature verification guide.

​
Next Steps

Submit a Transaction

Send your first transaction for monitoring.

User Journey

Understand the end-to-end flow from submission to resolution.