Event Catalog

Look up any Rain webhook event to see its category, whether it needs a response, and what triggers it.

Use this catalog to identify each event’s delivery behavior, response requirements, and where it applies. This catalog groups events by category. Synchronous events expect a response that influences the outcome, such as approving an authorization. Asynchronous events are informational and only need a 2xx acknowledgement. See Respond to webhooks for response requirements.

Some events reach only the tenants a feature is enabled for, and one is legacy. Check the “When it fires” column to see if an event applies to your program.

Event	Category	Delivery	When it fires
transaction.requested	Transactions	Synchronous	A cardholder attempts to authorize a purchase
transaction.created	Transactions	Asynchronous	Rain creates a spend, collateral, or payment transaction
transaction.updated	Transactions	Asynchronous	A transaction changes, such as an incremental authorization or refund
transaction.completed	Transactions	Asynchronous	A spend or payment transaction reaches a final, settled state
transactionReward.created	Transactions	Asynchronous	A card transaction settles and Rain finalizes its reward. Rain sends it only to partner-managed on-chain tenants
transactionTransfer.created	Transactions	Asynchronous	A transfer between accounts is created
transactionTransfer.updated	Transactions	Asynchronous	A transfer changes state
transactionTransfer.completed	Transactions	Asynchronous	A transfer reaches a final state
onchainRefund.created	Transactions	Asynchronous	Rain creates an on-chain refund and begins processing it. Rain sends it to tenants with on-chain refunds or Auth Pull enabled
onchainRefund.completed	Transactions	Asynchronous	An on-chain refund settles and the funds reach their destination. Rain sends it to tenants with on-chain refunds or Auth Pull enabled
card.created	Cards & Authentication	Asynchronous	You issue a card through the API, or Rain creates one internally
card.updated	Cards & Authentication	Asynchronous	A card status changes or a user adds a card to a digital wallet
card.notification	Cards & Authentication	Asynchronous	Rain reports a card provisioning or wallet token decision
challenge.requested	Cards & Authentication	Synchronous	Rain issues a 3D Secure challenge during authentication
3ds.notification	Cards & Authentication	Synchronous	Legacy. Rain initiates a 3D Secure challenge, for tenants that have not migrated to challenge.requested. Same 60-second, single-attempt delivery as challenge.requested
user.updated	Identity & Compliance	Asynchronous	A user’s KYC or application status changes
company.updated	Identity & Compliance	Asynchronous	A company’s KYB or application status changes
dispute.created	Disputes	Asynchronous	You create a new dispute
dispute.updated	Disputes	Asynchronous	A dispute changes status or you update evidence
dispute.evidenceRequested	Disputes	Asynchronous	Reserved; not currently emitted. Evidence requests reach you through your Rain contact
dispute.chargebackCreated	Disputes	Asynchronous	Rain processes a chargeback after the card network accepts a dispute
contract.created	Account & Reports	Asynchronous	Rain creates a collateral contract
report.created	Account & Reports	Asynchronous	A BIN report is ready
paymentRoute.created	Payment Routes	Asynchronous	A payment route becomes active and ready to receive deposits
microDeposit.received	Payment Routes	Asynchronous	A deposit under $2.00 arrives on a payment route with a bank account, usually to verify account ownership. Rain records it but never processes it
raindrop_balance.requested	Raindrops Rewards	Synchronous	Rain needs a user’s current Raindrops balance
raindrop_redemption.created	Raindrops Rewards	Asynchronous	A Rain-Managed redemption needs on-chain burn authorization
raindrop_redemption.completed	Raindrops Rewards	Asynchronous	A travel redemption is marked completed
raindrop_redemption.refunded	Raindrops Rewards	Asynchronous	A travel redemption is refunded

​

Embedded wallet events

Beta Embedded wallets don’t emit webhooks during the beta. The wallet-related state you can observe today comes from existing events: contract.created when a contract is deployed with the user’s wallet as owner, and transaction.created of type collateral when a deposit from the wallet (or anywhere else) lands in the contract. Wallet and transaction events for embedded wallets join this catalog at GA. Until then, see Transaction webhooks and history for what to poll and how to build so those events drop in.