Skip to main content
WEBHOOK

Authorizations

X-Hook0-Signature
string
header
required

HMAC-SHA256 signature of the raw request body, computed using your webhook secret. Webhook receivers should always verify this header before processing the event. The header value is hex-encoded and prefixed by the algorithm and timestamp, e.g. t=1700000000,v1=abc123... (refer to the Webhook Security docs for the exact verification algorithm).

This scheme applies to webhook delivery (outbound POSTs from CDP to your endpoint), not to inbound CDP API requests.

Body

application/json

The acceptance.top_up_link.funds_added webhook event payload.

The acceptance.top_up_link.funds_added event. Emitted when a purchase credits funds through a link, which spends it. A link funds a single purchase, so it produces at most one funds-added event; deliveries can repeat, so deduplicate on eventId. toppedUpAmount is the actual net amount credited by that purchase, denominated in asset; it is never cumulative and independent of the link's suggested amounts. topUpLinkId associates the event with the link the purchase spent.

eventId
string<uuid>
required

Unique identifier for this webhook event. Use this for idempotency.

Example:

"123e4567-e89b-12d3-a456-426614174000"

timestamp
string<date-time>
required

When this event occurred (ISO 8601 format).

Example:

"2026-09-11T20:00:00Z"

eventType
enum<string>
required

The type of webhook event.

Available options:
acceptance.top_up_link.funds_added
Example:

"acceptance.top_up_link.funds_added"

data
object
required

The data payload for the acceptance.top_up_link.funds_added event. The event reports the purchase that spent the link. eventId (from TopUpLinkEventBase) uniquely identifies and deduplicates this event; topUpLinkId associates it with the link the purchase spent.

Example:

Response

Webhook received and processed successfully.