# Webhooks

Receive real-time notifications when activity occurs within the Deluxe Payments Platform.

Webhooks provide real-time notifications when activity occurs within the Deluxe Payments Platform.

Instead of polling APIs for updates, your application can receive notifications automatically when subscribed events occur.

### Why Use Webhooks?

Use webhooks to:

- Monitor payment status changes
- Track ACH updates
- Receive settlement notifications
- Detect chargebacks and disputes
- Synchronize merchant systems
- Trigger downstream workflows
- Receive EMV transaction results from payment devices


### Core Concepts

| Term | Definition |
|  --- | --- |
| Event | A business activity that occurs within the platform. |
| Event Type | The classification that identifies the event that occurred. |
| Endpoint | The HTTPS URL configured to receive webhook notifications. |
| Payload | The data delivered with the webhook notification. |
| Subscription | The relationship between a webhook endpoint and supported events. |
| Delivery | The process of sending an event notification to a webhook endpoint. |


### How Webhooks Work

#### High-Level Flow

The high-level webhook flow shows how Deluxe Services generates and sends an event payload to the merchant endpoint. The merchant processes the event through the consumer or customer application and acknowledges receipt of the webhook.

**Business Activity Occurs**
Business activity occurs within Deluxe Services that triggers an event.

**Generate Event Payload**
Deluxe Services generates an event payload for the business activity.

**Send Payload**
Deluxe Services sends the event payload to the merchant endpoint.

**Process Event**
The merchant endpoint sends the event to the consumer or customer application for processing.

**Handle Event**
The consumer or customer application handles the event and returns the result to the merchant endpoint.

**Acknowledge Receipt**
The merchant endpoint acknowledges receipt of the event to Deluxe Services.

### Asynchronous Processing

Many payment-related activities do not complete immediately.

The asynchronous processing workflow shows how the consumer or customer application sends an API request to the Deluxe Platform and receives an immediate API response. Additional processing can occur after the response, with a webhook event notification delivered later when asynchronous activity occurs.

**Send API Request**
The consumer or customer application sends an API request to the Deluxe Platform.

**Receive API Response**
The Deluxe Platform returns an API response to the consumer or customer application.

**Receive Webhook Event Notification**
After additional processing occurs, the Deluxe Platform sends a webhook event notification to inform the consumer or customer application of asynchronous activity. The event is delivered later when the activity occurs.

Webhooks notify integrations when asynchronous activity occurs.

This distinction is particularly important for:

- ACH activity
- Merchant onboarding
- Chargebacks and disputes
- Transaction lifecycle updates
- EMV transaction processing


These workflows may continue after the initial API request has completed.

### Next Steps

Webhook Structures & Types
Review supported webhook events, payload structures, and example payloads.

Retry & Delivery
Understand webhook delivery behavior, retries, and failure handling.

Secure Webhooks
Implement webhook signature validation and request verification.

Implement Webhooks
Configure webhook subscriptions, endpoints, and event processing workflows.