> ## Documentation Index
> Fetch the complete documentation index at: https://docs.riseworks.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Webhook Overview

> What are webhooks and why use them with Rise

## 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?

<CardGroup cols={2}>
  <Card title="Real-time notifications" icon="bolt">
    Get instant updates when events occur in your Rise account, enabling you to build responsive applications that react immediately to changes.
  </Card>

  <Card title="Reduce API calls" icon="arrows-rotate">
    Instead of constantly polling Rise's API to check for updates, webhooks deliver information to you automatically, reducing server load and improving efficiency.
  </Card>

  <Card title="Better user experiences" icon="sparkles">
    Update your application's UI, send notifications to users, or trigger business processes the moment something happens, creating seamless experiences.
  </Card>

  <Card title="Reliable delivery" icon="shield-check">
    Rise webhooks include robust retry logic with exponential backoff, ensuring your application receives events even if your server is temporarily unavailable.
  </Card>
</CardGroup>

## 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

<Steps>
  <Step title="Register your endpoint">
    Tell Rise where to send webhook events by creating a webhook endpoint with your server's URL
  </Step>

  <Step title="Choose your events">
    Select which types of events you want to receive (payment received, deposit processed, etc.)
  </Step>

  <Step title="Receive events">
    Rise sends HTTP POST requests to your endpoint when subscribed events occur
  </Step>

  <Step title="Verify and process">
    Your application verifies the webhook signature and processes the event data
  </Step>

  <Step title="Respond quickly">
    Your endpoint responds with a 2xx status code to acknowledge receipt
  </Step>
</Steps>

## Webhook event structure

Every Rise webhook event follows a consistent structure:

```json theme={null}
{
  "object": "event",
  "created": 1751590453,
  "request_id": "req-1751590452487",
  "event_type": "payment.sent",
  "event_version": "2.0",
  "idempotency_key": "85420805-0b5e-4b11-b7f4-c6f05db7120b",
  "payment": {
    "nanoid": "pa-xyz789abc123456",
    "amount": "1000000000",
    "currency": "USD"
    // ... more event data
  }
}
```

<Note>
  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.
</Note>

## Security first

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

<CardGroup cols={3}>
  <Card title="HTTPS recommended" icon="lock">
    HTTPS recommended for production; HTTP supported for development/testing
  </Card>

  <Card title="Signature verification" icon="pen">
    Each webhook includes a signature that proves it came from Rise
  </Card>

  <Card title="Replay protection" icon="clock">
    Timestamps prevent old events from being replayed by attackers
  </Card>
</CardGroup>

## 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:

<CardGroup cols={2}>
  <Card title="Quick Start Guide" icon="rocket" href="/webhooks/getting-started/quickstart">
    Follow our step-by-step guide to set up your first webhook in under 10 minutes
  </Card>

  <Card title="Security Setup" icon="shield" href="/webhooks/getting-started/security">
    Learn about signature verification and securing your endpoints
  </Card>

  <Card title="Event Types" icon="list" href="/webhooks/implementation/event-types">
    Explore all available events you can subscribe to
  </Card>

  <Card title="Testing Tools" icon="flask" href="/webhooks/implementation/testing">
    Use our testing tools to validate your webhook integration
  </Card>
</CardGroup>

<Info>
  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](/webhooks/reference/migration) to upgrade.
</Info>