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; for a flat list of every event, see the Event catalog.
Partner-Managed programs only. Rain-Managed programs skip transaction.requested and go straight to transaction.created, because Rain decides authorizations internally.
