---
title: "EdenPay Payment Webhooks"
description: "Receive real-time notifications when payment events occur in your EdenPay integration."
sidebar_position: 1
last_updated: 2026-08-19
---

# EdenPay Payment Webhooks

Receive real-time notifications when payment events occur in your EdenPay integration.

## What are Webhooks?

Webhooks enable bex.co to push real-time event notifications to your server when important payment events occur. Instead of repeatedly polling our API to check for status changes, your server receives HTTP POST requests containing structured event data the moment something happens.

## Why Use Webhooks?

- **Real-time notifications**: Get instant updates when payments are confirmed, failed, or refunded
- **Reduced API calls**: Eliminate the need for polling, saving compute units and improving efficiency
- **Reliable delivery**: Automatic retries with exponential backoff ensure events reach you
- **Secure**: HMAC-SHA256 signature verification protects against unauthorized requests
- **Scalable**: Handle thousands of events without overwhelming your infrastructure

## How Webhooks Work

1. **You create an endpoint**: Set up a public HTTPS URL on your server to receive webhook events
2. **You register the endpoint**: Add your URL in the bex.co dashboard and select which events to receive
3. **Events occur**: When a payment is confirmed, fails, or changes status, we create an event
4. **We send the event**: bex.co sends an HTTP POST request to your endpoint with the event data
5. **You process the event**: Your server validates the signature, processes the event, and returns a 200 response
6. **We retry if needed**: If your endpoint doesn't respond, we automatically retry with exponential backoff

## Common Use Cases

### E-commerce Checkout
Automatically fulfill orders when payment is confirmed, update order status when payments fail, and process refunds.

### Subscription Services
Activate user accounts when initial payment is confirmed, handle failed recurring payments, and manage subscription lifecycle.

### Digital Content Delivery
Grant immediate access to purchased content, revoke access for failed payments, and track payment analytics.

### Multi-chain Payment Processing
Handle payments across multiple blockchain networks with a unified webhook interface.

## Event Types

EdenPay webhooks support the following event types:

- **`payment.created`** - A new payment has been initiated
- **`payment.pending`** - Payment transaction has been broadcast to the blockchain
- **`payment.confirmed`** - Payment has been confirmed on-chain (recommended for fulfillment)
- **`payment.failed`** - Payment has failed or expired
- **`payment.refunded`** - Payment has been refunded to the customer
- **`checkout.session.created`** - A new checkout session has been created
- **`checkout.session.completed`** - Checkout session completed successfully
- **`checkout.session.expired`** - Checkout session has expired

## Security

All webhook requests include an `x-eden-signature` header containing an HMAC-SHA256 signature. **Always verify this signature** before processing events to ensure the request came from bex.co.

## Getting Started

Ready to integrate webhooks? Follow our [Quick Start Guide](./quickstart.md) to set up your first webhook endpoint in under 5 minutes.

## Documentation Structure

- **[Quick Start Guide](./quickstart.md)** - Set up your first webhook in 5 minutes
- **[Event Reference](./events.md)** - Complete list of event types and payloads
- **[Signature Verification](./signatures.md)** - Security and signature validation
- **[Troubleshooting](./troubleshooting.md)** - Common issues and solutions

## Need Help?

- **Dashboard**: View delivery attempts, replay failed events, and test webhooks
- **Forum**: [https://bex.co/forum](https://bex.co/forum)
- **Support**: hello@bex.co
- **Discord**: [https://discord.gg/eWZvE4RSBw](https://discord.gg/eWZvE4RSBw)
