> ## Documentation Index
> Fetch the complete documentation index at: https://rain-sandbox-trial.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Webhook Event Flow
> A single swimlane showing the main card-program webhooks at the point they fire, from onboarding through spend, disputes, and reporting.
This diagram shows where the main webhooks fit across a card-issuing program, from onboarding through spend, disputes, and reporting. Most of the sequence is the same regardless of integration model, but authorization differs: Partner-Managed programs decide authorizations themselves and receive `transaction.requested`, while Rain-Managed programs skip straight to `transaction.created` because Rain decides authorizations internally. To set up your endpoint first, see [Set up webhooks](/docs/set-up-webhooks); for a flat list of every event, see the [Event catalog](/docs/event-catalog).
## Situational and program-specific steps
Some steps in the diagram do not happen for every program, or fire only in specific situations:
| Step | When it fires |
| -------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Authorization ([`transaction.requested`](/docs/transaction#transaction-requested)) | Partner-Managed programs only. Rain-Managed programs skip `transaction.requested` and go straight to [`transaction.created`](/docs/transaction#transaction-created), because Rain decides authorizations internally. |
| Company KYB ([`company.updated`](/docs/identity-and-compliance#company-updated)) | Corporate programs only. Consumer programs skip it and start at cardholder KYC. |
| Collateral ([`contract.created`](/docs/account-and-reports#contract-created), collateral [`transaction.created`](/docs/transaction#transaction-created)) | Only when each user posts their own collateral. Pooled-collateral programs deploy one contract at setup instead, not one per cardholder. |
| Card activation ([`card.updated`](/docs/card#card-updated)) | For every card. Physical cards activate after they arrive; virtual cards activate immediately. |
| Wallet provisioning ([`card.notification`](/docs/card#card-notification)) | Only when adding a card to a digital wallet is declined. A successful add sends [`card.updated`](/docs/card#card-updated) with `statusChangeReason: wallet_provisioned` instead. |
| Reporting ([`report.created`](/docs/account-and-reports#report-created)) | On a schedule, at the program level (statements and reports), not per cardholder. |
## What's next
Register your endpoint, choose a signing key, and verify signatures.
Look up any event by category, delivery model, and trigger.