---
title: "Hold limit breach update"
method: POST
path: "hold-limit-breach#update"
tags: ["webhook-event", "balance"]
---

# Hold limit breach update

`POST hold-limit-breach#update` (webhook)

Triggered whenever a hold limit breach is opened or closed for a profile. A hold limit breach occurs when a balance exceeds the regulatory hold limit (applicable in countries such as Singapore and Malaysia).

Use `data.state` to determine whether the breach has been opened or closed, and `data.closing_reason` to understand how it was resolved.

* Event type: `hold-limit-breach#update`
* Profile level subscriptions: Supported
* Application level subscriptions: Supported

Events may not be delivered in the order they occurred. Use `data.occurred_at` to reconcile the order.
See the [Event ordering guide](/guides/developer/webhooks/event-ordering) for details.

See the [Webhooks guide](/guides/developer/webhooks) for setup instructions, signature verification, and best practices.

## Headers

- `X-Signature-SHA256` string
- `X-Delivery-Id` string, uuid
- `X-Test-Notification` boolean

## Payload

- V40012
  - `schema_version` '4.0.0' — Version of the event schema. Determined by the `schema_version` on your [webhook subscription](/api-reference/webhook).
  - `subscription_id` string, uuid — ID of the webhook subscription that triggered this event.
  - `event_type` string — Event type identifier
  - `sent_at` string, date-time — Timestamp when the event was sent.
  - `data` object
    - `resource` object
      - `type` string — Resource type. Always `hold-limit-breach`.
      - `hold_limit_breach_id` integer — ID of the hold limit breach.
      - `profile_id` integer — ID of the profile that owns the breach.
    - `amount` number — Amount that exceeded the hold limit.
    - `currency` string — Currency code (ISO 4217) of the breach amount.
    - `state` 'OPEN' | 'CLOSED' — Current state of the breach.
    - `closing_reason` 'AUTOMATICALLY_RESOLVED' | 'MANUALLY_RESOLVED' | 'null', nullable — Reason the breach was closed. Null if state is `OPEN`.
    - `created_at` string, date-time — Timestamp when the breach was created (ISO 8601).
    - `updated_at` string, date-time — Timestamp when the breach was last updated (ISO 8601).
    - `occurred_at` string, date-time — Timestamp when the event occurred (ISO 8601). Use this field to reconcile out-of-order events.

## Acknowledgement `200`

Return any `2xx` status to acknowledge receipt of the event.

- object
  - `status` string

---

[API](https://skmtc.net/wise/apis/platform-api.md) · [All operations](https://skmtc.net/wise/apis/platform-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/wise/platform-api/revisions/4907a1d269ab/schema)