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

# Webhooks

> How payment events reach you with the Payments API.

> [!NOTE]
>
> **Coming soon.** The Payments API does not deliver its own webhooks to merchants yet. There is no webhook endpoint management on `/v1` and no events list.

## What to use today

**Your V2 webhooks keep working.** When a store moves to the Payments API, its payments still feed the commerce events you already receive through the [V2 webhooks](https://docs.tagada.io/developer-tools/node-sdk/webhooks-events.md) (orders, payments, subscriptions). Nothing changes in your webhook endpoint.

For a payment you just created with the Payments API, read it with `GET /v1/payments/{id}` to get its current status.

## What is coming

The Payments API records typed events for its own objects. When delivery opens, events will carry the API version that produced them (`api_version`) and a snapshot of the object. The event types recorded today:

| Object | Events |
| - | - |
| Payment | `payment.created`, `payment.requires_action`, `payment.capture_due`, `payment.authorized`, `payment.succeeded`, `payment.failed`, `payment.canceled` |
| Refund | `refund.created`, `refund.succeeded`, `refund.failed` |
| Renewal cycle | `renewal_cycle.created`, `renewal_cycle.try_failed`, `renewal_cycle.notice_due`, `renewal_cycle.notice_sent`, `renewal_cycle.waiting_card_update`, `renewal_cycle.needs_customer`, `renewal_cycle.needs_merchant`, `renewal_cycle.succeeded`, `renewal_cycle.failed`, `renewal_cycle.canceled` |
| Payment policy | `payment_policy.published` |
| Processor | `processor.paused` |

This list can change before delivery opens.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.