> ## 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.

# Notify — Managed Parties

> Single and multi-party disbursement orchestration. One API call manages the full lifecycle — notification, approval gating, identity verification, compliance screening, and delivery.

<div
  style={{
background: "#000000",
borderLeft: "4px solid #23ad4b",
borderRadius: "8px",
padding: "28px 32px",
marginBottom: "24px",
position: "relative"
}}
>
  <div
    style={{
fontSize: "11px",
fontWeight: "700",
color: "#23ad4b",
textTransform: "uppercase",
letterSpacing: "0.12em",
marginBottom: "8px"
}}
  >
    Ingo Payments · Notify — Managed Parties
  </div>

  <div
    style={{
fontSize: "24px",
fontWeight: "700",
color: "#ffffff",
lineHeight: "1.2",
marginBottom: "8px"
}}
  >
    One call. <span style={{ color: "#23ad4b" }}>Every step managed.</span>
  </div>

  <div
    style={{
fontSize: "13px",
fontWeight: "300",
color: "#b1b4b6",
lineHeight: "1.6",
marginBottom: "20px",
maxWidth: "560px"
}}
  >
    Single and multi-party. Fully orchestrated from notification through approval and delivery.
  </div>

  <div style={{ display: "flex", gap: "12px" }}>
    <a href="/docs/notify-managed/quick-start" style={{
          background: "#23ad4b",
          color: "#ffffff",
          fontWeight: "700",
          fontSize: "13px",
          padding: "8px 20px",
          borderRadius: "4px",
          textDecoration: "none"
        }}>Quick Start →</a>
    <a href="/docs/hub/authentication" style={{
          background: "transparent",
          color: "#b1b4b6",
          fontWeight: "400",
          fontSize: "13px",
          padding: "8px 20px",
          borderRadius: "4px",
          border: "1px solid rgba(255,255,255,0.2)",
          textDecoration: "none"
        }}>Authentication</a>
  </div>
</div>

Notify — Managed Parties is the preferred integration for all new programs. It delivers the complete managed disbursement lifecycle from a single API call — recipient notification, identity verification, OFAC screening, client-configured payment selection with amount-based thresholds, and real-time webhook updates at every stage. Standard single-recipient disbursements are fully supported, and multi-party orchestration is available today for programs that require approval gating or interested party visibility within the standard disbursement flow. Additional notification types — including standalone enrollment and recurring disbursement flows — are on the roadmap and will be prioritized based on client demand.

<Note>
  **SMS delivery options** — Notify can send recipient notifications via SMS through Ingo-managed delivery or through your own SMS infrastructure. With Ingo-managed SMS, Ingo sends directly to recipients and manages consent collection — though notifications identify Ingo as the sender rather than your brand. Many clients integrate their own SMS platform for full brand control, directing recipients to the Ingo-hosted disbursement URL. Both approaches are supported. See [Custom Domain & DNS Setup](/docs/hub/domain-setup#sms-delivery-options) for details, or ask your Integration Manager which approach fits your program.
</Note>

***

## Capabilities

<CardGroup cols={2}>
  <Card title="Multi-Party Orchestration" icon="users">
    Define up to three party roles per transaction. **Recipients** receive and claim
    funds. **Approvers** actively gate the disbursement — funds do not release until
    all designated approvers have acted. **Interested Parties** receive visibility
    into the transaction without taking any action.

    <div style={{ marginTop: "16px", paddingTop: "12px", borderTop: "1px solid rgba(255,255,255,0.1)" }}>
      <div style={{ display: "inline-block", fontSize: "10px", fontWeight: "700", background: "#6b7280", color: "#ffffff", padding: "2px 10px", borderRadius: "10px", marginBottom: "8px" }}>Coming Soon</div>
      <div style={{ fontSize: "13px", color: "#b1b4b6", lineHeight: "1.6" }}><strong>Role Delegation</strong> — Approvers will be able to delegate their approval authority to another party at any point in the lifecycle. <a href="/docs/notify-managed/notification-types">Tell us this matters to your program →</a></div>
    </div>
  </Card>

  <Card title="Single-Recipient Disbursements" icon="circle-check">
    Every capability available in a single-recipient flow is fully supported.
    Notification, identity and OFAC screening, client-configured payment options
    with amount-based thresholds, account tokenization, and real-time webhook
    updates at every status change — all managed by Ingo from a single staged
    notification.
  </Card>

  <Card title="Recipient Enrollment" icon="id-card">
    <div style={{ display: "inline-block", fontSize: "10px", fontWeight: "700", background: "#f59e0b", color: "#000000", padding: "2px 10px", borderRadius: "10px", marginBottom: "10px" }}>In Development</div>

    Collect payment preferences independently of any disbursement. The fully hosted
    enrollment experience will present your configured payment options through the
    Embedded Account Capture interface — no portal or payment UI to build or host.
    On completion, Ingo returns a <code>customer\_account\_token</code> ready for use
    in any future disbursement. [Tell us this matters to your program →](/docs/notify-managed/notification-types)
  </Card>

  <Card title="Recurring Disbursements" icon="arrows-rotate">
    <div style={{ display: "inline-block", fontSize: "10px", fontWeight: "700", background: "#f59e0b", color: "#000000", padding: "2px 10px", borderRadius: "10px", marginBottom: "10px" }}>In Development</div>

    Decouple enrollment from payment for programs that disburse on a recurring
    cadence. Enroll a recipient once; stage subsequent disbursements against their
    token without re-collecting account details or re-running the hosted experience.
    Ideal for payroll, earned wage access, insurance premiums, and recurring financial
    programs. [Tell us this matters to your program →](/docs/notify-managed/notification-types)
  </Card>
</CardGroup>

***

## API Reference

Notify — Managed Parties exposes one staging endpoint. Cancellation of a staged
notification before the recipient has claimed uses the shared Notify Cancel endpoint.

<CardGroup cols={2}>
  <Card title="Notify — Stage" icon="paper-plane">
    Submit a notification with recipient details, party roles, disbursement intent,
    and notification type. Ingo immediately begins the managed lifecycle on your behalf.

    <div style={{ display: "flex", gap: "8px", marginTop: "16px", flexWrap: "wrap" }}>
      <a href="/docs/notify-managed/notify/stage" className="spec-btn">Stage Disbursement</a>
    </div>
  </Card>

  <Card title="Notify — Cancel" icon="circle-xmark">
    Cancel a staged notification before the recipient has claimed their disbursement.
    Managed Parties shares the Cancel endpoint with Notify — Classic.

    <div style={{ display: "flex", gap: "8px", marginTop: "16px", flexWrap: "wrap" }}>
      <a href="/docs/notify-managed/notify/cancel" className="spec-btn">Cancel Disbursement</a>
    </div>
  </Card>
</CardGroup>