Account webhook events

Account webhook events inform you of activity on the accounts of your customers. Learn how to start receiving webhooks in the webhooks guide.

Prerequisites

• A webhook URL configured in your application settings.
• For low-balance webhooks only: the feature must be enabled by Weavr — contact us with the currency and threshold you require.

Available webhook events

We send the following account-related webhook events:

• Account IWTs (formerly "deposits")
• Account updates
• Low-balance webhooks

Account IWTs (incoming wire transfers)

We use webhooks to inform you when an IWTIWT Incoming Wire Transfer - a transaction that occurs when funds from a bank account held at a third-party financial institution are moved to a Weavr managed account. IWTs are initiated externally by the owner of the source bank account, and the managed account must have an assigned IBAN to receive funds. is received on an account. The webhook includes the fields transactionId and transactionAmount that represent the transaction identifier and its amount. You can use these webhooks to notify customers that funds are now available on their accounts.

The information is sent to you using the ${WEBHOOK_URL}/managed_accounts/deposits/watch webhook URL.

info

The ${WEBHOOK_URL} is the URL configured in your application settings.

Webhooks can also be used in conjunction with the following endpoint, which shows the effect of a deposit on the actualBalance and availableBalance of the account.

GET/managed_accounts/{id}Try it

Response

{
  "id": "string",
  "profileId": "string",
  "tag": "string",
  "friendlyName": "string",
  "currency": "str",
  "balances": {
    "availableBalance": 0,
    "actualBalance": 0
  },
  "state": {
    "state": "ACTIVE",
    "blockedReason": "USER",
    "destroyedReason": "SYSTEM"
  },
  "creationTimestamp": 0
}

IWTs credited immediately

When an IWTIWT Incoming Wire Transfer - a transaction that occurs when funds from a bank account held at a third-party financial institution are moved to a Weavr managed account. IWTs are initiated externally by the owner of the source bank account, and the managed account must have an assigned IBAN to receive funds. is credited immediately, just one webhook is sent with the state COMPLETED.

If the API endpoint is called, then the transactionAmount (from the webhook) is reflected in both the actualBalance and availableBalance in the API.

IWT held for compliance checks

When an IWTIWT Incoming Wire Transfer - a transaction that occurs when funds from a bank account held at a third-party financial institution are moved to a Weavr managed account. IWTs are initiated externally by the owner of the source bank account, and the managed account must have an assigned IBAN to receive funds. is held for compliance checks (e.g. a Source of Funds declaration is required), two webhooks are sent. The first webhook is sent when the deposit is received (and held) and has the state : PENDING. The IWTIWT Incoming Wire Transfer - a transaction that occurs when funds from a bank account held at a third-party financial institution are moved to a Weavr managed account. IWTs are initiated externally by the owner of the source bank account, and the managed account must have an assigned IBAN to receive funds. also shows up in Data Insights in your portal with the state UNDER_REVIEW. However, the IWTIWT Incoming Wire Transfer - a transaction that occurs when funds from a bank account held at a third-party financial institution are moved to a Weavr managed account. IWTs are initiated externally by the owner of the source bank account, and the managed account must have an assigned IBAN to receive funds. is not reflected in the balance of account at this point, and so the actualBalance and availableBalance do not show any changes if the API endpoint is called.

When compliance checks are completed, a second webhook is sent with the state : COMPLETED. If the API endpoint is called, then both the actualBalance and availableBalance reflect the deposit.

Example

Initial balance (amounts in cents/pence) = 77650, deposit for 1500000 (held for compliance checks).

Deposit received and held for compliance checks. The first webhook is sent with transactionAmount.amount : 1500000 and state : PENDING.

API balances:

"balances": {
        "actualBalance": 77650,
        "availableBalance": 77650

Compliance checks are completed, deposit fully processed and money can be used. The second webhook is sent with transactionAmount.amount : 1500000 and state : COMPLETED

API balances:

"balances": {
        "actualBalance": 1577650,
        "availableBalance": 1577650

Account updates

We use webhooks to inform you when there is an update to an account. The webhook includes the account object containing all information related to the account that has been updated. The type field describes the action that was performed on the account.

The information is sent to you using the ${WEBHOOK_URL}/managed_accounts/watch webhook URL.

Low-balance webhooks

Weavr can send a webhook when the balance of an account drops below a configured threshold. This allows you to react proactively — for example by automatically initiating a top-up — before transactions start failing due to insufficient funds.

How it works

When a transaction causes an account balance to fall below the threshold, a single webhook is sent. Further transactions that keep the balance below the threshold do not trigger additional webhooks. The webhook becomes eligible to fire again only once the balance has recovered to at or above the threshold.

Event	Webhook sent
Balance drops below threshold	Yes
Further transactions while still below threshold	No
Balance reaches or exceeds threshold	No (resets eligibility)
Balance subsequently drops below threshold again	Yes

The webhook payload includes the account ID, currency, and the balance at the time of the breach. See the webhook parameter reference for the full payload schema.

Configuration

The threshold is configured per currency, so you can set independent thresholds for EUR and GBP accounts, for example. The threshold value can be set to any amount that suits your use case.

Enabling low-balance webhooks

Low-balance webhooks are available on request. To enable this feature, contact Weavr with the currency and threshold amount you require. To turn the feature off, contact Weavr and the webhooks will stop immediately.