​
What are webhooks?

Webhooks are HTTP callbacks that Rise sends to your application when specific events occur in your account. Think of them as “reverse API calls” – instead of your application repeatedly asking Rise “did anything happen?”, Rise proactively notifies your application the moment something interesting occurs. When an event happens in your Rise account – like a payment being received or a payment group being created – Rise can immediately send an HTTP POST request to your server with the event details.

​
Why use Rise webhooks?

Real-time notifications

Get instant updates when events occur in your Rise account, enabling you to build responsive applications that react immediately to changes.

Reduce API calls

Instead of constantly polling Rise’s API to check for updates, webhooks deliver information to you automatically, reducing server load and improving efficiency.

Better user experiences

Update your application’s UI, send notifications to users, or trigger business processes the moment something happens, creating seamless experiences.

Reliable delivery

Rise webhooks include robust retry logic with exponential backoff, ensuring your application receives events even if your server is temporarily unavailable.

​
Common use cases

Rise webhooks enable you to build powerful, responsive applications:
  • Send confirmation emails when payments are received
  • Update order status in your system when payment groups are created
  • Trigger fulfillment processes when deposits are confirmed
  • Send push notifications to mobile apps for real-time updates
  • Sync data between Rise and your internal systems
  • Generate reports or analytics when specific events occur

​
How Rise webhooks work

1

Register your endpoint

Tell Rise where to send webhook events by creating a webhook endpoint with your server’s URL
2

Choose your events

Select which types of events you want to receive (payment received, deposit processed, etc.)
3

Receive events

Rise sends HTTP POST requests to your endpoint when subscribed events occur
4

Verify and process

Your application verifies the webhook signature and processes the event data
5

Respond quickly

Your endpoint responds with a 2xx status code to acknowledge receipt

​
Webhook event structure

Every Rise webhook event follows a consistent structure: 
{
  "object": "event",
  "created": 1751590453,
  "request_id": "req-1751590452487",
  "event_type": "payment.sent",
  "event_version": "1.0",
  "idempotency_key": "85420805-0b5e-4b11-b7f4-c6f05db7120b",
  "payment": {
    "nanoid": "pa-xyz789abc123456",
    "amount": "1000000000",
    "currency": "USD"
    // ... more event data
  }
}
All monetary amounts in blockchain context are transmitted as strings to prevent JSON number precision issues. Timestamps are always in UTC using ISO-8601 format.

​
Security first

Rise webhooks include built-in security features to protect your integration:

HTTPS recommended

HTTPS recommended for production; HTTP supported for development/testing

Signature verification

Each webhook includes a signature that proves it came from Rise

Replay protection

Timestamps prevent old events from being replayed by attackers

​
Team collaboration

Rise webhooks support both company-level and team-level configurations:
  • Company webhooks: Receive events for your entire organization
  • Team webhooks: Get targeted notifications for specific team activities

​
Getting started

Ready to start receiving Rise webhook events? Here’s what’s next:

Quick Start Guide

Follow our step-by-step guide to set up your first webhook in under 10 minutes

Security Setup

Learn about signature verification and securing your endpoints

Event Types

Explore all available events you can subscribe to

Testing Tools

Use our testing tools to validate your webhook integration
Rise webhooks v2 provides enhanced reliability, better security, and more granular event control compared to our previous webhook system. If you’re currently using Rise webhooks v1, check out our migration guide to upgrade.