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

# Compliance notifications

> Deprecated compliance_check_status_update and account_freeze_status_update webhook payloads. Retained for reference; migrate to Compliance Notifications v2.

Refer to [Compliance notifications (v2)](/v2/api-reference/webhooks/notifications/compliance-notifications-v2) instead.

## Introduction

Bastion sends these notifications when accounts in your organization gain or lose the ability to transact for compliance reasons.

Two types of events trigger compliance notifications:

1. **Compliance check status update events:** Sent when compliance checks for identities in your organization complete. As a reminder, Bastion initiates compliance checks for an identity when it receives a [Submit Compliance Data](/v2/api-reference/compliance/submit-compliance-data) request.
2. **Account freeze status update events**: Sent when accounts in your organization are frozen. An account is frozen when its corresponding identity fails compliance checks. Bastion's compliance team may also freeze an account at its discretion.

## Compliance check status update events

An example `Compliance Check Status Update` event payload:

<CodeGroup>
  ```json theme={"theme":{"light":"vitesse-light","dark":"vitesse-dark"}}
  {
    "id": "compliance_check_status_update:32n4BQ5ihrJjYTtYHwedggNIFjT:2025-09-16T17:14:31Z",
    "type": "compliance_check_status_update",
    "data": {
      "identity_id": "32n4BQ5ihrJjYTtYHwedggNIFjT",
      "compliance_check_passed": true,
      "compliance_check_failure_reason": "",
      "jurisdiction_check_passed": true,
      "jurisdiction_check_failure_reason": "",
      "allowed_to_transact_fungibles": true
    }
  }
  ```
</CodeGroup>

| Field                                    | Type    | Description                                                                                                                                |
| ---------------------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| `id`                                     | string  | Unique identifier for each event. It can be used to deduplicate events.                                                                    |
| `type`                                   | string  | The type of event. This is always `compliance_check_status_update` for compliance check status update events.                              |
| `data.identity_id`                       | string  | The ID of the identity whose compliance check status was updated.                                                                          |
| `data.compliance_check_passed`           | boolean | Flag indicating whether or not the identity passed compliance checks.                                                                      |
| `data.compliance_check_failure_reason`   | string  | Optional reason for the compliance check failure.                                                                                          |
| `data.jurisdiction_check_passed`         | boolean | Flag indicating whether or not the identity passed jurisdiction checks (i.e. that the identity is in a jurisdiction supported by Bastion). |
| `data.jurisdiction_check_failure_reason` | string  | Optional reason for the jurisdiction check failure.                                                                                        |
| `data.allowed_to_transact_fungibles`     | boolean | Flag indicating whether or not the identity is allowed to transact fungible assets.                                                        |

## Account freeze status update events

An example `Account Freeze Status Update` event payload:

<CodeGroup>
  ```json theme={"theme":{"light":"vitesse-light","dark":"vitesse-dark"}}
  {
    "id": "account_freeze_status_update:32n4AmrCrbTZC7jcopJXg4RYOla:2025-09-16T17:14:21Z",
    "type": "account_freeze_status_update",
    "data": {
      "account_id": "32n4AmrCrbTZC7jcopJXg4RYOla",
      "is_frozen": true,
      "message": "Account has been frozen - please contact Bastion support for assistance"
    }
  }
  ```
</CodeGroup>

| Field             | Type    | Description                                                                                               |
| ----------------- | ------- | --------------------------------------------------------------------------------------------------------- |
| `id`              | string  | Unique identifier for each event. It can be used to deduplicate events.                                   |
| `type`            | string  | The type of event. This is always `account_freeze_status_update` for account freeze status update events. |
| `data.account_id` | string  | The ID of the account that was frozen or unfrozen.                                                        |
| `data.is_frozen`  | boolean | Flag indicating whether the account was frozen or unfrozen.                                               |
| `data.message`    | string  | Optional message regarding the change in frozen status.                                                   |


## Related topics

- [Compliance notifications (v2)](/v2/api-reference/webhooks/notifications/compliance-notifications-v2.md)
- [Product updates](/changelog.md)
- [Deposit notifications](/v2/api-reference/webhooks/notifications/deposit-notifications.md)
- [Conversion notifications](/v2/api-reference/webhooks/notifications/conversions-notifications.md)
- [Transaction limit notifications](/v2/api-reference/webhooks/notifications/transaction-limit-notifications.md)