---
id: overview
title: "Overview"
sidebar_label: "Overview"
hide_title: true
description: "Overview of Walley webhooks and the events you can subscribe to"
---

import Ingress from "../../src/components/ingress/ingress.react";
import Link from "@docusaurus/Link";

<Ingress title="Overview">
  Webhooks let Walley notify your system the moment something happens, instead
  of you polling for changes. Register an HTTPS endpoint, choose the events you
  care about, and Walley calls your endpoint when they occur.
</Ingress>

## Events

Events are grouped into four categories. Each page lists the event types in
that category, with payload examples and when they are triggered.

<div className="overview-cards">
  <Link className="overview-card" to="/docs/webhooks/customer-tokens">
    <h3>🎫 Customer Tokens</h3>
    <p>
      Follow a stored payment token through its lifecycle: active, pending,
      suspended, cancelled, denied or revoked.
    </p>
  </Link>
  <Link className="overview-card" to="/docs/webhooks/authorizations">
    <h3>🔐 Authorizations</h3>
    <p>
      Track tokenized payment authorizations from created to authorized, and
      get the reason when an attempt is retried or fails.
    </p>
  </Link>
  <Link className="overview-card" to="/docs/webhooks/orders">
    <h3>📦 Orders</h3>
    <p>
      Know when an order is created, authorized, captured, refunded, canceled
      or expired, no matter which Walley product created it.
    </p>
  </Link>
  <Link className="overview-card" to="/docs/webhooks/settlements">
    <h3>💰 Settlements</h3>
    <p>
      Get notified the moment a new settlement is ready, so you can fetch the
      report through the Reports API right away.
    </p>
  </Link>
</div>

## Start here

1. [Receiving webhooks](/docs/webhooks/receiving) covers what your endpoint
   must support, what the requests look like, how retries work, and how to
   verify each request with HMAC.
2. [Webhook management in Merchant Hub](/docs/merchanthub/access/webhooks) is
   where you create your webhooks, choose events and stores, and test the
   configuration before going live.
3. Pick your events from the categories above and subscribe to them when you
   create the webhook.