Event Catalog - Paxos Labs

This page documents every webhook event type available in Paxos Labs. All events use a flat JSON structure with shared common fields and type-specific fields at the top level.

Event Types

Test Events
- ping — Lightweight connectivity test. Sent from the Paxos Labs Console with no specific event type selected.
Smart Deposit Routing Events
- smart_deposit.deposit.pending — Stablecoins received at the Smart Deposit Address; the deposit into the vault has been initiated.
- smart_deposit.deposit.confirmed — Stablecoins deposited into the vault and shares minted to the destination address.
- smart_deposit.deposit.finalized — Forward transaction reached chain-specific finality.
- smart_deposit.deposit.failed — Deposit could not be completed; payload includes the failure reason.

Common Fields

Every webhook event includes these fields:

{
  "id": "1234567890",
  "type": "ping",
  "timestamp": "2026-04-10T18:32:24.000Z",
  "version": "2026-03-01"
}

Field	Type	Description
`id`	`string`	Unique event identifier (UUID). Remains the same across retry attempts, so consumers can idempotently handle duplicate events. Test events use the prefix `evt_test_`.
`type`	`string`	The event type string (e.g. `ping`).
`timestamp`	`string`	RFC 3339 UTC timestamp of the webhook delivery creation (e.g., `2026-04-10T18:32:24.000Z`).
`version`	`string`	API version. Currently `v2`.

Handling Webhook Events

For guides on signature verification, idempotent processing, and more, see Common Implementation Patterns.

​Event Types

​Common Fields

​Handling Webhook Events

Event Types

Common Fields

Handling Webhook Events