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

​
Event categories

CategoryWhat it covers
Recipient NotificationNotification sent, received by the recipient, and bounced (undeliverable)
Party AuthenticationIdentity challenge success and failure
Recipient VerificationRVDM identity matching outcomes and OFAC screening results
Account VerificationCard (CNS/CD, AVS/CVV), ACH (RNV, ANV, NAV), and PayPal verification outcomes
Account TokenizationSuccessful account tokenization — includes the customer_account_token
Payment StatusCheck 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

Notify — Classic Webhook Events

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