Deposit Notification

The Deposit Webhook notifies merchants asynchronously when funds are deposited into their Bamboo balance to fund upcoming payouts. It allows merchants to reconcile incoming bank transfers with the corresponding balance credit without relying on manual balance checks or polling the Balance API.

📘
This webhook is specific to payout-funding deposits. It is not related to Payin transactions — for purchase and refund status updates, see the Transaction Webhook.

Notification Parameters

The data structure is modular. Below you will find the parameter breakdown separated by objects.

Parameter	Type	Description
`EventType`	String	Identifies the type of balance event. Currently, only `BALANCE_UPDATED` is supported for this webhook.
`MerchantId`	Number	Unique merchant identifier within Bamboo.
`Currency`	String	Three-letter ISO 4217 currency code of the deposited funds (e.g., `UYU`, `MXN`, `COP`).
`TriggeredBy`	Object	Contains details of the movement that generated the balance update. See TriggeredBy Object.
`Created`	String	ISO 8601 timestamp (`YYYY-MM-DDTHH:mm:ss.ffffffZ`) indicating when the notification was generated.

TriggeredBy Object

Parameter	Type	Description
`MovementType`	String	Type of movement that affected the balance. For this webhook, always `Deposit`.
`MovementId`	Number	Unique identifier of the balance movement within Bamboo.
`Reference`	String	Reference of the wire/bank transfer, as sent by the merchant when funding the deposit. Included only when available — depends on whether the originating bank forwards it.
`EndUserNotes`	String	Free-text banking details supplied with the incoming deposit (e.g., originating bank and account). Format is not standardized and may vary depending on the originating bank.
`Sign`	String	Indicates the direction of the movement. For deposits, always `Credit`.
`Amount`	Number	Deposited amount represented in minor units (e.g., cents, without decimal separators. E.g., `100000` represents `1,000.00`).

Example

The following is the JSON body Bamboo sends as a POST request to the merchant's configured webhook URL.

{
  "EventType": "BALANCE_UPDATED",
  "MerchantId": 1001,
  "Currency": "UYU",
  "TriggeredBy": {
    "MovementType": "Deposit",
    "MovementId": 987654,
    "Reference": "Deposit for payouts in UY, merchant 1001",
    "EndUserNotes": "Bank: Itau Uruguay; Account: 1234567",
    "Sign": "Credit",
    "Amount": 100000
  },
  "Created": "2026-09-11T18:35:12.509869Z"
}

Response Expected

The merchant's webhook endpoint must return HTTP 200 (OK) to confirm that the notification was successfully received and processed. If Bamboo receives any other status code or no response, the notification will be retried according to the Retry Policy.

Response Code	Meaning
`200`	Notification successfully received and processed.
`4xx`	Client-side error (invalid endpoint, payload rejection, or failed signature validation).
`5xx`	Temporary server error. Bamboo will retry the notification automatically.