Top-Up Link funds added
Triggered when the acceptance.top_up_link.funds_added webhook event is emitted. Your API will receive a POST request at the webhook URL you configured. The event reports the purchase that spent the link. Because a link funds a single purchase, 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.
Authorizations
HMAC-SHA256 signature supplied on every webhook delivery. The signature is computed from the raw request body using the webhook secret supplied during creation of the webhook subscription.
Webhook receivers can cryptographically verify this header before processing the event to ensure the authenticity of the webhook delivery.
Refer to the verify signatures documentation to learn details about the full payload and the exact verification algorithm.
X-Hook0-Signature is deprecated and will eventually be removed. Use X-Webhook-Signature going forward. Both headers are sent with identical values and use the same verification algorithm and webhook secret.
This scheme applies to webhook delivery (outbound POSTs from CDP to your endpoint), not to inbound CDP API requests.
Headers
HMAC-SHA256 signature supplied on every webhook delivery. The signature is computed from the raw request body using the webhook secret supplied during creation of the webhook subscription.
Webhook receivers can cryptographically verify this header before processing the event to ensure the authenticity of the webhook delivery.
Refer to the verify signatures documentation to learn details about the full payload and the exact verification algorithm.
X-Hook0-Signature is deprecated and will eventually be removed. Use X-Webhook-Signature going forward. Both headers are sent with identical values and use the same verification algorithm and webhook secret.
This scheme applies to webhook delivery (outbound POSTs from CDP to your endpoint), not to inbound CDP API requests.
HMAC-SHA256 signature supplied on every webhook delivery. The signature is computed from the raw request body using the webhook secret supplied during creation of the webhook subscription.
Webhook receivers can cryptographically verify this header before processing the event to ensure the authenticity of the webhook delivery.
Refer to the verify signatures documentation to learn details about the full payload and the exact verification algorithm.
X-Hook0-Signature is deprecated and will eventually be removed. Use X-Webhook-Signature going forward. Both headers are sent with identical values and use the same verification algorithm and webhook secret.
This scheme applies to webhook delivery (outbound POSTs from CDP to your endpoint), not to inbound CDP API requests.
Body
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.
Unique identifier for this webhook event. Use this for idempotency.
"123e4567-e89b-12d3-a456-426614174000"
When this event occurred (ISO 8601 format).
"2026-09-11T20:00:00Z"
The type of webhook event.
acceptance.top_up_link.funds_added "acceptance.top_up_link.funds_added"
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.
Response
Webhook received and processed successfully.