> ## 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 — Classic disbursements — notification delivery, authentication, verification, tokenization, and payment status.

Notify — Classic is an async-first product. The synchronous stage response confirms the notification was accepted; every subsequent lifecycle event — from the moment Ingo contacts the recipient through to funded — is delivered via webhook. Your integration should be built around these events rather than polling.

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                                                                                                                  |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| **Recipient Notification** | Notification sent, received by the recipient, and bounced (undeliverable)                                                       |
| **Party Authentication**   | Identity challenge success and failure                                                                                          |
| **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`                                                         |
| **Payment Status**         | Check issued, paid, canceled, stopped, and returned; payment success, failure, and return; disbursement expiry and cancellation |

***

## Lifecycle order

A typical single-recipient disbursement produces events in this sequence:

1. `transaction.recipient.notification.status.sent`
2. `transaction.recipient.notification.status.received`
3. `transaction.recipient.authentication.status.success`
4. `transaction.recipient.verification.rvdm.success` *(if RVDM is configured)*
5. `transaction.account.tokenization.success`
6. `transaction.recipient.payment.status.success` *(or payment-type-specific variant)*

Verification and account verification events appear between steps 3 and 5 depending on your configured risk controls. Not all events are guaranteed to fire for every transaction — your integration should handle any subset gracefully.

***

## Event reference

<Card title="Notify — Classic Webhook Events" icon="webhook" href="/notify-classic-webhooks/webhooks/notification-sent">
  Full event catalog — payload schemas, field definitions, and examples for every Notify — Classic webhook event.
</Card>