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

# Notifications (webhooks)

> LB Pay notifies your systems at each relevant change. There are 21 events in 7 groups.

| Group | Event | When it is sent |
| - | - | - |
| Lifecycle | `remittance.created` | The remittance was created by a withdrawal. |
| | `remittance.on_hold` | The remittance went to compliance review, at creation or during screening. |
| | `remittance.rejected` | The remittance was rejected. |
| | `remittance.funds_held_brl` | Final outcome: funds held in BRL after a definitive Pix failure or key holder mismatch. |
| FX | `remittance.fx_contracted` | FX was contracted. |
| | `remittance.fx_failed` | FX failed. |
| Funding | `remittance.funding_confirmed` | Funding was confirmed. |
| | `remittance.funding_failed` | Each failed funding attempt. LB Pay keeps retrying. |
| Pix | `remittance.payout_processing` | The Pix was sent. |
| | `remittance.payout_completed` | The beneficiary was credited. |
| | `remittance.payout_failed` | Each failed Pix attempt. |
| | `remittance.payout_returned` | The Pix was returned. |
| Settlement | `settlement.created` | A batch was opened. |
| | `settlement.closed` | A batch closed. The amount is final. |
| | `settlement.due` | A batch is due today. |
| | `settlement.overdue` | A batch is overdue. |
| | `settlement.completed` | A batch was paid. |
| Records | `sender.status_changed` | A sender’s status changed. |
| | `sender.compliance_level_changed` | A sender’s compliance level changed. |
| | `beneficiary.status_changed` | A beneficiary’s status changed. |
| Credit | `credit_line.threshold_reached` | Credit line usage reached 70%, 90% or 100%. |

* Every notification is signed, so your systems can confirm it came from LB Pay.
* A notification can arrive more than once. Each one has a unique event ID to identify repeats.
* The order of arrival is not guaranteed.
* Failed deliveries are retried automatically for up to 24 hours and can be resent from the portal.
* Resending a notification never repeats a financial effect.

> [!TIP]
>
> **What you do**
>
> * Verify the signature of every notification.
> * Use the event ID to ignore repeats.
> * Do not depend on the order of arrival. Use the status in the notification.


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