# Notifications and tracking

Combine webhook notifications, payout reads, and reconciliation for reliable status handling.

Product: Payment API
Guides follow API reference 0.1.0 and event reference 0.1.0.
Canonical page: https://docs.axiym.io/payment-api/concepts/notifications-and-tracking

During processing, a payment moves through review, settlement, and execution
stages asynchronously.
Axiym delivers signed webhook events for documented lifecycle changes:
payout creation, holds, completion, rejection, and cancellation. Confirmation,
approval, and settlement do not have separate payout events.

## Key concepts

| Concept         | Meaning                                                                                             |
| --------------- | --------------------------------------------------------------------------------------------------- |
| Event           | A notification about a payout, account movement or status change, or a requested subscription test. |
| Webhook         | The HTTPS delivery carrying the event to your system.                                               |
| Subscription    | The registered endpoint that receives events.                                                       |
| Payout resource | The authoritative current state returned by the API.                                                |

## How they work together



```mermaid
flowchart TD
  A["Payout changes"] --> B["Axiym creates event"]
  B --> C["Webhook delivery"]
  C --> D["Your system persists event"]
  D --> E["Fetch payout when current state matters"]
  E --> F["Update and reconcile"]
```



An event is a signal that something changed, not a replacement for the payout
resource. If your next action depends on the latest status, retrieve the
payout through the authenticated Payment API integration.

## A reliable integration uses all three

* **Webhooks** provide timely notification.
* **API reads** provide authoritative current state and complete details.
* **Periodic reconciliation** recovers from missed, delayed, or failed event
  processing.

Continue with the [Webhooks guide](/payment-api/webhooks/overview) for registration,
delivery, signature verification, and handling duplicate or out-of-order events.