Overview
Rise supports the following payment-related webhook events:payment.group.created
Payment group created with multiple payments
payment.sent
Individual payment processed and sent
payment.failed
Payment transaction failed on-chain
payment.group.created
When a payment group is created, this event is triggered. A payment group represents a collection of payments that are processed together as a single batch.Field reference
string
required
The type of object this webhook represents (always “event”)
number
required
The Unix timestamp when the event was created
string
required
The type of event that occurred
string
required
The version of the event schema
string
A unique identifier for the API request that triggered this event (optional)
string
required
Primary identifier for the webhook event and a unique key to ensure it is processed only once
payment.sent
When an individual payment is processed and sent, this event is triggered. This occurs after a payment has been successfully executed on the blockchain.Field reference
string
required
The type of object this webhook represents (always “event”)
number
required
The Unix timestamp when the event was created
string
required
The type of event that occurred
string
required
The version of the event schema
string
A unique identifier for the API request that triggered this event (optional)
string
required
A unique key to ensure the webhook is processed only once
object
required
Payment information and details
payment.failed
Triggered when a submitted payment transaction fails on-chain (for example, it reverts). The payment is never created on-chain, so it does not appear inGET /v2/payments. Requests rejected by validation return an error from the API call itself and do not trigger this event.
Field reference
string
required
The type of object this webhook represents (always “event”)
number
required
The Unix timestamp when the event was created
string
required
The type of event that occurred
string
required
The version of the event schema
string
Nanoid of the failed transaction
string
required
A unique key to ensure the webhook is processed only once
object
required
Details of the failed payment
Implementation Notes
Payment lifecycle: Payment groups are created first (triggering
payment.group.created), then individual payments within the group are processed and sent (triggering payment.sent for each).Tracking outcomes: Use
payment.sent and payment.failed as the primary signals for a payment’s outcome, and match them to the transaction returned by PUT /v2/payments. GET /v2/payments only lists payments that exist on-chain, so it can confirm success but cannot distinguish a pending payment from a failed one. A Removed state means the payer cancelled the payment; it is not a failure.