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

# Configure Fraud Alert Notifications in AntifraudAI

> Configure email, Slack, and webhook notifications in AntifraudAI to keep your team informed of fraud events, blocked transactions, and open cases.

Notifications proactively alert your team to fraud activity without requiring anyone to keep the dashboard open. Whether you need an instant Slack ping when a transaction is blocked, a daily email digest for your fraud ops team, or a programmatic webhook feed into your internal tooling, AntifraudAI has a notification channel for every workflow.

## Notification Channels

<CardGroup cols={3}>
  <Card title="Email" icon="envelope">
    Send fraud alerts and daily summaries to one or more email addresses. Ideal for fraud operations teams and management reporting.
  </Card>

  <Card title="Slack" icon="slack">
    Post real-time fraud event messages to any Slack channel. Keep your entire team informed without switching contexts.
  </Card>

  <Card title="Webhooks" icon="webhook">
    Deliver structured JSON payloads to your own HTTP endpoint for fully programmatic processing and custom integrations.
  </Card>
</CardGroup>

## Email Notifications

<Steps>
  <Step title="Open Email Notification settings">
    In the dashboard, navigate to **Settings → Notifications → Email**.
  </Step>

  <Step title="Add recipient addresses">
    Enter one or more email addresses in the **Recipients** field. You can add team aliases (e.g., `fraud-ops@yourcompany.com`) as well as individual addresses.
  </Step>

  <Step title="Choose trigger events">
    Select which events should send an email notification. Available triggers include:

    * **Case created** — notifies when a transaction is flagged for manual review.
    * **Daily summary** — sends a morning digest of the previous day's screening metrics.
    * **Blocked transaction spike** — alerts when the block rate rises sharply above baseline.
  </Step>

  <Step title="Save and verify">
    Click **Save**. AntifraudAI will send a test email to all listed recipients so you can confirm delivery before going live.
  </Step>
</Steps>

## Slack Integration

<Steps>
  <Step title="Connect your Slack workspace">
    Navigate to **Settings → Integrations → Slack** and click **Connect Workspace**. You will be redirected to Slack's OAuth flow to authorize AntifraudAI.
  </Step>

  <Step title="Choose a channel">
    After authorizing, select the Slack channel where notifications should be posted (e.g., `#fraud-alerts`). AntifraudAI will request only the permission needed to post messages to that channel.
  </Step>

  <Step title="Choose trigger events">
    Select the events that should post to Slack. You can enable different events for Slack independently of your email configuration.
  </Step>
</Steps>

When a notification fires, AntifraudAI posts a structured message to your chosen channel. Example:

```
🚨 *Transaction Blocked*
User:       usr_8f3kd92
Amount:     $1,249.00
Risk Score: 87 / 100
Decision:   block
Event ID:   evt_01HX3K9...
View in dashboard → https://dashboard.antifraudai.com/cases/evt_01HX3K9
```

## Webhook Notifications

For fully programmatic processing — such as opening a ticket in your internal case-management system or triggering a downstream workflow — use **webhook notifications**. Webhooks deliver a signed JSON payload to an HTTPS endpoint you control whenever a notification event fires.

See the [Webhooks guide](/guides/webhooks) for full setup instructions, payload schemas, and signature verification.

## Notification Events

The following events are available as notification triggers across all channels:

| Event | Description |
| - | - |
| `case.created` | A transaction was flagged for manual review |
| `transaction.blocked` | A transaction was automatically blocked |
| `daily_summary` | Daily digest of screening metrics |
| `rule.triggered` | A custom rule fired |
| `spike_alert` | Unusual spike in fraud activity detected |

<Tip>
  To avoid notification fatigue, enable `daily_summary` for broad visibility and reserve real-time alerts (`case.created` and `transaction.blocked`) for channels actively monitored by your fraud operations team. Routing every event to every channel typically leads to important alerts being ignored.
</Tip>


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