> ## Documentation Index > Fetch the complete documentation index at: https://developers.ingopayments.com/llms.txt > Use this file to discover all available pages before exploring further. # Webhooks > Event notifications for Notify — Managed Parties — staging, party notifications, authentication, verification, tokenization, approvals, and payment status. Notify — Managed Parties is an async-first product. The synchronous stage response confirms the notification was accepted; every subsequent lifecycle event — across all parties, through approvals and through to funded — is delivered via webhook. In a multi-party flow, events fire independently per party as each one moves through their engagement. Webhooks are delivered as JSON via HTTP POST to your registered endpoint. Return any `2xx` status to acknowledge receipt. See [Webhooks](/docs/hub/webhooks) for endpoint requirements, IP allowlist, and retry behavior. *** ## Event categories | Category | What it covers | | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | | **Transaction Staging** | Confirmation that a multi-party disbursement was successfully staged | | **Party Notification** | Notification sent, received, and bounced — fires per party | | **Party Authentication** | Identity challenge success and failure — fires per party | | **Recipient Verification** | RVDM identity matching outcomes and OFAC screening results | | **Account Verification** | Card (CNS/CD, AVS/CVV), ACH (RNV, ANV, NAV), and PayPal verification outcomes | | **Account Tokenization** | Successful account tokenization — includes the `customer_account_token` | | **Approvals** | All designated approvers have acted; disbursement released for processing | | **Payment Status** | Check issued, paid, canceled, stopped, and returned; payment success, failure, and return; disbursement expiry and cancellation | *** ## Multi-party behavior In a multi-party transaction, webhook events fire independently for each party as they engage. An approver's `notification.status.sent` event may arrive before or after the recipient's `authentication.status.success` event — events are not serialized across parties. The `transaction.recipient.payment.status.approvals.complete` event signals that all designated approvers have acted and the disbursement has been released. This is the gate event your integration should listen for if you need confirmation that the approval requirement has been satisfied before funds move. *** ## Event reference Full event catalog — payload schemas, field definitions, and examples for every Notify — Managed Parties webhook event.