Skip to main content
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.

Common Fields

Every webhook event includes these fields:
Direct transfer deposit events also include these shared fields:

Event Types

ping

A lightweight connectivity test. Sent when you click Send Test in the Paxos Labs Console with no specific event type selected.
The ping event contains only the common fields — no additional fields.

direct_transfer.deposit.pending

Paxos Labs has received the stablecoins and initiated the process to deposit them into the vault.

Event-Specific Fields


direct_transfer.deposit.confirmed

Stablecoins have been successfully deposited into the vault and shares have been minted to the destination address.

Event-Specific Fields


direct_transfer.deposit.failed

Unable to deposit stablecoins. Funds remain at the Direct Transfer Address. The customer must be notified.

Event-Specific Fields

When you receive a direct_transfer.deposit.failed event, stablecoins remain at the Direct Transfer Address. You should notify the end user and coordinate resolution.

Common Patterns

Idempotent Processing

Events may be delivered more than once. Use the id field to deduplicate:
In production, store processed event IDs in a database rather than in-memory to survive restarts.

Type-Based Routing

Route events to different handlers based on the type field:

Testing with the Paxos Labs Console

The Paxos Labs Console lets you send test events for any subscribed event type. Test events:
  • Have IDs prefixed with evt_test_
  • Contain representative sample data (not real transactions)
  • Are labeled Test in delivery history
Use test events to verify your endpoint connectivity and signature verification before going live.