Skip to main content
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 for endpoint requirements, IP allowlist, and retry behavior.

​
Event categories

​
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

Notify — Managed Parties Webhook Events

Full event catalog — payload schemas, field definitions, and examples for every Notify — Managed Parties webhook event.