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

# Notification Types

> The four notify_type values and when to use each — from standard one-time disbursements to recurring enrollment and payment flows.

The `notify_type` field in the v4 stage request controls the lifecycle mode of the notification. It determines whether the staged event triggers a disbursement, an enrollment experience, or both — and whether the recipient is new to the platform or already enrolled from a prior interaction.

Selecting the right notification type is the primary architectural decision for programs that intend to support recurring payments or standalone account capture.

***

## Type 0 — Standard Disbursement

<Note>
  **Available now.** This is the only notification type currently available for integration.
</Note>

The standard one-time disbursement. Ingo notifies the recipient, runs identity and OFAC screening, presents the payment options your program has configured, tokenizes the chosen account, and processes the payment — all from a single staged notification. Multi-party orchestration (approvers and interested parties) is fully supported within this notification type.

**Use when:** You have a disbursement amount ready to send and want the recipient to select their preferred payment method. This covers the vast majority of disbursement use cases.

```json theme={null}
"notify_type": 0
```

***

## Type 1 — Enrollment Only

<div style={{ display: "inline-block", fontSize: "10px", fontWeight: "700", background: "#f59e0b", color: "#000000", padding: "2px 10px", borderRadius: "10px", marginBottom: "16px" }}>In Development — Not yet available for integration</div>

Collect a recipient's payment preferences without staging a disbursement. The fully hosted experience presents your configured payment options through the Embedded Account Capture interface. On completion, Ingo returns a `customer_account_token` tied to the recipient's chosen account — no disbursement is triggered. The token can then be used with `notify_type: 2` for any number of future disbursements without repeating the enrollment experience.

**Use when:** You want to onboard recipients proactively — collecting payment preferences before a disbursement event occurs — so payments can be issued immediately when the time comes without putting the recipient through account capture at the point of payment.

**Common programs:** Earned wage access pre-enrollment, insurance claim pre-authorization, payroll onboarding, recurring benefits programs.

```json theme={null}
"notify_type": 1
```

***

## Type 2 — Disbursement Only (Enrolled Party)

<div style={{ display: "inline-block", fontSize: "10px", fontWeight: "700", background: "#f59e0b", color: "#000000", padding: "2px 10px", borderRadius: "10px", marginBottom: "16px" }}>In Development — Not yet available for integration</div>

Stage a disbursement against a recipient who is already enrolled. Rather than presenting the full payment selection experience again, Ingo uses the `party_id` from the prior enrollment to route the payment to the recipient's established account. The recipient is notified that a payment is on the way without being asked to re-select a payment method.

**Use when:** You have previously enrolled a recipient via `notify_type: 1` or `notify_type: 3` and are now issuing a recurring or subsequent payment to the same account.

**Requires:** A valid `party_id` from a prior enrollment. Pass this in the `settings.party_id` field rather than `settings.client_provided_id`.

```json theme={null}
"notify_type": 2
```

***

## Type 3 — Enrollment + Disbursement

<div style={{ display: "inline-block", fontSize: "10px", fontWeight: "700", background: "#f59e0b", color: "#000000", padding: "2px 10px", borderRadius: "10px", marginBottom: "16px" }}>In Development — Not yet available for integration</div>

Combines enrollment and disbursement in a single notification. The recipient selects a payment method through the hosted experience and, upon completion, the disbursement is immediately processed to their chosen account. Ingo returns both a `customer_account_token` and a completed payment — the account is enrolled for future use automatically.

**Use when:** You want to issue a first-time payment and establish the recipient's account preferences in a single interaction, so future payments can use `notify_type: 2` without a separate enrollment step.

**Common programs:** First-payment-plus-enrollment flows, benefits onboarding with immediate disbursement, insurance first-claim settlement.

```json theme={null}
"notify_type": 3
```

***

## Let us know what you need

Notification types 1, 2, and 3 are in development with no current release timeline. Client demand is a direct input into prioritization. If enrollment-only or recurring disbursement flows are important to your program, reach out to your integration manager — your input helps shape the roadmap.